Enhanced mode management techniques for multi-link operation

Abstract

A method can include sending, to an access point (AP), a frame including an operating mode indicator, where the operating mode indicator indicates an enablement, disablement, or modification of an operating mode associated with a wireless link. The method can also include receiving a response from the AP, and enabling, disabling, or modifying the operating mode associated with the wireless link based at least in part on the operating mode indicator and the response.

Description

Technical Field

[0001] This application relates to wireless communications, including enhanced mode management techniques for multi-link operation between wireless sites and / or access points in wireless networking systems.

[0002] Related technical descriptions The use of wireless communication systems is growing rapidly. Furthermore, wireless communication technology has evolved from voice communication alone to include the transmission of data such as the internet and multimedia content. A commonly used short- / mid-range wireless communication standard is Wireless Local Area Network (WLAN). Most modern WLANs are based on the IEEE 802.11 standard (and / or simply 802.11) and are sold under the Wi-Fi brand name. A WLAN network links one or more devices to a wireless access point, which in turn provides connectivity to the internet over a wider area.

[0003] In an 802.11 system, devices wirelessly connected to each other are called “sites,” “mobile stations,” “user equipment,” “user gear,” or simply STA or UE. A wireless site can be a wireless access point or a wireless client (and / or mobile station). An access point (AP), also known as a wireless router, acts as a base station for the wireless network. An AP sends and receives radio frequency signals used to communicate with wireless client devices. An AP can also be coupled to the Internet via wired and / or wireless means. A wireless client operating on an 802.11 network can be any of a variety of devices, such as laptops, tablets, smartphones, smartwatches, or fixed devices (such as desktop computers). This document refers to wireless client devices as user gear (and / or simply UE). Some wireless client devices are also collectively referred to herein as mobile devices or mobile stations (but as noted above, wireless client devices can also generally be stationary devices).

[0004] Mobile electronic devices can take the form of smartphones, laptops, or tablets that users typically carry. Wearable devices (also known as accessory devices) are a newer form of mobile electronic device, with examples including smartwatches, earbuds, and smart glasses. Additionally, low-cost, low-complexity wireless devices designed for static or dynamic deployment are rapidly increasing as part of the development of the “Internet of Things”. In other words, the required devices are becoming increasingly diverse in terms of complexity, capabilities, business models, and other characteristics.

[0005] Some WLANs can utilize multi-link operation (MLO), for example, the concurrent use of multiple channels (e.g., links). APs and / or STAs with MLO capability can be referred to as multi-link devices (MLDs). For example, an AP with MLO capability can be referred to as an AP-MLD, and an MLO-capable STA that does not act as an AP can be referred to as a non-AP MLD. Improvements in this art are expected. Summary of the Invention

[0006] The implementation schemes described herein relate to methods, systems, and apparatuses for enhanced mode management techniques in multi-link operation between wireless sites and / or access points in wireless networking systems.

[0007] In some implementations, a method may include sending a frame including an operation mode indicator to an access point (AP) indicating the enabling, disabling, or modification of an operation mode associated with a radio link. The method may also include receiving a response from the AP; and enabling, disabling, or modifying the operation mode associated with the radio link based at least in part on the operation mode indicator and the response.

[0008] According to some embodiments, the frame includes a link reconfiguration request frame. Additionally or alternatively, the operating mode indicator may be included in the mode change element of the link reconfiguration request frame. Furthermore, according to some embodiments, the operating mode indicator may be included in the mode control field of the mode change element. Additionally, according to some embodiments, the mode change element may include at least one of the following: a sub-element identifier (ID) corresponding to the operating mode; a mode control field indicating the enabling, disabling, or modification of the operating mode; or operating parameters associated with the operating mode.

[0009] In some implementations, the operating mode indicator may include a sub-element identifier (ID) corresponding to the operating mode, and the operating mode includes at least one of the following: Dynamic Unavailable Operation (DUO) mode; Dynamic Power Saving (DPS) mode; Non-Master Channel Access (NPCA) mode; Dynamic Subband Operation (DSO) mode; Coordinated Beamforming (Co-BF) mode; Coordinated Space Rejection (Co-SR) mode; Low Latency Indication (LLI) mode; Dynamic Bandwidth Extension (DBE) mode; or Limited Operation (LOM) mode. Additionally or alternatively, the method may further include adding or removing the radio link using a per-site (per STA) profile sub-element, wherein the radio link operates according to the operating mode.

[0010] According to other embodiments, an apparatus may include a processor configured to cause an access point (AP) multilink device (MLD) to perform operations upon execution of instructions stored in a memory. These operations include: sending a frame including an operation mode indicator to a non-access point (non-AP) station (STA) indicating the enabling, disabling, or modification of an operation mode associated with a radio link. Additionally, the operation may include: receiving a response from the non-AP STA; and enabling, disabling, or modifying the operation mode associated with the radio link, at least in part, based on the operation mode indicator and the response.

[0011] In some implementations, the operation mode indicator may be included in an ordered bitmap to indicate at least one of one or more operation modes to be enabled, disabled, or modified. Additionally or alternatively, the operation mode indicator may also indicate the presence of operation parameters for at least one of the one or more operation modes.

[0012] According to some implementations, the operation mode indicator may be included in a reconfiguration multi-link (ML) element. Furthermore, the operation mode indicator may be included in a mode enable profile sub-element corresponding to a sub-field of the ML control field of the reconfiguration ML element. Additionally or alternatively, the operation mode indicator may be included in at least one of the STA information fields in the per-site (STA) enable profile sub-element of the reconfiguration ML element. In some implementations, the reconfiguration ML element may include one or more per-site (per-STA) profile sub-elements, each of which includes a site (STA) control field, wherein the STA control field includes link identifier (ID) information and reconfiguration operation type information, and wherein the link ID information and the reconfiguration operation type information are usable to enable, disable, or modify the operation mode associated with the radio link.

[0013] According to an additional embodiment, a non-access point (non-AP) station (STA) may include: a radio component; and a processor operatively coupled to the radio component and configured to cause the non-AP STA to send a frame including an operation mode indicator to an access point (AP), the operation mode indicator indicating the enabling, disabling, or modification of an operation mode associated with a radio link. Additionally, the processor may be configured to cause the non-AP STA to: receive a response from the AP; and enable, disable, or modify the operation mode associated with the radio link, at least in part, based on the operation mode indicator and the response.

[0014] In some implementations, the operating mode indicator may include a feature enable element. According to some implementations, the processor may also be configured to cause the non-AP STA to start a first timer, wherein enabling, disabling, or modifying the operating mode associated with the radio link is based on the expiration of the first timer. Additionally or alternatively, the response from the AP may be an acknowledgment (ACK) frame. In some implementations, the first timer starts upon receipt of the ACK frame.

[0015] According to some implementations, the processor may also be configured to cause the non-AP STA to: receive a notification frame from the AP including another feature enabling element; and send an acknowledgment (ACK) frame to the AP. Additionally or alternatively, enabling, disabling, or modifying the operating mode associated with the radio link may be performed upon the expiration of a second timer that starts upon receiving the ACK frame.

[0016] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0017] A better understanding of the subject matter can be obtained by considering the following specific description of the implementation scheme in conjunction with the accompanying drawings.

[0018] Figure 1 Example wireless communication systems according to some implementation schemes are illustrated.

[0019] Figure 2 Simplified block diagrams of wireless devices according to some implementation schemes are shown.

[0020] Figure 3 An example WLAN communication system based on some implementation schemes is illustrated.

[0021] Figure 4 Simplified block diagrams of WLAN access points (APs) according to some implementation schemes are shown.

[0022] Figure 5 A simplified block diagram of a wireless station (STA) according to some implementation schemes is shown.

[0023] Figure 6 A simplified block diagram of a wireless node according to some implementation schemes is shown.

[0024] Figures 7 to 8 Examples of MLD implementations based on various implementation schemes are shown.

[0025] Figure 9 Example communication exchanges between APs and STAs during attempts to switch to Dynamic Power Saving (DPS) mode and from DPS mode are illustrated according to some implementation schemes.

[0026] Figure 10 This is a communication flowchart illustrating various aspects of an enhanced approach to pattern management technology for non-AP MLDs, based on some implementation schemes.

[0027] Figures 11A to 11B Example fields and element formats available for pattern-enabled frames according to some implementation schemes are shown.

[0028] Figure 12 Example frame formats for link reconfiguration request frames for mode change are shown according to some implementation schemes.

[0029] Figures 13A to 13C Example aspects of reconfiguring the link information field of an ML element according to some implementation schemes are illustrated.

[0030] Figures 14A to 14B Example aspects of enabling profile sub-elements per STA in the STA information field according to some implementation schemes are illustrated.

[0031] Figures 15A to 15C Example aspects of the operational parameter subfields for STA information fields of different mode types are illustrated according to some implementation schemes.

[0032] Figures 16A to 16B Example fields and formats of link reconfiguration request frames according to some implementation schemes are shown.

[0033] Figures 17A to 17B Example fields and formats for link reconfiguration response frames used for mode change, based on some implementation schemes, are illustrated.

[0034] Figure 18 This is a communication flowchart illustrating various aspects of an enhanced method for pattern management technology for AP MLD, based on some implementation schemes.

[0035] Figures 19A to 19B Example fields and formats for link reconfiguration request frames for UHR mode change are shown according to some implementation schemes.

[0036] Figures 20A to 20B Examples of elements and sub-element fields and formats are shown in the link reconfiguration framework according to some implementation schemes.

[0037] Figures 21A to 21B Example fields and formats for LR request frames for UHR mode change are shown according to some implementation schemes.

[0038] Figure 22 Example fields and formats of the perSTA profile sub-element in the link information field of the reconfiguration ML element according to some implementation schemes are shown.

[0039] Figure 23 Examples of fields and formats for elements that change according to a pattern without a link ID / bitmap in some implementation schemes are shown.

[0040] Figure 24 Examples of fields and formats of elements in ML elements are shown, illustrating how the schema changes in an element can be modified according to some implementation schemes.

[0041] Figure 25 Example fields and formats of pattern-changing elements in LR request frames are shown, based on some implementation schemes.

[0042] Figures 26A to 26B Examples of fields and formats for pattern-changing elements with corresponding link IDs or bitmaps are shown, depending on some implementation schemes.

[0043] Figure 27 Example subfields and formats of the operation parameter fields for DPS mode are shown according to some implementation schemes.

[0044] Figure 28 This is a communication flowchart illustrating various aspects of an enhanced approach to pattern management technology, including feature enable / update / deactivate, based on some implementation schemes.

[0045] Figure 29 This illustrates the activation process for enabling elements based on the usage characteristics of some implementation schemes.

[0046] Figure 30 Example modal conditions for feature enabling or updating are illustrated according to some implementation schemes.

[0047] Figure 31 This illustrates the process of enabling and disabling elements based on usage characteristics of some implementation schemes.

[0048] Figure 32 Example modal conditions for feature deactivation according to some implementation schemes are illustrated.

[0049] Figures 33A to 33G Examples of fields and formats related to the first option of feature-enabled element design are shown according to some implementation schemes.

[0050] Figures 34A to 34G Examples of fields and formats related to the second option of feature-enabled element design are shown according to some implementation schemes.

[0051] Figure 35 Examples of including a feature-enabled element in a link reconfiguration request frame according to some implementation schemes are shown.

[0052] Figure 36 Examples of including a feature enablement element in a link reconfiguration notification frame according to some implementation schemes are shown.

[0053] While the features described herein are susceptible to various modifications and alternatives, specific embodiments thereof are illustrated by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit one to the specific forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0054] Figures 1 to 2 —Wireless communication system Figure 1 Exemplary (and simplified) wireless communication systems are illustrated, in which various aspects of this disclosure can be implemented. It should be noted that... Figure 1 The system described herein is only one example of a possible system, and embodiments of this disclosure can be implemented in any of a variety of systems as needed.

[0055] As shown in the figure, the exemplary wireless communication system includes a ("first") wireless device 102 communicating with another ("second") wireless device 104. The first wireless device 102 and the second wireless device 104 may use any of a variety of wireless communication technologies, including ranging wireless communication technologies.

[0056] As an option, the first wireless device 102 and the second wireless device 104 may use wireless local area network (WLAN) communication technologies (e.g., IEEE 802.11 / Wi-Fi based communication) and / or WLAN-based wireless communication technologies to perform ranging. One or both of wireless devices 102 and 104 may also be able to communicate via one or more additional wireless communication protocols, such as any of Bluetooth (BT), Bluetooth Low Energy (BLE), Near Field Communication (NFC), LTE, LTE-A Advanced, NR, Ultra Wideband (UWB), etc.

[0057] Wireless device 102 and wireless device 104 can be any of a variety of wireless devices. As one possibility, one or more of wireless devices 102 and / or 104 can be substantially portable wireless user equipment (UE) devices, such as smartphones, handheld devices, wearable devices (such as smartwatches), tablets, motor vehicles, or virtually any type of wireless device. As another possibility, one or more of wireless devices 102 and / or wireless device 104 can be substantially stationary devices, such as set-top boxes, media players (e.g., audio or video equipment), game consoles, desktop computers, appliances, doors, access points, base stations, or any of a variety of other types of devices.

[0058] Each of wireless devices 102 and 104 may include wireless communication circuitry configured to enhance the performance of wireless communication, which may include various digital and / or analog radio frequency (RF) components, a processor configured to execute program instructions stored in memory, programmable hardware elements such as field-programmable gate arrays (FPGAs), and / or any of various other components. Wireless devices 102 and / or 104 may use any or all of these components to perform any of the method embodiments described herein, or any part thereof.

[0059] Each of wireless devices 102 and 104 may include one or more antennas for communicating using one or more wireless communication protocols. In some cases, one or more portions of the receive chain and / or transmit chain may be shared among multiple wireless communication standards; for example, the device may be configured to communicate using either Bluetooth or Wi-Fi with partially or fully shared wireless communication circuitry (e.g., using shared antennas and / or shared radio components). The shared communication circuitry may include a single antenna, or may include multiple antennas for performing wireless communication (e.g., for MIMO). Alternatively, the device may include independent transmit and / or receive chains (e.g., including independent antennas and other radio components) for each wireless communication protocol configured to communicate using it. As another possibility, the device may include one or more radios or radio components shared among multiple wireless communication protocols, as well as one or more radios or radio components specifically used by a single wireless communication protocol. For example, the device may include shared radio components for communicating using one or more of LTE and / or 5G NR, and separate radio components for communicating using Wi-Fi, UWB, and / or Bluetooth. Other configurations are also possible.

[0060] As mentioned above, it can be combined with Figure 1 The aspects of this disclosure are implemented using a wireless communication system. For example, a wireless device (e.g., either wireless device 102 or 104) may be configured to perform methods for: robust discovery of a new AP in an Access Point (AP) MLD, robust link addition to an AP MLD, AP beacon mode when an AP is added to or removed from an AP MLD, robust BSS transition management (BTM) signaling for guiding non-AP MLDs to the optimal AP MLD and the most suitable AP, and privacy improvements for associated non-AP MLDs.

[0061] Figure 2An exemplary wireless device 100 (e.g., corresponding to wireless devices 102 and / or 104) is illustrated and can be configured for use in conjunction with various aspects of this disclosure. Device 100 can be any of a variety of types of devices and can be configured to perform any of a variety of functionalities. Device 100 can be a substantially portable device or a substantially stationary device, and may include any of a variety of types of devices. Device 100 can be configured to perform one or more ranging wireless communication techniques or features, such as any techniques or features shown and / or described herein with respect to any or all of the accompanying drawings.

[0062] As shown, device 100 may include processing element 101. The processing element may include or be coupled to one or more memory elements. For example, device 100 may include one or more storage media (e.g., memory 105), which may include any of a variety of types of memory and be usable for any of a variety of functions. For example, memory 105 may be RAM used as system memory for processing element 101. Other types and functions are also possible.

[0063] Additionally, device 100 may include wireless communication circuitry 130. The wireless communication circuitry may include any of a variety of communication elements (e.g., antennas for wireless communication, analog and / or digital communication circuitry / controllers, etc.) and may enable the device to perform wireless communication using one or more wireless communication protocols.

[0064] It should be noted that in some cases, such as when processing element 101 is used, wireless communication circuitry 130 may include its own processing element (e.g., a baseband processor). For example, processing element 101 may be an "application processor" whose primary function may be to support application layer operations in device 100, while wireless communication circuitry 130 may be a "baseband processor" whose primary function may be to support baseband operations in device 100 (e.g., to facilitate wireless communication between device 100 and other devices). In other words, in some cases, device 100 may include multiple processing elements (e.g., it may be a multiprocessor device). Other configurations utilizing a multiprocessor architecture (e.g., alternatives to or other than the application processor / baseband processor configuration) are also possible.

[0065] Depending on the intended functionality of the device 100, the device 100 may additionally include any of a variety of other components (not shown) for implementing the device functionality, which may also include processing elements and / or memory elements (e.g., audio processing circuitry), one or more power supply elements (which may depend on battery power and / or external power), user interface elements (e.g., display, speaker, microphone, camera, keyboard, mouse, touch screen, etc.), and / or any of a variety of other components.

[0066] Components of device 100, such as processing element 101, memory 105, and wireless communication circuitry 130, may be operatively coupled via one or more interconnect interfaces, which may include any of a variety of types of interfaces, and possibly combinations of multiple types of interfaces. As an example, a USB High Speed ​​Chip-to-Chip (HSIC) interface may be provided for chip-to-chip communication between processing elements. Alternatively (and / or in addition), any of a Universal Asynchronous Receiver / Transmitter (UART) interface, Serial Peripheral Interface (SPI), Internal Integrated Circuit (I2C), System Management Bus (SMBus), and / or various other communication interfaces may be used for communication between various device components. Other types of interfaces (e.g., on-chip interfaces for communication within processing element 101, peripheral interfaces for communication with peripheral components inside or outside device 100, etc.) may also be provided as part of device 100.

[0067] Figure 3 —WLAN system Figure 3 An example WLAN system according to some implementations is illustrated. As shown, this exemplary WLAN system includes multiple wireless client sites or devices (e.g., STAs or User Equipment (UEs)) 106 configured to communicate with an access point (AP) 112 via a wireless communication channel 142. AP 112 may be a Wi-Fi access point. AP 112 may communicate with one or more other electronic devices (not shown) and / or another network 152 (such as the Internet) via a wired communication channel and / or a wireless communication channel 150. Additional electronic devices (such as remote device 154) may communicate with components of the WLAN system via network 152. For example, remote device 154 may be another wireless client site, a server associated with an application running on one of the STAs 106, etc. The WLAN system may be configured to operate according to any of a variety of communication standards, such as various IEEE 802.11 standards. In some implementations, at least one wireless device 106 is configured to communicate directly with one or more adjacent mobile devices without using access point 112.

[0068] Furthermore, in some implementations, wireless device 106 (which may be an exemplary specific implementation of device 100) may be configured to perform methods for: robust discovery of new APs in an access point (AP) MLD, robust link addition to an AP MLD, AP beacon mode when an AP is added to or removed from an AP MLD, robust BSS transition management (BTM) signaling for guiding non-AP MLDs to the best AP MLD and the most suitable AP, and privacy improvements for associated non-AP MLDs.

[0069] Figure 4 —Access Point Diagram Figure 4 An exemplary block diagram of access point (AP) 112 is shown, which can be Figure 4 This is one possible exemplary embodiment of the device 100 shown. It should be noted that... Figure 4 The block diagram of the AP is only one example of a possible system. As shown, AP 112 may include one or more processors 204 capable of executing program instructions for AP 112. Processor 204 may also be (directly or indirectly) coupled to memory management unit (MMU) 240 or other circuitry or devices, which may be configured to receive addresses from processor 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0070] AP 112 may include at least one network port 270. Network port 270 may be configured to couple to a wired network and provide internet access to multiple devices, such as mobile device 106. For example, network port 270 (and / or additional network ports) may be configured to couple to a local network, such as a home network or a business network. For example, port 270 may be an Ethernet port. The local network provides connectivity to additional networks, such as the internet.

[0071] AP 112 may include at least one antenna 234, which may be configured to operate as a wireless transceiver and may be further configured to communicate with mobile device 106 via wireless communication circuitry 230. Antenna 234 communicates with wireless communication circuitry 230 via communication link 232. Communication link 232 may include one or more receive links, one or more transmit links, or both. Wireless communication circuitry 230 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). For example, in small cell scenarios where the AP coexists with a base station, or in other situations where it may be desirable for AP 112 to communicate via various different wireless communication technologies, wireless communication circuitry 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including but not limited to LTE, LTE-A Advanced, 5G NR, etc.

[0072] Furthermore, in some implementations, as further described below, AP 112 may be configured to perform methods for: robust discovery of new APs in an Access Point (AP) MLD, robust link addition to an AP MLD, AP beacon mode when an AP is added to or removed from an AP MLD, robust BSS transition management (BTM) signaling for directing non-AP MLDs to the best AP MLD and the most suitable AP, and privacy improvements for associated non-AP MLDs.

[0073] Figure 5 —Client Site Diagram Figure 5 A simplified block diagram of a client site 106 is shown, which can be... Figure 4 This is one possible exemplary embodiment of the device 100 shown. According to various embodiments, the client site 106 may be a user equipment (UE) device, a mobile device or mobile station and / or a wireless device or wireless site. As shown, the client site 106 may include a system-on-a-chip (SOC) 300, which may include portions for various purposes. The SOC 300 may be coupled to various other circuitry of the client site 106. For example, the client site 106 may include various types of memory (e.g., including NAND flash memory 310), connector interfaces (I / F) (and / or docking stations) 320 (e.g., for coupling to computer systems, docking stations, charging stations, etc.), a display 360, cellular communication circuitry (e.g., cellular radio components) 330 (such as for 5G NR, LTE, etc.), and short-to-medium range wireless communication circuitry (e.g., Bluetooth). ™ and WLAN radio components) 329 (e.g., Bluetooth) ™(And WLAN circuitry). Client site 106 may further include one or more smart cards 315 incorporating SIM (Subscriber Identity Module) functionality, such as one or more UICCs (One or more Universal Integrated Circuit Cards). Cellular communication circuitry 330 may be coupled to one or more antennas, such as antennas 335 and 336 as shown. Medium-range wireless communication circuitry 329 may also be coupled to one or more antennas, such as antennas 337 and 338 as shown. Alternatively, in addition to being coupled to antennas 337 and 338, or as an alternative, medium-range wireless communication circuitry 329 may be coupled to antennas 335 and 336. Medium-range wireless communication circuitry 329 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams in a configuration such as Multiple-Input Multiple-Output (MIMO). Some or all of the components of medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may be used for ranging communication, for example, ranging communication using WLAN communication, Bluetooth communication, and / or cellular communication.

[0074] As shown, the SOC 300 may include a processor 302 and a display circuit 304. The processor executes program instructions for a client site 106, and the display circuit performs graphics processing and provides display signals to a display 360. The SOC 300 may also include motion sensing circuitry 370, which may detect motion of the client site 106, for example, using a gyroscope, accelerometer, and / or any of various other motion sensing components. One or more processors 302 may also be coupled to a memory management unit (MMU) 340 and / or other circuitry or devices (such as display circuitry 304, cellular communication circuitry 330, short-range wireless communication circuitry 329, connector interface (I / F) 320, and / or display 360). The memory management unit (MMU) may be configured to receive addresses from one or more processors 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some implementations, the MMU 340 may be included as part of the processor 302.

[0075] As noted above, client station 106 can be configured to directly communicate wirelessly with one or more adjacent client stations. Client station 106 can be configured to communicate according to a WLAN RAT to enable communication in applications such as... Figure 3 Communication in the WLAN network shown or as Figure 1 The distance measurement shown.

[0076] As described herein, client site 106 may include hardware and software components for implementing the features described herein. For example, processor 302 of client site 106 may be configured to implement some or all of the features described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (and / or in addition), processor 302 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit). Alternatively (and / or in addition), in conjunction with one or more of other components 300, 304, 306, 310, 315, 320, 329, 330, 335, 336, 337, 338, 340, 350, 360, 370, processor 302 of UE 106 may be configured to implement some or all of the features described herein.

[0077] In addition, as described herein, processor 302 may include one or more processing elements. Therefore, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 204.

[0078] Furthermore, as described herein, both the cellular communication circuit 330 and the short-range wireless communication circuit 329 may include one or more processing elements. In other words, one or more processing elements may be included in either the cellular communication circuit 330 or the short-range wireless communication circuit 329. Therefore, each of the cellular communication circuit 330 and the short-range wireless communication circuit 329 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 330 and the short-range wireless communication circuit 329, respectively. In addition, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 330 and the short-range wireless communication circuit 329.

[0079] Figure 6 —Wireless Node Diagram Figure 6 A possible block diagram of wireless node 107 is shown, which can be Figure 6One possible exemplary implementation of the device 100 shown is illustrated. As shown, the wireless node 107 may include a system-on-a-chip (SOC) 400, which may include components for various purposes. For example, as shown, the SOC 400 may include one or more processors 402 capable of executing program instructions for the wireless node 107 and display circuitry 404 capable of performing graphics processing and providing display signals to a display 460. The SOC 400 may also include motion sensing circuitry 470, which may detect motion of the wireless node 107, for example, using a gyroscope, accelerometer, and / or any of various other motion sensing components. The processor 402 may also be coupled to a memory management unit (MMU) 440, which may be configured to receive addresses from the processor 402 and translate these addresses into locations in memory (e.g., memory 406, read-only memory (ROM) 450, flash memory 410). The MMU 440 may be configured to perform memory protection and page table translation or setup. In some implementations, the MMU 440 may be included as part of the processor 402.

[0080] As shown in the figure, the SOC 400 can be coupled to various other circuits of the wireless node 107. For example, the wireless node 107 may include various types of memory (e.g., including NAND flash memory 410), connector interface 420 (e.g., for coupling to computer systems, docking stations, charging stations, etc.), display 460, and wireless communication circuitry 430 (e.g., for 5G NR, LTE, LTE-A, Bluetooth, Wi-Fi, NFC, etc.).

[0081] Wireless node 107 may include at least one antenna, and in some embodiments, may include multiple antennas 435 and 436 for performing wireless communication with a base station and / or other devices. For example, wireless node 107 may use antennas 435 and 436 to perform wireless communication. As noted above, wireless node 107 may be configured in some embodiments to perform wireless communication using a variety of wireless communication standards or radio access technologies (RATs).

[0082] The wireless communication circuit 430 may include a Wi-Fi logic component 432, a cellular modem 434, and a Bluetooth logic component 439. The Wi-Fi logic component 432 enables the wireless node 107 to perform Wi-Fi communication over a network such as 802.11. The Bluetooth logic component 439 enables the wireless node 107 to perform Bluetooth communication. The cellular modem 434 may be able to perform cellular communication according to one or more cellular communication technologies. Some or all components of the wireless communication circuit 430 may be used for ranging communication, for example, utilizing WLAN communication, Bluetooth communication, and / or cellular communication.

[0083] As described herein, wireless node 107 may include hardware and software components for implementing embodiments of the present disclosure. For example, one or more components of wireless communication circuitry 430 (e.g., Wi-Fi logic component 432) of wireless node 107 may be configured to implement some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium), a processor configured as an FPGA (Field Programmable Gate Array), and / or using dedicated hardware components that may include ASICs (Application-Specific Integrated Circuits).

[0084] Figures 7 to 8 —Multi-link device (MLD) operation One or more IEEE 802.11 versions, such as IEEE 802.11bi, may include multi-link device (MLD) capabilities. In current implementations, an access point (AP) MLD node can manage its associated APs. Therefore, an AP MLD node can modify, add, and / or remove associated APs. The AP MLD may do this for various reasons, such as to increase capacity, manage Basic Service Set (BSS) interference, and / or coverage, including by switching one or more APs to operate on less congested channels, and / or by directing associated non-AP MLD nodes to operate on higher-performing APs and / or AP MLD nodes.

[0085] Figure 7 An AP MLD 112 according to some implementation schemes is illustrated. This AP MLD can operate any number of auxiliary APs, such as APs 712a, 712b, 712c, and 712d in the illustrated example. Auxiliary APs can operate on any frequency band in a variety of frequency bands. Auxiliary APs can operate on different frequency ranges (e.g., channels) within the same frequency band or on different frequency bands.

[0086] AP MLDs can provide auxiliary APs from a single physical device (e.g., a single shared enclosure, and potentially using one or more antennas from the same antenna). In some implementations, AP MLDs can provide APs from multiple different devices (e.g., a first device can provide one or more APs, a second device can provide different one or more APs, etc.). In some implementations, the various auxiliary APs can be spatially separated (e.g., using beams in different directions, using different antennas with a shared enclosure (e.g., antennas from the same physical device) and / or different antennas from different devices, etc.).

[0087] In some implementations, spatially separated auxiliary APs can operate on the same (or overlapping) channels.

[0088] Figure 8An example is shown of an AP MLD 112 communicating with a non-AP MLD 106 according to some implementation schemes.

[0089] As shown in the figure, AP MLD 112 can operate three auxiliary APs. In the illustrated example, AP 812a can operate in the 2.4 GHz band, AP 812b can operate in the 5 GHz band, and AP 812c can operate in the 6 GHz band. It should be understood that any number of auxiliary APs can be used in any combination of frequency bands. For example, AP MLD can operate multiple auxiliary APs in one frequency band and / or may not operate any auxiliary APs in any frequency band. Auxiliary APs may include components that handle one or more layers (e.g., Media Access Control (MAC) and / or Physical (PHY) layers, and various other possibilities). Auxiliary APs may use different Basic Service Sets (BSS) and / or different BSS identifiers (BSSIDs), such as BSSID 1 through BSSID 3.

[0090] As shown in the figure, the non-AP MLD 106 can operate, for example, three auxiliary STAs corresponding to three auxiliary APs. In the illustrated example, STA 806a can operate in the 2.4 GHz band, STA 806b can operate in the 5 GHz band, and STA 806c can operate in the 6 GHz band. STAs can communicate with their corresponding APs. It should be understood that any number of auxiliary STAs can be used in any combination of frequency bands. For example, a non-AP MLD can operate multiple auxiliary STAs in one frequency band and / or may not operate any auxiliary STAs in any frequency band. The non-AP MLD can operate STAs of some or all of the APs corresponding to the AP MLD, or STAs of APs not corresponding to the AP MLD. Auxiliary STAs can include various layers, such as the PHY and / or MAC layers, and various other possibilities. Auxiliary STAs can use different addresses, such as addresses 1 through 3.

[0091] A non-AP MLD can provide auxiliary STAs from a single physical device (e.g., a single shared enclosure, and potentially using one or more antennas from the same antenna). In some embodiments, a non-AP MLD can provide STAs from multiple different devices (e.g., a first device can provide one or more STAs, a second device can provide different one or more STAs, etc.). In some embodiments, the various auxiliary STAs can be spatially separated (e.g., using beams in different directions, using different antennas with a shared enclosure (e.g., antennas from the same physical device) and / or different antennas from different devices, etc.).

[0092] In some implementations, various auxiliary STAs and APs can communicate concurrently / simultaneously. For example, STA 806a may exchange uplink and / or downlink data with AP 812a on a first link, while STA 806b may exchange uplink and / or downlink data with AP 812b on a second link, and so on. It should be understood that such concurrent communication may include (e.g., different) data being exchanged at the same time, at least partially overlapping times, and / or at different times on different links. For example, data between AP MLDs and non-AP MLDs may be routed via a first available link and / or a link selected based on other criteria (e.g., minimum energy usage, etc.). For example, a first packet or portion of data may be transmitted via the first link, and concurrently, a second packet or portion of data may be transmitted via the second link.

[0093] In some implementations, the AP MLD and non-AP MLD may include corresponding ML entities. The ML entity provides upper-layer MAC functionality for controlling individual APs and / or STAs, and can control service delivery over available links, such as between various APs and STAs. The corresponding MLD (e.g., AP and non-AP) may have only one corresponding MAC Service Access Point (SAP) interface. The ML entity manages this interface. The ML entity manages transmit buffers (e.g., bookkeeping and link selection in the sender) and data reordering buffers in the receiver (e.g., combinations of data transmitted on different links).

[0094] AP MLD 112 and non-AP MLD 106 can exchange information about their respective operations, operating parameters and / or capabilities.

[0095] Non-AP MLDs may have various capabilities for operating STAs in a specific frequency band. These capabilities may differ for different frequency bands. For example, the capabilities within a frequency band can describe the maximum (e.g., fastest, most flexible, most powerful, highest throughput, etc.) parameter values ​​that the STA of a non-AP MLD can use. Operation or operating parameters can describe parameter values ​​currently in use or planned for use in the future.

[0096] For example, this parameter may include the applicable PHY version and its parameters. This parameter may describe the available supported services and transmission formats. This parameter may also describe available resources, bandwidth, and the number of spatial streams. This parameter may describe power-saving support parameters that enable low-power transmission. For example, the AP may support Target Wake Time (TWT) power savings.

[0097] In some implementations, links may be located too close together (e.g., spatially and / or in frequency) so that non-AP STAs may not be able to operate these links independently (e.g., due to device limitations and / or for resource or performance management). The AP may support STAs that cannot transmit and receive simultaneously on link pairs (e.g., non-AP MLDs).

[0098] In some implementations, a non-AP MLD can operate a STA that communicates with multiple AP MLDs. For example, a first STA can communicate with a first AP MLD, and a second STA can communicate with a second AP MLD. Similarly, an AP MLD can communicate with multiple STAs. For example, a subsidiary AP can communicate with multiple STAs.

[0099] In the illustrated example, the number of APs provided by a non-AP MLD operation equals the number of STAs provided by an AP MLD operation. However, different numbers are possible. For example, an AP MLD operation may provide more APs than a non-AP MLD operation, or vice versa. The number of APs and / or the number of STAs may change over time.

[0100] According to some implementation schemes, it may be beneficial for a Client Privacy Enhancement (CPE) site (STA) (or client) to change or adjust certain parameters used to perform communication with the Access Point (AP). For example, an eavesdropper could attempt to intercept, extract, or listen to communication between certain CPE STAs and the AP. Therefore, clients could attempt to use various techniques involving address changes or adjustments to related parameters to perform more secure communication between the CPE STA and the AP.

[0101] For example, when re-associating from one CPE AP to another, it may be beneficial for the CPE client to change its own over-the-air (OTA) Media Access Control (MAC) address used to communicate with the AP. Additionally or alternatively, it may be beneficial for the CPE client to initiate a change of its own OTA MAC address used with the CPE AP in an associated state (e.g., STA state 4) without any connection loss. In some implementations, it may be beneficial for the CPE client to simultaneously initiate a change of the OTA MAC addresses of all associated CPE clients in the Basic Service Set (BSS) (e.g., those in associated STA state 4) without any connection loss. Furthermore, according to some implementations, it may be beneficial for the CPE client and CPE AP to change the transmitted sequence number (SN), packet number (PN), and flow identifier (TID) to new, irrelevant values ​​on the downlink and uplink, and new values ​​in associated STA state 4, without any connection loss. Furthermore, it may be further beneficial for the CPE client and CPE AP to change the CPE client's association identifier (AID) to a new, irrelevant value in associated STA state 4 without any connection loss.

[0102] Mode management for multi-link operations In recent Wi-Fi versions, mode changes (e.g., enabling, disabling, or modification / updating) may have been performed on a per-link basis due to the lack of support for certain cross-link mode changes. For example, if a non-AP MLD wants to enter power-saving (PS) mode on all links in a link, both the non-AP MLD and AP MLD may have previously been required to perform separate frame exchanges (e.g., mode changes) on each enabled link. However, such per-link frame exchanges for mode changes (e.g., separate frame exchanges) can be inefficient and may result in long delays for the non-AP MLD's STA to enter PS mode (in which they can transition to a sleep (e.g., nap) state). Therefore, improved methods for mode management are desired to increase efficiency and provide better interoperability and flexibility between non-AP MLDs and AP MLDs.

[0103] Figure 9 —Dynamic Power Saving (DPS) mode change Figure 9An example communication exchange between an AP and a STA attempting to switch to and from DPS mode according to some implementations is illustrated. According to some implementations, in some instances, DPS mode can be characterized as a power-saving feature or mode in which a super STA (e.g., such as a high reliability (UHR) STA as an example) may remain in a lower capability mode (LCM) until it receives an initial control frame (ICF). Upon receiving the ICF, the STA may switch to a higher capability mode (HCM) and optionally remain in that mode for the remainder of the transmission opportunity (TXOP).

[0104] For example and such Figure 9 As shown, according to some implementations, a non-AP MLD (e.g., STA 1) may transmit management frames on the link to enable DPS mode. According to some implementations, an STA (e.g., a non-AP MLD) may potentially operate in a lower capability (LC) mode on the link and, upon receiving an ICF in LC mode, transition to a higher capability (HC) mode for the remaining TXOP duration.

[0105] In some implementations, the ICF can be transmitted at a rate of 6 Mbps, 12 Mbps, or 24 Mbps (other data transmission rates are also possible) in non-high-throughput (non-HT) physical layer protocol data units (PPDUs). Additionally, if the STA has requested the mode change during activation, the ICF may include an Intermediate Frame Check Sequence (FCS). Furthermore, after a timeout interval, the STA may transition back to LC mode after a DPS transition delay. According to some implementations, the timeout interval may be characterized by a time associated with the sum of parameters, including but not limited to the SIFS (e.g., aSIFSTime) parameter, the slot duration (e.g., aSlotTime) parameter, and / or the physical layer receive delay (e.g., aRxPHYStartDelay) parameter.

[0106] In some implementations, if the UHR STA (e.g., a UHR non-AP STA or a UHR mobile AP) operates according to a DPS mode associated with the UHR STA's transition from LCM to HCM (e.g., upon receiving an ICF), then, according to some implementations, the associated peer STA that supports sending the intermediate FCS may optionally include the intermediate FCS in its ICF sent to the UHR STA (if the STA requires it). Alternatively, according to some implementations, the intermediate FCS may not be required if the UHR STA does not need to fill in the gaps.

[0107] In some implementations, a parameter update mechanism based on management-level signaling can be used to allow non-AP STAs to transition into and / or leave restricted operating or capability modes. For example, according to some implementations, an STA in a restricted operating or capability mode can change one or more transmit (TX) or receive (RX) parameters, including but not limited to maximum PPDU duration, maximum modulation and decoding scheme (MCS), low-density parity check (LDPC), high-throughput (HT) immediate block acknowledgment (ACK), deactivated subchannel bitmaps, and various other parameters. Therefore, defining management-level signaling for different operating modes of UHR STAs may be beneficial.

[0108] Figure 10 —An enhanced approach to pattern management for non-AP MLDs Figure 10 This is a communication flowchart illustrating various aspects of an enhanced approach for pattern management of non-AP MLDs, according to some implementation schemes. Such approaches can help provide a more efficient and flexible pattern management process (compared to traditional methods) and subsequently reduce power consumption between AP MLDs and non-AP MLDs.

[0109] For example, Figure 10 An example of an enhanced approach to pattern management performed by a non-AP MLD, based on some implementation schemes, is illustrated. Figure 10 Aspects of the method may be implemented by a non-AP MLD communicating with the AP MLD. The AP MLD and / or the non-AP MLD may be illustrated and described as in the various figures herein, or more generally, may be illustrated and described as needed in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the figures above. For example, the processor (and / or other hardware) of such a device may be configured to cause the device to perform any combination of the illustrated method elements and / or other method elements. For example, one or more processors (or processing elements) (e.g., processors 101, 204, 302, 402, 432, 434, 439, baseband processors, processors associated with communication circuits such as 130, 230, 232, 329, 330, 430, etc., and various possibilities) may enable wireless devices, STAs, UEs, non-APs and / or APs and / or other devices to perform such method elements.

[0110] It should be noted that, although described in a manner consistent with the communication technologies and / or features associated with IEEE and / or 802.11 (e.g., 802.11be) specification documents. Figure 10 The method includes at least some elements, but such description is not intended to limit this disclosure, and Figure 10Various aspects of the method can be used in any suitable wireless communication system as needed. Similarly, although described in a manner relevant to non-APs (e.g., STAs) that can be MLDs or UHR MLDs. Figure 10 The methods and elements thereof, but such description is not intended to limit this disclosure, and Figure 10 Various aspects of the method can be used by non-APs who are not MLDs or UHR MLDs, as needed. Additionally, although... Figure 10 Some aspects of the method can be implemented by non-AP MLDs, but with Figure 10 Some corresponding steps related to the method can be performed by the AP MLD that communicates with the non-AP MLD.

[0111] Among other devices, the illustrated method can also be used in conjunction with any of the systems, methods, or devices shown in the accompanying drawings (e.g., Figures 11 to 17). In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method can operate as follows.

[0112] At 1002, according to some embodiments, a non-AP STA may send a frame to the AP indicating the enabling, disabling, or modification of one or more operating modes. For example, the method may include sending a frame to the AP including at least one indicator indicating the enabling, disabling, or modification of one or more operating modes associated with one or more radio links, respectively. According to some embodiments, the frame may be a link reconfiguration request frame.

[0113] In some implementations, at least one indicator may be included in the mode change element of the link reconfiguration request frame. Furthermore, according to some implementations, at least one indicator may be included in the mode control field of the mode change element. Additionally, according to other implementations, the mode change element may include information including at least one of the following: one or more sub-element identifiers (IDs) corresponding to one or more operating modes; a mode control field indicating the enabling, disabling, or modification of one or more operating modes; or operating parameters for one or more operating modes.

[0114] In some implementations, at least one indicator may include one or more sub-element identifiers (IDs) corresponding to one or more operating modes. Additionally, one or more operating modes may include at least one of the following: Dynamic Unavailability Operation (DUO) mode; Dynamic Power Saving (DPS) mode; Non-Master Channel Access (NPCA) mode; Dynamic Subband Operation (DSO) mode; Coordinated Beamforming (Co-BF) mode; Coordinated Space Rejection (Co-SR) mode; Low Latency Indication (LLI) mode; Dynamic Bandwidth Extension (DBE) mode; or Limited Operation Mode (LOM).

[0115] At 1004, according to some implementations, a non-AP STA can receive a response from the AP. In some implementations, the response may include an acknowledgment (ACK) frame. Additionally or alternatively, the response may include an initial control frame (ICF).

[0116] At 1006, according to some implementation schemes, a non-AP STA may enable, disable, or modify one or more operating modes. For example, a non-AP STA may enable, disable, or modify one or more operating modes associated with one or more radio links, respectively, based at least in part on at least one indicator and the receipt of a response.

[0117] According to some implementations, the method may further include: using a per-site (per-STA) profile sub-element to add or delete at least one of one or more wireless links, wherein the at least one wireless link operates according to at least one of one or more operating modes.

[0118] Figures 11A to 11B — Enable mode using link reconfiguration request frames Figures 11A to 11B Example fields and element formats available for pattern-enabled frames according to some implementation schemes are illustrated. For example, Figure 11A An example format for the action field of a Link Reconfiguration Request (LRR) frame is shown, and Figure 11B An example format for reconfiguring a multi-link (ML) element is shown.

[0119] Figure 11A An example LRR frame action field format is illustrated, which may include sequences 1 through 5 corresponding to different meanings. For example, according to some implementations, sequence 1 may be associated with a category, sequence 2 may be associated with a protected Extremely High Throughput (EHT) action, sequence 3 may be associated with a session token, sequence 4 may be associated with a reconfiguration ML element, and sequence 5 may be associated with an OCI element.

[0120] Figure 11BAn example reconfiguration of the ML element format according to some implementations is illustrated, which includes fields such as: element ID, length, element ID extension (each of which is 1 octet in size); ML control of 2 octets; and public information (e.g., information) field and link information field of variable octet size.

[0121] In some implementations, it may be advantageous to use link reconfiguration request or notification frames to enable or disable operating modes (e.g., DPS). According to some implementations, these request or notification frames can be used during the roaming preparation and roaming execution phases of seamless roaming. Therefore, there may be specific advantages to using these frames for mode enabling or disabling. For example, according to some implementations, if a non-AP MLD intends to add a link and enable 802.11 features (e.g., DPS in 802.11bn), the non-AP MLD can use at least one of these frames to concurrently support these features. Similarly, if a non-AP intends to delete a link and disable existing features on that link, the non-AP MLD can use at least one of these frames to concurrently support these features. In some instances, link reconfiguration notification frames may be transmitted by the AP MLD, as described in previous specifications (e.g., 802.11be).

[0122] Figure 12 —Link reconfiguration request frame for mode change Figure 12 Example frame formats for link reconfiguration request frames for mode change, according to some implementations, are illustrated. For example, action frames (e.g., LR request frames) may be characterized as category protected EHT and can be used to enable or disable DPS. Additionally, and in previous 802.11 versions (e.g., 802.11be), according to some implementations, this LR request frame may have been used by non-AP MLDs to request the addition or removal of links in their ML settings.

[0123] For example and such Figure 12 As shown, according to some implementations, the LR request frame may include a 3-bit type field, a 1-bit reserved field, and a 12-bit presence bitmap. Furthermore, the 12-bit presence bitmap may include a 1-bit MLD MAC address presence field, a 1-bit EML capability presence field, and a 1-bit MLD capability and operation presence field. In some implementations, the type subfield in the multi-link control field may indicate the reconfiguration of multi-link elements.

[0124] Additionally and as Figure 12As shown in the bolded portion, according to some implementations, a 1-bit link capability and operational presence field, as well as an 8-bit reserved field, can also be included in the 12-bit presence bitmap. In other words, and to facilitate mode enabling or disabling, according to some implementations, the 1-bit link capability and operational presence subfield can be added to the presence bitmap subfield of the ML control field. Furthermore, the 8-bit reserved field can also... Figure 12 The ML control field format is included.

[0125] In other words, the 1-bit link capability and operation subfield can be included in the action field as a single reconfiguration ML element. Therefore, if a non-AP MLD intends to enable a mode (e.g., DPS) on an established link, this field can be set to 1. Additionally, and according to some implementations, if the value is set to 1, the public information field may not be present in the link reconfiguration request frame.

[0126] Figures 13A to 13C — New Link Information Field Sub-element Figures 13A to 13C Example aspects of reconfiguring the link information field of an ML element according to some implementation schemes are illustrated. Figure 13A The different sub-elements of the Link Information field are illustrated, along with their corresponding identifiers, names, and whether they are extensible (e.g., capable of being extended). For example, sub-element ID 0 is associated with a per-STA profile and is extensible; IDs 2 to 220, 222 to 253, and 255 may be reserved; ID 221 may be vendor-specific and have vendor-defined extensibility; and ID 254 may be a non-extensible fragment. In some implementations, the Link Information field may include sub-element ID 1 associated with an extensible mode enable profile, which can be used in either enable or disable mode.

[0127] like Figure 13B As shown, according to some implementations, the sub-element ID=1 (e.g., mode enable profile) can be characterized by a format including a sub-element ID field of 1 octet, a length field, an STA control field, and a variable-size STA information field. Furthermore, as... Figure 13C As shown, the STA control field may include a 4-bit link ID and a mode type subfield, a 1-bit operation parameter presence subfield, and a 7-bit reserved subfield. According to some implementations, the STA control field may indicate the mode type that the STA intends to enable or disable; the link ID subfield may indicate the link whose characteristics are indicated for enabling or disabling; the mode type subfield may indicate the mode type that the STA intends to enable or disable; the operation parameter presence subfield may indicate the parameters required to enable the mode type signaled in the mode type subfield; and the STA information field may indicate the operation parameters for enabling the mode.

[0128] Figures 14A to 14B — Enable the STA information field in the profile element for each STA. Figures 14A to 14B Example aspects of enabling profile sub-elements per STA in the STA information field according to some implementation schemes are illustrated. For example, Figure 14A This example illustrates a schema type subfield for STA control fields according to some implementation schemes. According to some implementation schemes, Figure 14A The mode type subfield may include values ​​associated with different mode types, including value 0 associated with Dynamic Unavailable Operation (DUO) mode, value 1 associated with DPS mode, value 2 associated with Non-Main Channel Access (NPCA) mode, value 3 associated with Dynamic Subband Operation (DSO) mode, and reserved values ​​4 to 15.

[0129] Additionally, the STA Information field may include a 1-octet STA Information Length subfield, which indicates the number of octets in the STA Information field. According to some embodiments, this subfield is included if the Variable Octet Operation Parameter Presence subfield is set to a value of 1 in the STA Control field. Furthermore, according to some embodiments, the Operation Parameter subfield may indicate the parameters required when enabling a mode corresponding to the value indicated in the Mode Type subfield of the STA Control field.

[0130] Figures 15A to 15C —Subfield of operation parameters for STA information field Figures 15A to 15C Example aspects of operational parameter subfields for STA information fields of different schema types are illustrated according to some implementation schemes. For example, Figure 15A Example operation parameter subfield formats are illustrated when the mode type subfield value is 1 according to some implementation schemes (e.g., DPS mode). Additionally, if the operation parameter presence subfield in the STA control field is set to 1, the operation parameter subfield in the STA information field may include a 1-bit DPS parameter update control subfield, which indicates whether an updated DPS fill delay value and DPS transition delay value exist relative to the transmission value in the last transmitted UHR mode enable notification frame. Furthermore, if this subfield is set to 1, the DPS fill delay subfield and DPS transition delay subfield may... Figure 15A The illustrated subfield format exists. Furthermore, according to some implementations, if this subfield is set to 1 and the value in the DPS fill delay subfield is non-zero, this may indicate that a STA with DPS mode enabled requires an intermediate FCS (I-FCS) in the ICF.

[0131] According to some implementations, the operation parameter subfield format may also include a 1-bit required ICF subfield, which indicates whether the STA requires ICF and ICR exchange before any frame exchange initiated with the DPS STA. For example, if ICF and / or ICR are required only for frame exchanges using HCM parameters, the required ICF subfield can be set to 0. Alternatively, if ICF and / or ICR are required for all frame exchanges, the required ICF subfield can be set to 1. In some instances, the 1-bit required ICF subfield can be used to indicate that the DPS STA is transitioning from Low Capability Mode (LCM) to High Capability Mode (HCM).

[0132] In some implementations, the DPS fill delay subfield may indicate an updated value of the DPS fill delay, which is in the range of 0 to 64 (with a resolution / increment of 4 microseconds (μs)). Additionally, the DPS transition delay subfield may indicate an updated value of the DPS transition delay, which is in the range of 0 to 64 (with a resolution / increment of 4 microseconds (μs)).

[0133] According to some implementations, when the mode type subfield value in the STA control field is set to a value of 0 (e.g., indicating DUO mode), the operation parameter presence subfield can be set to 0, and feedback information can be provided as an ICR frame in the multi-STA block acknowledgment (BA). Additionally, according to some implementations, when the mode type subfield value is set to a value of 0 (e.g., indicating DUO mode), the STA information field may not exist in the mode enable profile sub-element.

[0134] Figure 15B Example operation parameter subfield formats are illustrated when the mode type subfield value is 2 (e.g., NPCA mode) according to some implementations. For example, according to some implementations, when the mode type subfield value is set to value 2 (NPCA mode) in the STA control field, the operation parameter presence subfield can be set to value 1, and the STA information field can contain an NPCA switchover delay subfield and an NPCA switchback delay subfield with corresponding bit values.

[0135] Figure 15C Example operation parameter subfield formats are illustrated when the mode type subfield value is 3 (e.g., DSO mode) according to some implementations. For example, according to some implementations, when the mode type subfield value is set to value 3 (DSO mode) in the STA control field, the operation parameter presence subfield can be set to value 1, and the STA information field can include DSO handover delay, DSO handback delay, and 80MHz DSO subband selection (if the basic service set (BSS) bandwidth (BW) is 320MHz) subfields with corresponding bit values.

[0136] Figures 16A to 16B —Link reconfiguration request frame format Figures 16A to 16B Example fields and formats of link reconfiguration request frames based on some implementation schemes are shown. For example, Figure 16A An example is given of a reconfiguration ML element for adding and deleting links, and the format of the per-STA profile sub-element included in the link information field of the reconfiguration ML element. For example... Figure 16A As shown, according to some implementation schemes, the reconfiguration ML element for adding and deleting links may include: a single octet-sized element ID field, a length field, and an element ID extension field; a 2-octet-sized ML control field; and variable octet-sized public information and link information fields. Furthermore, the ML control field may include subfields such as: MLD MAC address presence, EML capability presence, and MLD capability presence.

[0137] In some implementations, one or more perSTA profile sub-elements may be included in the link information field for use in one or more link reconfigurations. Figure 16A The format of each STA profile sub-element shown may include fields such as: sub-element ID, length, STA control, STA information, and STA profile. Additionally, according to some implementations, the STA control field may include sub-fields such as: link ID, full profile, and reconfiguration operation type = add link (value = 2).

[0138] Furthermore, and as Figure 16B As shown, according to some implementations, the reconfigured ML element for mode enabling or disabling may include: a single octet-sized element ID field, a length field, and an element ID extension field; a 2-octet-sized ML control field; and a variable octet-sized public information field. Furthermore, the ML control field may include subfields such as MLDMAC address presence, EML capability presence, and MLD capability presence, which can be set to a value of zero. Additionally, the ML control field may include link capability and operation presence fields set to a value of 1. In this case, the public information field may not exist in the reconfigured ML element (e.g., ...). Figure 16B (As shown). In other words, when the link capability and operation fields are equal to 1, the public information field does not exist in the reconfiguration ML element used for mode enabling or disabling.

[0139] In some implementations, one or more mode enable profile sub-elements may be included in the link information field for use with a single mode change or multiple mode changes. Figure 16BThe pattern enable profile sub-element format shown may include fields such as: sub-element ID, length, STA control, and STA information. Furthermore, according to some implementations, the STA control field may include sub-fields such as: link ID, mode type (e.g., DUO, DPS, NPCA, DSO, and other possible modes), and the STA information field may include operation parameter sub-fields.

[0140] Figures 17A to 17B —Link reconfiguration response frame format Figures 17A to 17B Example fields and formats for link reconfiguration response frames used for mode changes, based on some implementation schemes, are illustrated. For example, Figure 17A The format of the link reconfiguration response frame action field, including sequences 1 through 8 and their associated meanings, is illustrated. For example, according to some implementations, the first sequence may be associated with a category, the second with a protected EHT action, the third with a session token, the fourth with a count, the fifth with a reconfiguration status list, the sixth with optional group key data, the seventh with an optional OCI element, and the eighth with an optional basic ML element.

[0141] In some implementations, the link reconfiguration response frame may include a count indicating the number of reconfiguration status tuples (e.g., link ID information, status) in the reconfiguration status list. Additionally, according to some implementations, the link reconfiguration response frame may include a link ID information subfield to indicate the link identifier of the AP, which is used to add to or remove from existing ML settings in the corresponding link reconfiguration request frame. Furthermore, according to some implementations, the link reconfiguration response frame may include a status subfield indicating the status of the link reconfiguration operation for the link corresponding to the link ID information subfield.

[0142] It may also be beneficial to define the following new status codes: rejection status codes (e.g., subcarrier spacing (SCS) flow rejection with suggested quality of service (QoS) characteristic elements); denial status codes (e.g., traffic identifier to link mapping (TTLM) and / or emergency prepared communication service (EPCS)).

[0143] For example, Figure 17B Example status codes 143, 144, 145, and 146 are shown according to some implementation schemes. These status codes indicate the successful activation of DUO mode, DPS mode, NPCA mode, and DSO mode. In other words, Figure 17BThe new status codes for mode enable or disable are illustrated in the status subfield. Therefore, when a link reconfiguration response frame is used for mode change, the link ID information subfield indicates the link identifier for which the mode is intended to be enabled. Furthermore, according to some implementations, the value in this subfield may be the same as the value in the link reconfiguration request frame.

[0144] In some implementations, the response frame may need to include certain information and / or be sent based on certain parameters upon receiving a request for a mode change. For example, when a non-AP STA of the UHR intends to enable DPS mode by transmitting a request frame, it may be necessary to send a response frame after the AP is ready to serve the non-AP STA in DPS mode.

[0145] According to some implementations, the AP may send a link reconfiguration response frame with status code 144 in the status subfield of the reconfiguration status list field. Furthermore, the value in the count subfield and the number of reconfiguration status tuples may be equal to the number of mode enable profile sub-elements included in the link reconfiguration request frame. Additionally, in some instances, subfields related to group key data, OCI elements, and basic multilink elements may be absent.

[0146] In other implementations, DUO mode can be enabled by an associated DUO auxiliary AP after the AP is ready to serve a non-AP STA in DUO mode, by transmitting a request frame and receiving a response frame. In other words, the AP can accept requests to enable DUO mode on the STA side, as well as the enabling process.

[0147] For example, according to some implementations, the AP may send a link reconfiguration response frame with status code 143 in the status subfield of the reconfiguration status list field. Furthermore, the value in the count subfield and the number of reconfiguration status tuples may be equal to the number of mode enable profile sub-elements included in the link reconfiguration request frame. In some implementations, subfields related to group key data, OCI elements, and basic multilink elements may not be present.

[0148] Figure 18 —An enhanced approach to pattern management technology for AP MLD Figure 18 This is a communication flowchart illustrating various aspects of an enhanced approach to mode management technology for AP MLDs, according to some implementation schemes. Such technologies can help provide a more efficient and flexible mode management process (compared to traditional methods) and subsequently reduce power consumption between AP MLDs and non-AP MLDs.

[0149] For example, Figure 18 An example of an enhanced approach to pattern management performed by the AP MLD, based on some implementation schemes, is illustrated. Figure 18 Aspects of the method may be implemented by an AP MLD communicating with a non-AP MLD. This AP MLD and / or the non-AP MLD may be illustrated and described as in the various figures herein, or more generally, may be illustrated and described as needed in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the figures above. For example, the processor (and / or other hardware) of such a device may be configured to cause the device to perform any combination of the illustrated method elements and / or other method elements. For example, one or more processors (or processing elements) (e.g., processors 101, 204, 302, 402, 432, 434, 439, baseband processors, processors associated with communication circuits such as 130, 230, 232, 329, 330, 430, etc., and various possibilities) may cause a wireless device, STA, UE, non-AP and / or AP, or other device to perform such method elements.

[0150] It should be noted that, although described in a manner consistent with the communication technologies and / or features associated with IEEE and / or 802.11 (e.g., 802.11be) specification documents. Figure 18 The method includes at least some elements, but such description is not intended to limit this disclosure, and Figure 18 Various aspects of the method can be used in any suitable wireless communication system as needed. Similarly, although described in a manner relevant to non-AP systems that can be MLDs or UHR MLDs... Figure 18 The methods and elements thereof, but such description is not intended to limit this disclosure, and Figure 18 Various aspects of the method can be used by non-APs who are not MLDs or UHR MLDs, as needed. Additionally, although... Figure 18 Some aspects of the method can be implemented by AP MLD, but with Figure 18 Some corresponding steps related to the method can be performed by a non-AP MLD that communicates with the AP MLD.

[0151] In addition to other equipment, the methods shown may also be used in conjunction with the accompanying drawings (e.g., such as Figures 19 to 10). Figure 27 This method may be used in any of the systems, methods, or apparatuses shown in the figure. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0152] At 1802, according to some implementations, the AP may send frames to non-AP STAs indicating the enabling, disabling, or modification of one or more operating modes. For example, the AP may send frames to non-AP STAs including at least one indicator indicating the enabling, disabling, or modification of one or more operating modes associated with one or more radio links, respectively.

[0153] In some embodiments, the at least one indicator may be included in an ordered bitmap to indicate at least one of the one or more operating modes to be enabled, disabled, or modified. Additionally or alternatively, the at least one indicator may also indicate the presence of operating parameters for at least one of the one or more operating modes.

[0154] According to some embodiments, the at least one indicator may be included in a reconfiguration multi-link (ML) element. Furthermore, the at least one indicator may be included in a mode enable profile sub-element corresponding to a sub-field of the ML control field of the reconfiguration ML element. Additionally or alternatively, the at least one indicator may be included in at least one of the STA information fields in a per-station (STA) enable profile sub-element of the reconfiguration ML element. In some embodiments, the reconfiguration ML element may include one or more per-station (per-STA) profile sub-elements, each of which includes a station (STA) control field. Furthermore, according to some embodiments, the STA control field may include link identifier (ID) information and reconfiguration operation type information. In some instances, the link ID information and reconfiguration operation type information can be used to enable, disable, or modify one or more operating modes associated with one or more radio links, respectively.

[0155] At 1804, according to some implementations, the AP may receive a response from a non-AP STA. In some implementations, the response may include an acknowledgment (ACK) frame.

[0156] At 1806, according to some implementations, the AP may enable, disable, or modify one or more operating modes. For example, the AP may enable, disable, or modify one or more operating modes associated with one or more wireless links, respectively, based at least in part on at least one indicator and a received response.

[0157] Figures 19A to 19B —UHR mode change using Link Reconfiguration Request Frame Figures 19A to 19B Example fields and formats for link reconfiguration request frames for UHR mode changes are shown according to some implementation schemes. For example, Figure 19AAn example of a link reconfiguration request frame action field format is provided, which may include sequences 1 through 5 corresponding to different meanings. For example, according to some implementations, sequence 1 may be associated with a category, sequence 2 may be associated with a protected Extremely High Throughput (EHT) action, sequence 3 may be associated with a session token, sequence 4 may be associated with a reconfiguration ML element, and sequence 5 may be associated with an OCI element.

[0158] Figure 19B An example reconfiguration of the ML element format according to some implementations is illustrated, which includes fields such as: element ID, length, element ID extension (each of which is 1 octet in size); ML control of 2 octets; and public information (e.g., information) field and link information field of variable octet size.

[0159] According to some implementations, frame switching for enabling or disabling a mode may include: sending a Link Reconfiguration (LR) request frame; and receiving an LR notification frame as a response frame. Additionally, and unlike the LR response frame, the LR notification frame may not contain a status code indicating an acceptance or rejection decision.

[0160] However, using LR frame switching for UHR mode change may have certain advantages. For example, the reconfiguration of multi-link elements in the LR request frame can be beneficially used for cross-link signaling of mode enable or disable across links. This allows for a more efficient mode change approach because a single frame switch can be used to indicate link addition and mode enable or disable.

[0161] For example, an LR request frame may carry a single reconfiguration ML element, and the type of the ML element may be indicated in the ML control field of that element. Additionally or alternatively, the per STA profile sub-element in the link information field may contain information about the addition or deletion of links.

[0162] Figures 20A to 20B —UHR mode change using the link reconfiguration framework Figures 20A to 20B This illustrates example elements and sub-element fields and formats within a link reconfiguration framework based on some implementation schemes. For example, Figure 20A The format of a UHR parameter update element is illustrated. This element may include an element ID, length, element ID extension, and operation parameter control and operation parameter information fields. Furthermore, the operation parameter control field may include 10 bits indicating whether five different modes (NPCA, DSO, DBE, DUO, LOM) are enabled and whether parameters are present. Additionally, the operation parameter information file may include operation information for the five modes.

[0163] According to some implementations, each "Enabled" field can indicate whether the corresponding feature is enabled. Furthermore, each "Presence" field set to a value of 1 can indicate that the corresponding operation information field exists in the operation information field. Alternatively, each "Presence" field set to a value of 0 can indicate that the corresponding operation information field does not exist in the operation information field. Therefore, according to some implementations, if the corresponding "Enabled" field of the presence bit is also set to a value of 1, then the presence bit can only be set to a value of 1.

[0164] Figure 20B An example per-STA profile sub-element format is illustrated, which may include a sub-element ID, length, and STA control, STA information, and STA profile fields. Additionally, the STA control field may include information corresponding to the link ID used for mode changes. Alternatively or additionally, this can be achieved by setting the reconfiguration operation type to a specific value (e.g., such as...). Figure 20B As shown in 5), the STA control field may include information associated with UHR parameter updates. Furthermore, according to some implementations, in addition to the UHR parameter update element, the STA profile may also include information associated with other fields and elements.

[0165] In other words, Figures 20A to 20B This illustrates aspects of a method for indicating a mode by using operational parameters that indicate a mode that the STA intends to enable or disable. For example, and regarding the current link, according to some implementations, an ordered bitmap can be used to indicate a specific mode that the STA intends to enable or disable.

[0166] Additionally, and regarding cross-link signaling, reconfigured ML elements can be used for mode change signaling. One benefit of doing so is the ability to change multiple modes for a specific link. However, in some aspects, the design may be constrained to enable or disable multiple modes. Depending on some implementations, such as and regarding single-mode change signaling, the operating parameter control field may need to include information on all existing modes in the appropriate 802.11 version (e.g., 802.11bn).

[0167] Figures 21A to 21B —UHR mode change element in LR request frame Figures 21A to 21B Example fields and formats for LR request frames used for UHR mode changes are shown according to some implementation schemes. For example, Figure 21A Example aspects of encoding new sub-element IDs, including the corresponding identifier, name, and whether they are extensible, are illustrated. For example, sub-element IDs 0 through 7 can be associated with UHR patterns (e.g., DUO, DPS, NPCA, DSO, DBE, LOM, Co-BF, and C-SR), and all are extensible. Additionally, according to some implementations, sub-element IDs 8 through 15 may be reserved.

[0168] like Figure 21B As shown, the format of the mode change element in the action field of the LR request frame can be characterized by a format including an element ID field, a length field, an element ID extension field, a sub-element ID field, a length field, a mode control field, and an operation parameter field. Furthermore, according to some implementations, the mode control field may include a mode-enabled subfield and a reserved subfield.

[0169] In other words, Figures 21A to 21B This relates to a method, according to some embodiments, for enabling or disabling different UHR modes using a sub-element framework via a mode change element in the action field of an LR request frame. Therefore, the sub-element ID field may indicate the mode the STA intends to change to, and the mode control field may indicate whether a mode is requested to be enabled or disabled. Furthermore, according to some embodiments, the operation parameter field may indicate the parameters used by the STA when the mode enable process is complete, as well as the operation parameters present for a specific sub-element.

[0170] Figure 22 —Reconfigure the per-STA profile sub-element in the link information field of the ML element. Figure 22 Example fields and formats of the per-STA profile sub-element in the link information field of the reconfiguration ML element according to some implementation schemes are shown. For example, Figure 22 Each STA profile sub-element may include a sub-element ID field, a length field, an STA control field, and an STA profile field. Additionally, according to some embodiments, the STA information field may not exist in these sub-elements. Furthermore, according to some embodiments, the STA control field may include information associated with the link ID and a reconfiguration operation type set to "mode change". Additionally, the STA profile field may include sub-fields such as: element ID, length, element ID extension, sub-element ID, length, mode control, and operation parameters.

[0171] In some implementations, such as when cross-link signaling is required, the mode change element can be included in the reconfiguration ML element. Therefore, the link ID in the STA control field of each STA profile sub-element... Subfields may be included in the link information field as link identifiers for anticipated mode changes. Additionally, mode change elements may be included in the STA profile field of each STA profile sub-element. Furthermore, according to some implementations, if the reconfiguration operation type subfield in the STA control field is set to "mode change," the STA information field may not exist in each STA profile sub-element.

[0172] Figure 23 —Mode-changing elements without link ID / bitmap Figure 23Example fields and formats of pattern change elements without link ID / bitmaps are illustrated according to some implementation schemes. For example, a non-AP MLD intending to enable DPS and DUO in an operational link can use pattern change elements such as Figure 23 The illustrated pattern-changing element.

[0173] In some implementations, the mode-changing element may include fields such as element ID, length, and element ID extension. Additionally, the mode-changing element may include two sets of sub-element IDs, along with corresponding length and mode control fields. Therefore, according to some implementations, DUO and DPS can be enabled for non-AP MLDs when the sub-element IDs for the first and second sets are set to 0 and 1, and both mode control fields are set to enabled. Furthermore, the second set may additionally include an operation parameter field associated with the DPS mode. Conversely, according to some implementations, the first set may not include the operation parameter field, as the DUO mode may not require it.

[0174] Figure 24 —Reconfigure the schema-changing element in the ML element Figure 24 Example fields and formats of the mode change element in a reconfiguration ML element according to some embodiments are illustrated. For example, a reconfiguration ML element may include two per-STA profile sub-elements 1 and 2, each of which includes a sub-element ID field, a length field, an STA control field, and an STA profile field. Additionally, according to some embodiments, the STA information field may not exist in these sub-elements. Furthermore, according to some embodiments, the STA control field may include information associated with the link ID (e.g., for sub-element 1, link ID=1; and for sub-element 2, link ID=2) and a reconfiguration operation type set to "mode change". Additionally, the STA profile field of sub-element 1 may include sub-fields such as: element ID, length, element ID extension, sub-element ID set to value 0, length, and mode control field set to enabled. Therefore, since the sub-element ID is set to value 0 (e.g., corresponding to DUO mode enabled), the operation parameter field may not exist in the STA profile of sub-element 1. Alternatively, the STA profile fields of child element 2 may include subfields such as: element ID, length, element ID extension, child element ID set to value 1, length, and mode control field set to enabled. Therefore, according to some implementations, since the child element ID is set to value 1 (e.g., corresponding to DPS mode enabled), the operation parameter field may exist in or be included in the STA profile of child element 2. In other words, Figure 24This illustrates how a non-AP MLD, according to some implementations, can use a mode-changing element to enable DPS on a link with link ID=1 and DUO on a link with link ID=2.

[0175] Figure 25 —Mode-changing elements in LR request frames Figure 25 Example fields and formats of mode change elements in an LR request frame according to some implementations are illustrated. For example, the mode change element format may include fields such as element ID, length, and element ID extension. Additionally, according to some implementations, the format may include a set of fields such as sub-element ID, length, mode control, and operating parameters (wherein this set of fields is repeated for each mode change on multiple links). Furthermore, the mode control field may include subfields including link ID / bitmap, mode enabled, and reserved.

[0176] In some implementations, it has the function of... Figure 25 The mode change element of the sub-element framework for the different modes illustrated (e.g., DPS, DUO, NPCA, DSO, DBE, LOM, Co-BF, C-SR) can be used for single-link or cross-link mode change signaling. For example, according to some implementations, the sub-element ID field can indicate the mode the STA intends to change, and the mode control field can indicate the link ID or bitmap (for DUO) sub-field to further indicate the intended link for which the mode is requested to be enabled. Furthermore, the mode-enabled sub-field can be used to indicate whether the mode is requested to be enabled or disabled. Additionally, the operation parameter field can indicate the parameters that the STA will operate on when the mode enablement process is complete. Therefore, according to some implementations, operation parameters for specific sub-elements may exist, and signaling may not be required in the reconfiguration ML element.

[0177] Figures 26A to 26B —Mode-changing elements with link ID / bitmap Figures 26A to 26B Examples of fields and formats for pattern-changing elements with corresponding link IDs or bitmaps are shown, based on some implementation schemes. For example, Figure 26AAn example mode-change element format in the action field of an LR request frame according to some implementation schemes is illustrated. This example mode-change element format may include fields such as element ID, length, element ID extension, and two sets of fields for DUO enabled and DPS enabled. The first set of fields may correspond to DUO enabled and includes fields such as: child element ID set to a value of zero, length, and a mode control field set to enabled with the link ID set to a value of 1. Additionally, the second set of fields may correspond to DPS enabled and includes fields such as: child element ID set to a value of one, length, a mode control field set to enabled with the link ID set to a value of 1, and an operation parameter field. In other words, Figure 26A This illustrates how a non-AP MLD can enable DPS and DUO in Link 1 using a mode-changing element, according to some implementation schemes.

[0178] Figure 26B An example mode-change element format in the action field of an LR request frame according to some implementation schemes is illustrated. This example mode-change element format may include fields such as element ID, length, element ID extension, and two sets of fields for DUO enabled and DPS enabled. The first set of fields may correspond to DUO enabled and includes fields such as: child element ID set to value zero, length, and a mode control field set to enabled with link ID set to value 1. Additionally, the second set of fields may correspond to DPS enabled and includes fields such as: child element ID set to value one, length, a mode control field set to enabled with link ID set to value 2, and an operation parameter field. In other words, Figure 26B This illustrates how a non-AP MLD, according to some implementations, can enable DUO on the link with link ID=1 and DPS on the link with link ID=2 using a mode-changing element. In some implementations, the mode-changing element can be considered a separate container for UHR mode changing because the ML reconfiguration ML element is not used.

[0179] Figure 27 — Operation parameter format when the sub-element ID sub-field value is 1 Figure 27 Example subfields and formats for the operation parameter fields used in DPS mode are illustrated according to some implementation schemes. For example, Figure 27An example operation parameter subfield format is illustrated when the sub-element ID subfield value is 1 (e.g., DPS mode) according to some implementation schemes. Therefore, if the sub-element ID subfield value is 1, the operation parameter subfield in the STA information field may include a 1-bit DPS parameter update control subfield, which may indicate whether there is an updated DPS fill delay value and DPS transition delay value relative to the transmission value in the last transmitted UHR mode enable notification frame. Furthermore, if this subfield is set to 1, the DPS fill delay subfield and DPS transition delay subfield may... Figure 27 The illustrated subfield format exists. Additionally, according to some implementations, if the subfield is set to 1 and the value in the DPS fill delay subfield is non-zero, this may indicate that a STA with DPS mode enabled requires an intermediate FCS (I-FCS) in the ICF.

[0180] The operation parameter subfield format may also include a 1-bit required ICF subfield, which indicates whether the STA requires ICF and ICR exchange before any frame exchange initiated with the DPS STA. For example, if ICF and / or ICR are required only for frame exchanges using HCM parameters, the required ICF subfield can be set to 0. Alternatively, if ICF and / or ICR are required for all frame exchanges, the required ICF subfield can be set to 1. Additionally or alternatively, the 1-bit required ICF subfield can be used to indicate that the DPS STA is transitioning from Low Capability Mode (LCM) to High Capability Mode (HCM).

[0181] In some implementations, the operation parameter field of the mode-changing element may include a 6-bit reserved subfield. Additionally, according to some implementations, the 6-bit reserved subfield can be used to indicate whether the STA intends to operate in a parameterized mode. For example, according to some implementations, if the appropriate value in the 6-bit reserved subfield is equal to zero, this may indicate that the STA intends to operate in the default mode (e.g., 20MHz, N). ss Operate under the condition that = 1, MCS ≤ 4). Alternatively, if the appropriate value in this field is equal to one, this indicates that the STA intends to operate in parameterized mode. Therefore, the STA can define the parameters of the mode in the operation parameter field of the mode-changing element.

[0182] In some implementations, the DPS fill delay subfield may indicate an updated value of the DPS fill delay, which is in the range of 0 to 64 (with a resolution / increment of 4 microseconds (μs)). Additionally, the DPS transition delay subfield may indicate an updated value of the DPS transition delay, which is in the range of 0 to 64 (with a resolution / increment of 4 microseconds (μs)).

[0183] According to some implementations, when the mode type subfield value in the STA control field is set to a value of 0 (e.g., indicating DUO mode), the operation parameter presence subfield can be set to 0, and feedback information can be provided as an ICR frame in the multi-STA block acknowledgment (BA). Additionally, according to some implementations, when the mode type subfield value is set to a value of 0 (e.g., indicating DUO mode), the STA information field may not exist in the mode enable profile sub-element.

[0184] Figure 28 —Feature enable / update / deactivate methods Figure 28 This is a communication flowchart illustrating various aspects of an enhanced approach to pattern management technology, including feature enable / update / deactivate, according to some implementation schemes. Such technologies can help provide a more efficient and flexible pattern management process (compared to traditional methods) and subsequently reduce power consumption between AP MLDs and non-AP MLDs.

[0185] For example, Figure 28 An example enhanced approach to pattern management technology performed by a non-AP MLD is illustrated according to some implementation schemes. Figure 28 Aspects of the method may be implemented by a non-AP MLD communicating with the AP MLD. The AP MLD and / or the non-AP MLD may be illustrated and described as in the various figures herein, or more generally, may be illustrated and described as needed in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the figures above. For example, the processor (and / or other hardware) of such a device may be configured to cause the device to perform any combination of the illustrated method elements and / or other method elements. For example, one or more processors (or processing elements) (e.g., processors 101, 204, 302, 402, 432, 434, 439, baseband processors, processors associated with communication circuits such as 130, 230, 232, 329, 330, 430, etc., and various possibilities) may cause a wireless device, STA, UE, non-AP and / or AP, or other device to perform such method elements.

[0186] It should be noted that, although described in a manner consistent with the communication technologies and / or features associated with IEEE and / or 802.11 (e.g., 802.11be) specification documents. Figure 28 The method includes at least some elements, but such description is not intended to limit this disclosure, and Figure 28 Various aspects of the method can be used in any suitable wireless communication system as needed. Similarly, although described in a manner relevant to non-AP systems that can be MLDs or UHR MLDs... Figure 28 The methods and elements thereof, but such description is not intended to limit this disclosure, and Figure 28Various aspects of the method can be used by non-APs who are not MLDs or UHR MLDs, as needed. Additionally, although... Figure 28 Some aspects of the method can be implemented by non-AP MLDs, but with Figure 28 Some corresponding steps related to the method can be performed by the AP MLD that communicates with the non-AP MLD.

[0187] In addition to other devices, the method shown may also be combined with the accompanying drawings (e.g., such as...). Figures 29 to 36 This method may be used in any of the systems, methods, or apparatuses shown in the figure. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0188] At 2802, according to some embodiments, the non-AP STA may send a frame to the AP indicating the enabling, disabling, or modification of one or more operating modes. For example, the non-AP STA may send a frame to the AP including at least one indicator indicating the enabling, disabling, or modification of one or more operating modes associated with one or more radio links, respectively. In some embodiments, the at least one indicator may include a feature enable element.

[0189] At 2804, according to some implementations, a non-AP STA can receive a response from the AP. For example, according to some implementations, this response from the AP can be an acknowledgment (ACK) frame.

[0190] At 2806, according to some implementations, a non-AP STA may start a first timer. For example, according to some implementations, this first timer may be started upon receipt of the ACK frame.

[0191] At 2808, according to some implementation schemes, a non-AP STA may enable, disable, or modify one or more operating modes. For example, a non-AP STA may enable, disable, or modify one or more operating modes associated with one or more radio links, respectively, based at least in part on at least one indicator, reception of a response, and expiration of a first timer.

[0192] According to some implementations, the method may further include: receiving a notification frame from the AP that includes another feature enabling element; and sending an acknowledgment (ACK) frame to the AP. Additionally or alternatively, enabling, disabling, or modifying one or more operating modes associated with one or more radio links, respectively, may be performed upon the expiration of a second timer that starts upon receiving an ACK frame.

[0193] Figure 29 —Enabling the element using features Figure 29 This illustrates the activation process for elements based on usage characteristics in some implementation schemes. For example, Figure 29 An example communication exchange between a UHR AP and a UHR non-AP STA for performing the activation process is illustrated. In some implementations, the UHR non-AP STA may send a request frame to the UHR AP that may include feature activation elements. The UHR AP may then send an ACK frame to the UHR non-AP STA. Additionally, and after the expiration of the first timer (as prior information), the feature corresponding to the mode (e.g., DUO, Co-BF, Co-SR, etc.) may be enabled or updated.

[0194] Additionally or alternatively, according to some implementations, the UHR AP may send a notification frame to the UHR non-AP STA that may include a feature enablement element. According to some implementations, the UHR non-AP STA may then send an ACK frame to the UHR AP, and after a second timer (also conveyed as prior information) expires, the feature corresponding to the mode (e.g., DUO, Co-BF, Co-SR, etc.) may be enabled or updated.

[0195] In other words, Figure 29 This involves a common feature enabling element that can be used to enable / update all 802.11 mode (e.g., 802.11bn mode) features (including DUO, DPS, NPCA, DSO, Co-BF, Co-SR, and other new features). For example, upon receiving a feature enable or update request from a STA, some features (e.g., DUO) may be enabled or updated after the duration of a first timer (e.g., timer 1) following the receipt of an ACK frame for the enable / update request frame. In some embodiments, the first timer may be a zero or non-zero value conveyed as prior information. In at least some instances, this prior information may be conveyed at least in part based on prior knowledge, assumptions, hypotheses, and / or analysis.

[0196] Additionally or alternatively, upon receiving a feature enable / update request from the STA for some mode features (e.g., DPS, NPCA, and DSO), the AP may send an enable / update notification frame, and the feature is enabled / updated after the duration of a second timer (e.g., timer 2) following the receipt of an ACK frame for the enable / update notification frame. In some embodiments, the second timer may be a zero or non-zero value conveyed as prior information.

[0197] Figure 30 — Modal conditions used for feature enabling / updating Figure 30 Examples of modal conditions for feature enabling or updating are illustrated according to some implementation schemes. For example, and as... Figure 30As shown, according to some implementations, enabling or updating DUO mode may not require a response frame from the AP, and the first timer (e.g., timer 1) and / or its corresponding timer value may be based at least in part on the AP’s management frame processing time for single-link enable / update and the additional cross-link processing time for ML enable / update.

[0198] Regarding DPS mode, NPCA mode, and DSO mode, depending on some implementations, an AP response frame may be required and a first timer (e.g., timer 1) may not be required, as the reception of the response frame can be used as the starting point for enabling / updating.

[0199] According to some implementation schemes, for Co-BF mode and Co-SR mode, an AP response frame may not be required, and the first timer (e.g., timer 1) and / or its corresponding timer value may be based at least in part on the AP's management frame processing time for single-link enable / update and the additional cross-link processing time for ML enable / update.

[0200] Furthermore and corresponding to Figure 30 In all the modes shown, according to some implementations, the second timer (e.g., timer 2) and / or its corresponding timer value may be based on the STA’s management frame processing time for single-link enable / update and the additional cross-link processing time for ML link enable / update.

[0201] Figure 31 —Use features to enable the deactivation process of elements. Figure 31 This illustrates the deactivation process for elements based on usage characteristics of certain implementation schemes. For example, Figure 31 An example communication exchange between a UHR AP and a UHR non-AP STA for performing the deactivation process is illustrated. In some implementations, the UHR non-AP STA may send a request frame to the UHR AP that may include feature enable elements with appropriate deactivation content. The UHR AP may then send an ACK frame to the UHR non-AP STA. Additionally, and after the expiration of a first timer (as prior information), the feature may be deactivated. According to some implementations, if all features are deactivated, the UHR AP may not need to send a notification frame to the UHR non-AP STA.

[0202] However, according to some implementations, if all features have not yet been deactivated (e.g., if some features corresponding to DPS, NPCA, or DSO (and other possible modes) are still in an enabled state), the UHR AP may send a notification frame to the UHR non-APSTA that may include feature enable elements. According to some implementations, the UHR non-AP STA may then send an ACK frame to the UHR AP, and the feature may be deactivated after a second timer (also conveyed as prior information) expires.

[0203] In other words, Figure 31 This involves methods for deactivating features via feature-enabled elements according to some implementation schemes. For example, STA can use... Figure 29 The activation process is similar to that of sending frames to request the updating or deactivation of one or more features. According to some embodiments, the request frame may contain an enable element, where the corresponding bit in the feature bitmap / existence field of the element is set to 0, and may not include sub-elements of the corresponding feature. Furthermore, according to some embodiments, as long as the feature is enabled on one (or more) links, the bit corresponding to the feature in the feature bitmap / existence field of the enable element can be set to 1, and thus the corresponding sub-elements of the feature can be included in the element.

[0204] Figure 32 —Modal conditions for feature deactivation Figure 32 Example modal conditions for feature deactivation are illustrated according to some implementation schemes. For example, and as... Figure 32 As shown, according to some implementations, disabling DUO mode, DPS mode, NPCA mode, and DSO mode may not require a response frame from the AP, and the first timer (e.g., timer 1) and / or its corresponding timer value may be based at least in part on the AP's management frame processing time for single-link enable / update and the additional cross-link processing time for ML enable / update. Furthermore, regarding the disabling of Co-BF mode and Co-SR mode, an AP response frame may also not be required. Furthermore, corresponding to... Figure 30 All the modes shown may not require a second timer (e.g., timer 2) and / or its corresponding timer value, depending on some implementations.

[0205] Figures 33A to 33G —Feature Enable Element Design—Option 1 Figures 33A to 33G Examples of fields and formats related to the first option of feature-enabled element design are illustrated according to some implementation schemes. For example, Figure 33AExample of a first option for a feature-enabled element according to some embodiments is shown, which may include: a 1-byte element ID field, an element length field, and an element ID extension field; a 2-byte feature bitmap / presence field; and an optional enable sub-element field of variable byte length for each mode, including DUO, DPS, DSO, NPCA, Co-BF, and Co-SR (and other possible modes). Furthermore, according to some embodiments, if a response / notification frame corresponding to the enable of the DUO mode is transmitted, the DUO enable sub-element may not be included in the response / notification frame.

[0206] according to Figure 33A Each feature has a fixed corresponding bit position. The bit can be set to 1 to enable on one or more links, and can be set to 0 to disable on all links. Therefore, according to some embodiments, when the corresponding bit is set to 1, the sub-element of the corresponding feature may be included in the element if the feature is enabled for the first time or the content of the sub-element is changed / updated. Alternatively, according to some embodiments, when the bit is set to 0, the sub-element of the corresponding feature may not be included in the element.

[0207] Figures 33B to 33G Example fields and formats for enabling sub-elements in DUO, DPS, NPCA, DSO, Co-BF, and Co-SR according to some implementation schemes are shown. For example, and as... Figures 33B to 33G As illustrated, the format may include a 16-bit child element ID field, an 8-bit length field, and a 16-bit enable bitmap field. Furthermore, since each different bit of the 16-bit enable bitmap can correspond to a different link, the 16-bit enable bitmap field can be used to indicate one or more links on which the appropriate mode is enabled.

[0208] Figures 33B to 33G Additional fields that may be included in the DUO, DPS, NPCA, DSO, Co-BF, and Co-SR enable sub-elements according to some embodiments are also illustrated. For example, according to some embodiments, the DUO enable sub-element may additionally include a preferred SU ICF type field and a required ICF field; the DPS enable sub-element may additionally include a DPS fill delay field and a DPS transition delay field; the NPCA enable sub-element may additionally include an NPCA switchover delay field and an NPCA switchback delay field; and the DSO enable sub-element may additionally include a DSO switchover delay field and a DSO switchback delay field.

[0209] Figures 34A to 34G —Feature Enable Element Design—Option 2 Figures 34A to 34G Examples of fields and formats related to the second option of feature-enabled element design are illustrated according to some implementation schemes. For example, Figure 34AA second option for enabling an element, according to some implementations, is illustrated, which may include: an octet element ID field, an element length field, and an element ID extension field; and an optional enable sub-element field of variable octet length for each mode, including DUO, DPS, DSO, NPCA, Co-BF, and Co-SR (and other possible modes). Furthermore, according to some implementations, if a response / notification frame corresponding to the enable of the DUO mode is transmitted, the DUO enable sub-element may not be included in the response / notification frame.

[0210] Figures 34B to 34G Example fields and formats for enabling sub-elements in DUO, DPS, NPCA, DSO, Co-BF, and Co-SR according to some implementation schemes are shown. For example, and as... Figures 34B to 34G As illustrated, the format may include a 16-bit child element ID field, an 8-bit length field, a 16-bit enable bitmap, and a 2-bit enable control field. Each different bit of the 16-bit enable bitmap may correspond to a different link, and therefore the 16-bit enable bitmap field can be used to indicate one or more links on which the appropriate mode is enabled.

[0211] Additionally, according to some embodiments, the 2-bit enable control field included in the DUO, DPS, NPCA, DSO, Co-BF, and Co-SR enable sub-elements may include 2-bit field values ​​associated with: enable features (e.g., bit value (0,0)); update enable link bitmap and / or parameters (if any) (e.g., bit value (0,1)); deactivate features (no subsequent field) (e.g., bit value (1,0)); and reserved values ​​(e.g., bit value (1,1)). Therefore, according to some embodiments, both the 16-bit enable bitmap field and the 2-bit enable control field are utilized. Figures 34B to 34G The enable sub-element shown in the example allows for indications of mode enable, disable, or update for one or more links.

[0212] Figures 34B to 34G Additional fields that may be included in the DUO, DPS, NPCA, DSO, Co-BF, and Co-SR enable sub-elements according to some embodiments are also illustrated. For example, according to some embodiments, the DUO enable sub-element may additionally include a preferred SU ICF type field and a required ICF field; the DPS enable sub-element may additionally include a DPS fill delay field and a DPS transition delay field; the NPCA enable sub-element may additionally include an NPCA switchover delay field and an NPCA switchback delay field; and the DSO enable sub-element may additionally include a DSO switchover delay field and a DSO switchback delay field.

[0213] In addition, according to some implementations, feature-enabled elements may be included in association request (and / or response) frames, link reconfiguration request (and / or notification) frames, any other management action frames, or any other container (e.g., frame container).

[0214] Figure 35 —Include feature enable elements in the link reconfiguration request frame. Figure 35 Examples are shown of including a feature-enabled element in a link reconfiguration request frame according to some implementation schemes. For example, Figure 35 The format of the link reconfiguration response frame action field, including sequences 1 through 6 and their associated meanings, is illustrated. Thus, according to some implementations, the first sequence may be associated with a category, the second sequence with a protected EHT action, the third sequence with a session token, the fourth sequence with a reconfiguration ML element, the fifth sequence with an OCI element, and a new sixth sequence with a feature-enabled element.

[0215] In some implementations, a reconfiguration ML element may be optionally included when sending data from a UHR STA to a UHR AP. Additionally, according to some implementations, if a reconfiguration ML element is included when no link is added, the reconfiguration ML element may include the minimum content of the element.

[0216] Figure 36 —Include feature enable elements in the link reconfiguration notification frame. Figure 36 Examples of including a feature-enabled element in a link reconfiguration notification frame, according to some implementation schemes, are illustrated. For example, Figure 36 The format of the link reconfiguration notification frame action field, including sequences 1 through 5 and their associated meanings, is illustrated. Thus, according to some implementations, the first sequence may be associated with a category, the second with a protected EHT action, the third with a session token, the fourth with a reconfiguration ML element, and a new fifth with a feature-enabled element.

[0217] Example Implementation Plan In some implementations, a method may include sending a frame including an operation mode indicator to an access point (AP) indicating the enabling, disabling, or modification of an operation mode associated with a radio link. The method may also include receiving a response from the AP; and enabling, disabling, or modifying the operation mode associated with the radio link based at least in part on the operation mode indicator and the response.

[0218] According to some embodiments, the frame includes a link reconfiguration request frame. Additionally or alternatively, the operating mode indicator may be included in the mode change element of the link reconfiguration request frame. Furthermore, according to some embodiments, the operating mode indicator may be included in the mode control field of the mode change element. Additionally, according to some embodiments, the mode change element may include at least one of the following: a sub-element identifier (ID) corresponding to the operating mode; a mode control field indicating the enabling, disabling, or modification of the operating mode; or operating parameters associated with the operating mode.

[0219] In some implementations, the operating mode indicator may include a sub-element identifier (ID) corresponding to the operating mode, and the operating mode includes at least one of the following: Dynamic Unavailable Operation (DUO) mode; Dynamic Power Saving (DPS) mode; Non-Master Channel Access (NPCA) mode; Dynamic Subband Operation (DSO) mode; Coordinated Beamforming (Co-BF) mode; Coordinated Space Rejection (Co-SR) mode; Low Latency Indication (LLI) mode; Dynamic Bandwidth Extension (DBE) mode; or Limited Operation (LOM) mode. Additionally or alternatively, the method may further include adding or removing the radio link using a per-site (per STA) profile sub-element, wherein the radio link operates according to the operating mode.

[0220] According to other embodiments, an apparatus may include a processor configured to cause an access point (AP) multilink device (MLD) to perform operations upon execution of instructions stored in a memory. These operations include: sending a frame including an operation mode indicator to a non-access point (non-AP) station (STA) indicating the enabling, disabling, or modification of an operation mode associated with a radio link. Additionally, the operation may include: receiving a response from the non-AP STA; and enabling, disabling, or modifying the operation mode associated with the radio link, at least in part, based on the operation mode indicator and the response.

[0221] In some implementations, the operation mode indicator may be included in an ordered bitmap to indicate at least one of one or more operation modes to be enabled, disabled, or modified. Additionally or alternatively, the operation mode indicator may also indicate the presence of operation parameters for at least one of the one or more operation modes.

[0222] According to some implementations, the operation mode indicator may be included in a reconfiguration multi-link (ML) element. Furthermore, the operation mode indicator may be included in a mode enable profile sub-element corresponding to a sub-field of the ML control field of the reconfiguration ML element. Additionally or alternatively, the operation mode indicator may be included in at least one of the STA information fields in the per-site (STA) enable profile sub-element of the reconfiguration ML element. In some implementations, the reconfiguration ML element may include one or more per-site (per-STA) profile sub-elements, each of which includes a site (STA) control field, wherein the STA control field includes link identifier (ID) information and reconfiguration operation type information, and wherein the link ID information and the reconfiguration operation type information are usable to enable, disable, or modify the operation mode associated with the radio link.

[0223] According to an additional embodiment, a non-access point (non-AP) station (STA) may include: a radio component; and a processor operatively coupled to the radio component and configured to cause the non-AP STA to send a frame including an operation mode indicator to an access point (AP), the operation mode indicator indicating the enabling, disabling, or modification of an operation mode associated with a radio link. Additionally, the processor may be configured to cause the non-AP STA to: receive a response from the AP; and enable, disable, or modify the operation mode associated with the radio link, at least in part, based on the operation mode indicator and the response.

[0224] In some implementations, the operating mode indicator may include a feature enable element. According to some implementations, the processor may also be configured to cause the non-AP STA to start a first timer, wherein enabling, disabling, or modifying the operating mode associated with the radio link is based on the expiration of the first timer. Additionally or alternatively, the response from the AP may be an acknowledgment (ACK) frame. In some implementations, the first timer starts upon receipt of the ACK frame.

[0225] According to some implementations, the processor may also be configured to cause the non-AP STA to: receive a notification frame from the AP including another feature enabling element; and send an acknowledgment (ACK) frame to the AP. Additionally or alternatively, enabling, disabling, or modifying the operating mode associated with the radio link may be performed upon the expiration of a second timer that starts upon receiving the ACK frame.

[0226] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0227] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein, if executed by a computer system, the program instructions cause the computer system to perform a method, such as any method embodiment of the method embodiments described herein, or any combination of method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0228] In some implementations, the wireless device may be configured to include a processor (and / or a set of processors) and a memory medium storing program instructions, wherein the processor is configured to read from and execute the program instructions, wherein the program instructions are executable to cause the wireless device to implement any of the various method implementations described herein (or any combination of the method implementations described herein, or any combination of these subsets). The device may be implemented in any of a variety of forms.

[0229] Furthermore, it is widely recognized that the use of personally identifiable information follows privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data can be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use can be clearly explained to users.

[0230] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A method for wireless communication, the method comprising: Send a frame to an access point (AP) including at least one operation mode indicator, wherein the operation mode indicator indicates the enabling, disabling, or modification of an operation mode associated with a wireless link; Receive a response from the AP; as well as The operating mode associated with the wireless link is enabled, disabled, or modified at least in part based on the operating mode indicator and the response.

2. The method according to claim 1, wherein the frame includes a link reconfiguration request frame.

3. The method of claim 2, wherein the operation mode indicator is included in the mode change element of the link reconfiguration request frame.

4. The method of claim 3, wherein the operation mode indicator is included in the mode control field of the mode change element.

5. The method of claim 3, wherein the mode-changing element comprises at least one of the following: The sub-element identifier (ID) corresponding to the operation mode; A mode control field indicating whether the operation mode is enabled, disabled, or modified; or Operating parameters associated with the operating mode.

6. The method of claim 1, wherein the operation mode indicator includes a sub-element identifier (ID) corresponding to the operation mode, and wherein the operation mode includes at least one of the following: Dynamic Unavailable Operation (DUO) mode; Dynamic Power Saving (DPS) mode; Non-primary channel access (NPCA) mode; Dynamic Subband Operation (DSO) mode; Coordinated beamforming (Co-BF) mode; Co-Spatial Rejection (Co-SR) mode; Low Latency Indication (LLI) mode; Dynamic Bandwidth Extension (DBE) mode; or Limited Operation Mode (LOM).

7. The method according to claim 1, further comprising: The wireless link is added or removed using a per-site (per-STA) profile sub-element, wherein the wireless link operates according to the operating mode.

8. The method of claim 1, wherein the operation mode indicator is included in an ordered bitmap to indicate at least one of one or more operation modes to be enabled, disabled or modified.

9. The method according to claim 1, wherein the operation mode indicator further indicates the presence of operation parameters of at least one of the one or more operation modes.

10. The method of claim 1, wherein the operation mode indicator is included in a reconfigurable multi-link (ML) element.

11. The method of claim 10, wherein the operation mode indicator is included in a mode enable profile sub-element corresponding to a sub-field of the ML control field of the reconfigured ML element.

12. The method of claim 10, wherein the operation mode indicator is included in the STA information field in the per-site (STA) enable profile sub-element of the reconfiguration ML element.

13. The method of claim 10, wherein the reconfiguration ML element comprises one or more per-site (per-STA) profile sub-elements, each of the one or more per-site (per-STA) profile sub-elements comprising a site (STA) control field, wherein the STA control field comprises link identifier (ID) information and reconfiguration operation type information, and wherein the link ID information and the reconfiguration operation type information are capable of enabling, disabling or modifying the one or more operation modes associated with the one or more radio links respectively.

14. The method of claim 1, wherein the operation mode indicator includes a feature enable element.

15. The method according to claim 1, further comprising: A first timer is started, wherein enabling, disabling, or modifying the operating mode associated with the wireless link is also based on the expiration of the first timer, and wherein the response from the AP is an acknowledgment (ACK) frame.

16. The method of claim 15, wherein the first timer is started upon receiving the ACK frame.

17. The method of claim 15, further comprising: Receive a notification frame from the AP that includes another feature enabling element; as well as Send an acknowledgment (ACK) frame to the AP.

18. The method of claim 17, wherein enabling, disabling, or modifying the operating mode associated with the wireless link is performed when the second timer expires, and wherein the second timer is started upon receiving the ACK frame.

19. An apparatus for wireless communication, the apparatus comprising: A processor configured to perform the method according to any one of claims 1 to 18 when executing instructions stored in memory.

20. A non-transitory computer-readable storage medium storing program instructions that can be executed by one or more processors to cause a non-access point (non-AP) station (STA) to perform the operation of any one of claims 1 to 18.

Images