Ml reconfiguration and tid to link mapping procedure

Abstract

Methods and apparatuses for reconfiguring established links between multi-link devices. An access point (AP) MLD includes APs and a processor. Each AP includes a transceiver configured to transmit on an established link with a respective STA of a non-AP MLD. The APs are affiliated with the AP MLD for ML operations on the established links. The processor is configured to generate a reconfigure ML element indicating affiliated APs to remove from affiliation with the AP MLD. The transceiver is configured to transmit the reconfigure ML element to the respective STAs of the non-AP MLD. The processor is configured to determine, after transmitting the reconfigure ML element, whether any of the affiliated APs to remove remain affiliated and update the element to indicate remaining affiliated APs to remove. The transceivers of the remaining affiliated APs are configured to transmit the updated reconfigure ML element to the respective STAs of the non-AP MLD.

Description

Technical Field

[0001] This disclosure generally relates to power management in wireless communication systems including multi-link devices. Embodiments of this disclosure relate to methods and apparatus for reconfiguring links that facilitate the establishment of connections between multi-link devices in a wireless local area network (WLAN) communication system. Background Technology

[0002] Wireless Local Area Network (WLAN) technology allows devices to access the Internet in the 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz frequency bands. WLAN is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The IEEE 802.11 standard family is designed to improve speed and reliability and extend the operational range of wireless networks.

[0003] Next-generation Ultra High Throughput (EHT) Wi-Fi systems (e.g., IEEE 802.11be) support multiple operating bands (called links) through which access points (APs) and non-AP devices can communicate with each other. Therefore, both APs and non-APs can communicate on different bands / links, a phenomenon known as Multi-Link Operation (MLO). Wi-Fi devices that support MLO are called multi-link devices. Using MLO, a non-AP MLD can discover, authenticate, associate, and establish multiple links with an AP MLD. Channel access and frame exchange can occur on each link established between the AP MLD and non-AP MLDs. The component of the MLD responsible for transmitting and receiving on a single link is called a Station (STA). By aggregating bandwidth across multiple channels / bands, MLO offers significant gains in throughput and latency performance compared to single-link operation in the previous generation (802.11ax).

[0004] Non-AP MLDs in 802.11be can have different capabilities in multilink operation. The current specification defines two special types of multilink operation: Enhanced Multilink Single Radio (EMLSR) operation and Enhanced Multilink Multiple Radio (EMLMR) operation.

[0005] Many 802.11be non-AP MLDs may have only a single radio. EMLSR enables multi-link operation using a single radio. Through EMLSR operation, such non-AP MLDs can achieve increased throughput while reducing latency—performance close to that of concurrent dual-radio non-AP MLDs.

[0006] EMLMR operation is another operating mode newly defined in the IEEE 802.11be specification. Using the EMLMR operating mode, an MLD with multiple radios can move the transmit (TX) / receive (RX) chain from one link (e.g., the first link) of the same MLD to another link (e.g., the second link), essentially increasing the spatial streaming capability of the second link. Summary of the Invention

[0007] Embodiments of this disclosure provide methods and apparatus for reconfiguring links that facilitate the establishment of MLDs in a WLAN.

[0008] In one embodiment, an AP MLD is provided, comprising an AP and a processor operatively coupled to the AP. Each AP includes a transceiver configured to transmit over a link established with a corresponding STA (not part of the AP MLD) for performing ML operations on the established link. The processor is configured to generate a reconfiguration ML element indicating the removal of one or more affiliated APs from the affiliation relationship with the AP MLD used for ML operations. The transceiver is also configured to send the reconfiguration ML element to the corresponding STA (not part of the AP MLD). The processor is further configured to determine, after sending the reconfiguration ML element, whether any of the affiliated APs to be removed remains affiliated, and to update the reconfiguration ML element to indicate the remaining affiliated APs to be removed. The transceivers of the remaining affiliated APs are also configured to send the updated reconfiguration ML element to the corresponding STA (not part of the AP MLD).

[0009] In one embodiment, a method for wireless communication performed by an AP MLD including APs is provided, wherein each AP includes a transceiver configured to transmit over a link established with a corresponding STA that is not an AP MLD, wherein the AP is attached to the AP MLD for performing ML operations on the established link. The method includes the steps of: generating a reconfiguration ML element by a processor of the AP MLD, the reconfiguration ML element indicating one or more attached APs to be removed from the attachment relationship with the AP MLD for ML operations; and transmitting the reconfiguration ML element to the corresponding STA of the non-AP MLD by the transceiver. The method further includes the steps of: after transmitting the reconfiguration ML element, determining by the processor whether any of the attached APs to be removed remains attached; and updating the reconfiguration ML element by the processor to indicate the remaining attached APs to be removed. The method further includes the step of transmitting the updated reconfiguration ML element by the transceiver of the remaining attached AP to the corresponding STA of the non-AP MLD.

[0010] The reconfiguration ML element may include a per-STA profile sub-element corresponding to each affiliated AP to be removed. The method may also include updating the reconfiguration ML element by a processor removing the per-STA profile sub-element corresponding to each AP removed from the affiliation relationship.

[0011] The method may include sending an updated reconfiguration ML element by the transceivers of the remaining affiliated APs based on at least one remaining per-STA configuration sub-element in the updated reconfiguration ML element.

[0012] The method may include setting the Media Access Control (MAC) Address Presence subfield in the reconfigured ML element to 0 by the processor, wherein the AP MLD is identified by the MLD MAC Address subfield of the underlying ML element corresponding to the AP MLD.

[0013] The method may include setting the MAC address presence subfield in the reconfiguration ML element to 1 by the processor based on a determination that an AP to be removed remains attached, and including the MLD MAC address of the AP MLD in the reconfiguration ML element by the processor.

[0014] In one embodiment, a non-AP MLD is considered to be de-associated with an AP MLD based on the absence of any remaining established links after the AP is removed from the association.

[0015] The transceiver can operate in Enhanced ML Single Radio (EMLSR) or Enhanced ML Multiple Radio (EMLMR) mode on at least one of the established links corresponding to the affiliated AP to be removed. The method may include the transceiver receiving a request from the corresponding STA of the non-AP MLD to remove at least one established link from EMLSR or EMLMR operation prior to removing the corresponding affiliated AP.

[0016] In one embodiment, a non-AP MLD is provided, including a STA and a processor operatively coupled to the STA. Each STA includes a transceiver configured to transmit on a link established with a corresponding AP of the AP MLD, wherein the AP is attached to the AP MLD for performing ML operations on the established link and receiving reconfiguration ML elements from the corresponding AP of the AP MLD. The processor is configured to determine that the reconfiguration ML elements indicate the removal of one or more attached APs from the attachment relationship with the AP MLD used for ML operations. The transceiver is also configured to receive updated reconfiguration ML elements from the corresponding remaining attached APs of the AP MLD after receiving the reconfiguration ML elements. The processor is further configured to determine the remaining attached APs to be removed from the updated reconfiguration ML elements.

[0017] Other technical features will be obvious to those skilled in the art based on the following figures, description and claims.

[0018] Before proceeding with the detailed description below, it may be advantageous to define certain words and phrases used throughout this patent document. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives cover both direct and indirect communication. The terms “comprising” and “including,” and their derivatives, mean including but not limited to. The term “or” is inclusive, meaning and / or. The phrase “associated with,” and its derivatives, mean including, being included within, interconnected with, containing, being contained within, connected to or connected with, coupled to or coupled with, capable of communicating with, cooperating with, interleaving, juxtaposing, proximate, bound to or bound with, having, possessing the properties of, having a relationship to or with, etc. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller can be centralized or distributed, local or remote. When used with a list of items, the phrase "at least one" means that different combinations of one or more of the listed items can be used, and it is possible that only one item from the list is needed. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C. As used herein, terms such as "first" and "second" or "first" and "second" can be used to simply distinguish one component from another without otherwise limiting the components (e.g., importance or order). It will be understood that, whether the terms “operably” or “communically” are used or not, if an element (e.g., a first element) is referred to as “coupled to another element (e.g., a second element),” “coupled to another element (e.g., a second element),” “connected to another element (e.g., a second element),” or “connected to another element (e.g., a second element)”, it means that the element can be directly (e.g., wired) connected to the other element, wirelessly connected to the other element, or connected to the other element via a third element.

[0019] As used herein, the term "module" can include units implemented in hardware, software, or firmware, and is used interchangeably with other terms such as "logic," "logic block," "part," or "circuit." A module can be a single integrated component adapted to perform one or more functions, or its smallest unit or part. For example, according to an embodiment, a module can be implemented as an application-specific integrated circuit (ASIC).

[0020] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media in which data can be permanently stored and media in which data can be stored and later rewritten, such as rewritable optical discs or erasable memory devices.

[0021] Definitions of certain other words and phrases are provided throughout this patent document. Those skilled in the art will understand that, in many cases (if not most), such definitions apply to the prior and future use of the words and phrases defined in this way. Attached Figure Description

[0022] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals denote like parts:

[0023] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;

[0024] Figure 2a An example AP according to an embodiment of this disclosure is shown;

[0025] Figure 2b An example STA is shown according to an embodiment of the present disclosure;

[0026] Figure 3 An example process for establishing a multi-link according to an embodiment of this disclosure is shown;

[0027] Figure 4 Example operations for continuing to include reconfigured multilink elements in beacon and probe response frames, according to embodiments of the present disclosure, are shown;

[0028] Figure 5 An example operation for removing EMLSR links prior to multi-link reconfiguration is shown according to an embodiment of this disclosure;

[0029] Figure 6 Example operations for removing EMLMR links prior to multi-link reconfiguration are shown according to embodiments of this disclosure; and

[0030] Figure 7 An example process for reconfiguring established links between MLDs according to an embodiment of this disclosure is shown. Detailed Implementation

[0031] The following discussion Figures 1 to 7 The various embodiments used to describe the principles of this disclosure in this patent document are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.

[0032] Embodiments of this disclosure recognize that an AP MLD can use a multi-link (ML) reconfiguration procedure to add or remove one or more links, or a non-AP MLD can use an ML reconfiguration procedure to request the addition or removal of one or more links. Embodiments of this disclosure further recognize that, using the advertised Service Identifier (TID) to Link Mapping (TTLM), an AP can disable all links of non-AP MLDs associated with the AP MLD.

[0033] However, the ML reconfiguration process and the TID-to-Link Mapping (TTLM) process are not fully defined. Therefore, embodiments of this disclosure provide systems and methods for facilitating the reconfiguration of links established between MLDs. For example, embodiments of this disclosure provide processes for including the MLD Media Access Control (MAC) address in the ML reconfiguration element, continuing to include the reconfigured ML element in beacon and probe response frames after removing the associated AP, removing the link using EMLSR or EMLMR operations, and deassociating the non-AP MLD with the AP MLD after removing (or disabling) all established links between the non-AP MLD and the AP MLD.

[0034] Figure 1 An example wireless network 100 according to one embodiment of the present disclosure is shown. Figure 1The embodiment of the wireless network 100 shown is for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0035] Wireless network 100 includes access points 101 and 103. Access points 101 and 103 communicate with at least one network 130 (such as the Internet, a proprietary Internet Protocol (IP) network, or other data network). Access point 101 provides wireless access to network 130 to multiple STAs 111-114 within its coverage area 120. Access points 101-103 can communicate with each other and with STAs 111-114 using Wi-Fi or other WLAN communication technologies.

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

[0037] In one embodiment of this disclosure, each of APs 101 and 103 and each of STAs 111-114 may be an MLD. In such an embodiment, APs 101 and 103 may be AP MLDs, and STAs 111-114 may be non-AP MLDs. Each MLD is attached to more than one STA. For ease of explanation, AP MLDs are described herein as being attached to more than one AP (e.g., more than one AP STA), and non-AP MLDs are described herein as being attached to more than one STA (e.g., more than one non-AP STA).

[0038] The dashed lines indicate the approximate extent of coverage areas 120 and 125, and are shown as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that coverage areas associated with an AP (such as coverage areas 120 and 125) can have other shapes, including irregular shapes, depending on the AP's configuration and variations in the radio environment associated with natural and man-made obstacles.

[0039] although Figure 1 An example of a wireless network 100 is shown, but more details can be found on other wireless networks. Figure 1 Various modifications can be made. For example, wireless network 100 can include any number of APs and any number of STAs in any suitable arrangement. Furthermore, AP 101 can communicate directly with any number of STAs and provide them with wireless broadband access to network 130. Similarly, each AP 101-103 can communicate directly with network 130 and provide STAs with direct wireless broadband access to network 130. Additionally, AP 101 and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0040] Figure 2a Example AP 101 is shown according to various embodiments of the present disclosure. Figure 2a The embodiment of AP 101 shown is for illustrative purposes only, and Figure 1 AP 103 can have the same or similar configuration. In the embodiments discussed below, AP 101 is an AP MLD. However, APs appear in a wide variety of configurations, and Figure 2a This disclosure is not intended to limit the scope to any particular implementation of AP.

[0041] AP MLD 101 is associated with multiple APs 202a-202n (which may be referred to as, for example, AP1-APn). Each of the associated APs 202a-202n includes multiple antennas 204a-204n, multiple RF transceivers 209a-209n, transmit (TX) processing circuitry 214, and receive (RX) processing circuitry 219. AP MLD 101 also includes a controller / processor 224, a memory 229, and a backhaul or network interface 234.

[0042] The components shown for each of the attached APs 202a-202n may represent the Physical (PHY) layer and the lower Media Access Control (LMAC) layer in an Open Systems Interconnection (OSI) network model. In such an embodiment, the components shown for AP MLD 101 represent a single Upper MAC (UMAC) layer and other higher layers in the OSI model, which are shared by all attached APs 202a-202n.

[0043] For each affiliated AP 202a-202n, RF transceivers 209a-209n receive incoming RF signals from antennas 204a-204n, such as signals transmitted by STAs in network 100. In some embodiments, each affiliated AP 202a-202n operates at a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), and therefore the incoming RF signals received by each affiliated AP may be at different RF frequencies. RF transceivers 209a-209n down-convert the incoming RF signals to generate an IF or baseband signal. The IF or baseband signal is sent to RX processing circuitry 219, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 219 sends the processed baseband signal to controller / processor 224 for further processing.

[0044] For each affiliated AP 202a-202n, TX processing circuitry 214 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from controller / processor 224. TX processing circuitry 214 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 209a-209n receive the outgoing processed baseband or IF signal from TX processing circuitry 214 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 204a-204n. In embodiments where each affiliated AP 202a-202n operates at different bandwidths (e.g., 2.4 GHz, 5 GHz, or 6 GHz), the outgoing RF signal transmitted by each affiliated AP may be at a different RF frequency.

[0045] The controller / processor 224 may include one or more processors or other processing devices that control the overall operation of the AP MLD 101. For example, the controller / processor 224 may control the RF transceivers 209a-209n, the RX processing circuitry 219, and the TX processing circuitry 214 to receive forward channel signals and transmit reverse channel signals, based on well-known principles. The controller / processor 224 may also support additional functions, such as more advanced wireless communication capabilities. For example, the controller / processor 224 may support beamforming or directional routing operations, where outgoing signals from multiple antennas 204a-204n are weighted differently to effectively direct the outgoing signals in a desired direction. The controller / processor 224 may also support OFDMA operations, where outgoing signals are assigned to different subsets of subcarriers for different receivers (e.g., different STAs 111-114). The controller / processor 224 may support any of a variety of other functions in the AP MLD 101. In some embodiments, the controller / processor 224 includes at least one microprocessor or microcontroller. The controller / processor 224 is also capable of executing programs and other processes, such as an operating system, residing in memory 229. The controller / processor 224 can move data into or out of memory 229 as needed by the executing process.

[0046] The controller / processor 224 is also coupled to a backhaul or network interface 234. The backhaul or network interface 234 allows the AP MLD 101 to communicate with other devices or systems via a backhaul connection or over a network. Interface 234 can support communication via any suitable wired or wireless connection. For example, interface 234 can allow the AP MLD 101 to communicate with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. Interface 234 includes any suitable architecture supporting communication via a wired or wireless connection, such as an Ethernet or RF transceiver. Memory 229 is coupled to the controller / processor 224. A portion of memory 229 may include RAM, and another portion of memory 229 may include flash memory or other ROM.

[0047] although Figure 2a An example of AP MLD 101 is shown, but it is possible to compare it with other models. Figure 2a Various changes can be made. For example, APMLD 101 can include any number of... Figure 2aEach component shown. As a specific example, AP MLD 101 may include multiple interfaces 234, and the controller / processor 224 may support routing functionality to route data between different network addresses. As another specific example, although each affiliated AP 202a-202n is shown as a single instance including TX processing circuitry 214 and a single instance of RX processing circuitry 219, AP MLD 101 may include multiple instances of each of one or more of the affiliated APs 202a-202n (such as one per RF transceiver). Alternatively, one or more of the affiliated APs 202a-202n (such as in a conventional AP) may include only one antenna and RF transceiver path. Moreover, Figure 2a The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0048] Figure 2b Example STA 111 is shown according to various embodiments of the present disclosure. Figure 2b The embodiment of STA 111 shown is for illustrative purposes only, and Figure 1 STAs 111-115 can have the same or similar configurations. In the embodiments discussed below, STA 111 is a non-AP MLD. However, STAs can appear in a wide variety of configurations, and Figure 2b This disclosure is not intended to limit the scope of any particular implementation of STA.

[0049] The non-AP MLD 111 is attached to multiple STAs 203a-203n (which may be referred to as, for example, STA1-STAn). Each of the attached STAs 203a-203n includes an antenna 205, a radio frequency (RF) transceiver 210, TX processing circuitry 215, and receive (RX) processing circuitry 225. The non-AP MLD 111 also includes a microphone 220, a speaker 230, a controller / processor 240, an input / output (I / O) interface (IF) 245, a touchscreen 250, a display 255, and a memory 260. The memory 260 includes an operating system (OS) 261 and one or more applications 262.

[0050] The components shown in each of the attached STAs 203a-203n may represent the PHY and LMAC layers in the OSI network model. In such an embodiment, the components shown in the non-AP MLD 111 represent a single UMAC layer and other higher layers in the OSI model, which are shared by all attached STAs 203a-203n.

[0051] For each affiliated STA 203a-203n, RF transceiver 210 receives incoming RF signals transmitted by the AP of network 100 from antenna 205. In some embodiments, each affiliated STA 203a-203n operates at a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), and therefore the incoming RF signals received by each affiliated STA may be at different RF frequencies. RF transceiver 210 down-converts the incoming RF signals to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 225, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 225 sends the processed baseband signal to speaker 230 (e.g., for voice data) or to controller / processor 240 for further processing (e.g., for web browsing data).

[0052] For each affiliated STA 203a-203n, TX processing circuitry 215 receives analog or digital voice data from microphone 220, or other outgoing baseband data (such as network data, email, or interactive video game data) from controller / processor 240. TX processing circuitry 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 210 receives the outgoing processed baseband or IF signal from TX processing circuitry 215 and up-converts the baseband or IF signal into an RF signal transmitted via antenna 205. In embodiments where each affiliated STA 203a-203n operates at different bandwidths (e.g., 2.4 GHz, 5 GHz, or 6 GHz), the outgoing RF signal transmitted by each affiliated STA may be at a different RF frequency.

[0053] The controller / processor 240 may include one or more processors and executes a basic OS program 261 stored in memory 260 to control the overall operation of the non-AP MLD 111. In one such operation, the main controller / processor 240 controls the RF transceiver 210, RX processing circuitry 225, and TX processing circuitry 215 to receive forward channel signals and transmit reverse channel signals according to well-known principles. The main controller / processor 240 may also include processing circuitry configured to facilitate the reconfiguration of links established between MLDs in a WLAN. In some embodiments, the controller / processor 240 includes at least one microprocessor or microcontroller.

[0054] The controller / processor 240 is also capable of executing other processes and programs residing in the memory 260, such as operations for reconfiguring links to facilitate the establishment of MLDs in the WLAN. The controller / processor 240 can move data into or out of the memory 260 as needed by the executing processes. In some embodiments, the controller / processor 240 is configured to execute multiple applications 262, such as applications for reconfiguring links to facilitate the establishment of MLDs in the WLAN. The controller / processor 240 can operate the multiple applications 262 based on the OS program 261 or in response to signals received from the AP. The main controller / processor 240 is also coupled to an I / O interface 245, which provides the non-AP MLD 111 with the ability to connect to other devices such as laptops and handheld computers. The I / O interface 245 is the communication path between these accessories and the main controller 240.

[0055] The controller / processor 240 is also coupled to the touchscreen 250 and the display 255. An operator of the non-AP MLD 111 can use the touchscreen 250 to input data into the non-AP MLD 111. The display 255 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text (such as from a website) and / or at least limited graphics. Memory 260 is coupled to the controller / processor 240. A portion of the memory 260 may include random access memory (RAM), and another portion of the memory 260 may include flash memory or other read-only memory (ROM).

[0056] although Figure 2b An example of a non-AP MLD 111 is shown, but it is possible to compare... Figure 2b Make various changes. For example, Figure 2b The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. In a specific example, one or more of the auxiliary STAs 203a-203n may include any number of antennas 205 for MIMO communication with AP 101. In another example, the non-AP MLD 111 may not include voice communication, or the controller / processor 240 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although... Figure 2b A non-AP MLD 111 configured as a mobile phone or smartphone is shown, but the non-AP MLD can be configured to operate as other types of mobile or fixed devices.

[0057] Figure 3An example procedure 300 for establishing a multi-link according to an embodiment of the present disclosure is illustrated. In this example, the AP MLD may be AP MLD 101, and the non-AP MLD may be non-AP MLD 111. Although AP MLD 101 is shown as having three affiliated APs (AP1, AP2, and AP3), and non-AP MLD 111 is shown as having three affiliated non-AP STAs (non-AP STA1, non-AP STA2, and non-AP STA3), it should be understood that this procedure can be applied to a suitable MLD with any number of affiliated APs or STAs. For ease of explanation, it should be understood that references to AP MLD and non-AP MLD in the following further embodiments refer to AP MLD 101 and non-AP MLD 111, respectively.

[0058] exist Figure 3 In the example, the exchange of association request frames and association response frames occurs on the 2.4 GHz link between the AP MLD and the non-AP MLD. This establishment is used to set up three links between the AP MLD and the non-AP MLD: one link in the 2.4 GHz band, a second link in the 5 GHz band, and a third link in the 6 GHz band. After a successful ML establishment, three links are established between the AP MLD and the non-AP MLD—link 1 between AP1 and non-AP STA1, link 2 between AP2 and non-AP STA2, and link 3 between AP3 and non-AP STA3.

[0059] After a successful ML establishment, the AP MLD can use the ML reconfiguration procedure to add or remove links (or add or remove associated APs) for ML operations. Similarly, non-AP MLDs can use the ML reconfiguration procedure to request the AP MLD to add or remove links (or add or remove associated APs) for ML operations. Additionally, the AP can use the advertised TID-to-Link Mapping (TTLM) procedure to disable links of all non-AP MLDs associated with the AP MLD. Embodiments of this disclosure provide solutions to several issues regarding ML reconfiguration and TTLM procedures.

[0060] According to one embodiment, when an AP MLD generates a reconfiguration multilink element to indicate that it is removing an AP MLD's associated AP from the associated relationship used for ML operations, the reconfiguration multilink element is included in the beacon and probe response frames, and the MLD MAC address presence subfield in the reconfiguration multilink element can be set to 1. If the MLD MAC address presence subfield is set to 1, the MLD MAC address in the reconfiguration multilink element can be the same as the MLD MAC address (or AP MLD ID subfield) of the AP MLD that provided the AP MLD removal information.

[0061] According to one embodiment, when an AP MLD intends to remove a first affiliated AP, the MLD MAC address presence subfield can be set to 1 in the reconfiguration multilink element included in the beacon and probe response frames sent by any APs affiliated with the AP MLD if only one AP remains affiliated with the AP MLD after the removal of the first AP. Conversely, if more than one AP remains affiliated with the AP MLD after the removal of the first AP, the MLD MAC address presence subfield can be set to 0, and the AP MLD that provides the AP removal information in the reconfiguration multilink element is identified by the MLD MAC address subfield of the basic multilink element corresponding to the same AP MLD carried in the same management frame.

[0062] According to one embodiment, after removing an AP attached to the AP MLD via an announcement in a beacon and probe response frame using the reconfiguration multilink element, if there are other attached APs still to be removed, the AP MLD continues to include the reconfiguration multilink element in the beacon and probe response frames sent by any attached APs, and the per-STA profile sub-element corresponding to each attached AP to be removed can continue to be included in the reconfiguration multilink element. For any AP that has been removed from the attachment relationship, the corresponding per-STA profile sub-element can be removed from the reconfiguration multilink element before subsequent transmissions. When there are no remaining per-STA profile sub-elements (i.e., when all attached APs to be removed have been removed), the AP MLD may stop including the reconfiguration multilink element in the beacon and probe response frames.

[0063] Figure 4 An example operation 400 for continuing to include reconfigured multilink elements in beacon and probe response frames according to embodiments of the present disclosure is illustrated. In this example, the AP MLD may be AP MLD 101, and the non-AP MLD may be non-AP MLD 111.

[0064] exist Figure 4In the example, message 402 includes the ML establishment process between an AP MLD and a non-AP MLD. ML establishment can be performed on any link established between an AP attached to an AP MLD and a STA attached to a non-AP MLD. In this example, after a successful ML establishment, three links (link 1, link 2, and link 3) are established for the ML operation.

[0065] Then, the AP MLD sends a beacon frame 404 including a reconfiguration multilink element that indicates that links 2 and 3 will be removed (e.g., the associated APs corresponding to links 2 and 3 will be disabled or removed from the associated relationships with the AP MLD used for ML operations). The per-STA profile sub-elements corresponding to links 2 and 3 are included in the reconfiguration multilink element.

[0066] Link 2 is then terminated, but Link 3 remains to be removed when the AP MLD sends beacon frame 406. Accordingly, beacon frame 406 continues to include a reconfiguration multilink element. The reconfiguration multilink element now indicates that Link 3 will be removed and includes a per-STA profile sub-element corresponding to Link 3 (e.g., the per-STA profile sub-element corresponding to Link 2 can be removed from the reconfiguration multilink element).

[0067] Link 3 is then terminated, and no further links remain to be removed. Accordingly, beacon frame 408 does not include the reconfiguration multilink element. For example, after removing the per-STA profile sub-element corresponding to link 3 from the reconfiguration multilink element, the AP MLD can determine that there are no remaining per-STA profile sub-elements in the reconfiguration multilink element and therefore determine not to continue including the reconfiguration multilink element in the beacon frame.

[0068] According to one embodiment, when a non-AP MLD and an associated AP MLD are operating in EMLSR mode and a first link between the AP MLD and the non-AP MLD is included in an EMLSR link, if the AP MLD intends to remove the first link using a multi-link reconfiguration procedure, the first link will be removed from the EMLSR link before the first link is removed from the MLO using the multi-link reconfiguration procedure.

[0069] Figure 5 An example operation 500 for removing an EMLSR link prior to multi-link reconfiguration, according to an embodiment of this disclosure, is illustrated. In this example, the AP MLD may be AP MLD 101, and the non-AP MLD may be non-AP MLD 111.

[0070] exist Figure 5In the example, message 502 includes the ML establishment process between an AP MLD and a non-AP MLD. ML establishment can be performed on any link established between an AP attached to an AP MLD and a STA attached to a non-AP MLD. In this example, after a successful ML establishment, three links (link 1, link 2, and link 3) are established for the ML operation.

[0071] Message 504 includes the EMLSR negotiation process between the AP MLD and non-AP MLD. In this example, EMLSR is enabled on links 1, 2, and 3 (i.e., links 1, 2, and 3 are included in the EMLSR links). The EMLSR operation occurs during time period 506, where links 1, 2, and 3 are EMLSR links.

[0072] Then, the AP MLD sends a beacon frame 508 that includes a reconfiguration multilink element indicating that link 2 will be removed (e.g., the associated AP corresponding to link 2 will be disabled or removed from the associated relationships with the AP MLD used for ML operations). The per-STA profile sub-element corresponding to link 2 is included in the reconfiguration multilink element.

[0073] In response to beacon frame 508, the non-AP MLD sends request 510 to change the EMLSR link list to link 1 and link 3 (i.e., remove link 2 from the EMLSR links). The AP MLD responds with an accept message 512. Subsequently, an EMLSR operation occurs, in which link 1 and link 3 become EMLSR links, and link 2 is removed (i.e., the associated AP corresponding to link 2 is removed or disabled).

[0074] According to one embodiment, when a non-AP MLD and an associated AP MLD are operating in EMLMR mode and a first link between the AP MLD and the non-AP MLD is included in an EMLMR link, if the AP MLD intends to remove the first link using a multi-link reconfiguration procedure, the first link will be removed from the EMLMR link before the first link is removed from the MLO using the multi-link reconfiguration procedure.

[0075] Figure 6 An example operation 600 for removing an EMLMR link prior to multi-link reconfiguration, according to an embodiment of this disclosure, is illustrated. In this example, the AP MLD may be AP MLD 101, and the non-AP MLD may be non-AP MLD 111.

[0076] exist Figure 6In the example, message 602 includes the ML establishment process between an AP MLD and a non-AP MLD. ML establishment can be performed on any link established between an AP attached to an AP MLD and a STA attached to a non-AP MLD. In this example, after a successful ML establishment, three links (link 1, link 2, and link 3) are established for the ML operation.

[0077] Message 604 includes the EMLMR negotiation process between the AP MLD and the non-AP MLD. In this example, EMLMR is enabled on links 1, 2, and 3 (i.e., links 1, 2, and 3 are included in the EMLMR links). The EMLMR operation occurs during time period 606, where links 1, 2, and 3 are EMLMR links.

[0078] Then, the AP MLD sends a beacon frame 608 that includes a reconfiguration multilink element indicating that link 2 will be removed (e.g., the associated AP corresponding to link 2 will be disabled or removed from the associated relationships with the AP MLD used for ML operations). A per-STA profile sub-element corresponding to link 2 is included in the reconfiguration multilink element.

[0079] In response to beacon frame 608, the non-AP MLD sends request 610 to change the EMLMR link list to link 1 and link 3 (i.e., remove link 2 from the EMLMR links). The AP MLD responds with an accept message 612. Subsequently, an EMLMR operation occurs, in which link 1 and link 3 become EMLMR links, and link 2 is removed (i.e., the associated AP corresponding to link 2 is removed or disabled).

[0080] According to one embodiment, when an AP MLD recommends adding a new link to an associated non-AP MLD, the AP MLD can provide the non-AP MLD with a complete profile that matches the link that the AP MLD is recommending to add for the non-AP MLD. According to this embodiment, the AP MLD sets the complete profile subfield in the per-STA profile sub-element of the reconfiguration multi-link element included in the link reconfiguration notification frame sent by the AP MLD to the non-AP MLD to 1, indicating the link addition recommendation. According to one embodiment, the STA MAC address presence subfield and the operation parameter presence subfield can be set to 1. The STA MAC address in the per-STA profile sub-element can be set to the MAC address of the AP that the AP MLD intends to add for the non-AP MLD.

[0081] According to one embodiment, when the AP MLD indicates both "delete link" and "add link" operations for the same non-AP STA by setting the STA MAC address subfield to the same value in two per-STA profile sub-elements included in the reconfiguration multi-link element, the link ID subfield of one of the two per-STA profile sub-elements can be set to the link ID of the link to be deleted, and the link ID subfield of the other per-STA profile sub-element can be set to the link ID of the link to be added.

[0082] According to one embodiment, when the AP MLD removes an affiliated AP using a multi-link reconfiguration process, any power savings (PS) and target wake-up time (TWT) information corresponding to the link associated with that affiliated AP can be deleted upon link removal. For example, if one or more TWT schedules or protocols are established on the link and the link is removed, information related to the TWT schedule or TWT protocol is deleted from the memory associated with that link upon link removal.

[0083] According to one embodiment, when the AP MLD removes an affiliated AP using a multi-link reconfiguration process, all power savings and TWT information corresponding to the link corresponding to that affiliated AP can be retained after the link is removed. For example, if one or more TWT schedules or protocols are established on that link and the link is removed, information related to the TWT schedule or TWT protocol is retained in the memory corresponding to that link when the link is removed. If the AP corresponding to the removed link is later added back to the AP MLD, the TWT schedule or protocol can be restored without new TWT negotiation.

[0084] According to one embodiment, if a link is to be enabled based on the advertised TID-to-link mapping (TTLM) when the target beacon transmission time (TBTT) of the delivery flow indication message (DTIM) beacon is in time units (TU) in the mapping switching time field of the corresponding TID-to-link mapping element, a non-AP STA operating on that link can initiate a transmission opportunity (TXOP) to the corresponding AP up to a threshold amount of time prior to the TBTT indicated by the DTIM beacon frame. According to one embodiment, the threshold amount can be one TU duration. According to one embodiment, the threshold amount can be a multiple of one TU duration. According to one embodiment, if the advertised TTLM indicates that the TTLM is used for uplink transmission of the TID of that link, a non-AP STA can initiate a TXOP to the AP.

[0085] According to one embodiment, once the AP MLD successfully establishes the advertised TTLM, the corresponding TID-to-link mapping element should be included in all beacon and probe response frames sent by all APs attached to the AP MLD until the advertised TTLM ends as indicated by the expected duration field (otherwise, a newly associated client device might initiate a new TTLM that could potentially violate the existing advertised TTLM). During this phase, the mapping switchover time field may not be included in the TID-to-link mapping element (e.g., the mapping switchover time presence subfield may be set to 0).

[0086] According to one embodiment, immediately after the expiration of the advertised TTLM (which may be indicated by the expected duration field of the TID-to-link mapping element), the non-AP MLD should fall back to any negotiated TTLM protocol it had before the advertised TTLM was established (if any) (rather than falling back to the default mapping). If there is no negotiated TTLM protocol for the non-AP MLD, the non-AP MLD may use the default TTLM after the expiration of the advertised TTLM.

[0087] In the example scenario, if a non-default TTLM is currently advertised, each AP attached to the AP MLD will advertise the TTLM in its transmitted beacon and probe response frame upon receiving the MLME-BSS-LINK-DISABLE.request primitive. This TTLM does not map any TID to the link on which the AP is operating corresponding to the BSSID parameter indicated in the primitive, and the TTLM will take effect after the time indication period in the expected duration field of the currently advertised TTLM has expired. According to one embodiment, the beacon and probe response frame sent by the AP attached to the AP MLD will include two TTLM elements—one for the existing advertised TTLM (where the mapping switch time is not present in the TID-to-link mapping element) and another for the newly advertised TTLM to disable the indicated link.

[0088] In the example scenario, when the AP MLD announces a link disablement for all associated non-AP MLDs, the non-AP MLDs remain associated with the AP MLD. According to one embodiment, if the link is the only link established between the non-AP MLD and the AP MLD, then when the link disablement takes effect, the non-AP MLD can detach from the AP MLD.

[0089] According to one embodiment, in a scenario where a non-AP MLD intends to establish a new link with its associated AP MLD, the non-AP MLD can send a link reconfiguration request frame to the AP MLD. The link reconfiguration request frame may include basic multi-link elements to indicate the link the non-AP MLD intends to add. The basic multi-link elements included in the link reconfiguration request frame may also contain information related to the requested link (or links). The basic multi-link elements included in the link reconfiguration request frame may also contain information related to links that may or may not be the requested link. According to one embodiment, possible formats for the link reconfiguration request frame are shown in Table 1.

[0090] Table 1

[0091]

[0092] According to one embodiment, in a scenario where a non-AP MLD is associated with an AP MLD and a first TWT protocol or TWT schedule is established on a first link between the AP MLD and the non-AP MLD, if the first link is deleted using the ML reconfiguration procedure, the information related to the first TWT protocol or TWT schedule is also deleted (i.e., it can be assumed that the first TWT protocol or TWT schedule has been torn down).

[0093] According to one embodiment, in a scenario where a non-AP MLD is associated with an AP MLD and a first TWT protocol or TWT schedule is established on a first link between the AP MLD and the non-AP MLD, if the first link is deleted using the ML reconfiguration process, the information related to the first TWT protocol or TWT schedule is not deleted (i.e., it can be assumed that the first TWT protocol or TWT schedule is suspended).

[0094] According to one embodiment, in a scenario where a non-AP MLD is associated with an AP MLD and a first TWT protocol or TWT schedule is established on a first link between the AP MLD and the non-AP MLD, if the first link is disabled using the TID to link mapping process, the information related to the first TWT protocol or TWT schedule is deleted (i.e., it can be assumed that the first TWT protocol or TWT schedule has been torn down).

[0095] According to one embodiment, in a scenario where a non-AP MLD is associated with an AP MLD and a first TWT protocol or TWT schedule is established on a first link between the AP MLD and the non-AP MLD, if the first link is disabled using the TID-to-link mapping process, the information related to the first TWT protocol or TWT schedule is not deleted (i.e., it can be assumed that the first TWT protocol or TWT schedule is suspended. When the link is re-enabled, the TWT protocol or TWT schedule is re-instantiated or restored).

[0096] According to one embodiment, in a scenario where a non-AP MLD receives a link reconfiguration recommendation from its associated AP MLD by receiving a link reconfiguration notification frame from the AP MLD, if the non-AP MLD subsequently sends a link recommendation request frame to the AP MLD as a response to the received link reconfiguration notification frame, the non-AP MLD may set the dialogue token field in the link recommendation request frame sent to the AP MLD to the same value indicated in the dialogue token field of the link recommendation notification frame received from the AP MLD. This will indicate that the request frame has the same notification / request / response sequence as the link recommendation notification frame.

[0097] According to one embodiment, in a scenario where a non-AP MLD is associated with an AP MLD and a single link (e.g., a first link) is established between the AP MLD and the non-AP MLD, if the AP MLD (using the ML reconfiguration process) announces the deletion of the first link, the non-AP MLD can send a link reconfiguration request frame to the AP MLD to indicate a request to establish a second link between the AP MLD and the non-AP MLD. The non-AP MLD can send this request to the AP MLD before planning to delete the first link (by sending the link reconfiguration request frame to the AP MLD to establish the second link between the AP MLD and the non-AP MLD). In this way, the non-AP MLD can avoid detaching from the AP MLD.

[0098] According to one embodiment, in a scenario where a first link is established between a first AP attached to an AP MLD and a first non-AP STA attached to a non-AP MLD associated with the AP MLD, the non-AP MLD can send a request to the AP MLD to delete the first link between the first AP and the first non-AP STA, and can request the AP MLD to establish a second link between the first non-AP STA and a second AP attached to the same AP MLD.

[0099] According to one such embodiment, in order to request the AP MLD to delete the first link between the first AP and the first non-AP STA, and also to request the AP MLD to establish a second link between the first non-AP STA and a second AP attached to the same AP MLD, the non-AP MLD can send a link reconfiguration request frame to the AP MLD through any enabled link between the AP MLD and the non-AP MLD.

[0100] A link reconfiguration request frame may contain a multi-link reconfiguration element, which may contain two per-STA profile sub-elements. The first per-STA profile sub-element can be indicated to delete an existing link (first link) by setting the reconfiguration operation type sub-field value to 3 (delete link). The link ID sub-field of the first per-STA profile sub-element can be set to the link ID value corresponding to the first AP, and the STA MAC address of the first per-STA profile sub-element can be set to the STA MAC address value of the first non-AP STA. The second per-STA profile sub-element can be indicated to add a new link (second link) by setting the reconfiguration operation type sub-field value to 2 (add link). The link ID sub-field of the second per-STA profile sub-element can be set to the link ID value corresponding to the second AP attached to the AP MLD, and the STA MAC address of the second per-STA profile sub-element can be set to the STA MAC address value of the first non-AP STA.

[0101] A non-AP MLD can send a link reconfiguration request frame to an AP MLD on the same link as the link being requested to be deleted, or on a different link than the link being requested to be deleted.

[0102] Figure 7 An example process 700 for reconfiguring established links between MLDs according to an embodiment of the present disclosure is shown. Figure 7 The process 700 is discussed as being executed by the AP MLD, but it should be understood that the corresponding non-AP MLD executes the corresponding process. Additionally, for convenience, Figure 7 The process is discussed as being performed by a Wi-Fi AP MLD comprising multiple APs, each AP including a transceiver configured to transmit on a link established with a corresponding STA of the Wi-Fi non-AP MLD, wherein the AP is attached to the AP MLD for performing ML operations on the established link. However, it should be understood that any suitable wireless communication device can perform this process.

[0103] refer to Figure 7 In step 705, the AP MLD processor may generate a reconfiguration ML element that indicates one or more of the affiliated APs to be removed from the affiliation relationships with the AP MLD used for ML operations. In some embodiments, the reconfiguration ML element includes a per-STA profile sub-element corresponding to each affiliated AP to be removed.

[0104] In some embodiments, the processor sets the MAC address presence subfield in the reconfiguration ML element to 0, and the AP MLD is identified by the MLD MAC address subfield of the base ML element corresponding to the AP MLD. In other embodiments, the processor sets the MAC address presence subfield in the reconfiguration ML element to 1, and includes the MLD MAC address of the AP MLD in the reconfiguration ML element. This can be done based on a determination that an auxiliary AP is to be removed.

[0105] Next, the transceiver can send the reconfigured ML element to the corresponding STA of the non-AP MLD (step 710).

[0106] After sending the reconfiguration ML element, the processor can determine whether any of the attached APs to be removed remain attached (step 715).

[0107] The processor can then update the reconfiguration ML element to indicate the remaining dependent APs to be removed (step 720). If the reconfiguration ML element in step 705 includes a perSTA profile sub-element corresponding to each dependent AP to be removed, the processor in step 720 can update the reconfiguration ML element by removing the perSTA profile sub-element corresponding to each AP removed from the dependent relationship.

[0108] Finally, the transceivers of the remaining affiliated APs can send the updated reconfiguration ML element to the corresponding STA of the non-AP MLD (step 725). In some embodiments, this step can be performed based on at least one remaining per-STA configuration sub-element in the updated reconfiguration ML element.

[0109] When no links remain after an AP is removed from its affiliate relationship, a non-AP MLD is considered to be disconnected from the AP MLD.

[0110] In some embodiments, the transceiver of the AP MLD operates in EMLSR or EMLMR mode on at least one of the established links corresponding to the affiliated AP to be removed. In such embodiments, after sending the reconfiguration ML element in step 710 or step 725, the transceiver may receive a request from the corresponding STA of the non-AP MLD to remove at least one established link from EMLSR or EMLMR operation before removing the corresponding affiliated AP.

[0111] The flowchart above illustrates an example method or process that can be implemented according to the principles of this disclosure, and various changes can be made to the method or process shown in the flowchart. For example, although shown as a series of steps, the steps may overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, steps may be omitted or replaced with other steps.

[0112] Although this disclosure has been described using exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims. Nothing described in this application should be construed as implying that any particular element, step, or function is an essential element that must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. An access point (AP) multi-link device (MLD), comprising: Each AP includes a transceiver configured to transmit on a link established with a corresponding STA (Station) that is not part of the AP MLD (Multi-Link Management Module), wherein the AP is attached to the AP MLD for performing multi-link ML (Multi-Link Management) operations on the established link; and A processor, operatively coupled to an AP, is configured to generate reconfiguration ML elements that indicate one or more affiliated APs to be removed from the affiliate relationship with the AP MLD used for ML operations. The transceiver is also configured to send reconfigured ML elements to the corresponding STAs of non-AP MLDs. The processor is also configured as follows: After sending the reconfiguration ML element, determine whether any of the attached APs to be removed remain attached, and Update the reconfigured ML element to indicate the remaining associated APs to be removed, and The transceivers of the remaining auxiliary APs are also configured to send updated reconfiguration ML elements to the corresponding STAs of the non-AP MLDs.

2. The AP MLD according to claim 1, wherein: The reconfiguration ML element includes a per-STA profile sub-element corresponding to each of the affiliated APs to be removed, and The processor is configured to update the reconfiguration ML element by removing the per-STA profile sub-element corresponding to each AP removed from the affiliate relationship.

3. The AP MLD according to claim 1 or 2, wherein, The transceivers of the remaining auxiliary APs are also configured to send updated reconfiguration ML elements based on at least one remaining per-STA configuration sub-element in the updated reconfiguration ML element.

4. The AP MLD according to any one of the preceding claims, wherein: The processor is also configured to set the Media Access Control MAC Address Presence subfield in the reconfigured ML element to 0, and AP MLD is identified by the MLD MAC address subfield of the basic ML element corresponding to AP MLD.

5. The AP MLD according to any one of the preceding claims, wherein, The processor is also configured as follows: Based on the determination that an AP to be removed remains attached, the MAC address presence subfield in the reconfigured ML element is set to 1, and Include the MLD MAC address of the AP MLD in the reconfigured ML element.

6. The AP MLD according to any one of the preceding claims, wherein, Based on the absence of established links after the AP was removed from the affiliate relationship, the non-AP MLD is considered to be disconnected from the AP MLD.

7. The AP MLD according to any one of the preceding claims, wherein, The transceiver is also configured as follows: Operating in enhanced ML single-radio EMLSR or enhanced ML multi-radio EMLMR mode on at least one of the established links corresponding to the affiliated AP to be removed, and Before the corresponding affiliated AP is removed, the corresponding STA of the non-AP MLD receives a request to remove at least one established link from the EMLSR or EMLMR operation.

8. A method for wireless communication performed by an access point (AP) multilink device (MLD), the MLD comprising APs, each AP including a transceiver configured to transmit on a link established with a corresponding station (STA) of a non-AP MLD, wherein, The AP is attached to the AP MLD and is used to perform multi-link ML operations on the established links. The methods include: The AP MLD's processor generates a reconfiguration ML element, which indicates that one or more affiliated APs should be removed from the affiliated relationship with the AP MLD used for ML operations. The transceiver sends the reconfigured ML element to the corresponding STA of the non-AP MLD; After the reconfiguration ML element is sent, the processor determines whether any of the attached APs to be removed should remain attached. The processor updates and reconfigures the ML element to indicate the remaining associated APs to be removed; and The remaining auxiliary AP transceivers send the updated reconfiguration ML elements to the corresponding STAs of the non-AP MLD.

9. The method according to claim 8, wherein: The reconfiguration ML element includes a per-STA profile sub-element corresponding to each of the affiliated APs to be removed, and The method also includes updating the reconfiguration ML element by the processor by removing the per-STA profile sub-element corresponding to each AP removed from the affiliate relationship.

10. A non-access point AP multi-link device (MLD), comprising: Each STA (Station) includes a transceiver, which is configured as follows: Transmissions are made on the link established with the corresponding AP of the AP MLD, wherein the AP is attached to the AP MLD for performing multi-link ML operations on the established link, and Receive reconfiguration ML elements from the corresponding AP in the AP MLD; and A processor, operably coupled to the STA, is configured to determine one or more affiliated APs in the reconfiguration ML element instruction to be removed from the affiliated relationship with the AP MLD used for ML operations. The transceiver is also configured such that, after receiving a reconfiguration ML element, the corresponding remaining affiliated APs of the AP MLD receive the updated reconfiguration ML element, and The processor is also configured to determine the remaining associated APs to be removed based on the updated reconfiguration ML element.

11. The non-AP MLD according to claim 10, wherein: The reconfiguration ML element includes a per-STA profile sub-element corresponding to each of the affiliated APs to be removed, and The per-STA profile sub-element corresponding to each AP removed from the affiliate relationship is removed from the updated reconfiguration ML element.

12. The non-AP MLD according to claim 10 or 11, wherein, At least one per-STA configuration file sub-element is retained in the updated reconfiguration ML element.

13. The non-AP MLD according to any one of claims 10 to 12, wherein, The processor is also configured to determine that the AP MLD is identified by the MLD MAC address subfield of the underlying ML element corresponding to the AP MLD, based on the fact that the media access control MAC address presence subfield in the reconfigured ML element is set to 0.

14. The non-AP MLD according to any one of claims 10 to 13, wherein: The processor is also configured to determine that the MLD MAC address of the AP MLD is included in the reconfiguration ML element based on the presence of a subfield set to 1 in the MAC address in the reconfiguration ML element. The MAC address existence subfield is set to 1 based on the fact that an AP to be removed remains attached.

15. The non-AP MLD according to any one of claims 10 to 14, wherein, Based on the fact that no established links remain after the AP is removed from the affiliate relationship, the non-AP MLD is considered to be disconnected from the AP MLD.

Images