Multi-link single radio abort and operating parameters
By coordinating and managing modes between non-AP MLDs and AP MLDs, the problem of unbalanced device capabilities is solved, improving the efficiency and performance of the wireless communication system.
Patent Information
- Application Number
- CN202310340997.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2023-03-22
- Filing Date
- 2023-03-31
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-03-31
AI Technical Summary
In existing wireless communication systems, non-access point multilink devices (non-AP MLDs) suffer from uneven device capabilities and low efficiency in enhanced multilink single radio (EMLSR) operation.
The non-AP MLD works in conjunction with the AP MLD through the processor to dynamically switch and restore the enhanced multi-link single radio mode, and communicates using the first and second radio components to achieve flexible link management.
It improves the communication efficiency and equipment capacity utilization between non-AP MLDs and AP MLDs, and optimizes the performance of wireless communication systems.
Smart Images

Figure CN116896797B_ABST
Abstract
Description
Technical Field
[0001] This application relates to wireless communication, including techniques for wireless communication between wireless stations and / or access points in a wireless networking system.
[0002] Related technical descriptions
[0003] 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.
[0004] 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 transmits 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. Wireless clients operating on an 802.11 network can be any device from a variety of sources, 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 mentioned above, wireless client devices can also generally be stationary devices).
[0005] Mobile electronic devices can take the form of smartphones or tablets that users typically carry. Wearable devices (also known as accessory devices) are a newer form of mobile electronic device, an example being a smartwatch. 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, traffic patterns, and other characteristics.
[0006] Some WLANs can utilize multi-link operation (MLO), for example, the concurrent use of multiple channels (e.g., links). An AP and / or STA with MLO capability can be called a multi-link device (MLD). For example, an AP with MLO capability can be called an AP-MLD, and a STA with MLO capability that does not act as an AP can be called a non-AP MLD.
[0007] Some non-AP MLDs can use different radios with different levels of capability. Such non-AP MLDs can, for example, switch between multiple links using a radio with higher capability according to Enhanced Multi-Link Single Radio (EMLSR) operation. Improvements in this art are expected. Summary of the Invention
[0008] The embodiments described herein relate to systems, methods, apparatus, and mechanisms for enhanced single-radio operation by AP MLD and non-AP MLD.
[0009] The apparatus may include a processor configured to associate a non-access point (AP) multilink device (MLD) (non-AP MLD) with an AP MLD. The non-AP MLD may exchange one or more multilink parameters associated with a first mode (e.g., Enhanced Multilink Single Radio (EMLSR) mode) for communicating with the AP MLD, and enable the first mode for both the first and second links. The non-AP MLD may determine to abort the first mode and transmit a request to the AP MLD to abort the first mode without disabling it. The non-AP MLD may abort the first mode and then resume it.
[0010] A non-access point (AP) multilink device (MLD) (non-AP MLD) may include: a first radio component; a second radio component having less capability than the first radio component (e.g., lower level of capability, such as lower bandwidth, lower number of spatial streams, lack of transmit capability, etc.); and a processor operatively coupled to the first and second radio components and configured to enable the non-AP MLD to establish communication with the AP MLD. The non-AP MLD may transmit at least one parameter to the AP MLD relating to an Enhanced Multilink Single Radio (EMLSR) mode and operate according to the EMLSR mode for a first time period. The non-AP MLD may suspend operation according to the EMLSR mode for a second time period after the first time period; and resume operation according to the EMLSR mode after the second time period.
[0011] A method at an Access Point (AP) Multilink Device (MLD) (AP MLD) may include providing a plurality of links including at least a first link and a second link. The method may further include: associating with a non-AP MLD; and exchanging at least one parameter with the non-AP MLD related to an Enhanced Multilink Single Radio (EMLSR) mode. The method may further include: receiving a request from the non-AP MLD on the first or second link to enter the EMLSR mode for the first and second links; and receiving a request from the non-AP MLD on the first or second link to terminate the EMLSR mode for the first and second links. The method may further include: for the non-AP MLD, terminating the EMLSR mode for the first and second links; and for the non-AP MLD, determining an end time for terminating the EMLSR mode for the first and second links. The method may further include: for the non-AP MLD, resuming the EMLSR mode for the first and second links.
[0012] 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
[0013] 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.
[0014] Figure 1 An exemplary wireless communication system according to some implementation schemes is shown.
[0015] Figure 2 An exemplary simplified block diagram of a wireless device according to some implementation schemes is shown.
[0016] Figure 3 An exemplary WLAN communication system according to some implementation schemes is shown.
[0017] Figure 4 An exemplary simplified block diagram of a WLAN access point (AP) according to some implementation schemes is shown.
[0018] Figure 5 An exemplary simplified block diagram of a wireless station (STA) according to some implementation schemes is shown.
[0019] Figure 6 An exemplary simplified block diagram of a wireless node according to some implementation schemes is shown.
[0020] Figure 7 An example of an AP MLD according to some implementation schemes is shown.
[0021] Figure 8 An example of two MLDs communicating according to some implementation schemes is shown.
[0022] Figures 9 to 1 7 illustrates exemplary aspects of EMLSR operation according to some implementation schemes.
[0023] Figure 18 An exemplary method for EMLSR operation, which may include EMLSR abortion, is shown according to some implementation schemes.
[0024] Figures 19 to 3 6 also illustrates exemplary aspects of EMLSR operation according to some implementation schemes.
[0025] 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 this document to the specific forms disclosed, but rather are intended 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
[0026] acronym
[0027] Various acronyms are used throughout this patent application. The definitions of the most prominent acronyms that may appear throughout this patent application are as follows:
[0028] UE: User Equipment
[0029] AP: Access Point
[0030] STA: Wireless Site
[0031] TX: Transmission / Transmission
[0032] RX: Receive / Receive
[0033] MLD: Multi-link device
[0034] LAN: Local Area Network
[0035] WLAN: Wireless Local Area Network
[0036] RAT: Radio Access Technology
[0037] QoS: Quality of Service
[0038] UL: Uplink
[0039] DL: Downlink
[0040] the term
[0041] The following is a glossary of terms used in this disclosure:
[0042] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems connected via a network, for example. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.
[0043] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks, and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals, or digital signals).
[0044] Computer system—any of all types of computing or processing systems, including personal computer systems (PCs), mainframe computers, workstations, networked appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (and / or combination of devices) having at least one processor that executes instructions from a memory medium.
[0045] Mobile device (and / or mobile station) — any of a variety of computer system devices that are mobile or portable and perform wireless communication using WLAN communication. Examples of mobile devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM (phones), and tablets such as iPads TM Samsung Galaxy TMVarious other types of devices that include Wi-Fi, or both cellular and Wi-Fi capabilities, will fall into this category, such as laptops (e.g., MacBooks). TM ), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM Portable internet devices and other handheld devices, as well as wearable devices such as smartwatches, smart glasses, headphones, pendants, earbuds, etc. Generally, the term "mobile device" can be broadly defined as any electronic, computing, and / or communication device (and / or combination of devices) that is easily transportable by the user and capable of wireless communication using WLAN or Wi-Fi.
[0046] Wireless device (and / or wireless site) — Any of a variety of computer system devices that perform wireless communication using WLAN communication. As used herein, the term “wireless device” can refer to a mobile device as defined above or a stationary device such as a stationary wireless client or wireless base station. For example, a wireless device can be any type of wireless site in an 802.11 system, such as an access point (AP) or client site (STA or UE). Other examples include televisions, media players (e.g., Apple TV). TM Roku TM Amazon FireTV TM Google Chromecast TM (etc.), refrigerators, washing machines, thermostats, etc.
[0047] WLAN—The term “WLAN” has the full range of its common meaning and includes at least wireless communication networks, or RATs, which are provided by WLAN access points and through which connectivity to the Internet is provided. Most modern WLANs are based on the IEEE 802.11 standard and are marketed under the name “Wi-Fi.” WLAN networks are different from cellular networks.
[0048] Processing element—refers to various specific implementations of digital circuitry that perform functions in a computer system. Furthermore, processing element can refer to various implementations of analog or mixed-signal (combination of analog and digital) circuitry that perform functions (and / or multiple functions) in a computer or computer system. Processing elements include, for example, circuits (such as integrated circuits (ICs), ASICs (Application-Specific Integrated Circuits), portions or circuits of individual processor cores), entire processor cores, individual processors, programmable hardware devices (such as field-programmable gate arrays (FPGAs)), and / or a large portion of a system comprising multiple processors.
[0049] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatically" is the opposite of an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent "automatically" performed actions are not specified by the user, for example, not performed "manually," where, in the case of manual execution, the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, a user can invoke the automatic filling of a form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.
[0050] Concurrency refers to the parallel execution or implementation of tasks, processes, signaling, messages, or programs in a manner that overlaps at least partially. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).
[0051] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In such contexts, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently powered on. Typically, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.
[0052] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.
[0053] Figures 1-2 —Wireless communication system
[0054] Figure 1 Exemplary (and simplified) wireless communication systems are shown, 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, an exemplary wireless communication system includes a ("first") wireless device 102 that communicates with another ("second") wireless device. The first wireless device 102 and the second wireless device 104 may use any of a variety of wireless communication technologies to perform wireless communication.
[0056] As a possibility, the first wireless device 102 and the second wireless device 104 may use wireless local area network (WLAN) communication technology (e.g., IEEE 802.11 / Wi-Fi based communication) and / or WLAN-based wireless communication technology to perform communication. One or both of wireless devices 102 and 104 may also communicate via one or more additional wireless communication protocols, such as Bluetooth (BT), Bluetooth Low Energy (BLE), Near Field Communication (NFC), cellular networks (e.g., 4G and / or 5G, such as LTE, NR, etc.), etc. Furthermore, the device is capable of wireless location determination, for example, using GPS.
[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 radio components or at least 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 4G, 5G, etc., and separate radio components for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.
[0060] As mentioned above, it can be combined Figure 1The 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 performing any / all of the following operations: robust discovery of new access points (APs) in an 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 2 An exemplary wireless device 100 (e.g., corresponding to wireless device 102 and / or wireless device 104) that can be configured for use in conjunction with various aspects of this disclosure is illustrated. Device 100 can be any of a variety of types of devices and can be configured to perform any of a variety of types of functions. Device 100 can be a substantially portable device or a substantially fixed device, and may include any of a variety of types of devices. Device 100 can be configured to perform one or more wireless communication technologies or features, such as any technologies or features subsequently shown and / or described herein with respect to any or all of the figures.
[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 type of memory and be usable for any function. 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 layer 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 function of device 100, device 100 may additionally include any of a variety of other components (not shown) for implementing the device function, 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 the following communication interfaces may be used for communication between various device components: Universal Asynchronous Receiver / Transmitter (UART), Serial Peripheral Interface (SPI), Internal Integrated Circuit (I2C), System Management Bus (SMBus), and / or various other communication interfaces. 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
[0068] Figure 3An exemplary WLAN system according to some embodiments is illustrated. As shown, the 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 wired and / or wireless communication channels 150. Additional electronic devices, such as remote devices 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 embodiments, at least one wireless device 106 is configured to communicate directly with one or more adjacent mobile devices without using access point 112.
[0069] Furthermore, in some implementations, wireless device 106 (which may be an exemplary embodiment of device 100) may be configured to perform methods for: robust discovery of new access points (APs) in AP MLDs, robust link addition to AP MLDs, 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.
[0070] Figure 4 —Access Point Diagram
[0071] Figure 4 An exemplary block diagram of access point (AP) 112 is shown, which may 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 a processor 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 these addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).
[0072] 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 may provide connectivity to additional networks such as the internet.
[0073] AP 112 may include at least one antenna 234, which may be configured to operate as a wireless transceiver and 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 4G, 5G, etc.
[0074] Furthermore, in some implementations, as further described below, AP 112 may be configured to perform methods for performing any / all of the following operations: robust discovery of new access points (APs) in the AP MLD, robust link addition to the AP MLD, AP beacon mode when an AP is added to or removed from the 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.
[0075] Figure 5 —Client Site Diagram
[0076] Figure 5 An exemplary simplified block diagram of client site 106 is shown, which can be Figure 4This 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, taskbars, charging stations, etc.), a display 360, cellular communication circuitry (e.g., cellular radio components) 330 (such as for 5G NR, LTE, GSM, etc.), and short-to-medium range wireless communication circuitry (e.g., Bluetooth). TM and WLAN radio components) 329 (e.g., Bluetooth) TM (And WLAN circuitry). Client site 106 may also 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. Short-to-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 or instead of being coupled to antennas 337 and 338, short-to-medium-range wireless communication circuitry 329 may be coupled to antennas 335 and 336. The short-to-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 short-to-medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may be used for wireless communication, such as using WLAN communication, Bluetooth communication, and / or cellular communication.
[0077] As shown, the SOC 300 may include one or more processors 302 and display circuitry 304. The processors execute program instructions for client site 106, and the display circuitry performs graphics processing and provides display signals to display 360. The SOC 300 may also include motion sensing circuitry 370, which may detect motion of 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 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.
[0078] As described 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 WLAN RAT communication used in a WLAN network, such as... Figure 3 or Figure 1 As shown in the image.
[0079] 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.
[0080] Furthermore, as described in this invention, 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. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 204.
[0081] 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. Thus, 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. Furthermore, 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.
[0082] Figure 6 —Wireless Node Diagram
[0083] Figure 6 A possible block diagram of wireless node 107 is shown, which can be Figure 5 One possible exemplary implementation of the device 106 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. One or more processors 402 may also be coupled to a memory management unit (MMU) 440, which may be configured to receive addresses from one or more processors 402 and translate these addresses into locations in memory (e.g., memory 406 and 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.
[0084] 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, GPS, etc.).
[0085] 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 described 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).
[0086] 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 on, for example, an 802.11 network. The Bluetooth logic component 439 enables the wireless node 107 to perform Bluetooth communication. The cellular modem 434 may be capable of performing cellular communication according to one or more cellular communication technologies. Some or all of the components of the wireless communication circuit 430 may be used for wireless communication, such as using WLAN communication, Bluetooth communication, and / or cellular communication.
[0087] As described herein, wireless node 107 may include hardware and software components for implementing embodiments of this 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 a processor 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).
[0088] Figures 7 to 1 7—Multi-Link Device (MLD) Operation
[0089] Various communication standards (such as IEEE 802.11) may include multi-link device (MLD) capabilities. In current implementations, access point (AP) MLD nodes can manage their associated APs. Therefore, AP MLD nodes can modify, add, and / or remove associated APs to increase capacity, manage Basic Service Set (BSS) interference and coverage, including switching APs to operate in channels with lower interference, and / or manipulating associated non-AP MLD nodes to operate on APs and / or AP MLD nodes with better performance.
[0090] Figure 7 An AP MLD 112 according to some embodiments is shown. 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 across 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. In the illustrated example, AP 712a can operate in the 2.4 GHz band, AP 712b can operate in the 5 GHz band, and APs 712c and AP 712d can operate in the 6 GHz band. Other arrangements (e.g., within the same and / or other frequency bands) are possible.
[0091] AP MLDs can provide auxiliary APs from a single physical device (e.g., a single shared enclosure) and potentially using 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., beams in different directions, using different antennas with a shared enclosure (e.g., antennas of the same physical device) and / or different antennas of different devices, etc.).
[0092] In some implementations, spatially separated auxiliary APs can operate on the same (or at least partially overlapping) channels.
[0093] An AP MLD can communicate with any number of non-AP MLDs. For example, device 106 can be a non-AP MLD. It should be understood that a non-AP MLD can use any number of various affiliated APs to communicate with an AP MLD. In other words, a non-AP MLD can operate on any number of links with AP MLDs. A non-AP MLD can have corresponding affiliated STAs for the corresponding links. Different non-AP MLDs can communicate with different and / or the same affiliated APs.
[0094] Figure 8An AP MLD 112 communicating with a non-AP MLD 106 is shown according to some implementation schemes. In the example shown, the AP MLD and non-AP MLD can communicate using two links between the corresponding auxiliary AP and STA. It should be understood that additional links may be used as needed.
[0095] These two links may (e.g., at the time shown) operate under Enhanced Multi-Link Single Radio (EMLSR) and various other possibilities. EMLSR operation may be specified as an operating mode in the 802.11be specification. EMLSR enables a non-APMLD to share one or more full radios and one or more auxiliary (e.g., partially capable, reduced capable, and / or limited capable) radios between two or more links, for example, those links being enabled for EMLSR. For example, a full radio may be switched between multiple EMLSR-enabled links. The full radio and auxiliary radios may be physically different radios within the same MLD. Various possible changes and / or additions to EMLSR may be discussed further below.
[0096] EMLSR mode enables a non-AP MLD with the following configuration to transmit and / or receive two or more spatial streams on either of an enabled link (e.g., whenever the channel medium on that link becomes available). Examples include, but are not limited to:
[0097] • One full radio (e.g., 2x2 spatial stream (SS)) and one auxiliary radio (receive-only (RX))
[0098] • One full radio (e.g., 2x2) and one auxiliary radio (limited bandwidth (BW), throughput, and / or SS for transmit (TX) and RX)
[0099] According to 802.11be (e.g., draft D1.4), when operating in EMLSR mode, a non-AP MLD may be able to support Idle Channel Access (CCA) (e.g., Energy Detection (ED)) and be able to receive Initial Control Frames (ICFs) on all EMLSR links (e.g., typically two links, but possibly more). ICFs can be transmitted at rates of 6, 12, or 24 Mbps and in various possibilities in one or more Orthogonal Frequency Division Multiplexing (OFDM) Physical Protocol Data Units (PPDUs) or non-HT replicated PPDUs (e.g., via the AP MLD). An ICF can be a multi-user (MU) request triggered by a Transmit (RTS) (MU-RTS) or Buffer Status Report Polling (BSRP) frame. An ICF can also be an instruction from the AP MLD to a non-AP MLD to switch the full radio from one EMLSR link to another.
[0100] In some implementations, the ICF can be used only for DL (e.g., not for UL) transmissions for EMLSR operations. For example, a non-AP MLD can freely switch between links during EMLSR for UL transmissions.
[0101] The AP MLD and non-AP MLD can exchange configuration information about the EMLSR, including various parameter values. The non-AP MLD can indicate the ICF fill duration, and the non-AP MLD can indicate the EMLSR transition delay. The ICF fill duration indicates the amount of time the ICF can be filled, so the non-AP MLD can switch the full radio from another link to the link on which the ICF is being transmitted, and be ready to transmit response frames to the ICF (e.g., Clear Transmission (CTS)) (e.g., on a link after a link switch due to the ICF). The EMLSR transition delay indicates the amount of time the non-AP MLD needs between the end of the frame exchange sequence and the non-AP MLD switching back to the EMLSR link for listening operations. The AP MLD can indicate the EMLSR transition timeout (e.g., the amount of time the AP MLD needs to enter / exit EMLSR mode). Configuration information including these indications can be transmitted at communication establishment, during association, when EMLSR is enabled, or as discussed elsewhere herein.
[0102] During a frame switching sequence (e.g., after an ICF), a non-AP MLD may communicate with an APMLD only on the link that received the ICF. When the non-AP determines that the frame switching sequence has ended, the non-AP MLD may begin using another EMLRD link immediately following the EMLRD transition delay after the end of the frame switching sequence.
[0103] Only one STA of a non-AP MLD corresponding to one EMLSR link can initiate frame exchange with the AP MLD at any given time. In some implementations, a non-AP MLD may not have more than one STA to initiate frame exchange sequences with the AP MLD simultaneously on more than one link.
[0104] Figure 9 The diagram illustrates a possible timeline of EMLSR operation for non-AP MLDs according to some implementation schemes, showing a comparison with... Figure 8The same sequence of events. As shown, the full radio can initially operate on link 1 (connecting AP1 and STA1), while the auxiliary radio can operate on link 2. The non-AP MLD can perform CCA on both links. The AP MLD can perform CCA on both links. The AP MLD can determine that the channel used for link 1 is busy. The AP MLD can transmit an ICF (e.g., on link 2). In response to receiving an ICF, the non-AP MLD can switch the full radio to the second link (the auxiliary radio may or may not switch to link 1). In some respects, the padding time can be considered part of the ICF, for example, the ICF can be made longer by adding padding.
[0105] The non-AP MLD may first transmit a response frame to the ICF. Subsequently, the non-AP MLD may receive downlink traffic or perform a triggered UL transmission on Link 2 (e.g., using a full radio, labeled as using 2SS).
[0106] Figure 10 Further details of DL operations using EMLSR according to some implementation schemes are shown. Similar to Figure 8 and Figure 9 The full radio can initially be on Link 1. The AP MLD can determine that the channel used for Link 1 is busy and transmit an ICF (in the form of a MU-RTS on any number of sub-channels (e.g., 4 sub-channels in the example shown)) on Link 2. It is worth noting that the non-AP MLD can only receive MU-RTS on narrowband (e.g., depending on the capabilities of the auxiliary radio). However, the non-AP MLD can identify MU-RTS as an ICF. Therefore, the non-AP MLD can switch the full radio to Link 2 in response to MU-RTS / ICF. After the fill time (e.g., after the handover is complete), the non-AP MLD can perform CCA on each sub-channel of Link 2 using the full radio. After the Short Interframe Spacing (SIFS), the non-AP MLD can transmit a Clear Transmission (CTS) on any sub-channel of Link 2 that is determined to be idle. After the second SIFS, the non-AP MLD can exchange data with the AP MLD on Link 2 using the full radio. For example, a DL transmission can use the full BW and / or many SS of the full radio. Additionally, (for example,) triggered (TB)PPDU-based UL transmissions can be performed using a full radio via a non-AP MLD in response to a trigger frame transmitted by an AP MLD.
[0107] EMLSR operations for DL at a non-AP MLD may include: receiving an ICF (e.g., MU-RTS) on a link with an auxiliary radio (e.g., link 2), and switching the full radio via the end (padding) of the MU-RTS to allow full BW CCA during SIFS. Note: The EMLSR non-AP MLD may inform the AP MLD of the padding length (e.g., a value between 0 and 256 µs).
[0108] Figure 11 Further details of UL operation using EMLSR according to some implementation schemes are shown. Similar to Figures 8 to 10 The full radio can initially be on Link 1. EMLSR operations for UL at the non-AP MLD may include: Clear Channel Assessment (CCA), Enhanced Distributed Channel Access (EDCA) (e.g., which may include CCA), and Network Allocation Vector (NAV) support on the link with the auxiliary radio (e.g., Link 2). The non-AP MLD may determine (e.g., during EDCA) that the channel for Link 1 is busy. In response, the non-AP MLD may switch the full radio to Link 2 (e.g., without receiving ICF / MU-RTS from the AP MLD). Note that, according to some implementations, ICF may be used for triggered UL transmissions but not for other types of UL transmissions. The switchover may occur during an ongoing Arbitrary Interframe Space (AIFS) associated with Link 2. When uplink transmission begins, the non-AP MLD may immediately complete the full-bandwidth CCA using the full radio during the Point Coordination Function (PCF) Interframe Space (PIFS) immediately before the EDCA countdown reaches 0. After PIFS, the AP MLD may use the full radio to transmit using up to the full bandwidth of Link 2.
[0109] For EMLSR UL TX, there may be no radio handover time requirement; however, some specific implementations may attempt to minimize radio handover delay in order to minimize channel blind periods.
[0110] Figure 12EMLSR enabling and disabling according to some implementation schemes are illustrated. As shown, a non-AP MLD can use three links to associate with an AP MLD. Links 1 and 2 can be indicated to enable EMLSR during ML association (e.g., and provide associated capabilities). EMLSR operation can be disabled after association (e.g., by default). A non-AP MLD can request EMLSR enabling via an indication on Link 2 (e.g., transmission of an EML operation mode notification frame with mode = 1). After the EMLSR transition timeout, at time 1201, EMLSR can be enabled and can remain enabled until time 1202 (e.g., for all times within the frame). Immediately following EMLSR enabling at time 1201, the STAs of the non-AP MLDs on both links can be in active mode (e.g., power saving mode (PM) = 0) to be ready to receive ICF. A non-AP MLD can request EMLSR disabling via an indication on either link (e.g., Link 1 in the example) (e.g., transmission of an EML operation mode notification frame with mode = 0). After the EMLSR transition timeout, the EMLSR can be disabled at time 1202. At this time, non-APMLD STAs on both links can be in power-saving mode (PM=1).
[0111] Figure 13A The diagram illustrates EML capability subfields that may be included in ML elements according to some implementation schemes. During ML (re)association, EMLSR mode may be disabled (e.g., by default), and the following EMLSR operation parameters may be included in the "ML element" within the ML association frame:
[0112] "EMLSR padding delay" (e.g., representing the duration of "padding" shown as such in the various figures herein, which may be, for example, the time it takes for a non-AP MLD to switch full radio between links upon receiving an ICF / MU-RTS transmitted by an AP MLD) and "EMLSR transition delay" (e.g., representing the time it takes for a non-AP to switch back to listening operation on both links (to prepare for receiving the next ICF) after frame switching (e.g., TXOP) has ended) can be transmitted from the non-AP MLD to the AP MLD; and
[0113] "EMLSR transition timeout" (e.g., indicating that when an EML Operation Mode Notification (EOMN) frame is received on the first link, the AP MLD provides the energy-saving status of the second link and the time for other possible processing to prepare for entering or exiting EMLSR mode) can be transmitted from the AP MLD to the non-AP MLD.
[0114] In addition to the EMLSR parameters, the EML capability subfield may include parameters related to Enhanced Multi-Link Multi-Radio (EMLMR) operation.
[0115] Figure 13A It reflects all aspects of draft D1.4 of 802.11be. Figure 13B It shows something similar to Figure 13A The EML capability subfield, which is updated according to various aspects of 802.11be draft D2.2.
[0116] Figure 14A The EML control field of an EML Operation Mode Notification (EOMN) frame according to some implementation schemes is shown. After association, a non-AP MLD can transmit an EOMN frame in which the "Mode" is set to 1 or 0, respectively, to enable or disable EMLSR mode. Within the EOMN frame, the non-AP MLD can use an "EMLSR Link Bitmap" to indicate the link used for EMLSR operation.
[0117] Figure 14A It reflects all aspects of draft D1.4 of 802.11be. Figure 14B It shows something similar to Figure 14A The EML control fields, which are updated according to various aspects of 802.11be draft D2.2.
[0118] Figure 15 The Very High Throughput (EHT) action field of an EHT action frame according to some implementation schemes is shown. In an EHT action frame, an EHT action field value equal to 1 indicates that the EHT action frame is an EML operation mode notification frame. The values shown can be consistent with the EHT action field values in Table 9-623a-802.11be_D1.4.
[0119] Figure 16 The Extremely High Throughput (EHT) Action field of an EHT Action frame according to some implementation schemes is shown. An EHT Action frame for an EML Operation Mode Notification frame includes a Category field, an EHT Action field, a Dialogue Token field, and an EML Control field. The values shown may be consistent with the EHT Action field values in Table 9-623a-802.11be_D1.4.
[0120] Figure 17A Examples of implementation schemes are shown. Figure 14A and Figure 14B Further details of the EML control field in the EOMN frame. Bit 0 (e.g., B0 (EMLSR mode)) can indicate whether a non-AP is operating in EMLSR mode (e.g., B0=1) or not in that mode (e.g., B0=0).
[0121] An EHT action frame can be a term describing a group of frame types, where an EOMN frame is one type of EHT action frame. Different EHT action frames can have different values, for example, such as... Figure 15 As shown. According to some implementations, the EOMN may include a category field, an EHT action field, a dialogue token field, and an EML control field, for example, such as... Figure 16 As shown. The format of the EML control field can be as follows: Figure 17A As shown.
[0122] Figure 17A It reflects all aspects of draft D1.4 of 802.11be. Figure 17B It shows something similar to Figure 17A The EML control fields, which are updated according to various aspects of 802.11be draft D2.2.
[0123] Figure 18 —Including the suspension and renewal of multi-link single radio operations
[0124] Under the current 802.11 standard, there may be a lack of mechanisms to allow EMLSR operation to be suspended (e.g., paused) for a specific period of time when EMLSR is enabled, and / or to allow the updating of specific EMLSR operation parameters after association. When EMLSR is enabled, there may be situations where pausing (e.g., temporary suspension) of EMLSR operation could be useful. For example, a non-AP MLD may be unavailable on any EMLSR link due to traffic from another RAT in the same device (e.g., interference from Bluetooth coexistence, etc.). Some EMLSR operation parameters can be changed, and updates after (re)association may be useful. For example, the EMLSR bitmap, EMLSR padding delay, and / or EMLSR transition delay can be updated as discussed below.
[0125] According to some implementations, the embodiments described herein provide systems, methods, apparatus, and devices that can be used to enable the abort of EMLSR operation when needed and / or allow flexible updates to EMLSR operation parameters. For example, according to Figure 18 In the implementation scheme, AP MLD and non-AP MLD can exchange various messages related to EMLSR operation, abort and / or parameters. Figure 18 The implementation scheme allows for the temporary suspension of EMLSR operation when EMLSR mode is enabled. Furthermore, relevant parameters relative to existing specifications can be added, such as EMLSR suspension timeout (notified by the AP MLD, e.g., the time required by the AP MLD to prepare to initiate suspension (e.g., but not limited to providing energy-saving status for the second link when an EMLSR suspension request is transmitted by a non-AP MLD on the first link) and EMLSR suspension duration (indicated by the non-AP MLD for some types of suspension). Additionally, specific EMLSR operation parameters can be established during the EMLSR enable and restore process, rather than during the association process.
[0126] Figure 18 Aspects of the method can be implemented by an AP MLD communicating with a non-AP MLD. The AP MLD and / or non-AP MLD may be shown and described as in the various figures herein, or more generally, may be shown 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 MLD, and / or AP MLD or other device to perform this method element.
[0127] It should be noted that, although described in a manner relating to the communication technologies and / or features associated with IEEE and / or 802.11 (e.g., 802.11be) specification documents. Figure 18 This description includes at least some elements of the method, but such a 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.
[0128] Among other devices, the method shown can be used in conjunction with any of the systems, methods, or devices shown in the figures. 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 in the figure, the method can operate as follows.
[0129] According to some implementations, non-AP MLD 106 and AP MLD 112 can establish communication (1802). For example, the AP MLD can provide one or more links (e.g., via one or more affiliated APs), and the non-AP MLD can be associated with the AP MLD via at least one of these links (e.g., using at least one affiliated STA).
[0130] AP MLDs can exchange configuration information with non-AP MLDs, such as configuration information related to the use of various links and / or EMLSRs. Configuration information may include information such as the identifier of the AP MLD and / or network (e.g., SSID, etc.). Some configuration information may relate to link mapping and usage; others may relate to other topics.
[0131] Configuration information may include parameters for EMLSR operation, such as timing parameters. For example, the AP MLD may indicate timeout values (e.g., EMLSR transition timeout or EMLSR abort timeout). The non-AP MLD may indicate EMLSR fill delay, EMLSR transition delay, and / or EMLSR bitmap.
[0132] Configuration information can be transmitted in one or more messages, including EML capability subfields and various other possibilities.
[0133] AP MLD can provide configuration information via beacons or other messages. For example, AP MLD can broadcast default mappings in a beacon to all STAs within AP MLD's communication range or to all STAs associated with AP MLD. AP MLD can also transmit individual configuration information, such as mappings, via separate beacons or messages.
[0134] According to some implementation schemes, a non-AP MLD can determine entry into the EMLSR (1804). A non-AP MLD can determine entry into the EMLSR at any time after being associated with an APMLD. For example, a non-AP MLD can determine entry into the EMLSR immediately or at a slightly later time after association.
[0135] According to some implementations, a non-AP MLD may transmit a message (e.g., an EOMN management frame) to an AP MLD indicating entry into the EMLSR (1805). This message may include an EMLSR bitmap indicating which links will enter the EMLSR.
[0136] In some implementations, the message may also indicate one or more parameters related to the potential termination of the EMLSR. For example, the message may indicate the type of termination that can be used (e.g., at a future time) for the EMLSR session.
[0137] In some implementations, the message may be formatted as shown in or similar to one or more of the accompanying drawings. For example, the message may include aspects of one or more of the drawings in Figures 13 to 17 and / or Figures 29 to 36, as well as various other possibilities.
[0138] In some implementations, messages for suspending or resuming EMLSR operation may consist of other frame types (such as control frames) and / or be included in the MAC or PHY header of a data frame.
[0139] According to some implementation schemes, non-AP MLDs can enter the EMLSR after the EMLSR transition timeout (measured from the time of the message).
[0140] According to some implementations, the AP MLD can determine to enter EMLSR mode (e.g., relative to a non-AP MLD) (1806). This determination can be made in response to receiving a message from a non-AP MLD. According to some implementations, the AP MLD can enter EMLSR after an EMLSR transition timeout (measured from the time of the message).
[0141] In some implementations, the AP MLD may determine to enter EMLSR mode (e.g., relative to the non-AP MLD, it should be noted that the AP MLD may continue to communicate with other STAs as needed). The determination to enter EMLSR mode may be based on an indication provided by the non-AP at an earlier time. For example, the AP MLD may transition to the EMLSR for the non-AP MLD at a pre-configured time following association, as indicated by the non-AP MLD. It should be understood that entering EMLSR can be done by sending an EOMN frame or initiated by the non-AP MLD at the pre-configured time. The non-AP MLD and AP MLD may enter EMLSR at the same (e.g., pre-configured and / or based on transition timeout) time or at different times.
[0142] According to some implementations, the non-AP MLD 106 and AP MLD 112 can operate according to EMLSR (1807). For example, the non-AP MLD can initially use a full radio on a first link with an AP MLD and a secondary radio on a second link. Compared to the secondary radio, the full radio may be able to have more spatial streams, wider BW, more duplex, and / or otherwise higher performance. The non-AP MLD can switch the full radio between links any number of times from the AP MLD. For a frame exchange sequence initiated by the AP MLD, if the full radio is not already on a link on which the AP MLD transmits ICFs, it can be switched to that link. For a frame exchange sequence initiated by the non-AP MLD, if the full radio is not already on a link selected by the non-AP MLD (e.g., for transition), it can be switched to that link. UL and / or DL communication can be performed.
[0143] According to some implementations, the non-AP MLD can determine to terminate the EMLSR (1808). The non-AP MLD can determine to terminate the EMLSR in response to ongoing and / or anticipated activity at the non-AP MLD. For example, the non-AP MLD can determine to terminate the EMLSR based on communication activity of another RAT (such as Bluetooth). As a possibility, if ongoing or scheduled communication activity of another RAT may interfere with communication (e.g., Wi-Fi) on the EMLSR link, the non-AP MLD can determine to terminate the EMLSR mode (e.g., and terminate some or all communication on the EMLSR link). In other words, terminating the EMLSR allows the non-AP MLD to perform communication on another RAT while EMLSR communication is suspended, thus avoiding / reducing coexistence interference between RATs. When the EMLSR mode is terminated, the non-AP MLD can remain in power-saving mode for the entire duration.
[0144] A non-AP MLD can determine one or more parameters related to the termination. For example, a non-AP MLD can determine the expected termination duration based on any available information about communication activity of another RAT. Similarly, a non-AP MLD can determine the preferred type of termination (e.g., fixed or variable duration). In some embodiments, a non-AP MLD can determine the preferred start and / or end times for the termination.
[0145] According to some implementations, a non-AP MLD may transmit a requested abort message and / or indication to the AP MLD (1809). For example, when EMLSR is enabled, a non-AP MLD may transmit an EMLSR abort request frame to the AP MLD to request the abort (e.g., suspension) of EMLSR operation. This message may be transmitted on one or more of these EMLSR links. In some implementations, the message may be transmitted on a different link (e.g., different from these EMLSR links or other than these EMLSR links). Before transmitting the message, the non-AP MLD may determine that the channel used for transmission is idle (e.g., CCA, EDCA, etc.) and / or otherwise follows channel access rules.
[0146] This message may include indications of any parameters related to EMLSR or abortion. For example, the indication may include the timing (e.g., start, stop, and / or duration) and / or type (e.g., fixed duration (Type 1) or variable duration (Type 2)) of the abortion. For instance, under Type 1 abortion, the fixed duration of the aborted EMLSR may be included in the EMLSR abortion request frame. For Type 2 abortion, a non-AP MLD may transmit an EMLSR recovery request frame to end the abortion and resume EMLSR operation.
[0147] In some embodiments, the message including these indications may be formatted as shown in or similar to one or more of the accompanying drawings. For example, the message may include aspects of one or more of the drawings in Figures 13 to 17 and / or Figures 29 to 36, as well as various other possibilities.
[0148] In some implementations, messages including these indications may consist of other frame types (such as control frames) and / or be included in the MAC or PHY header of a data frame.
[0149] According to some implementations, non-AP MLD 106 and AP MLD 112 can abort EMLSR (1810). In some implementations, EMLSR operation can be aborted (e.g., suspended) at the earliest possible time thereafter.
[0150] EMLSR operation can be aborted after a period of time equal to the elapsed "EMLSR abort timeout" following the successful transmission of the EMLSR abort request frame. Figure 20 The timing is shown according to some implementation schemes.
[0151] It should be understood that a successful transmission (e.g., an EMLSR abort request frame) may include receiving an acknowledgment (ACK) of the transmission. Therefore, according to some implementations, the time period measured from a successful transmission can be considered to begin upon receiving such an ACK.
[0152] EMLSR operation can be aborted after the non-AP MLD has received a response to the EMLSR abort request from the AP MLD (e.g., an EMLSR abort request response frame). Figure 21 This timing is shown according to some implementation schemes. Note that, as shown in the figure, this can be achieved as follows: Figure 20 The "EMLSR abort timeout" occurred before it was completed (e.g., in...). Figure 21 In this context, the duration between B and C may be less than the EMLSR abort timeout. Furthermore, it should be noted that the AP MLD can determine not to transmit such a response and may alternatively allow the EMLSR to continue until the abort timeout is complete.
[0153] EMLSR operation can be aborted based on indications that a transmission has been activated or entered power-saving mode for a different EMLSR link. Figure 22This timing is illustrated according to some implementation schemes. For example, after transmitting an EMLSR abort request frame on an EMLSR link (e.g., link 2), a non-AP MLD can switch its full radio to another EMLSR link (e.g., link 1), win channel access on that other link (e.g., link 1), and successfully transmit a frame on that other link (e.g., link 1) in which the power management (PM) bit (e.g., power saving mode) is set to 1 (e.g., PM=1). For example, the PM bit may be located in the frame control field of the frame's MAC header. The AP MLD can acknowledge the frame, and abort can begin (e.g., before the abort timeout completes). For example, in Figure 22 In this case, the duration between B and C can be less than the EMLSR abort timeout. Furthermore, it should be noted that if the acknowledgment transmitted by the AP MLD is not successfully received by the non-AP MLD, EMLSR operation can continue until the abort timeout is complete. Note: This non-AP MLD method can also be used to shorten the time a non-AP STA takes to exit EMLSR mode after successfully transmitting an EOMN frame (where the mode is set to 0) to request EMLSR disabling.
[0154] Figure 23 This illustrates energy-saving behavior associated with the start of EMLSR termination (e.g., the time when the link can enter energy-saving mode) according to some implementation schemes. Time B and Time C are referenced. Figures 20 to 22 As shown in the figure, STAs attached to non-AP MLD links can enter power-saving mode at different times depending on whether the power management (PM) bit in the frame control field of the MAC header of the EMLSR abort request frame is set to 1 or 0. When the PM bit in an EMLSR abort request frame sent on one link (e.g., link 2) is set to 1, an STA attached to a non-AP MLD on the same link (e.g., link 2) can enter power-saving mode at time B, and an STA attached to a non-AP MLD on another link (e.g., link 1) can enter power-saving mode at time C (e.g., when the abort begins). When the PM bit in an EMLSR abort request frame sent on one link (e.g., link 2) is set to 0, an STA attached to a non-AP MLD on the same link (e.g., link 2) can enter power-saving mode at time C (e.g., when the abort begins), and an STA attached to a non-AP MLD on another link (e.g., link 1) can also enter power-saving mode at time C (e.g., when the abort begins). After the CEMLSR was terminated, both STAs attached to the non-AP MLD on the two EMLSR links were in power-saving mode.
[0155] After the EMLSR is terminated, the two STAs attached to the non-AP MLD on the two EMLSR links remain in power-saving mode throughout the termination period, and the AP MLD can terminate / stop using the EMLSR links for downlink communication with the non-AP MLD. However, the AP MLD can continue to monitor the terminated EMLSR links for communication with the non-AP MLD.
[0156] During an EMLSR outage, non-AP MLDs and AP MLDs can use any other link (e.g., any active link that is not part of the outaged EMLSR link) to communicate. For example, if Link 1 and Link 2 are in the EMLSR and are outaged, non-AP MLDs and AP MLDs can use a third link (if available) to communicate.
[0157] According to some implementation schemes, non-AP MLD 106 and AP MLD 112 can determine the end time of EMLSR abortion (1812). The manner in which this determination can occur may depend on the type of abortion.
[0158] Figure 24 A fixed-duration (Type 1) abortion is illustrated according to some implementation schemes. For example, in the case of a fixed-duration (Type 1) abortion, both non-AP MLDs and AP MLDs can determine the end time based on instructions transmitted prior to the abortion (e.g., a duration associated with the abortion request, a default and / or specified duration, and / or otherwise previously agreed upon). In other words, EMLSR operation can be resumed after the pre-specified abortion duration.
[0159] As another possibility, in the case of a variable duration (Type 2) abortion, the non-AP MLD may transmit a message indicating the end of the abortion (e.g., an EMLSR recovery request) to the AP MLD. The message may be transmitted on one (e.g., or possibly multiple) EMLSR links. In some implementations, the message may be transmitted on a different link (e.g., different from or other than the one or more EMLSR links). Before transmitting the message, the non-AP MLD may determine that the channel used for transmission is idle (e.g., CCA, EDCA, etc.) and / or otherwise follows channel access rules.
[0160] In some implementations, the message indicating termination may be formatted as shown in or similar to one or more of the accompanying drawings. For example, the message may include aspects of one or more of the drawings in Figures 13 to 17 and / or Figures 29 to 36, as well as various other possibilities.
[0161] In the case of a variable duration (Type 2) abort, depending on some implementations, the EMLSR operation can be resumed at the earliest possible time thereafter.
[0162] Figure 25 The fixed duration of the message indicating the end of the abort is shown according to some implementation schemes. EMLSR operation can be resumed after the successful transmission of the EMLSR recovery request frame, when the time period equal to the elapsed "EMLSR abort timeout" has elapsed.
[0163] Figure 26 The diagram illustrates the termination of an abort based on a response from the AP MLD, according to some implementations. EMLSR operation can be resumed when the non-AP MLD has received an EMLSR recovery request response from the AP MLD. In other words, the AP MLD can receive the request and transmit a response. Both the AP MLD and the non-AP MLD can resume EMLSR when the response is successfully transmitted from the AP MLD to the non-AP MLD. In some implementations, successful transmission can be determined when the AP MLD successfully receives an acknowledgment (ACK) transmitted by the non-AP MLD. It should be noted that for 802.11 devices, a frame can be considered successfully transmitted if the transmitter receives an ACK from its peer. This time can be less than a timeout, for example, in... Figure 26 In this context, the duration between D and E may be less than the EMLSR abort timeout. It should be understood that an AP MLD may not be required to transmit a response. In other words, the AP MLD determines whether an abort timeout is permitted to continue and resume the EMLSR after the EMLSR abort timeout.
[0164] Figure 27 This illustrates the termination of signaling notification on different links according to some implementation schemes. When on one link (e.g., an EMSLR link, such as...) Figure 27 After transmitting an EMLSR recovery request frame on link 2), the non-AP MLD switches its full radio to another EMLSR link (e.g., link 1), wins channel access on that link (e.g., link 1), and resumes EMLSR operation when it successfully transmits a frame on that link (e.g., link 1) in which the power management (PM) bit (e.g., power saving mode) is set to 1 (e.g., PM=1). The AP MLD can acknowledge the frame, and the abort can be terminated (e.g., before the abort timeout completes). Figure 27In this context, the duration between D and E can be less than the EMLSR abort timeout. Furthermore, it should be noted that if the acknowledgment transmitted by the AP MLD is not successfully received by the non-AP MLD, the EMLSR abort may continue until the abort timeout completes. In other words, the non-AP MLD can terminate the abort by using a different EMLSR link to transmit frames (e.g., frames with information and / or control information) that include indications for that link to exit or disable power-saving mode (e.g., indicating that the link is in active mode (e.g., for use with a non-AP MLD)). Note: This method for non-AP MLDs can also be used to shorten the time it takes for a non-AP MLD to enter EMLSR mode after successfully transmitting an EOMN frame (where the mode is set to 1) to request EMLSR activation.
[0165] Figure 28 This illustrates energy-saving behavior associated with the end of EMLSR termination (e.g., the time when the link can enter active mode) according to some implementation schemes. Time D and Time E are referenced. Figures 25 to 27 As shown in the figure, STAs attached to non-AP MLD links can exit power-saving mode at different times depending on whether the power management (PM) bit in the frame control field of the MAC header of the EMLSR recovery request frame is set to 1 or 0. When the PM bit in an EMLSR request frame sent on one link (e.g., link 2) is set to 1, an STA attached to a non-AP MLD on the same link (e.g., link 2) can exit power-saving mode at time E (e.g., when the abort ends), and an STA attached to a non-AP MLD on another link (e.g., link 1) can also exit power-saving mode at time E (e.g., when the abort ends). When the PM bit in an EMLSR recovery request frame sent on one link (e.g., link 2) is set to 0, an STA attached to a non-AP MLD on the same link (e.g., link 2) can exit power-saving mode at time D, and an STA attached to a non-AP MLD on another link (e.g., link 1) can exit power-saving mode at time E (e.g., when the abort ends). After the EMLSR operation is restored at time E, the two STAs attached to the non-AP MLD on the two EMLSR links can be in active mode.
[0166] According to some implementations, non-AP MLD 106 and AP MLD 112 can recover EMLSR (1814) and return to EMLSR operation (1807). The EMLSR parameters can be the same (e.g., relative to the parameter values before abort).
[0167] In some implementations, one or more parameters of EMLSR operation can be changed (e.g., relative to their values before abort). For example, a message requesting abort or resumption of EMLSR may indicate such a changed parameter value. Such updates to parameter values can be initiated by either a non-AP MLD or an AP MLD.
[0168] According to some implementation plans Figure 18 The methods enable the termination of EMLSR operations and / or allow for flexible updates to EMLSR operation parameters.
[0169] Figures 19 to 3 6 and additional information .
[0170] It should be noted that EOMN frames (e.g., which can be transmitted to enable EMLSR) can also be used to transmit and / or update parameters not selected by APSTA, such as EMLSR padding delay, EMLSR transition delay, and EMLSR bitmap. A single EOMN frame can be used to perform any or all of these purposes. Alternatively, different EOMN frames can be used. Furthermore, instead of using EOMN management frames, transmission and / or updates can use one or more other frame types (such as control frames) and / or be included in the MAC or PHY header of the data frame.
[0171] Figure 19 The timeline for EMLSR abortion according to some implementation schemes is shown. As shown, EMLSR can be enabled at time A (e.g., after an EOMN frame where the mode is set to 1) and can remain enabled until time F (e.g., based on a second EOMN frame where the mode is set to 0). The time between EOMN (where the mode is set to 1) and the start of EMLSR enabling can be less than or equal to the EMLSR transition timeout period. The time between EOMN (where the mode is set to 0) and the end of EMLSR enabling can be less than or equal to the EMLSR transition timeout period. EMLSR can be aborted from time C to time E. Time C can occur after an EMLSR abortion timeout less than or equal to the abortion request at time B. In the case of type 2 abortion, time E can occur after an EMLSR abortion timeout less than or equal to the successful transmission of an EMLSR recovery request frame at time D. In the case of type 1 abortion, time E can occur for a fixed duration after time C.
[0172] In some implementations, various frame types can be used to include EMLSR abort requests and / or EMLSR recovery requests, or similar messages as discussed herein. Various lengths of the relevant fields can be configured as needed. The field lengths shown in the figures and description are merely examples. However, for illustrative purposes, various examples of frames that can be used to transmit EMLSR abort requests and / or EMLSR recovery requests are discussed and shown. Additional parameters necessary for EMLSR operation may also be included in these frames.
[0173] As one possibility, the frame could be a revised version of the EOMN frame in 11be_D1.4 (see Figures 29 to 2014). Figure 33 For example, as shown in Figure 29 for one example and for another example Figure 31A and Figure 31B As shown, the "EMLSR mode" field can be extended from 1 bit to 2 bits, such as... Figure 30 As shown, the following new modes are included: "EMLSR Abort Request" mode and "EMLSR Resume Request" mode.
[0174] As another possibility, a new management frame for EHT action management frames can be defined, in which... Figure 34 (For example, an EHT action field with a newly defined value "2" or another currently reserved value) and Figure 35 An exemplary design is shown in (e.g., a newly defined EMLSR abort control field). According to some embodiments, in the methods shown in these figures, new management frames may be added, which can be used (e.g., separately) for EMLSR abort requests and EMLSR recovery requests, while existing EOMN frames can be used for EMLSR enabling or disabling. Additional parameters necessary for EMLSR operation may also be included in these frames.
[0175] Figure 29A , Figure 29B , Figure 31A and Figure 31B Possible structures for EML control fields according to some implementations are shown, such as those that may be included in a revised EOMN frame. These figures illustrate revisions to 9-144i relative to 802.11be (draft 1.4). Figure 30 The meaning of the extended (e.g., 2-bit) EMLSR pattern field is shown.
[0176] In addition to parameters for EMLSR abortion and EMLSR recovery, Figure 29A , Figure 29B , Figure 31A and Figure 31BThis can also be an exemplary design for using revised EOMN frames to transmit and / or update EMLSR operation parameters during EMLSR enabling and / or EMLSR abortion or EMLSR recovery periods. Examples of such EMLSR operation parameters are EMLSR bitmaps, EMLSR padding delay, and EMLSR transition delay. When EMLSR mode = 1 or 3, the EMLSR padding delay and EMLSR transition delay can indicate the EMLSR operation parameters used for the currently enabled / recovered EMLSR session. According to some embodiments, when EMLSR mode = 0 or 2, the EMLSR padding delay and EMLSR transition delay can be retained. In some embodiments, the values 1 and 3 of the EMLSR mode can be combined into a single value (e.g., 1, for example, to enable or recover EMLSR), and the value "3" is left as a reservation. According to some embodiments, Figure 29A , Figure 29B , Figure 31A and Figure 31B Additional bits in the EML control field may be reserved (e.g., up to and including B31).
[0177] Figure 29A and Figure 31A It reflects various aspects of draft 802.11be D1.4 and other contents. Figure 29B and Figure 31B It shows something similar to Figure 29A and Figure 31A The EML control fields, which are updated according to various aspects of 802.11be draft D2.2.
[0178] Figure 32A Another possible structure for the EML control field according to some implementations is shown, for example, as it may be included in a revised EOMN frame. These figures illustrate revisions to 9-144i relative to 802.11be (draft 1.4). In the example shown, the EMLSR mode field may be 1 bit and may use data from... Figure 30 The meaning of values 0 and 1. However, in other implementations, the EMLSR pattern field can be 2 bits and can use the values as described above relative to... Figure 30 The meaning of the values 0 to 3 discussed. Additionally, the new EMLSR abort pattern field (the meaning of which is...) Figure 33 (as described in the text) may include in Figure 32A The example EML control field shown in the figure.
[0179] Figure 32A It reflects various aspects of draft 802.11be D1.4 and other contents. Figure 32B It shows something similar to Figure 32A The EML control fields, which are updated according to various aspects of 802.11be draft D2.2.
[0180] Figure 33 The following are illustrated according to some implementation schemes. Figure 32A and Figure 32B The possible meanings of the EMLSR abort mode field. When the EMLSR abort mode = 0 (e.g., abort request), various fields can indicate information about the abort. For example, the EMLSR abort type field (B17) can indicate the type of abort (e.g., fixed duration (type 1) or variable duration (type 2)). Similarly, B21 to B23 can carry information about the duration of the EMLSR abort (e.g., for type 1 abort). Additional parameters necessary for EMLSR operation may also be included.
[0181] Figure 34 and Figure 35 An example of a newly defined EHT action frame is shown, in which a new value 2 (e.g., the current reserved value) can be added to the EHT action field in the EHT action frame. Note that a different current reserved value can be used instead of the current reserved value 2. Such a new EHT action frame can be used (e.g., alone) for EMLSR abort and EMLSR recovery. Figure 34 Possible revisions to Table 9-623a (relative to 802.11be, draft 1.4) according to some implementations are shown, describing additional EHT action field values used for EMLSR abortion and EMLSR recovery. In an EHT action frame, the EHT action field, in the eight-bit byte immediately following the category field, distinguishes different EHT action frames. As shown, new meanings can be associated with values (e.g., 2 or another currently reserved value) to indicate the EHT action frame associated with EMLSR abortion that can be used. Figure 35 The new EHT abort control field is shown, which is included in the newly designed EHT action frame for entering or exiting EMLSR abort. In other words, the new EHT action frame can be signaled by adding a new value (e.g., 2 or another currently reserved value) for the EHT action field in the EHT action frame (which can be used only for EMLSR abort control). Figure 35The new EMLSR abort control field shown includes parameters related to EMLSR abort, such as EMLSR abort mode, abort type, and EMLSR abort duration (if type 1 abort is used). The abort type and EMLSR abort duration fields can be reserved for EMLSR recovery requests. Therefore, the EMLSR abort EHT action frame can be used to request abort of EMLSR operation and / or (e.g., at a separate time) resume EMLSR operation after abort. It should be understood that various designs can be used. However, in the example shown, the EMLSR abort mode B0 value can have the following meanings: 1 indicates an EMLSR abort request, and 0 indicates an EMLSR recovery request. Although in Figure 35 The example shown may not be explicitly shown, but this new EMLSR abort control field may also include parameters such as the EMLSR bitmap, EMLSR fill delay, and EMLSR transition delay. Therefore, these parameters can be transferred and / or updated when EMLSR operation resumes after an abort. Other EMLSR parameters may also be included in the new EMLSR abort control field.
[0182] Figure 36A The diagram illustrates possible message designs for indicating an EMLSR abort timeout, according to some implementation schemes. The indication of the duration of the "EMLSR abort timeout" may be included in the "EML Capability Field" of the ML element to be transmitted during the (re)association process (see [link to documentation]). Figure 13A and Figure 13B (used for comparison). For example, such as Figure 36A The EML capability subfield shown can be transmitted from the AP MLD to the non-AP MLD during the association or reassociation process, and can indicate to the non-AP MLD the duration of the timeout for transition and abort. "EMLSR Fill Delay" and "EMLSR Transition Delay" can be transmitted in the frame to enable or resume EMLSR operation, such as... Figure 29A , Figure 29B , Figure 31A , Figure 31B , Figure 32A and Figure 32B The document illustrates three design examples and various possibilities. Including the "EMLSR fill delay" and "EMLSR transition delay" in frames transmitted to enable or restore EMLSR operation, rather than in frames transmitted during the association and / or reassociation process, allows non-APs to transmit and / or update these parameters after association and / or reassociation.
[0183] Figure 36A It reflects various aspects of draft 802.11be D1.4 and other contents. Figure 36B It shows something similar to Figure 36AThe possible message design for instructing EMLSR to abort timeout is updated according to various aspects of draft 802.11be D2.2.
[0184] In some scenarios, different EMLSR links can be assigned different roles, such as primary and secondary links. The primary / full radio can default to the primary link and can only switch to the secondary link when the primary link becomes unavailable and there is an opportunity for traffic exchange on one of the secondary links. When frame exchange is completed on the secondary link, the primary / full radio can switch back to the primary link. (See Figure 29 to...) Figure 33 In the example, all EMLSR links may share a common EMLSR padding delay value and a common EMLSR transition delay value. However, different links may have different (e.g., link-specific) EMLSR padding delays and EMLSR transition delays, for example, in scenarios where EMLSR links are assigned primary and secondary link roles and various other possibilities. For instance, link-specific EMLSR padding values and / or link-specific EMLSR transition delay values may be included in the EMLSR operation mode notification frame (or other container), each with an indication of the corresponding link identifier.
[0185] As is widely recognized, the use of personally identifiable information should comply with 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 should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.
[0186] In one set of implementations, a method may include: at a non-access point (AP) multilink device (MLD) (non-APMLD): associating with the AP MLD; exchanging one or more multilink parameters associated with a first mode for communicating with the AP MLD; enabling the first mode for a first link and a second link; transmitting a request to the AP MLD to abort the first mode without disabling the first mode; receiving acknowledgment from the AP MLD of the request to abort the first mode without disabling the first mode; aborting the first mode; and resuming the first mode.
[0187] In some implementations, in order to terminate the first mode, the method may further include entering an energy-saving mode for both the first and second links, wherein both the first and second links are in the energy-saving mode for at least a portion of the time when the first mode is terminated.
[0188] In some implementations, exchanging one or more multi-link parameters with the AP MLD includes receiving an indication of the duration of a first mode abort timeout, wherein the abort of the first mode occurs after a period of time equal to the duration of the first mode abort timeout, which begins from the confirmation of the request to abort the first mode without disabling the first mode.
[0189] In some implementations, the abort of the first mode occurs upon receiving a response from the AP MLD to a request to abort the first mode without disabling it.
[0190] In some implementations, a request to abort the first mode without disabling the first mode is transmitted on the first link at a first time, wherein the abort of the first mode occurs at a second time after the first time when a frame including an indication of an energy-saving mode enabled for the second link is successfully transmitted to the APMLD on the second link.
[0191] In some implementations, the method may also include sending a request to the AP MLD to resume the first mode.
[0192] In some implementations, the transmission of the request to resume the first mode is a successful transmission, wherein exchanging one or more multi-link parameters with the AP MLD includes an indication of the duration of the first mode abort timeout, wherein the resumption of the first mode occurs after a period of time equal to the duration of the first abort timeout from the successful transmission of the request to resume the first mode.
[0193] In some implementations, the recovery response of the first mode occurs upon receiving a response from the AP MLD to a request to restore the first mode.
[0194] In some implementations, a request to restore the first mode is transmitted on the first link at a first time, wherein the restoration of the first mode occurs at a second time after the first time by transmitting a frame to the AP MLD on the second link that includes an indication of a power-saving mode disabled for the second link.
[0195] In some implementations, the first mode includes Enhanced Multilink Single Radio (EMLSR).
[0196] In one set of embodiments, the method at a non-access point (AP) multilink device (MLD) (non-AP MLD) can be as follows. The non-AP MLD may include: a first radio component and a second radio component having less capability than the first radio component. The method may include: establishing communication with the AP MLD; transmitting to the AP MLD at least one parameter related to an Enhanced Multilink Single Radio (EMLSR) mode; operating according to the EMLSR mode for a first time period; suspending operation according to the EMLSR mode for a second time period after the first time period; and resuming operation according to the EMLSR mode after the second time period.
[0197] In some implementations, in order to suspend operation according to the EMLSR mode, the method may further include transmitting an enhanced EMLSR operation mode notification frame including a first enhanced multilink control field, the first enhanced multilink control field including a first EMLSR mode field having more than 1 bit, wherein the value of the first EMLSR mode field indicates a request to suspend operation according to the EMLSR mode.
[0198] In some implementations, the first enhanced multilink control field also includes an indication of the duration of the requested suspension of operation according to the EMLSR mode.
[0199] In some implementations, in order to resume operation according to the EMLSR mode, the method may further include transmitting an enhanced EMLSR operation mode notification frame that includes a second enhanced multilink control field, the second enhanced multilink control field including a second EMLSR mode field having more than one bit, wherein the value of the second EMLSR mode field indicates a request to resume EMLSR operation.
[0200] In some implementations, the second enhanced multilink control field also includes an indication of the filling delay for the current EMLSR session.
[0201] In some implementations, in order to abort operation according to the EMLSR mode, the method may also include transmitting a third enhanced multilink control field that includes the EMLSR abort mode field.
[0202] In some implementations, in order to abort operation according to EMLSR mode, the method may also include transmitting an Extremely High Throughput (EHT) action frame, which includes a value indicating a request to abort operation according to EMLSR mode.
[0203] In some implementations, at least one parameter related to the EMLSR mode includes link-specific indications for the first link and for the second link.
[0204] In one set of embodiments, a method may include: at an access point (AP) multilink device (MLD) (AP MLD): providing a plurality of links including at least a first link and a second link; associating with a non-access point MLD (non-AP MLD); exchanging with the non-AP MLD at least one parameter related to an enhanced multilink single radio (EMLSR) mode; receiving from the non-AP MLD on the first link or the second link a request to enter the EMLSR mode for the first link and the second link; receiving from the non-AP MLD on the first link or the second link a request to terminate the EMLSR mode for the first link and the second link; terminating the EMLSR mode for the first link and the second link for the non-AP MLD; determining, for the non-AP MLD, a time to resume the EMLSR mode for the first link and the second link; and resuming the EMLSR mode for the first link and the second link for the non-AP MLD.
[0205] In some implementations, the determination of the time to restore the EMLSR mode is based on receiving the EMLSR recovery request and the earliest time after the EMLSR abort timeout occurs after receiving the EMLSR recovery request; transmitting an EMLSR recovery request response; or receiving a frame with a power-saving mode bit indicating that the power-saving mode is disabled for the different link on a link different from the EMLSR recovery request.
[0206] For example, by interpreting each message / signal X received by a non-AP MLD in the DL as a message / signal X transmitted by the AP MLD, and interpreting each message / signal Y transmitted by a non-AP MLD in the UL as a message / signal Y received by the AP MLD, any method described herein for operating an AP MLD can serve as the basis for a corresponding method for operating a non-AP MLD (and vice versa). Furthermore, methods described relative to AP MLDs can be interpreted as methods for non-AP MLDs in a similar manner.
[0207] 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.
[0208] 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.
[0209] 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.
[0210] 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 disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.
Claims
1. A device for communication, comprising: Processor, the processor being configured to make the non-access point AP multilink device MLD non-AP MLD: Associated with AP MLD; Exchange one or more multilink parameters associated with a first mode for communicating with the AP MLD; The first mode is enabled for both the first and second links; Send a request to the AP MLD to abort the first mode without disabling the first mode; Receive confirmation from the AP MLD of the request to suspend the first mode without disabling the first mode; Abort the first mode; as well as The first mode is resumed after the suspension.
2. The apparatus of claim 1, wherein, in order to terminate the first mode, the processor is further configured to cause the non-AP MLD to enter a power-saving mode for the first link and for the second link, wherein both the first link and the second link are in the power-saving mode for at least a portion of the time when the first mode is terminated.
3. The apparatus of claim 1, wherein exchanging the one or more multi-link parameters with the AP MLD includes receiving an indication of the duration of a first mode abort timeout, wherein the abort of the first mode occurs after a time period equal to the duration of the first mode abort timeout, starting from the confirmation of the request to abort the first mode without disabling the first mode.
4. The apparatus of claim 1, wherein the termination of the first mode occurs after receiving a response from the AP MLD to the request to terminate the first mode without disabling the first mode.
5. The apparatus of claim 1, wherein the request to abort the first mode without disabling the first mode is transmitted on the first link at a first time, wherein the abort of the first mode occurs in response to a successful transmission of a frame to the AP MLD on the second link at a second time after the first time, the frame including an indication of an energy-saving mode enabled for the second link.
6. The apparatus of claim 1, wherein the processor is further configured to cause the non-AP MLD to transmit a request to the AP MLD to resume the first mode.
7. The apparatus of claim 6, wherein exchanging the one or more multi-link parameters with the AP MLD includes receiving an indication of the duration of a first mode abort timeout, and wherein the recovery of the first mode occurs after a time period equal to the duration of the first abort timeout following the successful transmission of the request to resume the first mode.
8. The apparatus of claim 6, wherein the restoration of the first mode occurs after the request to restore the first mode is received from the AP MLD.
9. The apparatus of claim 6, wherein the request to restore the first mode is transmitted on the first link at a first time, wherein the restoration of the first mode occurs in response to the transmission of a frame to the APMLD on the second link at a second time after the first time, the frame including an indication of a power-saving mode disabled for the second link.
10. The apparatus of claim 1, wherein the first mode comprises an enhanced multi-link single-radio EMLSR mode.
11. A non-access point AP multi-link device MLD (non-AP MLD), comprising: First radio component; A second radio component having capabilities different from the first radio component; and A processor, operatively coupled to the first radio component and the second radio component, and configured to cause the non-AP MLD: Establish communication with AP MLD; Transmit at least one parameter related to the enhanced multilink single radio EMLSR mode to the AP MLD; The operation is performed according to the EMLSR mode for the first time period; The operation according to the EMLSR mode is suspended for a second time period after the first time period; and After the second time period, operation according to the EMLSR mode is resumed.
12. The non-AP MLD of claim 11, wherein, in order to suspend operation according to the EMLSR mode, the processor is further configured to cause the non-AP MLD to transmit an enhanced EMLSR operation mode notification frame including a first enhanced multilink control field, the first enhanced multilink control field including a first EMLSR mode field having more than 1 bit, wherein the value of the first EMLSR mode field indicates a request to suspend operation according to the EMLSR mode.
13. The non-AP MLD of claim 12, wherein the first enhanced multilink control field further includes an indication of the duration of the requested suspension of operation according to the EMLSR mode.
14. The non-AP MLD of claim 11, wherein, in order to resume operation according to the EMLSR mode, the processor is further configured to cause the non-AP MLD to transmit an enhanced EMLSR operation mode notification frame including a second enhanced multilink control field, the second enhanced multilink control field including a second EMLSR mode field having more than 1 bit, wherein the value of the second EMLSR mode field indicates a request to resume EMLSR operation.
15. The non-AP MLD of claim 14, wherein the second enhanced multi-link control field further includes a filling delay indication for the current EMLSR session.
16. The non-AP MLD of claim 11, wherein, in order to abort operation according to the EMLSR mode, the processor is further configured to cause the non-AP MLD to transmit a third enhanced multilink control field including the EMLSR abort mode field.
17. The non-AP MLD of claim 11, wherein, in order to abort operation according to the EMLSR mode, the processor is further configured to cause the non-AP MLD to transmit an ultra-high throughput EHT action frame, the ultra-high throughput action frame including a value indicating a request to abort operation according to the EMLSR mode.
18. The non-AP MLD of claim 11, wherein the at least one parameter relating to the EMLSR mode includes link-specific indications for the first link and for the second link.
19. A method for communication, comprising: At the access point AP multi-link device MLD: Provide multiple links, including at least a first link and a second link; Associated with non-access point MLD and non-AP MLD; At least one parameter related to the non-AP MLD switching and the enhanced multi-link single-radio EMLSR mode; Receive a request to enter the EMLSR mode for the first link and the second link from the non-AP MLD on the first link or the second link; The request for the EMLSR mode for the first link and the second link is terminated from the non-AP MLD received on the first link or the second link; For the non-AP MLD, the EMLSR mode for the first link and the second link is terminated; For the non-AP MLD, determine the time to restore the EMLSR mode for the first link and the second link; as well as For the non-AP MLD, restore the EMLSR mode for the first link and the second link.
20. The method of claim 19, wherein the determination of the time to restore the EMLSR mode is based on the earliest time when the EMLSR recovery request is received and occurs: Complete the EMLSR abort timeout after receiving the EMLSR recovery request; Send an EMLSR recovery request response; or Receive a frame with a power-saving mode bit indicating that the power-saving mode is disabled for the different link on a link different from the EMLSR recovery request.
Citation Information
Patent Citations
Signaling for multi-link communication in a wireless local area network (WLAN)
CN114097298A
Communication methods and device to signal enhanced multi-link operating mode
GB202113205D0
