Method and apparatus for link negotiation for multi-link multi-radio operation
By negotiating EMLMR links between AP MLD and non-AP MLD, the problem of unadjustable link configuration in the prior art in EMLMR mode is solved, the efficiency and stability of multi-link operation are improved, and the multi-link equipment is satisfied. Space flow requirements in different frequency bands.
Patent Information
- Application Number
- CN202380029516.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-03-13
- Filing Date
- 2023-03-21
- Publication Date
- 2024-11-08
AI Technical Summary
The existing 802.11be standard lacks a mechanism for negotiating EMLMR links between AP MLDs and non-AP MLDs, resulting in unadjustable link configuration in EMLMR mode, affecting the efficiency of multi-link operations.
A mechanism is provided that allows negotiation of EMLMR links between AP MLDs and non-AP MLDs, including denying or suggesting different sets of EMLMR links, ensuring flexibility and efficiency of link configuration in EMLMR mode.
Through the negotiation mechanism, link configuration flexibility and efficiency in EMLMR mode are improved, the stability and performance of multi-link operations are ensured, and the spatial flow requirements of multi-link devices under different frequency bands are met.
Smart Images

Figure CN118923195A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to transmission efficiency in a wireless communication system including multi-link devices. Embodiments of the present disclosure relate to methods and apparatus for supporting link negotiation for enhanced multi-link multi-radio operation. Background Art
[0002] Wireless Local Area Network (WLAN) technology allows devices to access the Internet in the 2.4GHz, 5GHz, 6GHz, or 60GHz frequency bands. WLAN is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The IEEE 802.11 family of standards is designed to increase speed and reliability and extend the operating range of wireless networks.
[0003] Multi-link Operation (MLO) is a feature currently being developed by the standards body for the next generation Extremely High Throughput (EHT) Wi-Fi system in IEEE 802.11be. A Wi-Fi device that supports MLO is called a Multi-link Device (MLD). With MLO, a non-access point (AP) Multi-link Device (MLD) can discover, authenticate, associate, and establish multiple links with an AP MLD. Channel access and frame exchange are possible on each link between an AP MLD and a non-AP MLD. Summary of the invention
[0004] Solution to the problem
[0005] Embodiments of the present disclosure provide methods and apparatus for supporting link negotiation for enhanced multi-link multi-radio operation.
[0006] In one embodiment, a non-AP MLD is provided, comprising: a station including a transceiver configured to receive a first enhanced multi-link operation mode notification (EML OMN) frame associated with a request to transition to an enhanced multi-link multi-radio (EMLMR) mode from an AP affiliated to the AP MLD. The non-AP MLD also includes a processor operably coupled to the transceiver, the processor configured to negotiate a link for EMLMR operation between the AP MLD and the non-AP MLD based on receiving the first EML OMN frame before transitioning to the EMLMR mode.
[0007] In one embodiment, an AP MLD is provided, comprising: an AP including a transceiver. The AP MLD also includes a processor operably coupled to the transceiver, the processor being configured to: generate a first enhanced multi-link operation mode notification (EML OMN) frame associated with a request for transitioning to an enhanced multi-link multi-radio (EMLMR) mode; determine whether the transition to the EMLMR mode is accepted; configure an EML OWN frame based on whether the transition to the EMLMR mode is accepted; and negotiate a link for EMLMR operation between the AP MLD and a non-AP MLD before transitioning to the EMLMR mode. The transceiver is configured to send the EML OWN frame to a station (STA) associated with the non-AP MLD.
[0008] In one embodiment, a method of wireless communication performed by a non-AP MLD is provided. The method includes: receiving a first enhanced multi-link operation mode notification (EML OMN) frame associated with a request for transitioning to an enhanced multi-link multi-radio (EMLMR) mode from an AP attached to the AP MLD; and negotiating a link for EMLMR operation between the AP MLD and the non-AP MLD before transitioning to the EMLMR mode based on receiving the first EML OMN frame.
[0009] Other technical features may be apparent to those skilled in the art from the following drawings, descriptions and claims.
[0010] Before the following detailed description, it may be advantageous to set forth the definitions of certain words and phrases used throughout this patent document.The term "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other.The terms "send", "receive" and "communication" and their derivatives include direct and indirect communication.The terms "include" and "comprise" and their derivatives mean including but not limited to this.The term "or" is inclusive, meaning and / or.The phrase "associated with..." and its derivatives mean including, included in, interconnected with, included in, connected to or connected with, coupled to or coupled with, can communicate with, collaborate with, interweave, juxtapose, be close to, be bound to or bound with, have, have the property of, have a relationship with, etc.The term "controller" means any device, system or part thereof that controls at least one operation.Such a controller can be implemented with hardware or a combination of hardware and software and / or firmware. Functionality associated with any particular controller may be centralized or distributed, whether local or remote. When used with a list of items, the phrase "at least one of..." means that different combinations of one or more of the listed items may be used, and only one item in the list may be required. 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" may be used to simply distinguish a corresponding component from another component, and do not limit the component in other aspects (e.g., importance or order). It should be understood that if an element (e.g., a first element) is referred to as "coupled with another element (e.g., a second element)", "coupled to another element", "connected to another element", or "connected to another element" with or without the term "operably" or "communicatively", it means that the element may be coupled to another element directly (e.g., wired), wirelessly, or via a third element.
[0011] As used herein, the term "module" may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with other terms (e.g., "logic," "logic block," "component," or "circuit"). A module may be a single integrated component or its smallest unit or portion suitable for performing one or more functions. For example, according to an embodiment, a module may be implemented in the form of an application specific integrated circuit (ASIC).
[0012] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a 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, processes, functions, objects, classes, instances, related data or a portion thereof suitable for implementation in a suitable 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 that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disc (DVD) or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and rewrite data later, such as rewritable optical disks or erasable memory devices.
[0013] Definitions for certain other words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most, instances, such definitions apply to prior, as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:
[0015] Figure 1 An example wireless network according to one embodiment of the present disclosure is shown;
[0016] Figure 2a An example AP according to one embodiment of the present disclosure is shown;
[0017] Figure 2b An example station (STA) according to one embodiment of the present disclosure is shown;
[0018] Figure 3 The use of an EML operation mode notification frame to transition to EMLSR mode according to an embodiment of the present disclosure is shown;
[0019] Figure 4 An example of a process of an EMLMR mode of operation according to an embodiment of the present disclosure is shown;
[0020] Figure 5 An example of rejecting a request to transition to EMLMR mode according to an embodiment of the present disclosure is shown;
[0021] Figure 6 A flowchart illustrating an example method performed by an AP MLD to deny a request to transition to EMLMR mode according to an embodiment of the present disclosure;
[0022] Figure 7 A flowchart illustrating an example method of a request to transition to EML MR mode performed by a non-AP MLD according to an embodiment of the present disclosure;
[0023] Figure 8 An example of an alternative EMLMR link suggestion of an AP MLD according to an embodiment of the present disclosure is shown;
[0024] Fig. 9 An example flow chart of a method performed by an AP MLD for suggesting an alternative EMLMR link according to an embodiment of the present disclosure is shown;
[0025] Fig.10 An example flow chart of a method for sending an EMLMR mode transition request based on an EMLMR link suggested by an AP MLD, performed by a non-AP MLD according to an embodiment of the present disclosure, is shown;
[0026] Fig.11 An example of link negotiation by suggesting an alternative link set according to an embodiment of the present disclosure is shown;
[0027] Fig.12 An example of an EMLMR link in a response frame that is a subset of a requested EMLMR link according to an embodiment of the present disclosure is shown;
[0028] Fig.13 An example of EML MR mode transition on a link indicated by AP MLD according to an embodiment of the present disclosure is shown;
[0029] Fig.14 shows an example of transitioning in EMLMR mode initiated by an unsolicited response from an AP MLD according to an embodiment of the present disclosure; and
[0030] Fig.15 An example of an EMLMR conversion request initiated by an AP MLD according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION
[0031] Discussed below Figures 1 to 15 The various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.
[0032] Embodiments of the present disclosure provide mechanisms for supporting link negotiation for next generation enhanced multi-link multi-radio operations.
[0033] Figure 1 An example wireless network 100 is shown according to one embodiment of the present disclosure. Figure 1 The embodiment of the wireless network 100 shown is for illustration only. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.
[0034] The wireless network 100 includes APs 101 and 103. The APs 101 and 103 communicate with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network. The AP 101 provides wireless access to the network 130 for a plurality of STAs 111-114 within a coverage area 120 of the AP 101. The APs 101-103 may communicate with each other and with the STAs 111-114 using Wi-Fi or other WLAN communication technologies.
[0035] 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 a remote terminal. In a WLAN, assuming that the AP also contends for a wireless channel, the AP may also be referred to as a STA (e.g., APSTA). In addition, 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 device". For convenience, the terms "station" and "STA" are used in this disclosure to refer to remote wireless equipment 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 smart phone) or is generally considered to be a fixed device (such as a desktop computer, AP, media player, fixed sensor, TV, etc.). This type of STA may also be referred to as a non-AP STA.
[0036] In one embodiment of the present disclosure, each of the APs 101 and 103 and each of the STAs 111-114 may be an MLD. In such an embodiment, the APs 101 and 103 may be AP MLDs, and the STAs 111-114 may be non-AP MLDs. Each MLD is attached to more than one STA. For ease of explanation, an AP MLD is described herein as being attached to more than one AP (e.g., more than one AP STA), and a non-AP MLD is described herein as being attached to more than one STA (e.g., more than one non-AP STA).
[0037] Dashed lines illustrate the approximate extents of coverage areas 120 and 125, which are shown as approximately circular for purposes of illustration and explanation only. It should be clearly understood that coverage areas associated with APs, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the AP and variations in the radio environment associated with natural and man-made obstacles.
[0038] As described in more detail below, one or more of the APs may include circuitry and / or programming to support link negotiation for next generation enhanced multi-link multi-radio operation. Figure 1 One example of a wireless network 100 is shown, but may be Figure 1 Various changes may be made. For example, the wireless network 100 may include any number of APs and any number of STAs in any suitable arrangement. In addition, the AP 101 may communicate directly with any number of STAs and provide these STAs with wireless broadband access to the network 130. Similarly, each AP 101-103 may communicate directly with the network 130 and provide the STAs with direct wireless broadband access to the network 130. In addition, the APs 101 and / or 103 may provide access to other or additional external networks (such as an external telephone network or other types of data networks).
[0039] Figure 2a An example AP 101 is shown according to one embodiment of the present disclosure. Figure 2a The embodiment of AP 101 shown in FIG. 1 is for illustration only, and Figure 1 The APs 103 of FIG. 104 may have the same or similar configurations. In the embodiments discussed below, the AP 101 is an AP MLD. However, the APs have a variety of configurations, and Figure 2a The scope of the present disclosure is not limited to any particular implementation of the AP.
[0040] The AP MLD 101 is attached to a plurality of APs 202a-202n (which may be referred to as, for example, AP1-APn). Each of the attached APs 202a-202n includes a plurality of antennas 204a-204n, a plurality of RF transceivers 209a-209n, a transmit (TX) processing circuit 214, and a receive (RX) processing circuit 219. The AP MLD 101 also includes a controller / processor 224, a memory 229, and a backhaul or network interface 234.
[0041] The illustrated components of each subordinate AP 202a-202n may represent the physical (PHY) layer and the lower media access control (LMAC) layer in the open systems interconnection (OSI) networking model. In such an embodiment, the illustrated components of the AP MLD 101 represent a single upper MAC (UMAC) layer and other higher layers in the OSI model, which are shared by all subordinate APs 202a-202n.
[0042] For each satellite AP 202a-202n, an RF transceiver 209a-209n receives an incoming RF signal from an antenna 204a-204n, such as a signal transmitted by a STA in the network 100. In some embodiments, each satellite AP 202a-202n operates at a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), and thus the incoming RF signals received by each satellite AP may be at a different RF frequency. The RF transceiver 209a-209n down-converts the incoming RF signal to generate an IF or baseband signal. The IF or baseband signal is sent to the RX processing circuit 219, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuit 219 sends the processed baseband signal to the controller / processor 224 for further processing.
[0043] For each of the attached APs 202a-202n, the TX processing circuitry 214 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from the controller / processor 224. The TX processing circuitry 214 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceivers 209a-209n receive the outgoing processed baseband or IF signals from the TX processing circuitry 214 and up-convert the baseband or IF signals to RF signals that are transmitted via the antennas 204a-204n. In embodiments where each of the attached APs 202a-202n operates at a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), the outgoing RF signals transmitted by each of the attached APs may be at different RF frequencies.
[0044] 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 reception of forward channel signals and the transmission of reverse channel signals by the RF transceivers 209a-209n, the RX processing circuit 219, and the TX processing circuit 214 according to well-known principles. The controller / processor 224 may also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 224 may support beamforming or directional routing operations, in which outgoing signals from multiple antennas 204a-204n are weighted differently to effectively guide the outgoing signals in the desired direction. The controller / processor 224 may also support OFDMA operations, in which outgoing signals are assigned to different subcarrier subsets of different recipients (e.g., different STAs 111-114). The controller / processor 224 may support any of a variety of other functions in the AP MLD 101, including supporting link negotiation for next-generation enhanced multi-link multi-radio operations. 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 OS, residing in the memory 229. The controller / processor 224 can move data into or out of the memory 229 as required by the executing process.
[0045] 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 over a backhaul connection or over a network. The interface 234 can support communication over any suitable wired or wireless connection. For example, the interface 234 can allow the AP MLD 101 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface 234 includes any suitable structure that supports communication over a wired or wireless connection (such as Ethernet or an RF transceiver). The memory 229 is coupled to the controller / processor 224. A portion of the memory 229 may include RAM, and another portion of the memory 229 may include flash memory or other ROM.
[0046] As described in more detail below, AP MLD 101 may include circuitry and / or programming for supporting link negotiation for next generation enhanced multi-link multi-radio operation. Figure 2a An example of AP MLD 101 is shown, but the same may be applied to Figure 2a For example, AP MLD 101 may include Figure 2a. As a specific example, the AP MLD 101 may include multiple interfaces 234, and the controller / processor 224 may support routing functions to route data between different network addresses. As another specific example, although each satellite AP 202a-202n is shown as including a single instance of the TX processing circuit 214 and a single instance of the RX processing circuit 219, the AP MLD 101 may include multiple instances of each AP (such as one for each RF transceiver) in one or more of the satellite APs 202a-202n. Alternatively, in one or more of the satellite APs 202a-202n, such as in a traditional AP, only one antenna and RF transceiver path may be included. In addition, Figure 2a The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs.
[0047] Figure 2b An example STA 111 is shown according to one embodiment of the present disclosure. Figure 2b The embodiment of STA 111 shown in FIG. is for illustration only, and Figure 1 STAs 111-115 may have the same or similar configurations. In the embodiments discussed below, STA 111 is a non-AP MLD. However, STAs may have a variety of configurations, and Figure 2b The scope of the present disclosure is not limited to any particular implementation of a STA.
[0048] The non-AP MLD 111 is attached to a plurality of 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, a TX processing circuit 215, and a receive (RX) processing circuit 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 touch screen 250, a display 255, and a memory 260. The memory 260 includes an operating system (OS) 261 and one or more applications 262.
[0049] The illustrated components of each dependent STA 203a-203n may represent the PHY layer and LMAC layer in the OSI networking model. In such an embodiment, the illustrated components of the non-AP MLD 111 represent a single UMAC layer and other higher layers in the OSI model, which are shared by all dependent STAs 203a-203n.
[0050] For each affiliated STA 203a-203n, the RF transceiver 210 receives an incoming RF signal sent by the AP of the network 100 from the antenna 205. In some embodiments, each affiliated STA 203a-203n operates at a different bandwidth (e.g., 2.4GHz, 5GHz, or 6GHz), and thus the incoming RF signal received by each affiliated STA can be at a different RF frequency. The RF transceiver 210 down-converts the input RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to the RX processing circuit 225, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuit 225 sends the processed baseband signal to the speaker 230 (such as for voice data) or to the controller / processor 240 for further processing (such as for web browsing data).
[0051] For each affiliated STA 203a-203n, the TX processing circuit 215 receives analog or digital voice data from the microphone 220, or receives other outgoing baseband data (such as web data, email, or interactive video game data) from the controller / processor 240. The TX processing circuit 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 210 receives the outgoing processed baseband or IF signal from the TX processing circuit 215 and up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna 205. In embodiments where each affiliated STA 203a-203n operates at a different bandwidth (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.
[0052] The controller / processor 240 may include one or more processors and execute a basic OS program 261 stored in the memory 260 to control the overall operation of the non-AP MLD 111. In one such operation, the main controller / processor 240 controls the reception of forward channel signals and the transmission of reverse channel signals by the RF transceiver 210, the RX processing circuit 225, and the TX processing circuit 215 according to well-known principles. The main controller / processor 240 may also include processing circuits configured to support link negotiation for next generation enhanced multi-link multi-radio operations. In some embodiments, the controller / processor 240 includes at least one microprocessor or microcontroller.
[0053] The controller / processor 240 is also capable of executing other processes and programs resident in the memory 260, such as operations for supporting link negotiation for next generation enhanced multi-link multi-radio operations. The controller / processor 240 can move data into or out of the memory 260 as needed for the execution process. In some embodiments, the controller / processor 240 is configured to execute multiple applications 262, such as applications for supporting link negotiation for next generation enhanced multi-link multi-radio operations. The controller / processor 240 can operate multiple applications 262 based on the OS program 261 or in response to a signal received from the AP. The main controller / processor 240 is also coupled to the 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.
[0054] The controller / processor 240 is also coupled to a touch screen 250 and a display 255. An operator of the non-AP MLD 111 can use the touch screen 250 to input data into the non-AP MLD 111. The display 255 can be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and / or at least limited graphics, such as from a website. A memory 260 is coupled to the controller / processor 240. A portion of the memory 260 can include random access memory (RAM), and another portion of the memory 260 can include flash memory or other read-only memory (ROM).
[0055] although Figure 2b An example of a non-AP MLD 111 is shown, but the Figure 2b Make various changes. For example, Figure 2b The various components in the embodiment may be combined, further subdivided, or omitted, and additional components may be added as required. In a specific example, one or more of the affiliated STAs 203a-203n may include any number of antennas 205 for MIMO communication with the AP 101. In another example, the non-AP MLD 111 may not include voice communications, 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). In addition, although Figure 2b The non-AP MLD 111 is shown configured as a mobile phone or smart phone, but the non-AP MLD may be configured to operate as other types of mobile or fixed devices.
[0056] Non-AP MLDs in 802.11be may have different capabilities in terms of multi-link operation. The current 802.11be specification defines two special types of multi-link operation, namely Enhanced Multi-Link Single Radio Operation (EMLSR) and Enhanced Multi-Link Multi-Radio Operation (EMLMR).
[0057] Many 802.11be non-AP MLDs may have only a single radio. Enhanced Multi-Link Single Radio (EMLSR) achieves multi-link operation with a single radio. With EMLSR operation, non-AP MLDs can achieve throughput enhancement with reduced latency - approaching the performance of concurrent dual-radio non-AP MLDs. EMLSR operation and the behavior of STAs attached to non-AP MLDs during EMLSR operation mode are defined in the 802.11be standard. According to the current specification, if a non-AP MLD intends to operate in EMLSR mode with its associated AP MLD, the STA attached to the non-AP MLD sends an EML operation mode notification frame to its associated AP attached to the AP MLD, wherein the EMLSR mode subfield in the EML control field in the EML operation mode notification frame is set to 1. Upon receiving the EML operation mode notification frame from the non-AP MLD, the AP MLD may send another EML operation mode notification frame on any enabled link between the AP MLD and the non-AP MLD, wherein the EMLSR mode subfield in the EML control field in the EML operation mode notification frame is set to 1. The AP attached to the AP MLD is expected to send an EML Operation Mode Notification frame in response to an EML Operation Mode Notification frame sent by a STA attached to the non-AP MLD within the timeout interval indicated in the Transition Timeout subfield in the EML Capability subfield in the Basic Variant Multi-Link element most recently exchanged between the AP MLD and the non-AP MLD. The non-AP MLD transitions to the EMLSR mode immediately after receiving an EML Operation Mode Notification frame with the EMLSR Mode subfield in the EML Control field set to 1 from the AP attached to the AP MLD, or immediately after the timeout interval indicated in the Transition Timeout subfield in the EML Capability field in the Basic Variant Multi-Link element elapses after the end of the last PPDU contained in the EML Operation Mode Notification frame sent by the non-AP MLD, whichever occurs first. Upon transitioning to the EMLSR operation mode, all STAs attached to the non-AP MLD transition to the active mode (listening mode). This process of transitioning to the EMLSR mode using the EML Operation Mode Notification frame exchange is performed in Figure 3 Shown in.
[0058] Figure 3 FIG. 300 shows a method of using an EML operation mode notification frame to transition to EMLSR mode according to an embodiment of the present disclosure. Figure 3 The embodiment of the EMLSR mode 300 shown in FIG. 1 is for illustration only. Other embodiments of transitioning to the EMLSR mode 300 using the EML operating mode notification frame may be used without departing from the scope of the present disclosure.
[0059] like Figure 3 As shown, AP1 and AP2 are two APs attached to the AP MLD. In addition, STA1 and STA2 are two non-AP STAs attached to the non-AP MLD. Two links are established between the AP MLD and the non-AP MLD - Link 1 between AP1 and STA1, and Link 2 between AP2 and STA2. In addition, in this illustration, both Link 1 and Link 2 are enabled links. The non-AP MLD intends to switch to the EMLSR mode, and therefore, STA2 sends an EML operation mode notification frame to AP2 through Link 2, in which the EMLSR mode subfield in the EML control field is set to 1. In response to the EML operation mode notification frame sent by the non-AP MLD, AP2 sends another EML operation mode notification frame to STA2, in which the EMLSR mode subfield in the EML control field is set to 1. After receiving the EML operation mode notification frame from the AP MLD, the non-AP MLD switches to the EMLSR mode, and both STA1 and STA2 switch to the listening mode.
[0060] Enhanced Multi-Link Multi-Radio (EMLMR) operation is another operation mode newly defined in the IEEE 802.11be specification. Using the EMLMR operation mode, a multi-link device 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), thereby substantially increasing the spatial stream capacity of the second link.
[0061] According to the current 802.11be specification, the process for a non-AP MLD to transition to EMLMR mode is very similar to the process for transitioning to EMLSR mode. According to the current 802.11be specification, if a non-AP MLD intends its associated APMLD to operate in EMLMR mode, the STA attached to the non-AP MLD sends an EML operation mode notification frame to its associated AP attached to the AP MLD, wherein the EMLMR mode subfield in the EML control field in the EML operation mode notification frame is set to 1 (and the EMLSR mode in the same frame is set to 0). Upon receiving the EML operation mode notification frame from the non-AP MLD, the AP MLD may send another EML operation mode notification frame on any enabled link between the AP MLD and the non-AP MLD, wherein the EMLMR mode subfield in the EML control field in the EML operation mode notification frame is set to 1. The AP attached to the AP MLD is expected to send an EML Operation Mode Notification frame in response to an EML Operation Mode Notification frame sent by a STA attached to the non-AP MLD within the timeout interval indicated in the Transition Timeout subfield in the EML Capability subfield in the Basic Variant Multilink element most recently exchanged between the AP MLD and the non-AP MLD. The non-AP MLD transitions to the EMLMR mode immediately after receiving an EML Operation Mode Notification frame with the EMLMR Mode subfield in the EML Control field set to 1 from the AP attached to the AP MLD, or immediately after the timeout interval indicated in the Transition Timeout subfield in the EML Capability field in the Basic Variant Multilink element elapses after the end of the last PPDU contained in the EML Operation Mode Notification frame sent by the non-AP MLD, whichever occurs first. The following are some steps for operating in the EMLMR mode:
[0062] After the non-AP MLD switches to EMLMR mode, the AP MLD sends an initial frame to the non-AP MLD. The subsequent EMLMR frame exchange occurs on the link where the AP MLD sent the initial frame.
[0063] According to the current specification, the initial frame may be any frame sent by the APMLD to the non-AP MLD as the first frame after the non-AP MLD transitions to EMLMR mode.
[0064] According to the current specification, for EMLMR frame exchange, the AP MLD should select one of the links to be included as the EMLMR link.
[0065] After the AP MLD sends an initial frame on a link, the non-AP MLD can operate on the link with maximum spatial flows, as indicated by the values in the EMLMR Rx NSS and EMLMR TxNSS subfields in the EML Capability subfield of the Common Information field of the Basic Multilink Element.
[0066] Immediately after the EMLMR frame exchange sequence is completed, the STAs attached to the AP MLD return to operating with the per-link spatial stream capability.
[0067] Figure 4 An example of a process of the EMLMR operation mode 400 according to an embodiment of the present disclosure is shown. Figure 4 The embodiment of the process for the EMLMR mode of operation 400 shown in FIG. 4 is for illustration only. Other embodiments of the process for the EMLMR mode of operation 400 may be used without departing from the scope of the present disclosure.
[0068] like Figure 4As shown, the AP MLD has three subordinate APs: AP1 operating on the 2.4 GHz band, AP2 operating on the 5 GHz band, and AP3 operating on the 6 GHz band. The non-AP MLD has three subordinate STAs: STA1 operating on the 2.4 GHz band, STA2 operating on the 5 GHz band, and STA3 operating on the 6 GHz band. Three links are established between the AP MLD and the non-AP MLD: Link 1 between AP1 and STA1, Link 2 between AP2 and STA2, and Link 3 between AP3 and STA3. The non-AP MLD is a multi-radio non-AP MLD, in which STA1, STA2, and STA3 each have two transmit chains and two receive chains. Both the AP MLD and the non-AP MLD support the EMLMR operation mode. The non-AP MLD lists all three links (Link 1, Link 2, and Link 3) as EMLMR links. In the Basic Multilink Element exchanged between the AP MLD and the non-AP MLD, the EML Capability Present subfield is set to 1, and the EMLMR Rx NSS and EMLME Tx NSS subfields in the EML Capability subfield are both set to a value of 4. At an operational time point, the non-AP MLD intends to enter the EMLMR mode, and sends an EML Operation Mode Notification frame to the AP MLD on Link 2. In the EML Operation Mode Notification frame, the EMLMR Mode subfield in the EML Control field is set to 1, and the EMLSR Mode subfield in the EML Control field is set to 0. Upon receiving the EML Operation Mode Notification frame on Link 2, in response, the AP2 attached to the AP MLD sends another EML Operation Mode Notification frame to the non-AP MLD on Link 2, and sets the EMLMR Mode subfield in the EML Control field to 1 and the EMLSR Mode subfield in the EML Control field to 0 in the EML Operation Mode Notification frame. The non-AP MLD switches to the EMLMR mode when receiving an EML operation mode notification frame from the AP MLD, which is sent before the expiration of the timeout timer indicated in the conversion timeout subfield in the EML capability subfield in the basic multilink element. After the non-AP MLD switches to the EMLMR mode, the AP MLD sends an initial frame on link 3 to initiate frame exchange for EMLMR operation. When the initial frame is received on link 3, the non-AP MLD-
[0069] Transfer 1 transmit chain and 1 receive chain from link 1 to link 3
[0070] Transfer 1 transmit chain and 1 receive chain from link 2 to link 3.
[0071] After the transmit and receive chain transfer process is completed, Link 3 now has 4 transmit chains and 4 receive chains. Therefore, STA3 attached to the non-AP MLD can now perform transmit and receive operations on Link 3 using 4 spatial streams according to the values set in the EMLMRRx NSS and EMLMR Tx NSS subfields in the EML Capability subfield of the Basic Multilink Element. Then, STA 3 attached to the non-AP MLD sends an Ack frame in response to the initial control frame sent by the AP MLD. Therefore, the AP MLD performs subsequent PPDU transmissions to the non-AP MLD on Link 3 using 4 spatial streams.
[0072] One embodiment of the present disclosure recognizes that, for the EMLMR operation mode, after the non-AP MLD transitions to the EMLMR mode, the AP MLD sends an initial frame to initiate an EMLMR frame exchange on any EMLMR link by exchanging EML operation mode notification frames with the associated AP MLD on any enabled link between the AP MLD and the non-AP MLD, such that the EMLMR Mode subfield in the EML Control field of the exchanged EML operation mode notification frames is set to 1. Subsequent EMLMR frame exchanges occur on the link on which the AP MLD sends the initial frame.
[0073] One embodiment of the present disclosure recognizes that, based on the current 802.11be specification, an EMLMR link is non-negotiable (similar to an EMLSR link) - when an EML operation mode notification frame is sent to a non-AP MLD in response to an EML operation mode notification frame received from the non-AP MLD, the AP MLD sets a parameter set in the response frame that is the same as the parameter set of the EML operation mode notification frame received from the non-AP MLD.
[0074] One embodiment of the present disclosure recognizes that an AP MLD may not have the same capability as indicated by a non-AP MLD to operate at maximum TX / RX flows on all links included in an EMLMR link. Currently, there is no mechanism defined in the 802.11be specification that enables negotiation of an EMLMR link between an AP MLD and a non-AP MLD prior to operating in EMLMR mode.
[0075] Therefore, one embodiment of the present disclosure provides a mechanism and framework for EMLMR link negotiation between an AP MLD and a non-AP MLD that supports the EMLMR operating mode. For example, one embodiment of the present disclosure provides a mechanism that allows the AP MLD to reject an EMLMR mode transition request made by a non-AP MLD and have the non-AP MLD submit a new request with a different set of EMLMR links. One embodiment of the present disclosure provides a mechanism that allows the AP MLD to suggest a different set of EMLMR links if the AP MLD cannot accept the EMLMR mode transition request made by the non-AP MLD. One embodiment of the present disclosure provides a mechanism that allows the AP MLD to suggest a subset of EMLMR links when accepting an EMLMR mode transition request made by a non-AP MLD.
[0076] Figure 5 5 shows an example of rejecting a request to switch to EMLMR mode 500 according to an embodiment of the present disclosure. Figure 5 The embodiment of the request for EMLMR mode 500 shown in FIG. 5 is for illustration only. Other embodiments of denying the request to transition to EMLMR mode 500 may be used without departing from the scope of the present disclosure.
[0077] According to one embodiment, when a non-AP MLD intends to transition to EMLMR mode and sends an EML operation mode notification frame to its associated AP MLD, the EML operation mode notification frame indicating an EMLMR link and setting the EMLMR mode subfield to 1, if the AP MLD cannot operate in the EMLMR mode on any EMLMR link indicated in the EML operation mode notification frame received from the non-AP MLD, the AP MLD may reject the EMLMR mode transition request made by the non-AP MLD.
[0078] According to one embodiment, the AP MLD may indicate rejection of the EMLMR mode transition request by sending an EML operation mode notification frame as a response to the non-AP MLD in which the EMLMR mode subfield is set to 0.
[0079] According to one embodiment, to indicate the rejection of the EMLMR mode transition request made by the non-AP MLD, the AP MLD sends an EML operation mode notification frame in which the EMLMR mode subfield is set to 0 to the requesting non-AP MLD before the expiration of the timeout timer indicated in the transition timeout subfield in the EML capability subfield in the basic multilink element. Upon receiving the EML operation mode notification frame in which the EMLMR mode subfield is set to 0 from the APMLD, the non-AP MLD is notified of the rejection of its request to transition in the EMLMR mode. The non-AP MLD may then send another EML operation mode notification frame to the AP MLD with a different EMLMR link set and the EMLMR mode subfield is set to 1. This may be considered as a new request to transition to the EMLMR mode. Figure 5 This embodiment is shown.
[0080] Figure 6 A flow chart is shown of an example method 600 performed by an AP MLD to deny a request to transition to EMLMR mode according to an embodiment of the present disclosure. Figure 6 The embodiment of the example method 600 for denying a request to transition to EMLMR mode performed by an AP MLD shown in FIG is for illustration only. Other embodiments of the example method 600 for denying a request to transition to EMLMR mode performed by an AP MLD may be used without departing from the scope of the present disclosure.
[0081] like Figure 6 As shown, method 600 starts at step 610, where the AP MLD receives an EML operation mode notification frame from a non-AP MLD, where EMLMR mode=1 and has an EMLMR link indication. At step 620, the AP MLD checks the EMLMR links indicated in the received EML operation mode notification frame and recognizes that it cannot operate in EMLMR mode on some indicated links. At step 630, the AP MLD sends an EML operation mode notification frame to the non-AP MLD, where the EMLMR subfield is set to 0.
[0082] Figure 7 FIG. 7 is a flow chart showing an example method 700 of requesting a transition to EMLMR mode performed by a non-AP MLD according to an embodiment of the present disclosure. Figure 7 The illustrated embodiment of the example method 700 of requesting to transition to EMLMR mode performed by a non-AP MLD is for illustration only. Other embodiments of the example method 700 of requesting to transition to EMLMR mode performed by a non-AP MLD may be used without departing from the scope of the present disclosure.
[0083] like Figure 7As shown, method 700 starts at step 710, where the non-AP MLD sends an EML operation mode notification frame to the associated AP MLD, where EMLMR mode = 1. At step 720, the non-AP MLD receives the EML operation mode notification frame from the AP MLD, where the EMLMR mode subfield = 0. At step 730, the non-AP MLD sends another EML operation mode notification frame to the associated AP MLD, where EMLMR mode = 1 and has a different EMLMR link set than the EMLMR link indicated in the first request.
[0084] Figure 8 An example of alternative EMLMR link suggestions by the AP MLD 800 according to an embodiment of the present disclosure is shown. Figure 8 The illustrated embodiment of the example alternative EMLMR link suggestion of AP MLD 800 is for illustration only. Other embodiments of the example alternative EMLMR link suggestion of AP MLD 800 may be used without departing from the scope of the present disclosure.
[0085] According to one embodiment, when the AP MLD receives an EML operation mode notification frame from an associated non-AP MLD, in which the EMLMR Mode subfield is set to 1, in which the EMLMR link indication has link set A, if the AP MLD cannot operate in EMLMR mode with the non-AP MLD on any EMLMR links indicated in the received EML operation mode notification frame, the APMLD may suggest an alternative EMLMR link set for EMLMR mode operation with the non-AP MLD. According to one embodiment, the APMLD may make a suggestion to the non-AP MLD by including its preferred link set (e.g., link set B) as EMLMR links in the EML operation mode notification frame as a response to the EML operation mode notification frame received from the non-AP MLD. In the EML operation mode notification frame sent by the AP MLD as a response frame, the AP MLD may set the EMLMR Mode subfield to 0. This indicates that the current request for EMLMR conversion is rejected, but if the non-AP MLD sends another request by sending another EML operation mode notification frame in which the link proposed by the AP MLD (link set B) is as the EMLMR link, the AP MLD may accept the request by sending an EML operation mode notification frame in which the EMLMR mode subfield is set to 1 in response. Figure 8 This embodiment is shown.
[0086] Fig. 9 An example flow chart of a method 900 for suggesting an alternative EMLMR link performed by an AP MLD according to an embodiment of the present disclosure is shown. Fig. 9The embodiment of the example method 900 performed by an AP MLD for suggesting an alternative EMLMR link shown in FIG. 9 is for illustration only. Other embodiments of the example method 900 performed by an AP MLD for suggesting an alternative EMLMR link may be used without departing from the scope of the present disclosure.
[0087] like Fig. 9 As shown, method 900 begins at step 910, where the AP MLD receives an EML operation mode notification frame from a non-AP MLD, where EMLMR mode=1 and has an EMLMR link indication. At step 920, the AP MLD checks the EMLMR links indicated in the received EML operation mode notification frame and recognizes that it cannot operate in EMLMR mode on some of the indicated links. At step 930, the AP MLD sends an EML operation mode notification frame with an alternative EMLMR link suggestion to the non-AP MLD in response.
[0088] Fig.10 FIG. 1 shows an example flow chart of a method 1000 for sending an EMLMR mode transition request based on an EMLMR link suggested by an AP MLD and executed by a non-AP MLD according to an embodiment of the present disclosure. Fig.10 The illustrated embodiment of the example method 1000 for sending an EMLMR mode transition request based on an EMLMR link suggested by an AP MLD and performed by a non-AP MLD is for illustration only. Other embodiments of the example method 1000 for sending an EMLMR mode transition request based on an EMLMR link suggested by an AP MLD and performed by a non-AP MLD may be used without departing from the scope of the present disclosure.
[0089] like Fig.10 As shown, method 1000 starts at step 1010, where the non-AP MLD sends an EML operation mode notification frame to the associated AP MLD, where EMLMR=1 and the EMLMR link is set to link set A. At step 1020, the non-AP MLD receives the EML operation mode notification frame with the alternative EMLMR link (link set B) from the AP MLD. At step 1030, the non-AP MLD sends another EML operation mode notification frame to the associated AP MLD, where EMLMR mode=1 and with the EMLMR link indication as link set B. At step 1040, the non-AP MLD receives another EML operation mode notification frame from the associated AP MLD, where EMLMR mode=1 and with the EMLMR link indication as link set B. At step 1050, the non-AP MLD transitions to EMLMR mode.
[0090] According to one embodiment, if the EMLMR link indicated in the EML operation mode notification frame sent by the AP MLD as a response frame is different from the EMLMR link indicated in the EML operation mode notification frame sent by the associated non-AP MLD as a request frame, it serves as an indication that the current EMLMR mode transition request is rejected.
[0091] According to one embodiment, the EMLMR Link subfield may be present in the response EML operation mode notification frame even if the EMLMR Mode subfield in the EML operation mode notification frame as the response frame is set to 0. This may indicate that the current EMLMR mode transition request is rejected and the EMLMR Link in the response frame indicates an alternative EMLMR link suggested by the AP MLD.
[0092] According to one embodiment, when the AP MLD sends an EML operation mode notification frame to the associated non-AP MLD in response to the EML operation mode notification frame received from the non-AP MLD, if the AP MLD sets the EMLMR mode subfield to 1 in the response frame, the EMLMR link indication is not present in the response EML operation mode notification frame. According to one embodiment, if the APMLD sets the EMLMR mode subfield to 1 in the response frame, the EMLMR link indication is present in the response EML operation mode notification frame, and the EMLMR link indicated in the response EML operation mode notification frame is the same as the EMLMR link indicated in the request EML operation mode notification frame from the non-AP MLD (e.g., Figure 8 example shown).
[0093] Fig.11 FIG. 1 shows an example of link negotiation by suggesting an alternative link set 1100 according to an embodiment of the present disclosure. Fig.11 The embodiment of the example of link negotiation of the alternative link set 1100 shown in FIG. 1 is for illustration only. Other embodiments of the example of link negotiation of the alternative link set 1100 may be used without departing from the scope of the present disclosure.
[0094] like Fig.11As shown, according to one embodiment, when the AP MLD sends an EML operation mode notification frame to the associated non-AP MLD in response to the EML operation mode notification frame received from the non-AP MLD, if the AP MLD sets the EMLMR mode subfield to 1 in the response frame, the EMLMR link indicated in the response EML operation mode notification frame may be different from the EMLMR link indicated in the request EML operation mode notification frame - it may indicate that the EMLMR mode transition negotiation has not been completed, and if the non-AP MLD sends another EML operation mode notification frame with the EMLMR link indicated by the AP MLD, the EMLMR mode transition request may be subsequently accepted.
[0095] Fig.12 An example of an EMLMR link in a response frame that is a subset of the requested EMLMR link 1200 according to an embodiment of the present disclosure is shown. Fig.12 The embodiment of the example of the EMLMR links in the response frame as a subset of the requested EMLMR links 1200 shown in FIG is for illustration only. Other embodiments of the example of the EMLMR links in the response frame as a subset of the requested EMLMR links 1200 may be used without departing from the scope of the present disclosure.
[0096] like Fig.12 As shown, according to one embodiment, when the AP MLD receives an EML operation mode notification frame from an associated non-AP MLD, wherein the EMLMR mode subfield is set to 1 and the EMLMR link indication has link set A, the AP MLD may respond by sending another EML operation mode notification frame to the non-AP MLD, wherein the EMLMR link indication has link set B, wherein link set B is a subset of link set A. This will indicate that the request to transition to the EMLMR mode has been accepted, but the EMLMR mode will operate on the EMLMR links of link set B. According to one embodiment, in the response frame, the AP MLD may set the EMLMR mode subfield to 1.
[0097] Fig.13 An example of EMLMR mode transition on a link indicated by the AP MLD 1300 according to an embodiment of the present disclosure is shown. Fig.13 The illustrated embodiment of the example of EMLMR mode transitions on a link indicated by AP MLD 1300 is for illustration only. Other embodiments of the example of EMLMR mode transitions on a link indicated by AP MLD 1300 may be used without departing from the scope of the present disclosure.
[0098] like Fig.13As shown, according to one embodiment, when the AP MLD receives an EML operation mode notification frame from an associated non-AP MLD, in which the EMLMR mode subfield is set to 1 and the EMLMR link indication is as link set A, even if link set B is not a subset of link set A, the AP MLD may send an EML operation mode notification frame to the associated non-AP MLD in response, in which the EMLMR mode subfield is set to 1 and the EMLMR link indication is as link set B. According to this embodiment, the non-AP MLD still transitions to the EMLMR mode, but operates on link set B as an EMLMR link.
[0099] Fig.14 An example of transitioning in EMLMR mode initiated by an unsolicited response from the AP MLD 1400 according to an embodiment of the present disclosure is shown. Fig.14 The illustrated embodiment of the example of transitioning in EMLMR mode initiated by an unsolicited response from AP MLD 1400 is for illustration only. Other embodiments of the example of transitioning in EMLMR mode initiated by an unsolicited response from AP MLD 1400 may be used without departing from the scope of the present disclosure.
[0100] like Fig.14 As shown, according to one embodiment, the AP MLD may send an EML operation mode notification frame to its associated non-AP MLD as an unsolicited response. Upon receiving the unsolicited response, the non-AP MLD may transition to EMLMR mode and operate on the EMLMR link as indicated in the unsolicited response frame.
[0101] Fig.15 An example of an EMLMR conversion request initiated by the AP MLD 1500 according to an embodiment of the present disclosure is shown. Fig.15 The illustrated embodiment of the example of the EMLMR conversion request initiated by the AP MLD 1500 is for illustration only. Other embodiments of the example of the EMLMR conversion request initiated by the AP MLD 1500 may be used without departing from the scope of the present disclosure.
[0102] like Fig.15 As shown, according to one embodiment, the AP MLD may send an EML operation mode notification frame to its associated non-AP MLD as a request for transition to the EMLMR mode. Upon receiving the request from the AP MLD, the non-AP MLD may send a response to the AP MLD by sending an EML operation mode notification frame. In the response frame, the non-AP MLD may set the same parameter set as that of the request frame from the APMLD, or set a parameter set different from that of the request frame. Fig.15 As shown, the EMLMR conversion request is initiated by the AP MLD, and different link sets are indicated in the request and response frames.
[0103] The above flow charts illustrate example methods that can be implemented according to the principles of the present disclosure, and various changes can be made to the methods or processes shown in the flow charts. For example, although shown as a series of steps, various steps can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, a step can be omitted or replaced by another step.
[0104] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. The present disclosure is intended to cover these changes and modifications that fall within the scope of the appended claims. The description in this application should not be interpreted as implying that any particular element, step or function is an essential element that must be included in the scope of the claims. The scope of the patent subject matter is defined by the claims.
Claims
1. A non-access point (AP) multi-link device (MLD), include: a station (STA) comprising a transceiver configured to receive a first enhanced multi-link operation mode notification (EMLOMN) frame associated with a request to transition to an enhanced multi-link multi-radio (EMLMR) mode from an AP attached to an AP MLD; as well as A processor is operably coupled to the transceiver, the processor being configured to negotiate a link for EMLMR operation between the AP MLD and the non-AP MLD before transitioning to the EMLMR mode based on receiving the first EML OMN frame.
2. The non-AP MLD according to claim 1, in: The transceiver is configured to send a second EML OMN frame to the AP MLD, the second EML OMN frame requesting a transition to the EMLMR mode and indicating a link set for EMLMR operation, and The first EML OMN frame responds to the second EML OWN frame and indicates whether the AP MLD accepts the transition to the EML MR mode.
3. The non-AP MLD according to claim 1 or claim 2, in: The first EML OWN frame indicates that the AP MLD refuses to transition to EMLMR mode, and The transceiver is configured to send a third EML OMN frame to the AP MLD, the third EML OMN frame indicating a link set different from a link set used for the EMLMR operation.
4. A non-AP MLD according to any one of the preceding claims, in: The first EML OMN frame indicates that the AP MLD accepts the transition to EMLMR mode, and The first EML OMN frame indicates one or more links to be used for EML MR operations that are different from the set of links indicated in the second EML OMN frame.
5. A non-AP MLD according to any one of the preceding claims, in, The first EML OMN frame requests a transition to EMLMR mode and indicates a link set to be used for EMLMR operation for non-AP MLDs.
6. A non-AP MLD according to any one of the preceding claims, in: A first EML OMN frame requests a transition to EMLMR mode and indicates a link set for EMLMR operation, and The transceiver is configured to send a second EML OMN frame to the AP MLD in response to the request for transition to the EML MR mode, the second EML OMN frame indicating acceptance of transition to the EML MR mode.
7. A non-AP MLD according to any one of the preceding claims, in: The first EML OMN frame requests a transition to EMLMR mode and indicates a link set for EMLMR operation. The transceiver is configured to send a second EML OMN frame to the AP MLD in response to the request for transition to the EML MR mode, the second EML OMN frame indicating acceptance of transition to the EML MR mode, and The second EML OMN frame indicates one or more links to be used for EML MR operations that are different from the set of links indicated in the first EML OMN frame.
8. An access point (AP) multi-link device (MLD), include: AP, including transceiver; and A processor operatively coupled to the transceiver, the processor configured to: generating a first enhanced multi-link operating mode notification (EML OMN) frame associated with a request to transition to an enhanced multi-link multi-radio (EMLMR) mode; Determine whether to accept the transition to EMLMR mode; configuring a first EML OWN frame based on whether the transition to the EMLMR mode is accepted; as well as Before transitioning to EMLMR mode, a link for EMLMR operation is negotiated between the AP MLD and the non-AP MLD; The transceiver is configured to send a first EML OWN frame to a station (STA) associated with the non-AP MLD.
9. The AP MLD according to claim 8, in: The transceiver is configured to receive a second EML OMN frame from the non-AP MLD, the second EML OMN frame requesting a transition to the EMLMR mode and indicating a link set for EMLMR operation, and The first EML OMN frame responds to the second EML OWN frame and indicates whether the AP MLD accepts the transition to the EML MR mode.
10. The AP MLD according to claim 8 or claim 9, in: The first EML OWN frame indicates that the AP MLD refuses to transition to EMLMR mode, and The transceiver is configured to send a third EML OMN frame to the AP MLD, the third EML OMN frame indicating a link set different from a link set used for the EMLMR operation.
11. The AP MLD according to any one of claims 8 to 10, in: The first EML OMN frame indicates that the AP MLD accepts the transition to EMLMR mode, and The first EML OMN frame indicates one or more links to be used for EML MR operations that are different from the set of links indicated in the second EML OMN frame.
12. The AP MLD according to any one of claims 8 to 11, in, The first EML OMN frame requests a transition to EMLMR mode and indicates a link set to be used for EMLMR operation for non-AP MLDs.
13. The AP MLD according to any one of claims 8 to 12, in: A first EML OMN frame requests a transition to EMLMR mode and indicates a link set for EMLMR operation, and The transceiver is configured to receive, in response to the request for transition to the EML MR mode, a second EML OMN frame from the non-AP MLD, the second EML OMN frame indicating acceptance of transition to the EML MR mode.
14. The AP MLD according to any one of claims 8 to 13, in: The first EML OMN frame requests a transition to EMLMR mode and indicates a link set for EMLMR operation. The transceiver is configured to receive, in response to the request for transition to the EMLMR mode, a second EML OMN frame from the non-AP MLD, the second EML OMN frame indicating acceptance of transition to the EMLMR mode, and The second EML OMN frame indicates one or more links to be used for EML MR operations that are different from the set of links indicated in the first EML OMN frame.
15. A method of wireless communication performed by a non-access point (AP) multi-link device (MLD), the method include: receiving, from an AP affiliated with the AP MLD, a first enhanced multi-link operation mode notification (EML OMN) frame associated with a request to transition to an enhanced multi-link multi-radio (EMLMR) mode; as well as Based on receiving the first EML OMN frame, a link for EMLMR operation is negotiated between the AP MLD and the non-AP MLD before transitioning to the EMLMR mode.
