Method and apparatus for communication

Abstract

The present disclosure relates to channel switching and operational channel verification. Methods, systems, and apparatus for performing channel switching by an access point (AP) multi-link device (MLD) and a non-AP MLD are described. The AP MLD can transmit information regarding AP parameters to be implemented following an upcoming channel switch. Furthermore, methods, systems, and apparatus for performing multi-link channel verification are described. The non-AP MLD and the AP MLD can verify multiple links for communication.

Description

Technical Field

[0001] The present application relates to wireless communications, including techniques for wireless communications between wireless stations and / or access points in wireless networking systems. Background Art

[0002] The use of wireless communication systems is growing rapidly. Furthermore, wireless communication technology has evolved from just voice communication to also include the transmission of data, such as the internet and multimedia content. A common short-range / medium-range wireless communication standard is the Wireless Local Area Network (WLAN). Most modern WLANs are based on the IEEE 802.11 standard (and / or 802.11 for short) and are marketed 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 wider internet.

[0003] In an 802.11 system, devices that are wirelessly connected to each other are referred to as "stations," "mobile stations," "user devices," "user equipment," or simply STAs or UEs. A wireless station may be a wireless access point or a wireless client (and / or a mobile station). An access point (AP), also known as a wireless router, acts as a base station for a wireless network. The AP transmits and receives radio frequency signals for communicating with wireless client devices. The AP may also be coupled to the Internet by wire and / or wireless means. A wireless client operating on an 802.11 network may be any of a variety of devices, such as a laptop, tablet device, smart phone, smart watch, or fixed device such as a desktop computer. Wireless client devices are referred to herein as user equipment (and / or UE for short). Some wireless client devices are also collectively referred to herein as mobile devices or mobile stations (but as mentioned above, wireless client devices may also be stationary devices as a whole).

[0004] Mobile electronic devices can take the form of smartphones or tablets that users often carry. Wearable devices (also known as accessory devices) are a newer form of mobile electronic device, with smartwatches being an example. Furthermore, 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 complexity, capabilities, traffic patterns, and other characteristics of the devices required are becoming increasingly broad.

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

[0006] The embodiments described herein relate to systems, methods, apparatus, and mechanisms for channel switching and channel verification by AP MLDs and non-AP MLDs.

[0007] The AP MLD may transmit a first beacon on a first channel for a first subordinate AP, wherein the first beacon indicates at least one parameter for operation of the first subordinate AP on the first channel. The AP MLD may transmit a second beacon on a second channel different from the first channel for a second subordinate AP, wherein the second beacon indicates at least one parameter for operation of the second subordinate AP on the second channel. The AP MLD may determine, before a first time, to perform a channel switch from the first channel to a third channel different from the first channel for the first subordinate AP at a first time, and may determine, before the first time, at least one parameter for operation of the first subordinate AP on the third channel. The AP MLD may transmit a third beacon on the first channel for the first subordinate AP before the first time, wherein the third beacon indicates at least one parameter for operation of the first subordinate AP on the third channel; and transmit a fourth beacon on the third channel for the first subordinate AP after the first time, wherein the fourth beacon indicates at least one parameter for operation of the first subordinate AP on the third channel.

[0008] This summary is intended to provide a brief overview of some of the subject matter described in this document. Therefore, it should be understood that the above-described features are merely examples and should not be construed as narrowing the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, accompanying drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A better understanding of the present subject matter may be obtained when the following detailed description of the embodiments is considered in conjunction with the accompanying drawings.

[0010] Figure 1 An exemplary wireless communication system is shown in accordance with some embodiments.

[0011] Figure 2 An exemplary simplified block diagram of a wireless device according to some embodiments is shown.

[0012] Figure 3 An exemplary WLAN communication system is shown in accordance with some embodiments.

[0013] Figure 4 An exemplary simplified block diagram of a WLAN access point (AP) is shown in accordance with some embodiments.

[0014] Figure 5 An exemplary simplified block diagram of a wireless station (STA) is shown in accordance with some embodiments.

[0015] Figure 6 An exemplary simplified block diagram of a wireless node according to some embodiments is shown.

[0016] Figures 7 and 8 An example of an MLD according to some embodiments is shown.

[0017] Figure 9 An exemplary method of channel switching by an MLD according to some embodiments is shown.

[0018] Figures 10 to 39 Aspects of channel switching according to some embodiments are shown.

[0019] Figure 40 An exemplary method of operating channel verification for multiple channels according to some embodiments is shown.

[0020] Figures 41 to 49 Aspects of authenticating multiple channels are shown according to some embodiments.

[0021] While the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. However, it should be understood that the drawings and detailed description thereof are not intended to limit this disclosure to the specific forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0022] Acronyms

[0023] Various acronyms are used throughout this patent application. The definitions of the most prominent acronyms used that may appear throughout this patent application are as follows:

[0024] UE: User Equipment

[0025] AP: Access Point

[0026] STA: wireless station

[0027] TX: Transmit / Transmit

[0028] RX: Receive / Receive

[0029] MLD: Multi-Link Device

[0030] LAN: Local Area Network

[0031] WLAN: Wireless Local Area Network

[0032] RAT: Radio Access Technology

[0033] ACK: Acknowledgement

[0034] BA: Block Acknowledgement

[0035] NACK: Negative Acknowledgement

[0036] N-BA: Negative Block Acknowledgement

[0037] TSF: Time synchronization function

[0038] QoS: Quality of Service

[0039] the term

[0040] The following is a glossary of terms used in this disclosure:

[0041] Memory medium—any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include installation media, such as CD-ROMs, floppy disks, or 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, such as hard drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of non-transitory memory or combinations thereof. In addition, the memory medium may be located in the first computer system executing the program, or may be located 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 medium" may include two or more memory media that may reside in different locations in different computer systems connected, for example, via a network. The memory medium may store program instructions (e.g., represented as a computer program) that can be executed by one or more processors.

[0042] Carrier Media—storage media as described above, and physical transmission media such as a bus, network, and / or other physical transmission media that carry signals such as electrical, electromagnetic, or digital signals.

[0043] Computer System—Any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combination of devices. 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.

[0044] Mobile Device (and / or Mobile Station)—Any of various types of computer system devices that are mobile or portable and that perform wireless communications using WLAN communications. Examples of mobile devices include mobile phones or smartphones (e.g., iPhones). TM , based on Android TM phones), and tablets such as iPads TM 、Samsung Galaxy TM etc. Various other types of devices would fall into this category if they include Wi-Fi or both cellular and Wi-Fi communication capabilities, such as laptop computers (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 smart watches, smart glasses, headphones, pendants, earbuds, etc. In general, the term "mobile device" can be broadly defined to include any electronic, computing and / or communication device (and / or combination of devices) that a user can easily transport and that is capable of wireless communication using WLAN or Wi-Fi.

[0045] Wireless device (and / or wireless station) - any of various types of computer system devices that perform wireless communications using WLAN communications. 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 station for an 802.11 system, such as an access point (AP) or a client station (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.

[0046] WLAN—The term "WLAN" has the full scope of its ordinary meaning and includes at least a wireless communication network, or RAT, that is served by WLAN access points and provides connectivity to the Internet through these access points. Most modern WLANs are based on the IEEE 802.11 standard and are marketed under the name "Wi-Fi." WLAN networks are distinct from cellular networks.

[0047] Processing Element—refers to various specific implementations of digital circuitry that performs functions in a computer system. Additionally, a processing element may refer to various implementations of analog or mixed-signal (a combination of analog and digital) circuitry that performs a function (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 larger portions of systems that include multiple processors.

[0048] Automatic—refers to an action or operation being performed by a computer system (e.g., software executed by the computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without requiring user input to directly specify or execute the action or operation. Thus, the term "automatically" is in contrast to an action being manually performed or specified by a user, where the user provides input to directly perform the action. An automatic process may be initiated by user-provided input, but the subsequent "automatically" performed actions are not specified by the user, e.g., not "manually" performed, where the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting checkboxes, radio selections, etc.) is not manually filling out the form, even though the computer system must update the form in response to the user's actions. The form may be automatically filled out by a computer system, where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills it out without requiring any user input to specify the answers to the fields. As indicated above, a user may invoke the automatic filling of a form without participating in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields and they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions that a user has taken.

[0049] Concurrency - refers to parallel execution or implementation, where tasks, processes, signaling, messages, or programs are executed in an at least partially overlapping manner. For example, concurrency can be achieved using "strong" or strict parallelism, where tasks are executed (at least partially) in parallel on respective computing elements, or using "weak parallelism," where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0050] Configured to—Various components may be described as being “configured to” perform one or more tasks. In such contexts, “configured to” is a broad statement that generally means “having the structure” to perform one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently performing the task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, “configured to” can be a broad statement that generally means “having the circuitry” to perform one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently turned on. Generally, the circuitry that forms the structure corresponding to “configured to” may include hardware circuitry.

[0051] 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." Representing a component as being configured to perform one or more tasks expressly intends that the component not be interpreted under 35 U.S.C. §112(f).

[0052] Figure 1-Figure 2 —Wireless communication system

[0053] Figure 1 An exemplary (and simplified) wireless communication system is shown in which aspects of the present disclosure may be implemented. Figure 1 The system is but one example of possible systems, and embodiments of the present disclosure may be implemented in any of a variety of systems as desired.

[0054] As shown, the exemplary wireless communication system includes a ("first") wireless device 102 communicating with another ("second") wireless device. The first wireless device 102 and the second wireless device 104 can communicate wirelessly using any of a variety of wireless communication technologies, including ranging wireless communication technologies.

[0055] As one possibility, the first wireless device 102 and the second wireless device 104 can perform ranging using a wireless local area network (WLAN) communication technology (e.g., communication based on IEEE 802.11 / Wi-Fi) and / or a technology based on WLAN wireless communication. One or both of the wireless device 102 and the wireless device 104 can also communicate via one or more additional wireless communication protocols, such as Bluetooth (BT), Bluetooth Low Energy (BLE), Near Field Communication (NFC), GSM, UMTS (WCDMA, TDSCDMA), LTE, Advanced LTE (LTE-A), NR, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-MAX, GPS, etc.

[0056] Wireless device 102 and wireless device 104 may be any of various types of wireless devices. As one possibility, one or more of wireless devices 102 and / or 104 may be substantially portable wireless user equipment (UE) devices, such as a smartphone, a handheld device, a wearable device (e.g., a smartwatch), a tablet, a motor vehicle, or virtually any type of wireless device. As another possibility, one or more of wireless device 102 and / or wireless device 104 may be substantially stationary devices, such as a set-top box, a media player (e.g., an audio or audio-visual device), a game console, a desktop computer, an appliance, a door, an access point, a base station, or any of various other types of devices.

[0057] Each of the wireless device 102 and the wireless device 104 may include wireless communication circuitry configured to facilitate the performance of wireless communications, which may include various digital and / or analog radio frequency (RF) components, a processor configured to execute program instructions stored in a memory, a programmable hardware element such as a field programmable gate array (FPGA), and / or any of various other components. The wireless device 102 and / or the wireless device 104 may use any or all of these components to perform any method embodiment described herein, or any portion of any method embodiment described herein.

[0058] 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 a receive chain and / or transmit chain may be shared across multiple wireless communication standards; for example, a device may be configured to communicate using either Bluetooth or Wi-Fi while utilizing partially or fully shared wireless communication circuitry (e.g., utilizing 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, a device may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol it is configured to communicate using. As another possibility, a device may include one or more radios or radio components shared across multiple wireless communication protocols, as well as one or more radios or radio components used exclusively by a single wireless communication protocol. For example, a device may include shared radio components for communicating using one or more of LTE, CDMA2000 1xRTT, GSM, and / or 5G NR, as well as separate radio components for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0059] As mentioned above, it can be combined with Figure 1 Aspects of the present disclosure may be implemented in a wireless communication system. For example, a wireless device (e.g., either wireless device 102 or 104) may be configured to perform methods for robust discovery of new access points (APs) in an AP MLD, robust link addition to an AP MLD association, AP beacon mode when an AP is added to or deleted from an AP MLD, and robust BSS transition management (BTM) signaling for steering non-AP MLDs to the best AP MLD and the most suitable AP, as well as privacy improvement for associated non-AP MLDs.

[0060] Figure 6 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 the present disclosure is shown. 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 stationary device, potentially including any of a variety of types of devices. Device 100 can be configured to perform one or more ranging wireless communication techniques or features, such as any of the techniques or features subsequently shown and / or described herein with respect to any or all of the figures.

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

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

[0063] It should be noted that in some cases, for example, wireless communication circuitry 130 may include its own processing element (e.g., a baseband processor) in addition to processing element 101. 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., may be a multi-processor device). Other configurations utilizing a multi-processor architecture (e.g., instead of or in addition to an application processor / baseband processor configuration) are also possible.

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

[0065] Components of device 100, such as processing element 101, memory 105 and wireless communication circuit 130, can be operably coupled via one or more interconnect interfaces, which can include any of various types of interfaces, possibly including a combination of multiple types of interfaces. As an example, a USB high-speed inter-chip (HSIC) interface can be provided for inter-chip communication between processing elements. Alternatively (and / or in addition), any of a universal asynchronous receiver-transmitter (UART) interface, a serial peripheral interface (SPI), an internal integrated circuit (I2C), a system management bus (SMBus) and / or various other communication interfaces can be used for communication between various device components. Other types of interfaces (e.g., an intra-chip interface for communication within processing element 101, a peripheral device interface for communicating with peripheral components inside or outside device 100, etc.) can also be provided as part of device 100.

[0066] Figure 3 —WLAN system

[0067] Figure 3An exemplary WLAN system according to some embodiments is shown. As shown, the exemplary WLAN system includes multiple wireless client stations or devices (e.g., STAs or user equipment (UE)) 106, which are configured to communicate with an access point (AP) 112 via a wireless communication channel 142. AP 112 can be a Wi-Fi access point. AP 112 can communicate with one or more other electronic devices (not shown) and / or another network 152 (such as the Internet) via a wired and / or wireless communication channel 150. Additional electronic devices, such as remote devices 154, can communicate with components of the WLAN system via network 152. For example, remote device 154 can be another wireless client station, a server associated with an application executed on one of STAs 106, etc. The WLAN system can 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 neighboring mobile devices without using access point 112.

[0068] Furthermore, in some embodiments, the wireless device 106 (which may be an exemplary implementation of the device 100) may be configured to perform methods for robust discovery of new access points (APs) in AP MLDs, robust link addition to AP MLD associations, AP beacon mode when adding or removing an AP from an AP MLD, and robust BSS transition management (BTM) signaling for steering non-AP MLDs to the best AP MLD and most suitable AP, as well as privacy improvements for associated non-AP MLDs.

[0069] Figure 4 —Access Point Block Diagram

[0070] Figure 4 An exemplary block diagram of an access point (AP) 112 is shown, which may be Figure 4 One possible exemplary implementation of the device 100 is shown. Note that Figure 4 The block diagram of the AP 112 is only one example of a possible system. As shown, the AP 112 may include a processor 204 that may execute program instructions for the AP 112. The processor 204 may also be coupled (directly or indirectly) to a memory management unit (MMU) 240 or other circuit or device that may be configured to receive addresses from the processor 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0071] AP 112 may include at least one network port 270. Network port 270 may be configured to couple to a wired network and provide access to the Internet for 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 an enterprise network. For example, port 270 may be an Ethernet port. The local network may provide connectivity to additional networks, such as the Internet.

[0072] AP 112 may include at least one antenna 234 that may be configured to operate as a wireless transceiver and may be further configured to communicate with mobile device 106 via wireless communication circuitry 230. Antenna 234 communicates with wireless communication circuitry 230 via communication chain 232. Communication chain 232 may include one or more receive chains, one or more transmit chains, or both. Wireless communication circuitry 230 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). Wireless communication circuitry 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including, but not limited to, Long Term Evolution (LTE), LTE-Advanced (LTE-A), Global System for Mobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000, etc., for example, when the AP is co-located with a base station in a small cell scenario, or in other scenarios where it may be desirable for AP 112 to communicate via various different wireless communication technologies.

[0073] Additionally, in some embodiments, as further described below, the AP 112 may be configured to perform methods for robust discovery of new access points (APs) in AP MLDs, robust link addition to AP MLD associations, AP beacon mode when adding or removing APs from an AP MLD, and robust BSS transition management (BTM) signaling for steering non-AP MLDs to the best APMLD and most suitable AP, as well as privacy improvements for associated non-AP MLDs.

[0074] Figure 5 —Client site diagram

[0075] Figure 5 An exemplary simplified block diagram of a client site 106 is shown, which may be Figure 4One possible exemplary implementation of the device 100 is 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 station. As shown, the client site 106 may include a system on a chip (SOC) 300, which may include parts for various purposes. The SOC 300 may be coupled to various other circuits of the client site 106. For example, the client site 106 may include various types of memory (e.g., including NAND flash memory 310), a connector interface (I / F) (and / or docking station) 320 (e.g., for coupling to a computer system, taskbar, charging station, etc.), a display 360, cellular communication circuitry (e.g., cellular radio components) 330 (such as for 5G NR, LTE, GSM, etc.), and medium and short range wireless communication circuitry (e.g., Bluetooth TM and WLAN radio components) 329 (e.g., Bluetooth TM and WLAN circuitry). The 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). The cellular communication circuitry 330 may be coupled to one or more antennas, such as antennas 335 and 336 as shown. The short-range 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 in lieu of being coupled to antennas 337 and 338, the short-range to medium-range wireless communication circuitry 329 may be coupled to antennas 335 and 336. The short-range 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 the short- and medium-range wireless communication circuitry 329 and / or the cellular communication circuitry 330 may be used for ranging communication, for example, using WLAN communication, Bluetooth communication, and / or cellular communication.

[0076] As shown, the SOC 300 may include one or more processors 302 that may execute program instructions for the client station 106 and display circuitry 304 that may perform graphics processing and provide display signals to a display 360. The SOC 300 may also include motion sensing circuitry 370 that may detect motion of the client station 106 using, for example, a gyroscope, an accelerometer, and / or any of a variety of other motion sensing components. The one or more processors 302 may also be coupled to a memory management unit (MMU) 340 and / or other circuits or devices (such as the display circuitry 304, cellular communication circuitry 330, short-range wireless communication circuitry 329, a connector interface (I / F) 320, and / or the display 360). The MMU may be configured to receive addresses from the 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 embodiments, MMU 340 may be included as part of processor 302 .

[0077] As described above, the client station 106 may be configured to communicate directly with one or more neighboring client stations in wireless communication. The client station 106 may be configured to communicate according to a WLAN RAT to enable communication in environments such as Figure 3 WLAN network communication as shown in Figure 1 The ranging shown in .

[0078] As described herein, the client site 106 may include hardware and software components for implementing the features described herein. For example, the processor 302 of the 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), the 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 combination with one or more of the other components 300, 304, 306, 310, 315, 320, 329, 330, 335, 336, 337, 338, 340, 350, 360, 370, the processor 302 of the UE 106 may be configured to implement some or all of the features described herein.

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

[0080] Furthermore, as described herein, each of the cellular communication circuitry 330 and the short-range wireless communication circuitry 329 may include one or more processing elements. In other words, one or more processing elements may be included in both the cellular communication circuitry 330 and the short-range wireless communication circuitry 329. Thus, each of the cellular communication circuitry 330 and the short-range wireless communication circuitry 329 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuitry 330 and the short-range wireless communication circuitry 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 circuitry 330 and the short-range wireless communication circuitry 329.

[0081] Figure 6 —Wireless node block diagram

[0082] Figure 6 A possible block diagram of a wireless node 107 is shown. The wireless node may be Figure 6 . As shown, the wireless node 107 may include a system-on-chip (SOC) 400, which may include components for various purposes. For example, as shown, the SOC 400 may include one or more processors 402 that may execute program instructions for the wireless node 107 and display circuitry 404 that may perform graphics processing and provide 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 using, for example, a gyroscope, an accelerometer, and / or any of various other motion sensing components. The one or more processors 402 may also be coupled to a memory management unit (MMU) 440, which may be configured to receive addresses from the 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 embodiments, MMU 440 may be included as part of processor 402 .

[0083] As shown, the SOC 400 may 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), a connector interface 420 (e.g., for coupling to a computer system, a docking station, a charging station, etc.), a display 460, and wireless communication circuitry 430 (e.g., for 5G NR, LTE, LTE-A, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.).

[0084] The wireless node 107 may include at least one antenna, and in some embodiments, may include multiple antennas 435 and 436 for performing wireless communications with base stations and / or other devices. For example, the wireless node 107 may perform wireless communications using antennas 435 and 436. As described above, the wireless node 107 may, in some embodiments, be configured to perform wireless communications using multiple wireless communication standards or radio access technologies (RATs).

[0085] Wireless communication circuitry 430 may include Wi-Fi logic 432, a cellular modem 434, and Bluetooth logic 439. Wi-Fi logic 432 is configured to enable wireless node 107 to perform Wi-Fi communications over, for example, an 802.11 network. Bluetooth logic 439 is configured to enable wireless node 107 to perform Bluetooth communications. Cellular modem 434 may be configured to perform cellular communications according to one or more cellular communication technologies. Some or all of wireless communication circuitry 430 may be configured to perform ranging communications, for example, using WLAN communications, Bluetooth communications, and / or cellular communications.

[0086] As described herein, the wireless node 107 may include hardware components and software components for implementing embodiments of the present disclosure. For example, one or more components of the wireless communication circuitry 430 (e.g., Wi-Fi logic 432) of the wireless node 107 may be configured to implement some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), by a processor configured as an FPGA (field programmable gate array), and / or using dedicated hardware components that may include an ASIC (application-specific integrated circuit).

[0087] Figures 7 and 8 —Multi-Link Device (MLD) operation

[0088] IEEE 802.11be may include Multi-Link Device (MLD) capabilities. In the current implementation, an access point (AP) Multi-Link Device (MLD) node can manage its subordinate APs. Thus, an AP MLD node can modify, add, and / or remove subordinate APs to increase capacity, manage basic service set (BSS) interference and coverage, including switching APs to operate on channels with minimal interference, and / or steer associated non-AP MLD nodes to operate on the best performing AP and / or AP MLD node.

[0089] Figure 7 An AP MLD 112 is shown according to some embodiments. The AP MLD can operate any number of subordinate APs, such as APs 712a, 712b, 712c, and 712d in the illustrated example. The subordinate APs can operate on any of a variety of frequency bands. The subordinate APs can operate on different frequency ranges (e.g., channels) of the same frequency band or on different frequency bands.

[0090] The AP MLD can provide attached APs from a single physical device (e.g., a single shared housing) and potentially using the same antennas. In some embodiments, the AP MLD can provide APs from multiple different devices (e.g., a first device can provide one or more APs, a second device can provide a different one or more APs, etc.). In some embodiments, the various attached APs can be spatially separated (e.g., beams in different directions, using different antennas with a shared housing (e.g., antennas of the same physical device) and / or different antennas on different devices, etc.).

[0091] In some embodiments, spatially separated subsidiary APs may operate on the same (or overlapping) channels.

[0092] Figure 8 AP MLD 112 is shown communicating with non-AP MLD 106 according to some embodiments.

[0093] As shown, AP MLD 112 can operate three subordinate APs. In the illustrated example, AP 812a can operate in the 2.4 GHz band, AP 812b can operate in the 5 GHz band, and AP 812c can operate in the 6 GHz band. It should be understood that any number of subordinate APs can be used in any combination of frequency bands. For example, AP MLD can operate multiple subordinate APs in a single frequency band and / or can operate no subordinate APs in a frequency band. The subordinate APs can include various layers, such as the media access control (MAC) and / or physical (PHY) layers, as well as various possibilities. The subordinate APs can use different basic service sets (BSSs) and / or different BSS identifiers (BSSIDs), such as BSSIDs 1-3.

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

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

[0096] Various affiliated STAs and APs may communicate concurrently / simultaneously. For example, STA 806a may exchange uplink and / or downlink data with AP 812a on a first link, while STA 806b may exchange uplink and / or downlink data with AP 812b on a second link, and so on. It should be understood that such concurrent communication may include (e.g., different) data being exchanged on different links at the same time, overlapping times, and / or different times. For example, data between an AP MLD and a non-AP MLD may be routed via the first available link and / or a link selected based on other criteria (e.g., lowest energy usage, etc.). For example, a first data packet or portion may be sent via the first link, and concurrently, a second data packet or portion may be sent via the second link.

[0097] In some embodiments, an AP MLD and a non-AP MLD may include a corresponding ML entity. The ML entity may provide upper-layer MAC functionality for controlling individual APs and / or STAs and may control traffic delivery across available links, for example, between various APs and STAs. A corresponding MLD (e.g., an AP and a non-AP) may have only one corresponding MAC SAP interface. The MAC SAP interface connects the MLD to a distribution system that can deliver traffic to and from the MLD from the Internet. For example, with a single MAC SAP interface, all APs affiliated with an AP MLD may appear as a single device (e.g., an AP MLD) to the Internet. The ML entity may manage this interface. The ML entity may manage transmit buffering (e.g., bookkeeping and link selection in the transmitter) and data reordering buffering in reception (e.g., combining data transmitted on different links).

[0098] The AP MLD 112 and the non-AP MLD 106 may exchange information regarding their respective operations, operating parameters, and / or capabilities.

[0099] A non-AP MLD may have various capabilities for operating a STA in a specific frequency band. Capabilities may vary for different frequency bands. For example, a capability in a frequency band may describe the maximum parameter values (e.g., fastest, most flexible, most powerful, highest throughput, etc.) that a non-AP MLD STA can use. Operations or operating parameters may describe parameter values currently in use or planned for future use.

[0100] For example, parameters may include the applicable PHY version and its parameters. Parameters may describe available supported services and transmission formats. Parameters may also describe available resources, bandwidth, and number of spatial streams. Parameters may also describe power-saving support parameters that enable low-power transmission. For example, the AP may support target wake time (TWT) power saving.

[0101] In some embodiments, the links may be located too close together (e.g., spatially and / or in frequency) for non-AP STAs to independently operate the links (e.g., due to device limitations and / or due to management resources or performance). The AP may support STAs that are unable to transmit and receive simultaneously on a link pair (e.g., non-AP MLD).

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

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

[0104] Figure 9 -Channel switching

[0105] In some embodiments, the AP MLD node may perform a channel switch, e.g., change / move an attached AP from one channel to another. Such a channel switch may be performed between channels in a frequency band (e.g., 2.4 GHz, 5 GHz, or 6 GHz, etc.) or between multiple frequency bands (e.g., from a 5 GHz channel to a 6 GHz channel, etc.). For example, a channel switch may be the movement of a first attached AP from a first channel on a first frequency band to a second channel on the first frequency band or on a different frequency band. The first attached AP may be operating on the first channel before the switch (e.g., not operating on the second channel at that time) and may be operating on the second channel after the switch (e.g., not operating on the first channel at that time).

[0106] A non-AP MLD can perform similar channel switching, for example, changing a STA from a first channel to a second channel. A non-AP MLD can switch channels for attached STAs in response to an AP MLD switching channels or indicating that it will switch channels. A non-AP MLD can request an AP MLD to perform a channel switch, and the AP MLD can initiate the channel switch in response to such a request.

[0107] The AP MLD may signal the channel switch (via the subordinate AP that will change channels and / or other subordinate APs). For example, the AP that changes channels may signal the upcoming channel switch in one or more beacons it transmits. Similarly, other subordinate APs may signal the switch, for example, in the multilink (ML) element of the beacon frames they transmit. Such beacons may indicate the new channel and the switch time (e.g., the point in time at which the switch is scheduled to begin, e.g., when the AP may no longer provide a link on the first channel, and may also include additional information such as the duration).

[0108] In some embodiments, a channel switch and / or extended channel switch element may be included in beacons from the switching AP and / or other subordinate APs. During the channel transition, a channel switch duration may be added to beacons from subordinate APs. A silence element may be added to beacons from subordinate APs. For example, a silence element may indicate that the switching AP is currently switching, for example, and therefore may not transmit beacons and / or other frames and may not receive transmissions for a certain period of time.

[0109] In some embodiments, when an AP is signaled to switch channels, the operating parameters of the switched AP (e.g., on the new channel) may be signaled only after the channel switch is complete. As a result, associated STAs may not be prepared to operate with the new parameters until after the switch. Therefore, associated / associated STAs may set their parameters based on the AP's parameters before the switch until the new parameters are signaled.

[0110] In some embodiments, as described below with respect to Figure 9 The channel switching may be faster than the channel switching described above.

[0111] In the 6 GHz band, before a STA can operate with the AP on the new channel, it may be necessary to obtain the prescribed power level of the AP after the switch. This may prevent or delay operation with the AP, for example, until the AP MLD and non-AP MLD determine the prescribed power level. The STA may have low-latency traffic with the switched AP. The channel switch delay may result in a reduction in the quality of service (QoS) of any applications running on the non-AP MLD. In addition, the STA may not be prepared to operate in the new channel. Obtaining parameters before and / or during the switch may allow for a longer preparation time. This may reduce or avoid management traffic storms (for example, multiple STAs attempting to establish communication with the AP on the new channel within a similar time period), especially in cases where the AP has a large number of associated STAs. This may allow the STAs more time to determine and indicate their new parameters.

[0112] The embodiments described herein provide systems, methods, and mechanisms for APs and non-AP MLDs to perform channel switching. Figure 9 In an embodiment, the parameters that the AP will use after the channel switch can be signaled by the AP and / or other subordinate APs before the switch. This solution can help reduce latency, reduce power consumption and / or improve security. For example, Figure 9 An exemplary method of channel switching according to some embodiments is shown.

[0113] Figure 9Aspects of the method may be implemented by an AP MLD communicating with a non-AP MLD. The AP MLD and / or the non-AP MLD may be as shown and described with respect to the various figures herein, or more generally, as needed, in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the figures above. For example, a 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 circuitry such as 130, 230, 232, 329, 330, 430, and various possibilities) may cause a wireless device, a STA, a UE, a non-AP MLD, and / or an AP MLD, or other device to perform such method elements.

[0114] Note that although described in relation to the use of communication techniques and / or features associated with IEEE and / or 802.11 (e.g., 802.11be) specification documents, Figure 9 but this description is not intended to limit the present disclosure, and Figure 9 Various aspects of the method may be used in any suitable wireless communication system as desired. Similarly, although described in relation to AP MLD and / or non-AP MLD, Figure 9 elements of the method, but this description is not intended to limit the present disclosure, and Figure 9 Aspects of the method may be used by STAs that are not MLDs (eg, APs or non-APs) as needed.

[0115] The method shown may also be used with any of the systems, methods, or devices shown in the figures, in addition to other devices. In various embodiments, some of the method elements shown may be performed concurrently in an order different from the order shown, or may be omitted. Additional method elements may also be performed as needed. As shown, the method may operate as follows.

[0116] According to some embodiments, AP MLD 112 may transmit beacons (902a, 902b) from a first satellite AP and a second satellite AP. The first AP may operate on a first channel (903a) and the second AP may operate on a second channel (903b). The first channel and the second channel may be in the same or different frequency bands.

[0117] The beacon may include an indication of various parameters of the corresponding AP. For example, a beacon of a first AP may indicate the parameters of the first AP. Such indicated parameters may include the frequency, bandwidth, channel, basic service set identifier (BSSID), operation category, number of spatial streams (NSS), support for power save modes (e.g., such as TWT), beacon periodicity, EDCA parameters, MU EDCA parameters, uplink opportunistic random access (UORA) parameters (e.g., random access related parameters), capabilities for different PPDU types and / or transmission modes (e.g., extended range, optional MCS), color values (e.g., to identify APs in new channels), etc. of the corresponding AP. It should be understood that the parameters of different APs may be the same or different. For example, any or all parameter values may be the same (and / or different) for a first AP and a second AP (or additional APs to an MLD AP).

[0118] In addition, an AP's beacon may include indications of other APs. For example, a beacon transmitted by a first AP may include indications of a second AP (and / or any other / additional APs subordinate to AP MLD), and vice versa. An AP's beacon may include indications of parameters of other APs. In some embodiments, a transmitting AP's beacon may include values for the same set of parameters for subordinate APs as the transmitting AP. In some embodiments, a transmitting AP's beacon may include values for fewer, different, and / or additional parameters for subordinate APs.

[0119] The non-AP MLD 106 may receive the beacon. It should be understood that the non-AP MLD may include or operate multiple subordinate STAs corresponding to the subordinate APs of the AP MLD, for example, as described with respect to Figure 8 Such affiliated STAs are shown and described in Figure 9 is shown as a single line in the beacon. The non-AP MLD may use the indication of the parameters in the beacon to determine (e.g., set, reset, and / or adjust, etc.) any of its own parameters. For example, the parameters of the first subordinate AP may be used to determine one or more parameters of a corresponding subordinate STA that operates on the same channel as the first subordinate AP and communicates with the first subordinate AP.

[0120] According to some embodiments, the AP MLD may determine to perform a channel switch of one (or more) of the attached APs (904). For example, the AP MLD may determine to switch the first AP from the first channel (903a) to the third channel (903c). The third channel may be in the same or a different frequency band as the first channel (e.g., and / or the second channel).

[0121] According to some embodiments, the AP MLD may determine (e.g., new or revised) parameters for the first AP on the new channel (e.g., the third channel 903c) (906). These parameters may be determined when the first AP is operating on the first channel (e.g., 903a). Any or all parameters of the first AP may change in association with the channel switch. For example, the channel bandwidth and / or the number of spatial streams (NSS) may or may not change, among other possibilities.

[0122] The following table shows the change of per-STA (eg, per-AP) parameters according to the new and old frequency bands of the AP, according to some embodiments.

[0123]

[0124] It should be understood that the above table is an example and other implementations may be used as needed. For example, the per-STA parameters may or may not change in association with a channel switch that does not change the AP's frequency band (e.g., from 2.4 GHz to 2.4 GHz, etc.). Similarly, some or all per-STA parameters may not change in association with a channel switch that changes the AP's frequency band (e.g., from 2.4 GHz to 5 GHz or 6 GHz, etc.).

[0125] It should be understood that the determination to perform a channel switch (e.g., 904) and the determination of parameters (e.g., 906) can be made simultaneously and / or in any order. These determinations can be based on any of a variety of factors, which can be the same or different. For example, the AP MLD can determine to perform a channel switch and / or select parameters based on channel conditions, load levels, traffic patterns of the non-AP MLD (and / or any other non-AP MLD), requests from the non-AP MLD (and / or any other non-AP MLD) (e.g., in an association request, etc.), and / or other information. For example, the AP MLD can determine to perform a channel switch based on interference from another device. The AP MLD can determine to perform a channel switch based on parameters it determines are appropriate to service the load and / or manage resources. The AP MLD can determine to perform a channel switch based on avoiding interference on the current channel (e.g., 903a) and selecting a new channel with lower interference (e.g., 903c). The AP MLD can perform a channel switch to adjust the amount of resources used to match the desired throughput. For example, the AP MLD may determine to perform a channel switch from a frequency band that provides relatively low throughput (e.g., 2.4 GHz) to a frequency band that provides higher throughput (e.g., due to a larger channel bandwidth and / or a higher NSS) (e.g., 6 GHz). The AP MLD may also receive information regarding the associated STA's ability to operate a link pair with simultaneous transmit and receive capabilities. For example, the associated STA may be able to simultaneously transmit on link 1 and receive on link 2. If the non-AP MLD does not have this capability, transmission on one link may cause too much interference, making reception on another link (similar in frequency and / or space) inefficient, impractical, etc. Based on the non-AP MLD's capabilities, the AP MLD may decide to change the AP to operate on a different channel, thereby enabling the non-AP MLD's link to operate independently. For example, the AP MLD may perform a channel switch to create sufficient separation between the two links to allow the non-AP MLD to use both channels simultaneously.

[0126] As another example, a parameter may signal the transmit power after switching. For example, in the 6 GHz band, in some areas, it may be possible to use location-specific transmit power controlled by an automatic frequency controller server. In some cases, an AP may be operating in a mobile device, and the device may be moved to a location that allows the AP to operate with higher transmit power in the new frequency band. The AP may switch to the new channel to operate at the higher power.

[0127] As another example, in a 5 GHz radar detection channel, the AP may detect a radar and the AP may need to change to a new channel.

[0128] For another example, in some cases, an AP cannot maintain all of its links due to poor coverage in the current frequency band. The AP can switch to a lower frequency band to provide better coverage with associated STAs. If the AP is a mobile device, it can also employ extended-range PPDUs and modulation for long range. These enhancements can increase AP coverage and help maintain all of the AP's links.

[0129] As another example, in some cases, an AP may have associated STAs that are at the edge of coverage but consume a lot of transmission resources. The AP may perform channel switching to reduce the coverage of the BSS and stop serving these STAs to have more resources available for other associated STAs.

[0130] As another example, AP MLD can be part of a larger network, and when the network load increases, AP MLD can switch one or more APs to operating channels and parameters that enable a denser deployment. Similarly, when the traffic load decreases, the deployment can return to the original channels and parameters.

[0131] For example, AP MLD might use too much traffic on one AP and too little on another. AP MLD can use channel switching in various ways to rebalance traffic loads across APs. AP MLD can change used APs to new channels to get more traffic for them. AP MLD can also change the most frequently used APs to other channels to more evenly distribute AP utilization.

[0132] For another example, a mobile device operating as an AP may begin operating using other radio technologies (e.g., using an additional or different RAT) and may reorganize WLAN AP operating channels to avoid coexistence interference. In other words, the APMLD may initiate channel switching to reduce or avoid coexistence interference with other communications on another RAT within the AP MLD.

[0133] For another example, a mobile device operating as an AP may transmit or plan to transmit D2D communications on other channels. To simplify the two independent transmission operations, the mobile device may change the AP to operate on the same channel as the D2D transmission.

[0134] As described above, for example, due to limitations of certain devices, a link pair may be located so close together that transmission on link 1 and reception on link 2 may be impractical or impossible. These limitations may apply to either or both AP MLD and / or non-AP MLD. For example, a mobile device operating as an AP may have such limitations. Several capabilities and / or parameters exist that describe how, whether, or when operation in a link pair is possible:

[0135] Enhanced Multi-link Single Radio (EMLSR) assumes a start frame transmission, after which DL data transmission or UL triggering can be performed on a link for a STA. During the duration of the TXOP initiated by the start frame, the other link may not transmit anything to the STA.

[0136] Non-synchronous transmit reception (NSTR) may be a general mode in which data may be transmitted directly (without a start frame) to the STA, but when the STA transmits on link 1 , the AP may not transmit to the STA on link 2 .

[0137] The determination to perform a switch and / or the determination of parameters may be referred to as the beginning of a “grace period.” For example, the grace period may last until the first AP begins performing a channel switch, eg, thereby becoming temporarily unavailable.

[0138] According to some embodiments, the AP MLD may transmit one or more beacons (908a, 908b) via the first and second subordinate APs. The beacons transmitted by the first AP may be transmitted on a first channel (903a), and the beacons transmitted by the second AP may be transmitted on a second channel (903b).

[0139] The beacon may indicate information regarding a channel switch (e.g., planned, upcoming, and / or ongoing). For example, the beacon may indicate the time of the channel switch, such as the start time, end time, and / or duration. Similarly, the beacon may indicate parameters of the first AP to be used after the channel switch (e.g., as determined in 906). Additionally, the beacon may indicate parameters of the first AP, the second AP, and / or any other subordinate APs on the first channel (903a).

[0140] It should be understood that such beacons may be transmitted periodically. For example, the first and / or second AP may transmit any number of beacons during the grace period. For example, beacons may be transmitted at periodic intervals.

[0141] Additionally, during the channel switch (e.g., discussed below with reference to 914), the second AP may continue to transmit one or more beacons (916). It should be understood that when the channel switch begins, the information indicated by the second AP's beacon may change. For example, before the channel switch begins, the second AP's beacon may indicate the operating parameters of the first AP before and after the switch (e.g., the parameters for both time periods may be transmitted in the beacon). However, once the switch begins, the second AP's beacon may no longer indicate the parameters of the first AP before the switch. In some embodiments, once the switch begins and / or as the time of the switch approaches, the second AP's beacon may indicate additional details of the parameters.

[0142] In the event that the first AP does not change parameters associated with the channel switch (e.g., the first AP will use the same parameter values in the new channel 903c as in the old channel 903a), then the beacon may indicate that there are no changes. For example, the channel switch element and / or the extended channel switch element may have a field set to 1 to indicate that the AP parameters are the same in the new channel. In some embodiments, AP capabilities and operating parameters may be signaled via different band-specific elements.

[0143] If the first AP changes parameters in association with the channel switch (e.g., the first AP will use one or more parameter values that change in the new channel 903c relative to the old channel 903a), then the beacon may indicate that there has been a change. For example, the subordinate AP may transmit an ML reconfiguration variant multilink element in the beacon and / or any ML probe response. The ML reconfiguration variant multilink element may include a per-STA profile for the switching AP including parameter values in the new channel. In addition, the ML reconfiguration variant multilink element may include a field (or fields) for signaling multilink parameters for simultaneous transmission support or lack thereof (e.g., STR / NSTR) to the AP MLD after the channel switch.

[0144] In some embodiments, instead of and / or in addition to transmitting a beacon indicating the new parameters, the AP MLD may transmit similar information in a probe response. For example, a non-AP MLD may transmit a probe request to the AP MLD (e.g., via the first and / or second AP). In response to the probe request, the AP MLD may transmit a probe response that includes information about the channel switch, e.g., including the timing of the switch and / or the parameters to be used by the first AP on the third channel 903c.

[0145] The non-AP MLD may receive beacons and / or probe responses from the first and / or second APs. The non-AP MLD may decode parameters and / or other information indicated by the beacons.

[0146] According to some embodiments, the non-AP MLD may determine capability information and / or one or more operating parameters (910). The capability information and / or parameters may be based on parameters of the first AP in the new channel (e.g., 903c). For example, in response to a channel switch that includes a frequency band change, the non-AP MLD may determine its capabilities (e.g., maximum bandwidth, NSS, etc.) in the frequency band (e.g., of the new channel). Additionally, the non-AP MLD may determine specific parameters that it will use with the first AP in the new channel. For example, in response to any indication that the first AP will use parameters that allow for higher throughput (e.g., greater bandwidth, higher NSS, etc.), the non-AP MLD may determine whether it will increase its own corresponding parameter values (e.g., greater bandwidth, higher NSS, etc.). For example, in addition to or in lieu of the first AP's parameters (e.g., as indicated in a beacon), the parameters may be based on information including traffic patterns, applications executing on the non-AP MLD, the non-AP MLD's battery level, user preferences, parameters of other APs, etc. For example, the non-AP MLD may determine parameters in response to an AP indicating, for example, that the parameters are effective after the channel switch.

[0147] In some embodiments, the non-AP MLD may select and / or modify the operation of one or more other / additional RATs based on an upcoming AP channel switch. For example, based on the channel switch (e.g., and / or the new parameters of the first AP in the new channel), the non-AP MLD may activate an additional RAT, deactivate an active RAT, modify the parameters of another RAT, etc. As one possibility, the non-AP MLD may determine that the channel switch may allow the additional RAT to operate, for example, if coexistence interference is below a threshold. For example, based on the new channel, the non-AP MLD may determine that activating a Bluetooth link may be feasible (e.g., because the new channel 903c may interfere less with Bluetooth than the old channel 903a), and may therefore activate or increase usage of the Bluetooth link. Conversely, the non-AP MLD may deactivate or reduce usage of the link (e.g., in the opposite scenario where the new channel potentially increases interference with the link). Furthermore, the non-AP MLD may attempt to modify the frequency range used by the alternative link, for example, to increasingly use bandwidth near the first channel 903a and avoid bandwidth near the new channel 903c.

[0148] In some embodiments, the non-AP MLD may start operating, stop, or modify D2D transmissions based on an upcoming AP channel switch. For example, similar to the previous example, based on determining that D2D communications are available on the first channel 903a, the non-AP MLD may start operating such D2D communications.

[0149] According to some embodiments, the non-AP MLD may indicate capability information and / or one or more operating parameters to the AP MLD (912). For example, the non-AP MLD may transmit a message to the AP MLD (e.g., via the first and / or second AP) including an indication of any capability information and / or parameters determined in 910, as well as various possibilities.

[0150] As shown, the indication may be transmitted, for example, as an indication to a first AP on a first channel and / or a second AP on a second channel before a channel switch. In some embodiments, the indication may be transmitted to the second AP during and / or after the channel switch. In some embodiments, the indication may be transmitted to the first AP after the channel switch is complete (e.g., on a third channel). These embodiments may be combined in various ways. In other words, the non-AP MLD may transmit an indication to the first and / or second AP before the switch, to the second AP during the switch, and / or to the first and / or second AP after the switch. For example, such an indication may be sent to the first and / or second AP before the channel switch (e.g., via channels 903a and / or 903b, respectively), to the second AP during the channel switch, and / or to the first and / or second AP after the channel switch (e.g., via channels 903c and / or 903b, respectively).

[0151] According to some embodiments, the AP MLD may perform a channel switch, for example, the first subordinate AP may perform a channel switch from the first channel 903a to the third channel 903c (914). The first subordinate AP may cease using some or all parameters associated with the first channel and may begin using parameters associated with the third channel (e.g., as determined in 906).

[0152] The channel switch may occur over a period of time (e.g., as may be indicated by the beacon discussed in 908a, 908b). The first AP may be unavailable during this period of time. For example, the first AP may not send a beacon, transmit data / messages, or receive data / messages during this period of time.

[0153] However, other APs affiliated with the AP MLD may continue to operate during this time period. For example, the second AP may transmit one or more beacons or probe responses. Such beacons and / or probe responses may indicate that a channel switch is in progress, when the channel switch will be completed, parameters of the second AP, and / or parameters of the first AP on the third channel 903c.

[0154] Similarly, the non-AP MLD may continue to operate during this time period.For example, the non-AP MLD may exchange data with the second AP and / or send probes and receive probe responses.

[0155] Furthermore, for example, after the channel switch is complete, the non-AP MLD may update its parameters (e.g., as determined in 910) to prepare for operation with the first AP on the third channel. For example, the non-AP MLD (e.g., an affiliated STA that will communicate with the first AP on the third channel) may activate or deactivate any antennas or other communication circuits based on any changed parameters. Similarly, the non-AP MLD (e.g., an affiliated STA) may adjust any band filters, etc., for the new channel.

[0156] According to some embodiments, the AP MLD may transmit beacons (918a, 918b) after the channel switch. The beacons may describe the current (e.g., after the switch) operating parameters of the first AP (e.g., on channel 903c) and / or the second AP. Beacons 918a and 918b may be transmitted by the first and / or second AP on the third and / or second channels, respectively. The beacons transmitted by the APs may be different, for example, as described above with respect to 902a and 902b.

[0157] According to some embodiments, the non-AP MLD may verify the link with the first AP on the new channel (920). For example, the non-AP MLD may verify the link based on receiving a beacon (e.g., 918a) from the first AP on channel 903c. The link may be verified by the non-AP MLD transmitting uplink data to the AP MLD (e.g., to the first AP on channel 903c). In some embodiments, after exchanging such uplink data, both the AP MLD and the non-AP MLD may consider the link verified.

[0158] The non-AP MLD and the AP MLD may exchange uplink and / or downlink data via the first and / or second AP.

[0159] In some embodiments, the AP MLD may not provide a second AP (eg, operating on the second channel 903b). Figure 9 The method may be applied to an AP MLD that operates only a single AP (eg, during a relevant time period). The actions discussed above associated with such a second AP may be omitted and / or may be performed by the first AP.

[0160] In some embodiments, AP MLD may provide multiple second APs (e.g., operating on other / additional channels). Figure 9 The method may be applied to (e.g., during a relevant time period) only operating AP MLD for any number of second APs. The actions discussed above associated with such second APs may not be performed by such second APs, or may be performed by some or all of such second APs.

[0161] Figures 10 to 39 and additional information about channel switching

[0162] Figure 10 Messages that may be transmitted by an AP (eg, any of 712a-712d, etc.) are shown according to some embodiments. Figures 11 to 25 Additional details are included in the Messages. The messages may be used as beacons and / or probe responses (e.g., as with respect to Figure 9 ) as discussed with respect to 902, 908, 916, and / or 918. The message may include information about the AP of AP MLD 112 and / or other subordinate APs.

[0163] It should be understood that Figures 10 to 25 The illustrated structure of the message shown is an example, and other structures and / or element combinations may be used as needed. For example, some elements may be omitted, other elements may be added, and / or a different order may be used. Various fields may also include subfields or bits that are reserved for future use.

[0164] As shown, the message may include information identifying the AP (e.g., a service set identifier (SSID), a BSSID, etc.). The message may include elements describing the capabilities and operations of the AP (e.g., operating parameters). For example, the message may describe the frame structure used by the AP. The message may include a Reduced Neighbor Report (RNR) element that may include entries for other APs affiliated with AP MLD 112 (e.g., for a message transmitted by AP 712a, there may be entries for APs 712b, 712c, and / or 712d). The RNR element may be as follows with respect to Figure 11 The message may include elements describing the AP's high throughput (HT) (eg, extremely high throughput (EHT), etc.) capabilities, operations, and / or parameters.

[0165] The message may include a multi-link (ML) element, for example, as described below with respect to Figure 17 Further description. In some embodiments, if Simultaneous Authentication of Peers (SAE) is used, only the ML element may be used. In some embodiments, if SAE is not used, the ML element may be included. The ML element may include information common to all subordinate APs of the AP MLD (e.g., parameters, capabilities, etc.). The ML element may also include per-STA information, such as the profile of each subordinate AP.

[0166] In some embodiments, the message may include an indication of the timing of the channel switch, e.g. Figures 28 to 29 Further description.

[0167] The following table describes the Figure 10 Some elements of the message.

[0168]

[0169]

[0170] In the table above, "frame body" refers to standard fields in a frame. For example, a frame may contain multiple elements as defined in 802.11 or another wireless standard.

[0171] Figure 11 FIGURE 1 illustrates an RNR element according to some embodiments. As shown, the RNR element may include an element identifier, a length field, and any number of neighbor AP information fields, e.g., information about Figure 12 For example, the RNR element may include the corresponding neighbor information fields of the corresponding other affiliated APs of the APMLD. For example, the message transmitted by AP 712a may include the RNR element with the neighbor AP information fields of APs 712b-712d.

[0172] Figure 12 FIG2 shows a neighbor AP information field according to some embodiments. The neighbor AP information field may include subfields for different information about the corresponding neighbor AP. As shown, the neighbor AP information field may include a TBTT information header field, for example, to indicate timing information of the beacon transmitted by the corresponding neighbor AP, such as information about the Figure 15 Further description. The neighbor AP information field may include the operation category information and channel number of the corresponding neighbor AP. The operation category and channel number may indicate the channel in which the AP operates. The neighbor AP information field may include a TBTT information set, which includes information about Figure 13 Any number of TBTT information fields as further described. For example, the RNR may first describe the frequency band and channel, and then include the TBTT information fields for the APs in that channel.

[0173] Figure 13 FIG2 shows a TBTT information field according to some embodiments. The TBTT information field may include an indication of the TBTT offset of the corresponding neighbor AP, for example, relative to the transmitting AP. The TBTT information field may include an indication of the BSSID and / or short SSID of the corresponding neighbor AP. The TBTT information field may include an indication of the BSS parameters of the corresponding neighbor AP, for example, Figure 14 The TBTT information field may include an indication of the 20 MHz power spectral density (PSD) of the corresponding neighbor AP. The TBTT information field may include an indication of the MLD parameters of the corresponding neighbor AP, such as Figure 16 Further discussion.

[0174] Figure 14The BSS parameter field according to some embodiments is shown. The BSS parameter field may include an indication of whether on-channel tunneling (OCT) is recommended, for example, whether a STA can tunnel management frames through one AP to another AP. The BSS parameter may indicate whether the corresponding neighbor AP uses the same SSID as the transmitting AP and / or may indicate the SSID of the corresponding neighbor AP. The BSS parameter may indicate one or more BSSIDs of the corresponding neighbor AP. The BSS parameter may indicate the transmitted BSSID of the corresponding neighbor AP, for example, the BSSID used by the corresponding neighbor AP to transmit beacons. The BSS parameter may indicate whether the corresponding neighbor AP is a member of an extended service set (ESS). The ESS indication may further indicate whether the AP is a member of an ESS with co-located or non-co-located APs in the 2.4 GHz and / or 5 GHz frequency bands. The BSS parameter may indicate whether the corresponding neighbor AP actively responds to unsolicited probe responses. The BSS parameter may indicate whether the corresponding neighbor AP is co-located with the transmitting AP.

[0175] Figure 15 A TBTT information header according to some embodiments is shown. The TBTT information header may include an indication of the TBTT information field type. In some embodiments, the number of indications may correspond to the number of TBTT information fields included in the neighbor AP information field. In some embodiments, a single indication of the TBTT information field type may apply to all included TBTT information fields. The TBTT information header may include an indication of whether the corresponding neighbor AP is filtered. The TBTT information header may include an indication of the number of TBTT information fields. The TBTT information header may include an indication of the length of the TBTT information fields (e.g., individually or as a group).

[0176] Figure 16 The MLD parameter field according to some embodiments is shown. The MLD parameter field may include an indication of the MLD ID of the corresponding AP MLD. For example, a single physical device may include multiple AP MLDs, for example, and each AP MLD may include multiple APs. The MLD ID may identify the corresponding AP MLD relative to the AP MLD list. The Link ID may indicate the link identifier of the corresponding AP within the AP MLD to which the transmitting AP is attached. In other words, the MLD ID may describe one AP MLD among multiple AP MLDs, and the Link ID may describe one AP for a particular AP MLD. For example, where the transmitting AP is 712a and the corresponding AP is 712b, the MLD ID may indicate that both APs have the same AP MLD. The Link ID may indicate that the corresponding AP is the first AP among three other APs (e.g., 712b-712d) for the AP MLD.

[0177] The MLD parameter field may include an indication of a change sequence, such as a version ID. The change sequence may be incremented when a beacon corresponding to the AP changes (e.g., significantly). For example, the change sequence field may be incremented when a channel switch is announced (e.g., in 908) and / or when a channel switch is completed (e.g., in 918), among other possibilities.

[0178] Figure 17 ML elements according to some embodiments are shown. As summarized in the table below, ML elements can be any of various variant forms, such as basic, probe request, or reconfiguration.

[0179]

[0180] The ML element may include an element identifier, a length indication, and an element ID extension. In the illustrated example, the element identifier may be 255, for example, indicating that an extension ID may be present. The ML element may include an ML control field (e.g., regarding Figure 18 ML elements may include common information (e.g., about Figure 19 Further described) and link information of a specific link (e.g., AP). For example, link-specific information may include a per-STA profile. In addition, vendor-specific information may be included.

[0181] The ML element may also include an indication of a (eg, upcoming) channel switch by the transmitting AP and / or the subordinate AP. The indication may indicate which AP is changing channels and / or whether parameters of the AP changing channels will change.

[0182] It should be understood that the ML element may be transmitted by an AP MLD or a non-AP MLD. For example, an AP MLD may include a beacon or a probe request response (e.g., as compared to Figure 9 The non-AP MLD may transmit an ML element indicating its capabilities and / or parameters, as discussed with respect to 912.

[0183] Figure 18 An exemplary multilink control field according to some embodiments is shown. The ML control field may indicate the type of ML element (e.g., basic, probe request, or reconfiguration, as discussed above; see also Figure 34 ). The ML control field may include a 1-bit indicator indicating: whether an MLD MAC address exists, whether link identification information exists, whether a BSS parameter change count exists, whether medium synchronization delay information exists, whether enhanced ML (EML) capability exists, and whether MLD capability exists.

[0184] Figure 19An exemplary common information field according to some embodiments is shown. The common information field may include the MAC address of the APMLD. The common information field may include information of all link IDs. The common information field may include parameters or information of all links. For example, a transmit power increment may be included. The common information field may include an indication of a BSS parameter change count. The common information field may include medium synchronization delay information (see Figure 20 ). Common information fields may include EML capabilities (see Figure 21 ). The public information field may include MLD capabilities (see Figure 22 ).

[0185] Figure 20 An exemplary medium synchronization delay information field is shown according to some embodiments.

[0186] Figure 21 An example EML capability field is shown according to some embodiments.

[0187] Figure 22 An exemplary MLD Capability field according to some embodiments is shown. The MLD Capability field may indicate the maximum number of links that a transmitting MLD (eg, AP MLD or non-AP MLD) may support simultaneously.

[0188] Figure 23 Shown is a diagram similar to Figure 17 ML elements. Figure 23 The first per-STA profile (eg, profile x) is highlighted. Figure 24 The per-STA profile is further described.

[0189] Figure 24 Each STA profile according to some embodiments is shown. Each STA profile may include a sub-element ID, a length indicator, a STA control field (for Figure 25 Further described). The per-STA profile may include STA information, including MAC address, beacon interval, Delivery Traffic Indication Message (DTIM) count, DTIM, period, NSTR bitmap, etc. An attached AP may have a separate beacon interval and DTIM periodicity. In some embodiments, the beacon period may change in association with a channel switch. Thus, this field may indicate a new beacon period for an upcoming channel switch. In some embodiments, in the absence of an indication of a new interval, a non-AP may perform a passive scan, for example, assuming that the interval between beacons is 100ms or assuming that the beacon interval remains unchanged. An NSTR bitmap value of 1 may indicate that the reported link and other links are operating in NSTR mode. When present, the per-STA profile may include NSTR information for all link pairs. The per-STA profile may include a STA profile, including STA-specific capability information.

[0190] Figure 25 The STA Control field according to some embodiments is shown. The STA Control field may include a link ID. The corresponding subordinate AP of the AP MLD may have a unique link ID. The link ID may be constant (e.g., may not change) during the lifetime of the AP MLD. The STA Control field may include an indication of whether the STA profile is complete and whether a MAC address is present. The STA Control field may include an indication of whether a beacon interval exists and an indication of whether DTIM information exists. The STA Control field may include an indication of whether an NSTR link pair and / or NSTR bitmap exists.

[0191] Figure 26 An example of link reconfiguration according to some embodiments is shown. As shown, the AP MLD and the non-AP MLD may have two links. According to some embodiments, the non-AP MLD may request a third link (2614). To do so, the non-AP MLD may request configuration of STA 3, for example, in message [1]. After reconfiguration, the MLD may have three links (2616) and may use them to exchange and confirm data.

[0192] During ML reconfiguration, non-AP MLD and AP MLD can maintain the same security. Non-AP MLD can request to add and / or delete links. AP MLD can accept or reject link deletions. Reconfigure ML elements can be used to communicate single-link changes. When the AP switches channels, the link can be maintained. No additional signaling from the non-AP MLD may be required to continue operating on the link (e.g., on the new channel).

[0193] Figure 9 One use case of the method may include a SoftAP that performs capability changes. A SoftAP may refer to a device such as a smartphone that temporarily acts as an AP. The AP MLD may change its subordinate AP capabilities. Operational parameters may be changed and the new values of these elements may be signaled via the Change Sequence Number and Critical BSS Update fields in the Beacon and Probe Response frames. However, according to some embodiments, capability parameters such as HT Capability, VHT Capability, HE Capability, EHT Capability may not be changed in the same manner. One possibility for performing such an update of subordinate AP capability parameters is to perform such an update of the subordinate AP capability parameters according to Figure 9 For example, the AP MLD may signal the AP to switch channels as described above. Figure 9The channel switch described above. In some cases, the subordinate AP may perform a channel switch to the same channel and only change its capabilities. The AP MLD may time the channel switch to coincide with the change in capabilities and thereby allow the associated STAs to prepare new parameter and / or capability values. For example, such parameter / capability changes may be performed to save power (e.g., in response to the battery level of the soft AP MLD) or otherwise adapt to changing circumstances. As another example, this may allow the soft AP MLD to modify its AP operation, for example, by switching to an idle channel. An idle channel may be a channel without interference or other transmissions. All transmission resources of an idle channel are available to the AP.

[0194] in addition, Figure 9 The method can increase AP availability (e.g., and reduce latency, delay, etc.).

[0195] Figure 27 1 illustrates channel switching according to some embodiments. As shown, AP1 may operate on link 1 and may transmit a beacon (e.g., on link 1) indicating that it will switch channels. After the switch, AP1 may operate on the new channel and may transmit beacons, e.g., without signaling related to the channel switch. The maximum channel switch time may be indicated in beacons transmitted by AP2 and / or AP3 during the channel switch time. Thus, the non-AP MLD may use the indication of the maximum channel switch time to determine when AP1 may begin operating on the new channel.

[0196] Figure 28 An extended channel switch element according to some embodiments is shown. Such an extended channel switch element may be included, for example, in a beacon transmitted by the switching AP and / or subordinate APs before a channel switch. The extended channel switch element may include an element ID, a length, a channel switch mode, a new operating category, a new channel number, and a channel switch count. The new operating category and the new channel number may indicate the channel on which the AP will operate after the switch. The channel switch count may describe the number of TBTTs before the switch. The channel switch mode may describe whether the associated STA may transmit in the old channel during a grace period. For example, if an AP or STA detects a radar in its old operating channel, the AP may not allow its associated STAs to continue operating in the channel.

[0197] Figure 29 FIG2 shows a maximum channel switching time element according to some embodiments. The maximum channel switching time element may be included in a beacon transmitted by an attached AP during a channel switching time. The switching time may indicate the number of time units (TUs) that the AP will continue to operate in the first / old channel.

[0198] Figure 30 , including using ML elements (e.g., as described with respect to Figure 17 Channel switching described).

[0199] As shown, AP1 may operate on Link 1 and may transmit (e.g., on Link 1) a beacon indicating that it will switch channels. Beacons transmitted by AP1 during a grace period (e.g., after determining the switch and before the switch) may include ML elements, such as reconfiguration variants. For example, the ML element may include a per-STA profile indicating operational parameters to be implemented for AP1 after the switch. Beacons transmitted by AP1 before the switch may include an extended channel switch element.

[0200] During the grace period, AP2 and / or AP3 may transmit beacons on their respective channels. These beacons may include an extended channel switch element. Furthermore, these beacons may include, for example, an ML element for a reconfiguration variant. For example, the ML element may include a per-STA profile indicating operational parameters to be implemented for AP1 after the switch. The ML elements of beacons transmitted by AP2 and / or AP3 may differ from those of beacons transmitted by AP1 (e.g., by identifying AP1 as an attached AP rather than a transmitting AP, as in the case of beacons transmitted by AP1).

[0201] During the handover, AP2 and / or AP3 may transmit beacons on their respective channels. These beacons may include a maximum channel switch time element. In addition, these beacons may include, for example, an ML element indicating a reconfiguration variant. For example, the ML element may include a per-STA profile indicating operational parameters to be implemented for AP1 after the handover.

[0202] After switching, AP1 may operate on the new channel and may transmit beacons, e.g., without signaling associated with the channel switch. After switching, AP2 and / or AP3 may continue to operate on their respective channels and transmit beacons, e.g., without signaling associated with the channel switch.

[0203] It should be understood that, according to some embodiments, any or all of the beacons transmitted during the grace period and / or the handover period may include an ML element indicating operational parameters to be implemented for AP1 after the handover. For example, beacons transmitted by AP2 and / or AP3 during the grace period may omit this information in some cases, while this information may be included in beacons transmitted by AP1 during the grace period and by AP2 and / or AP3 during the handover period.

[0204] The following table provides examples of the types of information included in beacons during different time periods according to some embodiments.

[0205]

[0206] During a grace period when one or more APs are switching channels, a reconfiguration variant ML element can be added to beacons and ML-Probe Responses (e.g., by the changing AP and / or other subordinate APs). The ML element can contain one per-STA profile sub-element for each AP in the grace period for the upcoming channel switch. According to some embodiments, the basic variant and reconfiguration variant ML elements can be similar. The reconfiguration ML element can include a link ID and a deletion request as additional fields, as well as various possibilities.

[0207] When a reconfiguration variant ML element is added to a beacon or ML-Probe Response, the Link Id may identify the AP for which the parameters are listed in the corresponding per-STA profile. For example, for a per-STA profile describing the added AP or the AP after the change, the new Link Id is set to 15 (a signaling unknown value). Similarly, a deletion request may be indicated as a Link ID set to 0. Thus, for a reconfiguration ML element associated with a channel switch, the per-STA profile of the AP before the switch may include a Link ID set to 0, and the per-STA profile of the AP after the channel switch may include a Link ID set to 15. Both per-STA profiles of the AP may be included in the same ML element. Thus, the ML element may include both the parameters of the AP before and after the channel switch.

[0208] Figure 31 Capabilities and operations in different frequency bands according to different 802.11 standards are shown according to some embodiments.

[0209] As described above, according to some embodiments, channel switching may or may not include changes in AP parameters. Correspondingly, channel switching may be indicated differently depending on whether a parameter change is included, for example, Figures 32 to 33 shown.

[0210] Figure 32 The beacon frame format is shown when a channel switch does not change the AP MLD or the parameters of the switched AP (e.g., the AP MLD and the parameters of the switched AP are the same after the switch as before the switch). For example, a beacon may be transmitted by a first AP (e.g., AP1) before a channel switch is made by the changed AP. AP1 may be the same as or different from the first AP that transmitted the beacon. The channel switch may not change the parameters of AP1. The beacon frame may include link-specific information (e.g., BSSID, capabilities, etc.) and RNR, for example, as described with respect to Figure 10 In addition, the beacon frame may include an ML element with a per-STA profile of the affiliated AP. The ML element may also include a bit indicating that channel switching will be performed without parameter changes.

[0211] In some embodiments, information regarding whether / how the parameters were changed may be included in the channel switch element.

[0212] Figure 33 The beacon frame format is shown when a channel switch changes the AP MLD or the parameters of the switched AP (e.g., the APMLD and / or the parameters of the switched AP are different after the switch than before the switch). For example, a beacon may be transmitted by a first AP (e.g., AP1) before a channel switch is made by the changed AP. AP1 may be the same as or different from the first AP that transmitted the beacon. The channel switch may change the parameters of AP1. The beacon frame may include link-specific information (e.g., BSSID, capabilities, etc.) and RNR, for example, as described with respect to Figure 10 and Figure 32 In addition, Figure 32 As shown, the beacon frame may include an ML element with a per-STA profile for the attached AP. Additionally, the beacon frame may include a second ML element with a reconfiguration variant. The reconfiguration variant ML element may, for example, describe the attached AP after the handover of the AP MLD in the ML control, common information, and / or link information fields. Furthermore, a per-STA profile for AP1 may be included, describing the AP1 parameters to be in place after the handover.

[0213] Figure 34 The following diagram shows possible encodings and values of the ML Type subfield of, for example, the ML Control field according to some embodiments. As shown, the ML Type subfield may indicate a base variant, a probe request variant, or a reconfiguration variant of the ML element.

[0214] Figure 35 Possible sub-element IDs of an ML element according to some embodiments are shown.

[0215] The per-STA sub-element may begin with the per-STA control field. Figure 36 shows the per-STA control field transmitted by a non-AP, and Figure 37 A per-STA control field transmitted by the AP (eg, AP MLD) is shown.

[0216] In association with channel switching, the associated non-AP MLD may take various courses of action.

[0217] As one possibility, the STA may continue to operate with the parameters signaled during the initial association / link setup (e.g., by the STA to the AP MLD). The parameter values used by the STA after the switch may be the greater of the parameter values indicated by the STA at association or the parameter values indicated by the AP for the new channel / link. In other words, the non-AP may lower its parameter values in response to the AP lowering its parameter values. Furthermore, for example, if the STA cannot operate with the same parameters in the new channel (or otherwise determines to lower its parameters), the STA may limit its bandwidth and NSS by using an Operational Mode Indication (OMI). This OMI may be transmitted before, during, or after the channel switch. If the STA does nothing (e.g., does not transmit an indication of capabilities or other data), the AP may assume that the STA is in power-save mode in the new channel and may not send traffic to the STA on the new channel (e.g., until the STA verifies the new channel).

[0218] As another possibility, the non-AP MLD can add a link to the AP in the new channel by using ML reconfiguration. In other words, the non-AP MLD can request the AP MLD to add such a link. According to some embodiments, the non-AP MLD can indicate the requested parameters for the new link, for example, using a per-STA profile in an ML element.

[0219] As another possibility, the non-AP MLD may reconfigure parameters of an attached STA (e.g., on the non-AP side) that has a link with the switched AP. In other words, the non-AP MLD may request parameters of the attached AP in response to an indication that a channel switch is possible. For example, the non-AP MLD may send an ML reconfiguration request (e.g., ML element, reconfiguration variant) with the requested modified parameters for the STA and AP (e.g., via an attached STA linked to the changed AP and / or via a different STA).

[0220] Figure 38 The diagram illustrates the operation of STA 1 associated with AP 1, for example, continuing a link in a new channel, according to the possibilities discussed in the three previous paragraphs. As indicated by the bold line in the diagram, prior to the channel switch, associated STA 1 may be operating in communication with AP 1 via link 1. After the channel switch, STA 1 may verify the new channel and may resume operating in communication with AP 1 on the new channel. AP 1 may consider STA 1 to be in power-saving mode and / or may not send any downlink data to STA 1 (e.g., via the new link) until STA 1 verifies the new link.

[0221] As another possibility, according to some embodiments, the non-AP MLD may terminate the link associated with the channel switch. For example, the STA may send an ML reconfiguration and signal the link deletion. If the non-AP MLD is unable to operate in the new channel (e.g., with acceptable performance, parameters, etc.) due to interference from other radios, other links, etc., the non-AP MLD may signal the link deletion. For example, if the interference at the non-AP MLD is above a threshold on the new channel (e.g., due to activity on other radios or other links of the non-AP MLD and / or activity of other devices), the non-AP MLD may determine to terminate the link and may signal the AP MLD accordingly.

[0222] Figure 39 The diagram illustrates the operation of STA 1 associated with AP 1, for example, terminating a link, according to the possibilities discussed in the previous paragraph. As indicated by the bold line in the diagram, prior to a channel switch, associated STA 1 may operate in communication with AP 1 via link 1 for a period of time. In response to an indication of a channel switch, interference levels, and / or other information, STA 1 may terminate the link. This termination may occur before or coincide with the channel switch time.

[0223] As above about Figure 9 As described above, channel switching can occur in response to a request from a non-AP MLD. For example, the non-AP MLD can transmit an association request or other message with an ML element to the AP MLD to request the establishment of a new link or modification of an existing link. For example, the ML element can be a basic variant. The ML element can include a complete per-STA profile for each link requested by the non-AP MLD.

[0224] In response, the AP MLD may transmit an association response or other message to the non-AP. The response may include an ML connection. The ML element may be a basic variant. The ML element may include a complete per-STA profile for each link that the AP MLD will provide. In some embodiments, the ML element may include a complete per-STA profile for each link that the AP MLD accepts (e.g., a link requested by a non-AP MLD).

[0225] In some embodiments, the association request and response may not include an RNR. In some embodiments, an RNR may be included.

[0226] The following table describes ML elements that may be used to correlate requests and responses in various time periods according to some embodiments.

[0227]

[0228] According to some embodiments, the following table describes non-AP MLD operations during various time periods. The second column describes operations that may be performed in embodiments where the AP MLD signals the AP's parameters before the AP changes channels. The third column describes operations that may be performed when the AP MLD does not signal post-switching parameters before switching.

[0229]

[0230] Figures 40 to 49 and Operational Channel Verification (OCV)

[0231] In some embodiments, the association information may not be encrypted or integrity protected. An attacker could send an association response with incorrect information, causing interoperability issues.

[0232] Operational Channel Verification (OCV) may be a means to signal and verify the following parameters: BSS primary channel, secondary 20 MHz and / or 80+80 MHz configuration (eg, 160 MHz bandwidth divided into two 80 MHz parts), among other possibilities.

[0233] A non-AP MLD (e.g., a STA) can verify parameters, for example, to ensure that the AP is operating on a channel and / or with parameters signaled by the AP (e.g., or another subordinate AP of the AP MLD). The AP MLD can transmit Operational Channel Information (OCI) to the non-AP MLD. The OCI can indicate channels and / or parameters for one or more APs. Thus, the STA can send and receive data with the AP based on verification of the AP using the OCI.

[0234] The embodiments described herein provide systems, methods, and mechanisms for AP MLD and non-AP MLD to perform OCV of multiple links. Figure 40 In an embodiment of the present invention, links between any number of attached APs and attached STAs can be authenticated and data can be securely exchanged using these links.

[0235] Figure 40Aspects of the method may be implemented by an AP MLD communicating with a non-AP MLD. The AP MLD and / or the non-AP MLD may be as shown and described with respect to the various figures herein, or more generally, as needed, in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the figures above. For example, a 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 circuitry such as 130, 230, 232, 329, 330, 430, and various possibilities) may cause a wireless device, a STA, a UE, a non-AP MLD, and / or an AP MLD, or other device to perform such method elements.

[0236] Note that although described in relation to the use of communication techniques and / or features associated with IEEE and / or 802.11 (e.g., 802.11be) specification documents, Figure 40 but this description is not intended to limit the present disclosure, and Figure 40 Aspects of the method may be employed in any suitable wireless communication system as desired.

[0237] The method shown may also be used with any of the systems, methods, or devices shown in the figures, in addition to other devices. In various embodiments, some of the method elements shown may be performed concurrently in an order different from the order shown, or may be omitted. Additional method elements may also be performed as needed. As shown, the method may operate as follows.

[0238] According to some embodiments, non-AP MLD 106 may verify a first link with AP MLD 112 (4002). The first link may be verified as part of a 4-way handshake and association. The first link may be between a first subordinate AP (e.g., 812a, 812b, or 812c, etc.) and a corresponding first STA (e.g., 806a, 806b, or 806c, etc.). The first link may operate on a first channel.

[0239] The AP MLD may transmit information about one or more other affiliated APs (e.g., 812a, 812b, or 812c, etc.) to the non-AP MLD. For example, the information may be or include an OCI. For example, the AP MLD may transmit a Reduced Neighbor Report (RNR) or an ML element including the information (e.g., including an OCI element). The information may be transmitted as part of a beacon, a probe response (e.g., in response to a probe request from a non-AP MLD), and / or an association response (e.g., in response to an association request for the first link from a non-AP MLD). The information may be transmitted before, concurrently with, and / or after verification of the first link. The information may be transmitted by the first AP and received by the first STA, and / or the information may be transmitted by the second AP and received by the second STA via a second channel.

[0240] According to some embodiments, non-AP MLD 106 may verify 4004 the second link with AP MLD 112. Non-AP MLD 106 may verify any number of additional links with AP MLD 112. For example, a link between any subordinate AP (e.g., 812a, 812b, or 812c, etc.) and a corresponding STA (e.g., 806a, 806b, or 806c, etc.) may be verified.

[0241] According to some embodiments, to verify a link (e.g., a second link), the following steps may be performed. AP MLD 112 may transmit a beacon using the associated AP corresponding to the link. Non-AP MLD 106 may receive the beacon. The non-AP may confirm that the beacon corresponds to previously known information about the AP. For example, the non-AP may compare attributes of the received beacon (e.g., operating category, primary channel number, etc.) with attributes indicated by the AP MLD in the OCI element.

[0242] If the attributes do not match, the AP MLD may determine that the beacon is invalid. Therefore, the AP MLD may not respond to the beacon. In addition, the AP MLD may not transmit data on the link unless or until a valid beacon is received.

[0243] If the attributes match, the non-AP MLD may determine that the beacon is valid and may transmit an uplink message (e.g., data) to the AP MLD using the link. For example, the transmission may be from an affiliated STA corresponding to the link. The AP MLD may receive the data using the affiliated AP corresponding to the link.

[0244] After the non-AP MLD receives the beacon and the AP MLD receives the uplink message, the two devices may consider the link verified.Thus, the devices may be operable to exchange further messages in the uplink and / or downlink directions.

[0245] Figure 41 STAs associated with an AP are shown according to some embodiments. In the illustrated example, a single link is used.

[0246] Figure 42 An example of an OCI element according to some embodiments is shown. An AP MLD may send such an OCI element to describe an affiliated AP operating on a particular channel. A non-AP MLD may use this information to determine whether a beacon it receives is a valid beacon for an affiliated AP. Figures 47 and 48 Additional diagrams of OCI elements are described, such as may be used in multi-link communications.

[0247] Figure 43 An AP MLD communicating with a non-AP MLD is shown according to some embodiments. The link between AP1 and STA1 can be the first link, which can be verified, for example, during the association and 4-way handshake process. Other links (e.g., between AP2 and STA2 and between AP3 and STA3) can also be verified, as described above with respect to 4004.

[0248] Figure 44A 、 Figure 44B and Figure 44C An example of OCV during ML setup according to some embodiments is shown. The process may proceed as follows:

[0249] [1] The first AP, shown on vertical line B, may transmit a beacon to the first STA. The beacon may be transmitted on channel 2. The beacon may include an ML element without an AP profile. The beacon may indicate that the first AP may switch from channel 2 to channel 4. The beacon may include RNRs describing APs on channels 5 and 6. These APs are shown on vertical lines D and F, respectively. The first STA (vertical line A) may receive the beacon on channel 2.

[0250] [2] The first STA may transmit an ML-Probe Request to the first AP on channel 2. The Probe Request may include an ML element requesting information about all affiliated APs.

[0251] [3] The first AP may transmit an ML probe response to the first STA on channel 2. The response may include an ML element with a complete profile of the AP operating on channels 5 and 6.

[0252] [4] A second STA operating on channel 5 may transmit a probe request to a second AP operating on channel 5.

[0253] [5] In response to the probe request, the second AP may transmit a probe response including an ML element without an AP profile and an RNR identifying the APs on channels 2 (changed to channels 4) and 6. Thus, at this point, the non-AP MLD may receive channel information about all subordinate APs. This may include timing information for channel switching.

[0254] [6] The second AP may transmit a beacon that includes an ML element without an AP profile and an RNR identifying the APs on channels 2 (changed to channel 4) and 6. Thus, at this point, the non-AP MLD can receive channel information about all attached APs. This may include timing information for channel switching. The beacon may replace or supplement the probe response in [5].

[0255] The AP MLD and non-AP MLD may start a SAE handshake (4414), for example, using channel 5.

[0256] [7] The third AP may transmit a beacon including an ML element without an AP profile and RNR identifying the APs on channels 2 (changed to channel 4) and 5. Timing information for channel switching may be included.

[0257] [8] The second STA may transmit an association request message including an ML element with a complete profile of the first STA (on channel 2) and the third STA (on channel 6, shown on vertical line E). The association request message may request association for the STAs listed in the ML element. Thus, the association request may indicate a request for three links (e.g., the first STA on channel 2, later on channel 4, and the second and third STAs on channels 5 and 6). The association request may indicate that the first and third STAs are in power save mode.

[0258] [9] The second AP may transmit an association response including the complete profiles of the first and third APs.

[0259] [10-13] The second AP and the second STA may perform a 4-way handshake including messages 1-4. A key distribution element (KDE), a group transient key (GTK), and an integrity group transient key (IGTK) may be exchanged. The GTK may encrypt the group frame. The IGTK may be used for integrity protection of the group frame. The handshake may include information (e.g., OCI) for all links, for example, in msg3

[12] . Thus, at this point, the non-AP MLD may receive information sufficient to verify the links with any or all of the attached APs. The 4-way handshake may be completed (4418). At this point, the non-AP MLD may consider all links verified. However, the AP MLD may consider the first and third links to be inactive (e.g., in power save mode) until further indication or message is received from the non-AP MLD.

[0260] In some embodiments, link verification may require the STA attached to the associated non-AP MLD to transmit frames on the verified link or receive frames from the AP attached to the associated AP MLD. Prior to the 4-way handshake, there may be probe request / response and beacon frame reception. This can be considered a required TX or RX. In other words, verification may be based in part on frames exchanged in the uplink or downlink direction prior to the handshake. In some embodiments, after receiving the OCI value, the non-AP MLD may send additional encrypted and integrity-protected frames on these verified links.

[0261]

[14] The second STA may transmit an add block acknowledgement (ADDBA) request to the second AP. The ADDBA request may request the initiation of a block acknowledgement (BA) for one or more traffic identifiers (TIDs) (e.g., TID7).

[15] The second AP may transmit a response. A BA may be initiated in each direction for the requested TIDs (4420).

[0262]

[16] The second AP may transmit messages linking TID0 to traffic on channels 2, 4, and 5.

[0263]

[17] The second STA may accept the mapping.

[0264]

[18] The second STA may transmit data, and

[19] the second AP may BA acknowledge the data.

[0265]

[20] The first AP may transmit a beacon indicating a channel switch.

[0266] [21-24] The first STA may exchange data and BA with the first AP, for example, on channel 2.

[0267] In some embodiments, the data exchange of [21-24] can verify the link. For example, the STA can check that its data is received and, in response, that the STA receives a corresponding acknowledgment (e.g., BA) on the correct channel. If this data exchange and acknowledgment is not performed, the non-AP MLD can consider the channel verification to have failed and can stop operating with the AP MLD.

[0268]

[25] The second AP may transmit a beacon indicating a channel switch.

[0269] Figure 45 An example of OCV during a fast ML transition (e.g., channel switching) according to some embodiments is shown. This process may be performed between AP MLD1 and non-AP MLD1, which may have links between three corresponding dependent STAs and the AP. The process may be performed as follows:

[0270] STA1 (4502) of non-AP MLD1 may associate with the first AP1 (4504) of AP MLD1. [1] AP3 (4512) may transmit a beacon. The beacon may include channel information (e.g., RNR, identifying the channel of the AP affiliated with AP MLD1).

[0271] [2] STA2 may transmit an authentication request.

[0272] [3] In response to the authentication request, AP2 may transmit an association request including the ML-OCI (e.g., the OCI of the subordinate AP of AP MLD1). Thus, the non-AP MLD may have sufficient information to verify the link.

[0273] [4-5] STA2 may transmit an association request, and AP2 may transmit a response.

[0274] The non-AP MLD can verify all 3 links based on the OCI information and the authentication response. The non-AP MLD can now start using all APs.

[0275] Figure 46 An example of OCV during a channel switch (e.g., fast ML transition) according to some embodiments is shown. Non-AP MLD can learn new channel information in the beacon (e.g., the AP's OCI after a channel switch). The beacon can be integrity protected, for example, using BIGTK. Link-specific authentication can be used, for example, as discussed above.

[0276] In some embodiments, after an AP switches channels (e.g., after AP1 starts on a new link), a STA may send a robust SA-Query Request to request encryption information for the AP's new channel. The AP may respond with an SA-Query Response, for example, providing security parameters. The SA-Query Request and Response may be transmitted over any link. According to some embodiments, the SA-Query may be transmitted during the time the AP transitions to a new channel. The SA-Query Request may include channel information for all APs or the AP to which the STA is associated.

[0277] The non-AP MLD may verify the link (eg, based on receipt of an SA query response or a beacon in the new channel). For example, the non-AP MLD may determine that attributes of the beacon or other message in the new channel match attributes indicated in the OCI.

[0278] Figure 47 1 shows an ML-OCI element according to some embodiments. The ML-OCI element may include an indication of the number of links (e.g., N links) and link-specific OCI information for each of the number of links. The link-specific OCI information may be, for example, about Figure 48 The OCI link information field.

[0279] Figure 48 The OCI link information field according to some embodiments is shown. The OCI information field may include the following information: Figure 42 Similar information as discussed for a single link.

[0280] Figure 49 The traditional elements / fields are shown compared to the new elements / fields described herein. It is worth noting that various ML-OCI information has been added. The ML-OCI information supports the verification of multiple links.

[0281] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining 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 stated to users.

[0282] In one set of embodiments, a method may include: at an access point (AP) multi-link device (AP MLD): transmitting a first beacon on a first channel for a first auxiliary AP, wherein the first beacon indicates at least one parameter for operation of the first auxiliary AP on the first channel; transmitting a second beacon on a second channel different from the first channel for a second auxiliary AP, wherein the second beacon indicates at least one parameter for operation of the second auxiliary AP on the second channel; determining before a first time to perform a channel switch from the first channel to a third channel different from the first channel for the first auxiliary AP at the first time; determining before the first time at least one parameter for operation of the first auxiliary AP on the third channel; transmitting a third beacon on the first channel for the first auxiliary AP before the first time, wherein the third beacon indicates the at least one parameter for operation of the first auxiliary AP on the third channel; and transmitting a fourth beacon on the third channel for the first auxiliary AP after the first time, wherein the fourth beacon indicates at least one parameter for operation of the first auxiliary AP on the third channel.

[0283] In some embodiments, the method may further include transmitting a fifth beacon on the second channel for the second subordinate AP before the first time, wherein the fifth beacon indicates at least one parameter for operation of the first subordinate AP on the third channel.

[0284] In some embodiments, the third beacon and the fifth beacon further indicate a maximum channel switching time starting at the first time.

[0285] In some embodiments, the method may further include transmitting a sixth beacon on the second channel for the second accessory AP during the maximum channel switching time, wherein the sixth beacon indicates: the maximum channel switching time; and at least one parameter for operation of the first accessory AP on the third channel.

[0286] In some embodiments, the sixth beacon further indicates that the first subordinate AP is switching channels.

[0287] In some embodiments, the maximum channel switching time begins at a first time, wherein the third beacon and the fifth beacon further indicate the first time.

[0288] In some embodiments, at least one parameter for operation of the first accessory AP on the third channel is different from at least one parameter for operation of the first accessory AP on the first channel.

[0289] In some embodiments, the method may further include transmitting a sixth beacon on the second channel for the second subordinate AP during the maximum channel switching time when the first subordinate AP is unavailable, wherein the sixth beacon includes a reconfiguration variant multilink element.

[0290] In some embodiments, the method may further include: exchanging data with the non-AP-MLD using the first subordinate AP before the first time; and waiting until the non-AP-MLD authenticates the first subordinate AP on the third channel before transmitting data to the non-AP-MLD using the first subordinate AP on the third channel after the first time.

[0291] In a second set of embodiments, an apparatus may include: a processor configured to cause a non-access point (AP) multi-link device (MLD) (non-AP MLD): receive a first message from an AP MLD, the first message including: an indication that a channel switch of an attached AP will be performed at a future time; and an indication of a first parameter value to be used by the attached AP after the channel switch; before the future time: determine, based on the first parameter value, a second parameter value to be used by the non-AP MLD to communicate with the attached AP after the channel switch; and transmit a second message including an indication of the second parameter value to the AP MLD; and implement the second parameter value at the first time; and exchange data with the attached AP using the second parameter value after the channel switch.

[0292] In some embodiments, the processor is further configured to cause the non-AP MLD to: transmit a request for channel switching to the AP MLD, wherein the request for channel switching indicates at least one of the first parameter value or the second parameter value.

[0293] In some embodiments, the request for channel switching comprises an association request; and the first message comprises an association request response.

[0294] In some embodiments, the request for a channel switch includes a request to add an auxiliary AP.

[0295] In some embodiments, the processor is further configured to cause the non-AP MLD to: transmit a probe request to the AP MLD, wherein the first message includes a response to the probe request.

[0296] In some embodiments, the probe request includes a multi-link (ML) element that includes a complete profile of the attached AP after the channel switch.

[0297] In some embodiments, the second parameter value corresponds to the same parameter as the first parameter value. In other words, the first parameter value and the second parameter value can correspond to a common parameter type, for example, they can both refer to the same setting / parameter and can have the same or different values.

[0298] In some embodiments, the processor is further configured to cause the non-AP MLD to verify the new link with the AP.

[0299] In a third set of embodiments, a non-access point (AP) multi-link device (MLD) (non-AP MLD) may include: a radio component; and a processor operably coupled to the radio component and configured to cause the non-AP MLD to: establish communication with the AP MLD on a first channel using a first subordinate AP of the APMLD, wherein establishing communication includes: performing a handshake with the AP MLD; receiving information of a second subordinate AP of the AP MLD; and verifying the first subordinate AP; and verifying the second subordinate AP of the APMLD based on the information.

[0300] In some embodiments, verifying the second subordinate AP of the AP MLD includes: receiving a beacon of the second subordinate AP on a second channel different from the first channel; and transmitting data to the AP MLD using the second subordinate AP on the second channel.

[0301] In some implementations, the receiving information occurs during one of: a multilink setup; or a fast multilink transition (eg, a channel switch).

[0302] In some embodiments, the receiving information includes receiving a multi-link operations channel information element.

[0303] In some embodiments, the multilink operating channel information element is received in message 3 (MSG3) of a handshake.

[0304] In some embodiments, the processor is further configured to cause the non-AP MLD to: receive second information associated with a third subordinate AP of the AP MLD.

[0305] In some embodiments, the processor is further configured to cause the non-AP MLD to: verify a third subordinate AP of the AP MLD based on at least the second information.

[0306] In a fourth set of embodiments, a method may include: an access point (AP) multi-link device (AP MLD) establishing communication with a non-AP MLD on a first channel using a first subordinate AP of the AP MLD. Establishing communication may include: performing a handshake with the non-AP MLD; and transmitting information that can be used to authenticate a second subordinate AP to the non-AP MLD. The method may also include exchanging data with the non-AP MLD via the second subordinate AP of the AP MLD.

[0307] In some embodiments, information that can be used to authenticate the second subordinate AP is transmitted in message 3 (MSG3) of the handshake.

[0308] In some embodiments, message 3 (MSG3) also includes information that can be used to authenticate the first affiliated AP.

[0309] In some embodiments, message 3 (MSG3) also includes information of a third subordinate AP that can be used to verify the AP MLD.

[0310] In some embodiments, information useful for authenticating the second subordinate AP is transmitted during the multi-link setup.

[0311] In some embodiments, information useful for authenticating the second subordinate AP is transmitted during a fast multi-link transition.

[0312] In some embodiments, information useful for authenticating the second affiliated AP is transmitted in a query response in response to a query request received from a non-AP MLD.

[0313] In a fifth set of embodiments, a non-access point (AP) multi-link device (MLD) (non-AP MLD) may establish communication with an AP MLD on a first channel using a first subordinate AP of the AP MLD, wherein establishing communication includes performing a handshake with the AP MLD. The non-AP MLD may receive a beacon from a second subordinate AP of the AP MLD. The non-AP MLD may transmit an authentication request to the AP MLD and receive an association request from the AP MLD, the association request including information about the second subordinate AP. The non-AP MLD may authenticate the second subordinate AP based on the information about the second subordinate AP.

[0314] In some embodiments, the non-AP MLD may compare at least one attribute of the beacon with a corresponding attribute included in the information about the second affiliated AP.

[0315] In some embodiments, the at least one attribute includes an operation category.

[0316] In some embodiments, the at least one attribute includes a primary channel number.

[0317] In some embodiments, the information includes a multi-link operating channel information element.

[0318] In a sixth embodiment, a non-access point (AP) multi-link device (MLD) (non-AP MLD) may establish communication with an AP MLD. The non-AP MLD may receive an indication from the AP MLD that a first subordinate AP of the AP MLD is changing from a first channel to a second channel. In response to the indication, the non-AP MLD may: determine to switch a first subordinate STA of the non-AP MLD from the first channel to the second channel; determine parameters for the first subordinate STA to be used on the second channel; and communicate with the first subordinate AP via the first subordinate STA on the second channel.

[0319] In some embodiments, the indication includes an indication of a first time that the first subordinate AP is to change from the first channel to the second channel.

[0320] In some embodiments, the non-AP MLD may transmit a request to the AP MLD to switch the first affiliated AP from the first channel to the second channel, wherein the request indicates parameters of the first affiliated STA to be used on the second channel.

[0321] In some embodiments, the non-AP MLD may transmit a probe request to the AP MLD, wherein the indication is a response to the probe request.

[0322] In some embodiments, a device comprising: an antenna; a radio component coupled to the antenna; and a processing element coupled to the radio component is configured to implement a method according to any of the preceding examples.

[0323] In some embodiments, a memory medium comprises: program instructions that, when executed, cause a device to implement a method according to any of the preceding examples.

[0324] In some embodiments, a computer program comprises instructions for performing any of the methods described in the preceding examples.

[0325] In some embodiments, an apparatus includes means for performing any of the method elements described in any of the preceding examples.

[0326] In some embodiments, a method may include any act or combination of acts as substantially described herein in the detailed description and claims.

[0327] In some embodiments, a method may be substantially as described herein with reference to each or any combination of the figures contained herein, with reference to each or any combination of the paragraphs in the detailed description, with reference to each or any combination of the figures and / or detailed description, or with reference to each or any combination of the claims or examples.

[0328] In some embodiments, a wireless device may be configured to perform any action or combination of actions as substantially described herein in the detailed description, figures, examples, and / or claims.

[0329] In some embodiments, a wireless device may include any component or combination of components as described herein in the detailed description and / or figures as included in a wireless device.

[0330] In some embodiments, a non-transitory computer-readable medium may store instructions that, when executed, cause performance of any act or combination of acts as substantially described herein in the detailed description and / or figures.

[0331] In some embodiments, an integrated circuit can be configured to perform any act or combination of acts as substantially described herein in the detailed description and / or figures.

[0332] In some embodiments, a mobile station may be configured to perform any act or combination of acts as substantially described herein in the detailed description and / or figures.

[0333] In some embodiments, a mobile station may include any component or combination of components as described herein in the detailed description and / or figures as included in a mobile station.

[0334] In some embodiments, a mobile device may be configured to perform any action or combination of actions as substantially described herein in the detailed description and / or figures.

[0335] In some embodiments, a mobile device may include any component or combination of components as described herein in the detailed description and / or figures as included in a mobile device.

[0336] In some embodiments, a network node may be configured to perform any action or combination of actions as substantially described herein in the detailed description and / or figures.

[0337] In some embodiments, a network node may include any component or combination of components as included in a mobile device as described herein in the detailed description and / or figures.

[0338] In some embodiments, a non-access point multi-link device may be configured to perform any action or combination of actions as substantially described herein in the detailed description and / or accompanying drawings.

[0339] In some embodiments, a non-access point multi-link device may include any component or combination of components as included in a mobile device as described herein in the detailed description and / or figures.

[0340] In some embodiments, an access point multi-link device may be configured to perform any action or combination of actions as substantially described herein in the detailed description and / or accompanying drawings.

[0341] In some embodiments, an access point multi-link device may include any component or combination of components as included in a mobile device as described herein in the detailed description and / or figures.

[0342] The embodiments of the present 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.

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

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

[0345] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A method for communication, comprising: On the access point (AP) and multi-link device (AP MLD): transmitting a first beacon on a first channel for a first subordinate AP, wherein the first beacon indicates at least one parameter for operation of the first subordinate AP on the first channel; transmitting a second beacon on a second channel different from the first channel for a second subordinate AP, wherein the second beacon indicates at least one parameter for operation of the second subordinate AP on the second channel; determining, before a first time, to perform a channel switch from the first channel to a third channel different from the first channel for the first subordinate AP at the first time; determining, before the first time, at least one parameter for operation of the first subordinate AP on the third channel; transmitting a third beacon on the first channel for the first subordinate AP before the first time, wherein the third beacon indicates the at least one parameter for operation of the first subordinate AP on the third channel; as well as A fourth beacon is transmitted on the third channel for the first subordinate AP after the first time, wherein the fourth beacon indicates the at least one parameter for operation of the first subordinate AP on the third channel.

2. The method according to claim 1, further comprising: A fifth beacon is transmitted on the second channel for the second subordinate AP before the first time, wherein the fifth beacon indicates the at least one parameter for operation of the first subordinate AP on the third channel.

3. The method of claim 2, wherein the third beacon and the fifth beacon further indicate a maximum channel switching time starting at the first time, wherein the method further comprises: transmitting a sixth beacon on the second channel for the second subordinate AP during the maximum channel switching time, wherein the sixth beacon indicates: The maximum channel switching time; as well as The at least one parameter for operation of the first subordinate AP on the third channel. The method of claim 3 , wherein the sixth beacon further indicates that the first subordinate AP is switching channels. 5 . The method of claim 3 , wherein the maximum channel switching time starts at the first time, wherein the third beacon and the fifth beacon further indicate the first time.

6. The method of claim 1, wherein the at least one parameter for operation of the first auxiliary AP on the third channel is different from the at least one parameter for operation of the first auxiliary AP on the first channel.

7. The method according to claim 1, further comprising: Transmitting a sixth beacon on the second channel for the second subordinate AP during a maximum channel switching time when the first subordinate AP is unavailable, wherein the sixth beacon includes a reconfiguration variant multilink element.

8. The method according to claim 1, further comprising: exchanging data with a non-AP MLD using the first subordinate AP on the first channel before the first time; as well as Before transmitting data to the non-AP MLD on the third channel using the first subordinate AP after the first time, waiting until the non-AP MLD authenticates the first subordinate AP on the third channel.

9. An apparatus for communication, comprising a processor configured to cause a wireless device to perform the method according to any one of claims 1 to 8.

10. The apparatus of claim 9, further comprising a radio operatively coupled to the processor.

11. A computer program product comprising program instructions, wherein the program instructions are configured to cause a device to execute the method according to any one of claims 1 to 8.

Images