Method and apparatus for communication

Abstract

The invention relates to a method and device for communication. Methods, systems, and apparatus are described for performing channel switching by an access point (AP) multi-link device (MLD) and a non-AP MLD. The AP MLD may transmit information about parameters of the AP to be implemented after an upcoming channel handover. Further, methods, systems, and apparatus for performing multi-link channel authentication are described. The non-AP MLD and the AP MLD may verify the plurality of links for communication.

Description

[0001] Related application citation

[0002] This application is a divisional application of the invention patent application with international application number PCT / US2022 / 034804, international application date of June 23, 2022, entry into the Chinese national phase date of December 13, 2022, Chinese national application number 202280005016.4, and invention title "Method and apparatus for communication". Technical Field

[0003] This application relates to wireless communication, including techniques for wireless communication between wireless stations and / or access points in a wireless networking system. Background Technology

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

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

[0006] Mobile electronic devices can take the form of smartphones or tablets that users typically carry. Wearable devices (also known as accessory devices) are a newer form of mobile electronic device, an example being a smartwatch. Additionally, low-cost, low-complexity wireless devices designed for static or dynamic deployment are rapidly increasing as part of the development of the “Internet of Things”. In other words, the required devices are becoming increasingly diverse in terms of complexity, capabilities, traffic patterns, and other characteristics.

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

[0008] The implementation schemes described herein relate to systems, methods, apparatuses, and mechanisms for channel switching and channel verification by AP MLDs and non-AP MLDs.

[0009] The AP MLD can transmit a first beacon for a first affiliated AP on a first channel, wherein the first beacon indicates at least one parameter for operation of the first affiliated AP on the first channel. The AP MLD can transmit a second beacon for a second affiliated AP on a second channel different from the first channel, wherein the second beacon indicates at least one parameter for operation of the second affiliated AP on the second channel. The AP MLD can determine, before a first time, that a channel handover from the first channel to a third channel different from the first channel can be performed for the first affiliated AP at a first time, and can determine, before the first time, at least one parameter for operation of the first affiliated AP on the third channel. The AP MLD can transmit a third beacon for the first affiliated AP on the first channel before the first time, wherein the third beacon indicates at least one parameter for operation of the first affiliated AP on the third channel; and transmit a fourth beacon for the first affiliated AP on the third channel after the first time, wherein the fourth beacon indicates at least one parameter for operation of the first affiliated AP on the third channel.

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

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

[0012] Figure 1 An exemplary wireless communication system according to some implementation schemes is shown.

[0013] Figure 2 An exemplary simplified block diagram of a wireless device according to some implementation schemes is shown.

[0014] Figure 3 An exemplary WLAN communication system according to some implementation schemes is shown.

[0015] Figure 4 An exemplary simplified block diagram of a WLAN access point (AP) according to some implementation schemes is shown.

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

[0017] Figure 6 An exemplary simplified block diagram of a wireless node according to some implementation schemes is shown.

[0018] Figures 7 to 8 Examples of MLDs based on some implementation schemes are shown.

[0019] Figure 9 An exemplary method for channel switching by MLD according to some implementation schemes is shown.

[0020] Figures 10 to 39 Various aspects of channel switching according to some implementation schemes are illustrated.

[0021] Figure 40 An exemplary method for channel verification of multiple channels according to some implementation schemes is shown.

[0022] Figures 41 to 49 The verification of multiple channels according to some implementation schemes is shown.

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

[0024] acronym

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

[0026] UE: User Equipment

[0027] AP: Access Point

[0028] STA: Wireless Station

[0029] TX: Transmission / Transmission

[0030] RX: Receive / Receive

[0031] MLD: Multi-link device

[0032] LAN: Local Area Network

[0033] WLAN: Wireless Local Area Network

[0034] RAT: Radio Access Technology

[0035] ACK: Confirmation

[0036] BA: Block Confirmation

[0037] NACK: Negative Acknowledgment

[0038] N-BA: Negative Block Confirmation

[0039] TSF: Timed Synchronization Function

[0040] QoS: Quality of Service

[0041] the term

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

[0043] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems connected via a network, for example. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0044] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks, and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals, or digital signals).

[0045] Computer system—any of all types of computing or processing systems, including personal computer systems (PCs), mainframe computers, workstations, networked appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (and / or combination of devices) having at least one processor that executes instructions from a memory medium.

[0046] Mobile device (and / or mobile station) — any of a variety of computer system devices that are mobile or portable and perform wireless communication using WLAN communication. Examples of mobile devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM (phones), and tablets such as iPads TM Samsung Galaxy TM Various other types of devices that include Wi-Fi, or both cellular and Wi-Fi capabilities, will fall into this category, such as laptops (e.g., MacBooks). TM ), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM Portable internet devices and other handheld devices, as well as wearable devices such as smartwatches, smart glasses, headphones, pendants, earbuds, etc. Generally, the term "mobile device" can be broadly defined as any electronic, computing, and / or communication device (and / or combination of devices) that is easily transportable by the user and capable of wireless communication using WLAN or Wi-Fi.

[0047] Wireless device (and / or wireless site) — Any of a variety of computer system devices that perform wireless communication using WLAN communication. As used herein, the term “wireless device” can refer to a mobile device as defined above or a stationary device such as a stationary wireless client or wireless base station. For example, a wireless device can be any type of wireless site in an 802.11 system, such as an access point (AP) or client site (STA or UE). Other examples include televisions, media players (e.g., Apple TV). TM Roku TM Amazon FireTV TM Google Chromecast TM (etc.), refrigerators, washing machines, thermostats, etc.

[0048] WLAN—The term “WLAN” has the full range of its common meaning and includes at least wireless communication networks, or RATs, which are provided by WLAN access points and through which connectivity to the Internet is provided. Most modern WLANs are based on the IEEE 802.11 standard and are marketed under the name “Wi-Fi.” WLAN networks are different from cellular networks.

[0049] Processing element—refers to various specific implementations of digital circuitry that perform functions in a computer system. Furthermore, processing element can refer to various implementations of analog or mixed-signal (combination of analog and digital) circuitry that perform functions (and / or multiple functions) in a computer or computer system. Processing elements include, for example, circuits (such as integrated circuits (ICs), ASICs (Application-Specific Integrated Circuits), portions or circuits of individual processor cores), entire processor cores, individual processors, programmable hardware devices (such as field-programmable gate arrays (FPGAs)), and / or a large portion of a system comprising multiple processors.

[0050] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatically" is the opposite of an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent "automatically" performed actions are not specified by the user, for example, not performed "manually," where, in the case of manual execution, the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, a user can invoke the automatic filling of a form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0051] Concurrency refers to the parallel execution or implementation of tasks, processes, signaling, messages, or programs in a manner that overlaps at least partially. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0052] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In such contexts, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently powered on. Typically, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.

[0053] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.

[0054] Figures 1-2 —Wireless communication system

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

[0056] As shown in the figure, 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 perform wireless communication using any of a variety of wireless communication technologies, possibly including ranging wireless communication technologies.

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

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

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

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

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

[0062] 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 this disclosure is illustrated. Device 100 can be any of a variety of types of devices and can be configured to perform any of a variety of types of functions. Device 100 can be a substantially portable device or a substantially fixed device, and may include any of a variety of types of devices. Device 100 can be configured to perform one or more ranging wireless communication techniques or features, such as any techniques or features subsequently shown and / or described herein with respect to any or all of the accompanying drawings.

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

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

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

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

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

[0068] Figure 3 —WLAN system

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

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

[0071] Figure 4 —Access Point Diagram

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

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

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

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

[0076] Figure 5 —Client Site Diagram

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

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

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

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

[0081] Furthermore, as described in this invention, processor 302 may include one or more processing elements. Therefore, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 204.

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

[0083] Figure 6 —Wireless Node Diagram

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

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

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

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

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

[0089] Figures 7 to 8 —Multi-link device (MLD) operation

[0090] IEEE 802.11be may include multi-link device (MLD) capabilities. In current implementations, an access point (AP) multi-link device (MLD) node can manage its associated APs. Therefore, an AP MLD node can modify, add, and / or remove associated APs to increase capacity, manage Basic Service Set (BSS) interference and coverage, including switching APs to operate in channels with minimal interference, and / or manipulating associated non-AP MLD nodes to operate on the AP and / or AP MLD node with optimal performance.

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

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

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

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

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

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

[0097] A non-AP MLD can provide auxiliary STAs from a single physical device (e.g., a single shared enclosure) 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 different one or more STAs, etc.). In some embodiments, the various auxiliary STAs can be spatially separated (e.g., beams in different directions, using different antennas with a shared enclosure (e.g., antennas of the same physical device) and / or different antennas of different devices, etc.).

[0098] Various auxiliary STAs and APs can communicate concurrently / simultaneously. For example, STA 806a can exchange uplink and / or downlink data with AP 812a on a first link, while STA 806b can 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 AP MLDs and non-AP MLDs can be routed via a first available link and / or a link selected based on other criteria (e.g., minimum energy usage, etc.). For example, a first data packet or portion can be sent via the first link, and concurrently, a second data packet or portion can be sent via the second link.

[0099] In some implementations, the AP MLD and non-AP MLDs may include corresponding ML entities. The ML entity provides upper-layer MAC functionality to control individual APs and / or STAs, and can control traffic delivery over available links, such as between various APs and STAs. The corresponding MLD (e.g., AP and non-AP) may have only one corresponding MAC SAP interface. The MAC SAP interface connects the MLD to a distribution system that can deliver traffic to / from the MLD from the Internet. For example, due to having a single MAC SAP interface, all affiliated APs of the AP MLD are visible to the Internet as a single device (e.g., the AP MLD). The ML entity manages this interface. The ML entity manages transmission buffers (e.g., bookkeeping and link selection in the transmitter) and data reordering buffers in reception (e.g., combinations of data transmitted over different links).

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

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

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

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

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

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

[0106] Figure 9 —Channel Switching

[0107] In some implementations, the AP MLD node can perform channel switching, such as changing / moving an affiliated AP from one channel to another. This channel switching can be performed between channels within a frequency band (e.g., 2.4 GHz, 5 GHz, or 6 GHz) or between multiple frequency bands (e.g., from a 5 GHz channel to a 6 GHz channel). For example, channel switching could be the movement of a first affiliated AP from a first channel in a first frequency band to a second channel in the first frequency band or a different frequency band. The first affiliated AP may operate on the first channel before the switch (e.g., not on the second channel at that time) and may operate on the second channel after the switch (e.g., not on the first channel at that time).

[0108] Non-AP MLDs can perform similar channel handovers, such as changing a STA from channel one to channel two. A non-AP MLD can respond to an AP MLD by switching channels or instructing it to switch channels for an affiliated STA. A non-AP MLD can request an AP MLD to perform a channel handover, and the AP MLD can initiate a channel handover in response to such a request.

[0109] AP MLDs can signal channel switching (via the affiliated AP that will change the channel and / or other affiliated APs). For example, the AP making the change can signal the upcoming channel switch in one or more beacons it transmits. Similarly, other affiliated APs can signal the switch, for example, in the multi-link (ML) element of their transmitted beacon frames. Such beacons can indicate the new channel and the switch time (e.g., the time when the switch plan begins, for example, when the AP may no longer provide a link on the first channel), and may also include additional information such as the duration.

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

[0111] In some implementations, when an AP is signaled to switch channels, the operating parameters of the switched AP (e.g., on the new channel) can 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 / related STAs can set their parameters based on the AP's parameters before the switch until the new parameters are signaled.

[0112] In some implementation schemes, the following applies: Figure 9 The channel switching described herein can be faster than the channel switching described above.

[0113] In the 6 GHz band, a STA may need to obtain the specified power level of the AP after the handover before it can operate with the AP on the new channel. This can prevent or delay operation with the AP, for example, until the specified power level is determined by both the AP MLD and the non-AP MLD. STAs may have low-latency traffic with the AP being handed over. Channel handover delays can lead to a degraded Quality of Service (QoS) for any applications performing on the non-AP MLD. Furthermore, STAs may not be ready to operate on the new channel. Obtaining parameters before and / or during the handover allows for a longer preparation time. This reduces or avoids administrative traffic storms (e.g., multiple STAs attempting to establish communication with the AP on the new channel within a similar timeframe), especially when the AP has a large number of associated STAs. This allows STAs more time to determine and indicate their new parameters.

[0114] The implementation schemes described herein provide systems, methods, and mechanisms for APs and non-AP MLDs to perform channel switching. For example, according to Figure 9In this implementation scheme, the parameters that the AP will use after a channel switch can be signaled by the AP and / or other affiliated APs before the switch. This scheme can help reduce latency, lower power consumption, and / or improve security. For example, Figure 9 An exemplary method for channel switching according to some implementation schemes is shown.

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

[0116] It should be noted that, although described in a manner relating to the communication technologies and / or features associated with IEEE and / or 802.11 (e.g., 802.11be) specification documents. Figure 9 This description describes at least some elements of the method, but it is not intended to limit this disclosure. Figure 9 Various aspects of the method can be used in any suitable wireless communication system as needed. Similarly, although described in relation to AP MLD and / or non-AP MLD... Figure 9 The method includes elements, but this description is not intended to limit this disclosure, and Figure 9 Various aspects of the method can be used by STAs that are not MLDs (e.g., APs or non-APs) as needed.

[0117] Among other devices, the method shown can be used in conjunction with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown in the figure, the method can operate as follows.

[0118] According to some implementation schemes, AP MLD 112 can transmit beacons (902a, 902b) from a first auxiliary AP and a second auxiliary AP. The first AP can operate on a first channel (903a), and the second AP can operate on a second channel (903b). The first channel and the second channel can be in the same or different frequency bands.

[0119] Beacons may include indications of various parameters of the corresponding AP. For example, a beacon for a first AP may indicate parameters of that first AP. Such indicated parameters may include the corresponding AP's frequency, bandwidth, channel, Basic Service Set Identifier (BSSID), Operation Class, Spatial Stream Number (NSS), support for power-saving 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. It should be understood that parameters for different APs may be the same or different. For example, for a first AP and a second AP (or an additional AP to an MLD AP), any or all parameter values ​​may be the same (and / or different).

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

[0121] The non-AP MLD 106 can receive beacons. It should be understood that a non-AP MLD may include or operate multiple associated STAs corresponding to the associated AP of the AP MLD, for example, as per [reference to...]. Figure 8 As shown and described. Such subsidiary STAs in Figure 9 The diagram shows a single line. A non-AP MLD can use the indications of 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 affiliated AP can be used to determine one or more parameters of a corresponding affiliated STA, for example, operating on the same channel as and communicating with the first affiliated AP.

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

[0123] According to some implementations, the AP MLD can determine (e.g., new or modified) parameters (906) of the first AP on a new channel (e.g., the third channel 903c). These parameters can be determined when the first AP operates on the first channel (e.g., 903a). Any or all parameters of the first AP can be changed in association with channel switching. For example, the channel bandwidth and / or spatial stream number (NSS) may or may not change, and various other possibilities exist.

[0124] The following shows the variation of parameters per STA (e.g., per AP) based on the new and old frequency bands of the AP according to some implementation schemes.

[0125]

[0126] It should be understood that the table above is an example, and other implementations may be used as needed. For example, per-STA parameters may or may not be associated with channel switching 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 be associated with channel switching that changes the AP's frequency band (e.g., from 2.4 GHz to 5 GHz or 6 GHz, etc.).

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

[0128] For example, parameters can signal the transmission power after a switch. For instance, in some areas of the 6GHz band, there may be a possibility of using specific location transmission power controlled by an automatic frequency controller server. In some cases, the AP can operate from a mobile device, and this device can be moved to a location that allows the AP to operate with higher transmission power in the new band. The AP can switch to a new channel to be able to operate at higher power.

[0129] For example, in a 5GHz radar detection channel, the AP can detect radar, and the AP may need to switch to a new channel.

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

[0131] For example, in some cases, an AP may have associated STAs located at the edge of its coverage area but consuming a lot of transmission resources. The AP can perform channel switching to reduce the coverage of the BSS and stop serving these STAs, so that more resources can be used for other associated STAs.

[0132] For example, an AP MLD can be part of a larger network, and when network load increases, the AP MLD can switch one or more APs to operating channels and parameters for a more intensive deployment. Similarly, when traffic load decreases, the deployment can revert to the original channels and parameters.

[0133] For example, an AP MLD might use too much bandwidth on one AP and too little on others. An AP MLD can use channel switching in various ways to rebalance traffic load across APs. An AP MLD can change the APs being used to a new channel to give them more bandwidth. An AP MLD can change the most frequently used APs to other channels to distribute AP utilization more evenly.

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

[0135] For example, a mobile device operating as an access point (AP) can transmit or plan to transmit D2D communication on other channels. To simplify the two separate transmission operations, the mobile device can change the AP to operate on the same channel as the D2D transmission.

[0136] As mentioned above, for example, due to limitations of certain devices, link pairs may be positioned too close together that transmission on link 1 and reception on link 2 may be impractical or impossible. These limitations may exist in either or both of the AP MLD and / or non-AP MLD. For example, mobile devices operating as APs may have such limitations. There are some capabilities and / or parameters describing how, whether, or when operation in a link pair is possible:

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

[0138] Asynchronous transmit and receive (NSTR) can be a normal mode in which data can be transmitted directly (without a start frame) to the STA, but when the STA is transmitting on link 1, the AP may not transmit to the STA on link 2.

[0139] The determination of the handover and / or the determination of the parameters may be referred to as the start of a “grace period”. For example, the grace period may continue until the first AP begins to perform a channel handover, thus becoming temporarily unavailable.

[0140] According to some implementation schemes, the AP MLD can transmit one or more beacons (908a, 908b) via a first auxiliary AP and a second auxiliary AP. Beacons transmitted via the first AP can be transmitted on the first channel (903a), and beacons transmitted via the second AP can be transmitted on the second channel (903b).

[0141] The beacon may indicate information about (e.g., planned, upcoming, and / or ongoing) channel handovers. For example, the beacon may indicate the time of a channel handover, such as the start time, end time, and / or duration. Similarly, the beacon may indicate parameters of the first AP that will be used, for example, after the channel handover (e.g., as determined in 906). Additionally, the beacon may indicate parameters of the first AP, the second AP, and / or any other auxiliary APs on the first channel (903a).

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

[0143] Furthermore, during channel handover (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 the information indicated by the beacons of the second AP may change when channel handover begins. For example, before channel handover begins, the beacons of the second AP may indicate the operating parameters of the first AP before and after the handover (e.g., parameters for two time periods may be transmitted in the beacons). However, once handover begins, the beacons of the second AP may no longer indicate the parameters of the first AP before the handover. In some embodiments, once handover begins and / or as the handover time approaches, the beacons of the second AP may indicate additional details of the parameters.

[0144] If the first AP changes its parameters without being associated with a channel switch (e.g., the first AP will use the same parameter values ​​in the old channel 903a as in the new channel 903c), the beacon can indicate that no change has occurred. For example, channel switching elements and / or extended channel switching elements may have a field set to 1 to indicate that the AP parameters are the same in the new channel. In some implementations, AP capabilities and operating parameters can be signaled via different frequency band-specific elements.

[0145] If the first AP changes parameters in association with a channel switch (e.g., the first AP will use one or more parameter values ​​that differ from the old channel 903a in the new channel 903c), the beacon can indicate the change. For example, the auxiliary 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 contain a per-STA profile of the switched AP containing the parameter values ​​in the new channel. Furthermore, the ML reconfiguration variant multilink element may contain fields (or fields) for signaling to the AP MLD after a channel switch the multilink parameters for simultaneous transmission support or lack thereof (e.g., STR / NSTR).

[0146] In some implementations, instead of and / or in addition to transmitting beacons indicating new parameters, the AP MLD may transmit similar information in the probe response. For example, a non-AP MLD may transmit a probe request to the AP MLD (e.g., via a first and / or second AP). In response to the probe request, the AP MLD may transmit a probe response that includes information about channel switching, such as the timing of the switching and / or parameters that the first AP will use on the third channel 903c.

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

[0148] According to some implementations, 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 handover including a change in frequency band, the non-AP MLD may determine its capabilities (e.g., maximum bandwidth, NSS, etc.) in the frequency band of the new channel. Furthermore, 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 replacing the parameters of the first AP (e.g., as indicated in the beacon), parameters may be based on information including: traffic patterns, applications running 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, for example, indications from the AP that parameters will take effect after a channel handover.

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

[0150] In some implementations, a non-AP MLD can initiate, halt, or modify D2D transmissions based on an upcoming AP channel switchover. For example, similar to the previous example, a non-AP MLD can initiate such D2D communication based on the determination that D2D communication is valid on the first channel 903a.

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

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

[0153] According to some implementation schemes, the AP MLD can perform channel switching, for example, the first auxiliary AP can perform channel switching from the first channel 903a to the third channel 903c (914). The first auxiliary AP can stop using some or all of the parameters associated with the first channel and can start using the parameters associated with the third channel (e.g., as determined in 906).

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

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

[0156] Similarly, the non-AP MLD can continue operating during this period. For example, the non-AP MLD can exchange data with the second AP and / or send probes and receive probe responses.

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

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

[0159] According to some implementations, a non-AP MLD can verify the link with a first AP on a new channel (920). For example, the non-AP MLD can verify the link based on receiving a beacon (e.g., 918a) from the first AP on channel 903c. The link can 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 implementations, after exchanging such uplink data, both the AP MLD and the non-AP MLD may consider the link verified.

[0160] Non-AP MLDs and AP MLDs can exchange uplink and / or downlink data via the first and / or second APs.

[0161] In some implementations, the AP MLD may not provide a second AP (e.g., operating on a second channel 903b). Therefore, Figure 9 This method can be applied to AP MLDs that operate only a single AP (e.g., within a relevant time period). The actions associated with such a second AP discussed above can be omitted and / or performed by the first AP.

[0162] In some implementations, the AP MLD can provide (e.g., operating on other / additional channels) multiple second APs. Therefore, Figure 9 The method can be applied to an AP MLD that operates only any number of second APs (e.g., within a relevant time period). The actions associated with such second APs discussed above may not be performed by such second APs, or may be performed by some or all of such second APs.

[0163] Figures 10 to 39 And additional information regarding channel switching

[0164] Figure 10 The diagram illustrates messages that can be transmitted by an AP (e.g., any of 712a-712d, etc.) according to some implementation schemes. Figures 11 to 25 Further details are included. The message can serve as a beacon and / or probe response (e.g., as relative to...). Figure 9 Transmissions (as discussed with respect to 902, 908, 916, and / or 918). Messages may include information about the AP MLD 112 and / or other associated APs.

[0165] It should be understood that, such as Figures 10 to 25 The structure shown for the message is an example, and other structures and / or element combinations can 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 reserved for future use.

[0166] As shown in the figure, the message may include information identifying the AP (e.g., Service Set Identifier (SSID), BSSID, etc.). The message may include elements describing the AP's capabilities and operations (e.g., operating parameters). For example, the message may describe the frame structure used by the AP. The message may include Reduced Neighbor Report (RNR) elements, which may include entries for other affiliated APs of AP MLD 112 (e.g., for a message transmitted by AP 712a, entries for APs 712b, 712c, and / or 712d may exist). The RNR elements may be as follows regarding... Figure 11 Further description. The message may include elements describing the AP's high throughput (HT) capabilities (e.g., extremely high throughput (EHT) capabilities, operations, and / or parameters).

[0167] Messages may include multi-link (ML) elements, such as the following regarding Figure 17 Further description. In some implementations, if simultaneous peer authentication (SAE) is used, only the ML element may be used. In some implementations, if SAE is not used, the ML element may be included. The ML element may include information common to all affiliated APs of the AP MLD (e.g., parameters, capabilities, etc.). The ML element may also include per-STA information, such as a profile of each affiliated AP.

[0168] In some implementations, the message may include an indication of the timing of a channel switch, for example, as per [the relevant information]. Figures 28 to 29 Further description.

[0169] The following table describes some implementation schemes. Figure 10 Some elements of the message.

[0170]

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

[0172] Figure 11 The diagram illustrates an RNR element according to some implementation schemes. As shown, an RNR element may include an element identifier, a length field, and any number of neighbor AP information fields, such as information about... Figure 12 As discussed. For example, an RNR element may include the corresponding neighbor information field of the other affiliated APs of the APMLD. For example, a message transmitted by AP 712a may include an RNR element with neighbor AP information fields of AP712b-712d.

[0173] Figure 12 The diagram illustrates a neighbor AP information field according to some implementation schemes. The neighbor AP information field may include subfields containing different information about the corresponding neighbor AP. As shown, the neighbor AP information field may include a TBTT information header field, for example, timing information indicating the beacon transmitted by the corresponding neighbor AP, such as information about... Figure 15 Further description. The Neighbor AP Information field may include the corresponding neighbor AP's operation category information and channel number. The operation category and channel number indicate the channel in which the AP operates. The Neighbor AP Information field may include a TBTT information set, which includes information such as... Figure 13 Further description of any number of TBTT information fields. 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.

[0174] Figure 13 The diagram illustrates TBTT information fields according to some implementation schemes. TBTT information fields may include an indication of the TBTT offset of the corresponding neighboring AP, for example, relative to the transmitting AP. TBTT information fields may include an indication of the BSSID and / or short SSID of the corresponding neighboring AP. TBTT information fields may include an indication of the BSS parameters of the corresponding neighboring AP, for example, regarding... Figure 14 Further description of the fields. The TBTT information field may include an indication of the 20 MHz power spectral density (PSD) of the corresponding neighboring AP. The TBTT information field may also include an indication of the MLD parameters of the corresponding neighboring AP, such as, for example, regarding... Figure 16 Further discussion.

[0175] Figure 14The BSS parameter fields according to some implementation schemes are shown. The BSS parameter fields may include an indication of whether tunneling on the channel (OCT) is recommended, for example, whether a STA can tunnel management frames to another AP via one AP. The BSS parameter may indicate whether the corresponding neighboring AP uses the same SSID as the transport AP, and / or may indicate the SSID of the corresponding neighboring AP. The BSS parameter may indicate one or more BSSIDs of the corresponding neighboring AP. The BSS parameter may indicate the BSSID transmitted by the corresponding neighboring AP, for example, the BSSID used by the corresponding neighboring AP to transmit beacons. The BSS parameter may indicate whether the corresponding neighboring 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 bands. The BSS parameter may indicate whether the corresponding neighboring AP actively responds to unsolicited probe responses. The BSS parameter may indicate whether the corresponding neighboring AP is co-located with the transport AP.

[0176] Figure 15 A TBTT information header according to some embodiments is shown. The TBTT information header may include an indication of the type of TBTT information field. 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 be applied 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).

[0177] Figure 16 The MLD parameter fields are shown according to some implementation schemes. The MLD parameter fields may include an indication of the MLD ID of the corresponding AP MLD. For example, a single physical device may include multiple AP MLDs, and each AP MLD may include multiple APs. The MLD ID identifies the corresponding AP MLD relative to a list of AP MLDs. The Link ID indicates the link identifier of the corresponding AP within the AP MLD to which the transmitting AP is attached. In other words, the MLD ID describes one AP MLD among multiple AP MLDs, and the Link ID describes one AP for a particular AP MLD. For example, in the case 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) in the AP MLD.

[0178] The MLD parameter field may include an indication of a change sequence, such as a version ID. The change sequence may increment when a (e.g., significant) change occurs in the beacon of the corresponding AP. For example, the change sequence field may increment when a channel handover is announced (e.g., in 908) and / or when a channel handover is completed (e.g., in 918), among other possibilities.

[0179] Figure 17 The following diagram illustrates ML elements according to several implementation schemes. As summarized in the table below, ML elements can be any of various variant forms, such as basic, probe request, or reconfiguration.

[0180]

[0181] ML elements may include an element identifier, a length indicator, and an element ID extension. In the illustrated example, the element identifier could be 255, and the indicator could include an extended ID. ML elements may include ML control fields (e.g., about...). Figure 18 (Further description). ML elements can include common information about all links (e.g., APs) (e.g., information about...). Figure 19 Further description) and link information for specific links (e.g., APs). For example, link-specific information may include per-STA profiles. Additionally, vendor-specific information may be included.

[0182] The ML element may also include an indication of a (e.g., upcoming) channel switch performed by the transmitting AP and / or affiliated APs. This indication may specify which AP is changing the channel and / or whether the parameters of the AP changing the channel will change.

[0183] It should be understood that ML elements can be transmitted by either AP MLD or non-AP MLD. For example, AP MLD may include beacon or probe request responses (e.g., as relative to...). Figure 9 The ML elements discussed in 902, 908, 916 and / or 918. Non-AP MLDs may transmit ML elements indicating their capabilities and / or parameters, as discussed in 912.

[0184] Figure 18 Exemplary multi-link control fields according to some implementation schemes are shown. ML control fields can 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 media synchronization delay information exists, whether enhanced ML (EML) capability exists, and whether MLD capability exists.

[0185] Figure 19Exemplary public information fields according to some implementation schemes are shown. Public information fields may include the MAC address of the APMLD. Public information fields may include information about all link IDs. Public information fields may include parameters or information about all links. For example, transmission power increments may be included. Public information fields may include indications of BSS parameter change counts. Public information fields may include media synchronization delay information (see...). Figure 20 Public information fields may include EML capabilities (see...). Figure 21 Public information fields may include MLD capabilities (see...). Figure 22 ).

[0186] Figure 20 An exemplary media synchronization delay information field according to some implementation schemes is shown.

[0187] Figure 21 Exemplary EML capability fields are shown according to some implementation schemes.

[0188] Figure 22 Exemplary MLD capability fields are shown according to some implementation schemes. The MLD capability field can indicate the maximum number of links that a transport MLD (e.g., AP MLD or non-AP MLD) can support simultaneously.

[0189] Figure 23 Similar to some implementation schemes are shown. Figure 17 ML elements. Figure 23 The first per-STA profile (e.g., profile x) is highlighted. About Figure 24 Further description of each STA profile.

[0190] Figure 24 This illustrates a per-STA profile according to some implementation schemes. A per-STA profile may include a sub-element ID, a length indicator, and STA control fields (about...). Figure 25 (Further description). Each STA profile may include STA information, including MAC address, beacon interval, Delivery Traffic Indication Message (DTIM) count, DTIM, period, NSTR bitmap, etc. Subordinate APs may have separate beacon intervals and DTIM periodicity. In some implementations, the beacon period may change in association with channel handover. Therefore, this field may indicate the new beacon period for an upcoming channel handover. In some implementations, in the absence of an indication of a new interval, non-APs may perform passive scanning, for example, assuming the interval between beacons is 100 ms or assuming 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, each STA profile may contain NSTR information for all link pairs. Each STA profile may include an STA profile, including STA-specific capability information.

[0191] Figure 25 The STA control fields according to some implementation schemes are shown. The STA control fields may include a link ID. The corresponding associated AP of the APMLD 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 fields may include indications of whether the STA profile is complete and whether a MAC address is present. The STA control fields may include indications of the presence of a beacon interval and the presence of DTIM information. The STA control fields may include indications of the presence of NSTR link pairs and / or NSTR bitmaps.

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

[0193] During ML reconfiguration, both the non-AP MLD and AP MLD maintain the same security. The non-AP MLD can request the addition and / or deletion of links. The AP MLD can accept or reject link deletion. Reconfiguration ML elements can be used to communicate single-link changes. Links can be maintained when the AP switches channels. Additional signaling from the non-AP MLD is not required to continue operation on the link (e.g., on the new channel).

[0194] Figure 9 One use case for this method may include a soft AP that performs capability changes. A soft AP can refer to a device such as a smartphone (e.g., temporarily acting as an AP). The AP MLD can change its associated AP capabilities. Operating parameters can be changed, and the new values ​​of these elements can be signaled via the change sequence number and key BSS update field in the beacon and probe response frame. However, according to some implementations, capability parameters such as HT capability, VHT capability, HE capability, and EHT capability may not be changed in the same way. One possibility for performing such an update of the associated AP capability parameters is based on... Figure 9 Channel switching is performed using methods such as [method name missing]. For example, an auxiliary AP can (at least) select a new primary channel to ensure that all STAs detect changes in AP parameters. The AP MLD can signal as described above regarding [method name missing]. Figure 9The aforementioned channel switching. In some cases, an affiliated AP can perform a channel switch to the same channel, changing only its capabilities. The AP MLD can time the channel switch to coincide with the capability change, and thus allow associated STAs to prepare new parameters and / or capability values. For example, such parameter / capability changes can be performed to save power (e.g., in response to the soft AP MLD's battery level) or otherwise adapt to changing conditions. Alternatively, this can allow the soft AP MLD to modify its AP operation, for example, by switching to an idle channel. An idle channel can be a channel free from interference or other transmissions. All transmission resources on an idle channel are available to the AP.

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

[0196] Figure 27 Channel handover according to some implementation schemes is illustrated. As shown, AP1 can operate on link 1 and can transmit (e.g., on link 1) a beacon indicating that it will switch channels. After the handover, AP1 can operate on the new channel and can transmit the beacon, for example, without signaling related to the channel handover. The maximum channel handover time can be indicated in the beacon transmitted by AP2 and / or AP3 during the channel handover time. Therefore, the non-AP MLD can use the indication of the maximum channel handover time to determine when AP1 can begin operating on the new channel.

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

[0198] Figure 29 The maximum channel handover time element is illustrated according to some implementation schemes. The maximum channel handover time element may be included in the beacon transmitted by the affiliated AP during the channel handover time. The handover time can indicate the number of time units (TUs) during which the AP will continue to operate in the first / old channel.

[0199] Figure 30 The illustration shows, according to some implementation schemes, the use of ML elements (e.g., as shown in the section on...). Figure 17 Channel switching (as described above).

[0200] As shown in the figure, AP1 can operate on Link 1 and can transmit (e.g., on Link 1) beacons indicating that it will switch channels. Beacons transmitted by AP1 during a grace period (e.g., after the handover is determined and before the handover) may include ML elements, such as reconfiguration variants. For example, the ML element may include a per-STA profile indicating the operating parameters to be implemented for AP1 after the handover. Beacons transmitted by AP1 before the handover may include extended channel handover elements.

[0201] During the grace period, AP2 and / or AP3 may transmit beacons on their respective channels. These beacons may include extended channel handover elements. Furthermore, these beacons may include ML elements, for example, reconfiguration variants. For instance, the ML elements may include a per-STA profile indicating the operating parameters implemented for AP1 after the handover. 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 affiliated AP rather than a transit AP, as in the case of beacons transmitted by AP1).

[0202] During handover, AP2 and / or AP3 may transmit beacons on their respective channels. These beacons may include a maximum channel handover time element. Furthermore, these beacons may include ML elements, for example, reconfiguration variants. For instance, the ML element may include a per-STA profile indicating the operating parameters implemented for AP1 after the handover.

[0203] After the handover, AP1 can operate on the new channel and can transmit beacons, for example, without signaling related to the channel handover. After the handover, AP2 and / or AP3 can continue to operate on their respective channels and transmit beacons, for example, without signaling related to the channel handover.

[0204] It should be understood that, according to some implementations, any one or all of the beacons during the grace period and / or handover period may include ML elements indicating the operational parameters to be implemented for AP1 after the handover. For example, this information may be omitted in some cases from beacons transmitted by AP2 and / or AP3 during the grace period, while such information may be included in beacons transmitted by AP1 during the grace period and by AP2 and / or AP3 during the handover period.

[0205] The table below provides examples of the types of information included in beacons during different time periods, according to some implementation schemes.

[0206]

[0207] During the grace period when one or more APs are switching channels, a reconfiguration variant ML element can be added to the beacon and ML-probe response (e.g., by the changing AP and / or other affiliated APs). The ML element may contain a per-STA profile sub-element for each AP during the grace period for the upcoming channel switch. Depending on some implementations, the basic variant and reconfiguration variant ML elements may be similar. The reconfiguration ML element may include a link ID and a deletion request as additional fields, among various other possibilities.

[0208] When a reconfiguration variant ML element is added to a beacon or ML-probe response, the Link ID can identify the AP for which its parameters are listed in the corresponding per-STA profile. For example, for a per-STA profile describing an added AP or a changed AP, the new Link ID is set to 15 (signaling unknown value). Similarly, a deletion request can be indicated as a Link ID set to 0. Therefore, for a reconfiguration ML element associated with a channel handover, the AP's per-STA profile before the handover can include a Link ID set to 0, and the AP's per-STA profile after the channel handover can include a Link ID set to 15. Both AP per-STA profiles can be included in the same ML element. Therefore, the ML element can include both the AP's parameters before and after the channel handover.

[0209] Figure 31 The capabilities and operation in different frequency bands according to different 802.11 standards are shown according to some implementation schemes.

[0210] As described above, according to some implementations, channel handover may or may not include changes in AP parameters. Correspondingly, channel handover can be indicated differently depending on whether or not parameter changes are included, for example, as... Figures 32 to 33 As shown.

[0211] Figure 32 This illustrates the beacon frame format when channel switching 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). For example, the beacon may be transmitted by a first AP before the channel switch is performed by the changed AP (e.g., AP1). AP1 may be the same as or different from the first AP transmitting the beacon. Channel switching may not change the parameters of AP1. The beacon frame may include link-specific information (e.g., BSSID, capabilities, etc.) and RNR, such as information about... Figure 10 As discussed above. Furthermore, the beacon frame may include ML elements of the per-STA profile with the associated AP. The ML elements may also include bits indicating that channel handover will occur without changing parameters.

[0212] In some implementations, information about whether / how parameters are changed may be included in the channel switching element.

[0213] Figure 33 This illustrates the beacon frame format when a channel switch changes the AP MLD or the parameters of the switched AP (e.g., the AP MLD and / or the parameters of the switched AP are different after the switch than before). For example, the beacon may be transmitted by a first AP before the channel switch is performed by the changed AP (e.g., AP1). AP1 may be the same as or different from the first AP transmitting 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, such as information about... Figure 10 and Figure 32 The discussion continues. Furthermore, as... Figure 32 As shown, the beacon frame may include ML elements of a per-STA profile with an associated AP. Additionally, the beacon frame may include a second ML element of a reconfiguration variant. The reconfiguration variant ML element may, for example, describe the associated AP of the AP MLD after the handover in the ML control, common information, and / or link information fields. Furthermore, a per-STA profile describing AP1 parameters to be in place after the handover may be included.

[0214] Figure 34 The diagram illustrates the possible encodings and values ​​of ML type subfields, such as ML control fields, according to some implementation schemes. As shown, ML type subfields can indicate basic variants, probe request variants, or reconfiguration variants of ML elements.

[0215] Figure 35 The possible child element IDs of an ML element are shown according to some implementation schemes.

[0216] Each STA child element can start with a control field per STA. Figure 36 The control fields for each STA transmitted by non-AP are shown, and Figure 37 The control fields per STA transmitted by the AP (e.g., AP MLD) are shown.

[0217] In connection with channel switching, the associated non-AP MLD can take various actions.

[0218] As a possibility, the STA can continue operating 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 handover can be the larger of the parameter values ​​indicated by the STA at association or the parameter values ​​indicated to the AP in the new channel / link. In other words, the non-AP can reduce its parameter values ​​in response to the AP reducing the AP's parameter values. Furthermore, for example, if the STA cannot operate in the new channel with the same parameters (or otherwise determines to reduce its parameters), the STA can limit its bandwidth and NSS by using an Operation Mode Indication (OMI). This OMI can be transmitted before, during, or after the channel handover. If the STA does nothing (e.g., does not transmit indications of capacity or other data), the AP can assume that the STA in the new channel is in power-saving mode, and the AP can refrain from sending traffic to the STA on the new channel (e.g., until the STA verifies the new channel).

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

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

[0221] Figure 38 The diagram illustrates the operation of STA 1, associated with AP1, in a new channel, based on the possibilities discussed in the three preceding paragraphs. As indicated by the thick lines in the figure, prior to channel switching, associated STA 1 can operate communicatively with AP1 via link 1. After channel switching, STA 1 can verify the new channel and resume communicative operation with AP1 on the new channel. AP1 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.

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

[0223] Figure 39 The diagram illustrates the operation of STA 1, associated with AP1, for example, terminating the link, based on the possibilities discussed in the previous paragraph. As indicated by the thick line in the figure, the associated STA 1 can operate communicatively with AP 1 via link 1 for a period of time prior to channel switching. In response to a channel switching indication, interference level, and / or other information, STA 1 can terminate the link. This termination can occur before or coincide with the channel switching time.

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

[0225] In response, the AP MLD may transmit an associated response or other message to a non-AP. This response may include an ML connection. The ML element can 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 implementations, the ML element may include a complete per-STA profile for each link accepted by the AP MLD (e.g., a link requested by a non-AP MLD).

[0226] In some implementations, the associated request and response may not contain an RNR. In other implementations, an RNR may be included.

[0227] The table below describes ML elements that can be used to associate requests and responses at various time periods, according to some implementation schemes.

[0228]

[0229] The table below describes non-AP MLD operations during various time periods, based on several implementation schemes. The second column describes the operations that can be performed in an implementation where the AP MLD signals parameters to the AP before the AP changes channel. The third column describes the operations that can be performed when the AP MLD does not signal post-switching parameters before the handover.

[0230]

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

[0232] In some implementations, the associated information may be unencrypted or its integrity may be compromised. An attacker could send incorrect associated responses, leading to interoperability issues.

[0233] Operational Channel Verification (OCV) can be a means of signaling and verifying the following parameters: BSS primary channel, secondary 20MHz and / or 80+80MHz configuration (e.g., a 160MHz bandwidth divided into two 80MHz sections), and various other possibilities.

[0234] A non-AP MLD (e.g., STA) can verify parameters, such as ensuring that the AP is operating in the channel and / or operating with parameters signaled by the AP (e.g., or other affiliated APs of the AP MLD). The AP MLD can transmit Operation Channel Information (OCI) to the non-AP MLD. The OCI can indicate the channel and / or parameters of one or more APs. Therefore, the STA may be able to send and receive data with the AP based on verifying the AP using the OCI.

[0235] The implementation schemes described herein provide systems, methods, and mechanisms for AP MLDs and non-AP MLDs to perform OCV on multiple links. For example, according to Figure 40 The implementation scheme can verify the links between any number of affiliated APs and affiliated STAs and use these links to exchange data securely.

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

[0237] It should be noted that, although described in a manner relating to the communication technologies and / or features associated with IEEE and / or 802.11 (e.g., 802.11be) specification documents. Figure 40 This description describes at least some elements of the method, but it is not intended to limit this disclosure. Figure 40 Various aspects of the method can be used in any suitable wireless communication system as needed.

[0238] Among other devices, the method shown can be used in conjunction with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown in the figure, the method can operate as follows.

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

[0240] AP MLDs can transmit information about one or more other affiliated APs (e.g., 812a, 812b, or 812c, etc.) to non-AP MLDs. For example, this information may be or include OCIs. For example, AP MLDs can transmit Reduced Neighbor Reports (RNRs) or ML elements that include this information (e.g., including OCI elements). Information may be transmitted as part of a beacon, probe response (e.g., in response to a probe request from a non-AP MLD), and / or association response (e.g., in response to an association request for a first link from a non-AP MLD). Information may be transmitted before, concurrently with, and / or after the authentication of the first link. Information may be transmitted by a first AP and received by a first STA, and / or information may be transmitted by a second AP and received by a second STA via a second channel.

[0241] According to some implementation schemes, the non-AP MLD 106 can verify a second link (4004) with AP MLD 112. The non-AP MLD 106 can verify any number of additional links with AP MLD 112. For example, it can verify the link between any affiliated AP (e.g., 812a, 812b, or 812c, etc.) and the corresponding STA (e.g., 806a, 806b, or 806c, etc.).

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

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

[0244] If the attributes match, the non-AP MLD can determine that the beacon is valid and can use the link to transmit uplink messages (e.g., data) to the AP MLD. For example, the transmission could originate from a subordinate STA corresponding to the link. The AP MLD can then use the subordinate AP corresponding to the link to receive the data.

[0245] After the non-AP MLD receives the beacon and the AP MLD receives the uplink message, the two devices can consider the link authenticated. Therefore, the devices can be used to exchange additional messages in the uplink and / or downlink directions.

[0246] Figure 41 The diagram illustrates a STA associated with an AP according to some implementation schemes. In the illustrated example, a single link is used.

[0247] Figure 42 An example of an OCI element according to some implementation schemes is shown. An AP MLD can send this OCI element to describe an affiliated AP operating on a specific channel. A non-AP MLD can use this information to determine whether a beacon it receives is a valid beacon from an affiliated AP. About Figures 47 to 48 Additional illustrations depict OCI elements, for example, that can be used in multi-link communication.

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

[0249] Figure 44A , Figure 44B and Figure 44C An example of OCV during the ML setup process according to some implementation schemes is shown. The process can be performed as follows:

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

[0251] [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.

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

[0253] [4] The second STA operating on channel 5 may transmit a probe request to the second AP operating on channel 5.

[0254] [5] In response to a probe request, the second AP may transmit a probe response including the ML element without an AP profile and the RNR of the APs on channel 2 (changed to channel 4) and 6. Therefore, at this time, the non-AP MLD can receive channel information about all affiliated APs. This may include timing information for channel switching.

[0255] [6] The second AP can transmit beacons that include ML elements without an AP profile and the RNRs of APs on channel 2 (changed to channel 4) and 6. Therefore, at this time, the non-AP MLD can receive channel information about all affiliated APs. This may include timing information for channel switching. The beacon may replace or supplement the probe response in [5].

[0256] AP MLD and non-AP MLD can, for example, use channel 5 to initiate an SAE handshake (4414).

[0257] [7] The third AP may transmit ML elements, including those without an AP profile, and beacons identifying the RNRs of APs on channels 2 (changed to channel 4) and 5. Channel switching timing information may be included.

[0258] [8] The second STA may transmit an association request message including an ML element with a complete profile of a first STA (on channel 2) and a third STA (on channel 6, shown on vertical line E). The association request message may request association with 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-saving mode.

[0259] [9] The second AP can transmit an associated response that includes complete profiles of the first and third APs.

[0260] [10-13] The second AP and the second STA can perform a 4-way handshake including messages 1-4. Key Distribution Element (KDE), Group Temporary Key (GTK), and Integrity Group Temporary Key (IGTK) can be exchanged. The GTK can be used to encrypt the frame. The IGTK can be used for integrity protection of the frame. The handshake can include information about all links (e.g., OCI) in msg3

[12] . Thus, at this point, the non-AP MLD can receive enough information to verify the links with any or all of the affiliated APs. The 4-way handshake can be completed (4418). At this point, the non-AP MLD can assume that all links have been verified. However, the AP MLD can assume that the first and third links are inactive (e.g., in power-saving mode) until further indication or message is received from the non-AP MLD.

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

[0262]

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

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

[0263]

[16] The second AP can transmit messages that link TID0 to traffic on channels 2, 4 and 5.

[0264]

[17] The second STA is acceptable for mapping.

[0265]

[18] The second STA can transmit data, and

[19] the second AP can BA confirm the data.

[0266]

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

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

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

[0269]

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

[0270] Figure 45 An example of OCV during a rapid ML transition (e.g., channel switching) is shown according to some implementation schemes. This process can occur between AP MLD1 and non-AP MLD1, which may have links between three corresponding affiliated STAs and APs. The process can proceed as follows:

[0271] STA1 (4502) of non-AP MLD1 may be associated with AP1 (4504) of AP MLD1. [1] AP3 (4512) may transmit beacons. Beacons may include channel information (e.g., RNR, identifying the channel of the affiliated AP of AP MLD1).

[0272] [2]STA2 can transmit authentication requests.

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

[0274] [4-5]STA2 can transmit association requests, and AP2 can transmit responses.

[0275] The non-AP MLD can verify all three links based on OCI information and authentication responses. The non-AP MLD can now be used with all APs.

[0276] Figure 46 Examples of OCV during channel handover (e.g., fast ML transition) are shown according to some implementation schemes. Non-AP MLDs can learn new channel information in beacons (e.g., the AP's OCI after channel handover). Beacons can be protected for integrity, for example, using BIGTK. Link-specific authentication can be used, for example, as discussed above.

[0277] In some implementations, after an AP channel switch (e.g., after AP1 starts on a new link), the STA may send a robust SA query request to request encrypted information about the AP's new channel. The AP may respond to the SA query with, for example, a security parameter response. The SA query request and response can be transmitted on any link. According to some implementations, the SA query may be transmitted during the time the AP switches to the new channel. The SA query request may contain channel information for all APs or APs to which the STA is associated.

[0278] Non-AP MLDs can verify the link (e.g., based on a received SA query response or a beacon in a new channel). For example, a non-AP MLD can determine that the attributes of a beacon or other message in a new channel match the attributes indicated in the OCI.

[0279] Figure 47 An ML-OCI element according to some implementation schemes is shown. An ML-OCI element may include an indication of the number of links (e.g., N links) and link-specific OCI information for each of those links. The link-specific OCI information may be as follows: Figure 48 The aforementioned OCI link information field.

[0280] Figure 48 The OCI link information fields are shown according to some implementation schemes. OCI information fields may include, as described above, […]. Figure 42 Similar information discussed for a single link.

[0281] Figure 49 Traditional elements / fields are shown compared to the new elements / fields described herein. Notably, various ML-OCI information has been added. This ML-OCI information supports verification across multiple links.

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

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

[0284] In some implementations, the method may further include: transmitting a fifth beacon on a second channel for the second auxiliary AP prior to a first time, wherein the fifth beacon indicates at least one parameter for the operation of the first auxiliary AP on a third channel.

[0285] In some implementations, the third and fifth beacons further indicate the maximum channel handover time that begins at the first time.

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

[0287] In some implementations, the sixth beacon further indicates that the first affiliated AP is switching channels.

[0288] In some implementations, the maximum channel switching time begins at a first time, with the third and fifth beacons further indicating the first time.

[0289] In some implementations, at least one parameter used for the operation of the first auxiliary AP on the third channel is different from at least one parameter used for the operation of the first auxiliary AP on the first channel.

[0290] In some implementations, the method may further include: transmitting a sixth beacon on a second channel for a second affiliated AP during the maximum channel switching time when the first affiliated AP is unavailable, wherein the sixth beacon includes a reconfigured variant multilink element.

[0291] In some implementations, the method may further include: exchanging data with a non-AP-MLD using a first auxiliary AP before the first time; and waiting until the non-AP-MLD verifies the first auxiliary AP on the third channel before transmitting data to the non-AP-MLD using the first auxiliary AP on the third channel after the first time.

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

[0293] In some implementations, 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 a first parameter value or a second parameter value.

[0294] In some implementations, the request for channel switching includes an association request; and the first message includes an association request response.

[0295] In some implementations, requests for channel switching include requests to add an auxiliary AP.

[0296] In some implementations, the processor is further configured to enable the non-AP MLD to transmit probe requests to the AP MLD, wherein the first message includes a response to the probe request.

[0297] In some implementations, the probe request includes a multi-link (ML) element, which includes a complete profile of the associated AP after a channel switch.

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

[0299] In some implementations, the processor is further configured to enable non-AP MLD authentication with a new link to the AP.

[0300] In the third set of embodiments, the non-access point (AP) multilink device (MLD) (non-AP MLD) may include: a radio component; and a processor operatively coupled to the radio component and configured to enable the non-AP MLD to: establish communication with the AP MLD using a first affiliated AP of the AP MLD on a first channel, wherein establishing communication includes: performing a handshake with the AP MLD; receiving information from a second affiliated AP of the AP MLD; and verifying the first affiliated AP; and verifying the second affiliated AP of the AP MLD based on the information.

[0301] In some implementations, the second auxiliary AP for verifying the AP MLD includes: receiving a beacon from the second auxiliary AP on a second channel different from the first channel; and transmitting data to the AP MLD using the second auxiliary AP on the second channel.

[0302] In some implementations, the information reception occurs during one of the following: multilink setup; or rapid multilink transition (e.g., channel switching).

[0303] In some implementations, the received information includes a received multi-link operation channel information element.

[0304] In some implementations, the multi-link operation channel information element is received in handshake message 3 (MSG3).

[0305] In some implementations, the processor is further configured to enable the non-AP MLD to receive second information associated with a third affiliated AP of the AP MLD.

[0306] In some implementations, the processor is further configured to enable a third associated AP of the non-AP MLD to verify the AP MLD based at least on the second information.

[0307] In the fourth set of embodiments, a method may include: an Access Point (AP) Multilink Device (AP MLD) using a first affiliated AP of the AP MLD to establish communication with a non-AP MLD on a first channel. Establishing communication may include: performing a handshake with the non-AP MLD; and transmitting information to the non-AP MLD that can be used to verify a second affiliated AP. The method may also include exchanging data with the non-AP MLD via the second affiliated AP of the AP MLD.

[0308] In some implementations, information that can be used to verify the second affiliated AP is transmitted in handshake message 3 (MSG3).

[0309] In some implementations, Message 3 (MSG3) also includes information that can be used to verify the first associated AP.

[0310] In some implementations, message 3 (MSG3) also includes information that can be used to verify the third associated AP of AP MLD.

[0311] In some implementations, information that can be used to verify the transmission of a second auxiliary AP during a multi-link setup can be used.

[0312] In some implementations, information that can be used to verify the transmission of a second auxiliary AP during rapid multi-link transitions can be used.

[0313] In some implementations, information that can be used to verify the second affiliated AP is transmitted in a query response in response to a query request received from a non-AP MLD.

[0314] In the fifth set of embodiments, a non-access point (AP) multilink device (MLD) (non-AP MLD) can establish communication with the AP MLD on a first channel using a first affiliated AP of the AP MLD, wherein establishing communication includes performing a handshake with the AP MLD. The non-AP MLD can receive beacons from a second affiliated AP of the AP MLD. The non-AP MLD can 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 affiliated AP. The non-AP MLD can authenticate the second affiliated AP based on the information about the second affiliated AP.

[0315] In some implementations, 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.

[0316] In some implementations, the at least one attribute includes the operation category.

[0317] In some implementations, the at least one attribute includes the master channel number.

[0318] In some implementations, this information includes multi-link operation channel information elements.

[0319] In the sixth implementation scheme, a non-access point (AP) multilink device (MLD) (non-AP MLD) can establish communication with the AP MLD. The non-AP MLD can receive from the AP MLD an indication that the AP MLD's first affiliated AP will change from a first channel to a second channel. In response to this indication, the non-AP MLD can: determine to switch the non-AP MLD's first affiliated STA from the first channel to the second channel; determine the parameters of the first affiliated STA to be used on the second channel; and communicate with the first affiliated AP via the first affiliated STA on the second channel.

[0320] In some implementations, the indication includes an indication of the first time that the first affiliated AP will switch from the first channel to the second channel.

[0321] In some implementations, 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 the parameters of the first affiliated STA to be used on the second channel.

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

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

[0324] In some embodiments, a memory medium includes program instructions that, when executed, cause the device to perform the method according to any of the foregoing examples.

[0325] In some implementations, a computer program includes instructions for executing any of the methods described according to the foregoing examples.

[0326] In some embodiments, an apparatus includes: a component for performing any one of the method elements according to any of the foregoing examples.

[0327] In some implementations, a method may include any action or combination of actions as substantially described herein in the detailed description and claims.

[0328] In some embodiments, a method may be as substantially described herein with reference to each or any combination of the accompanying drawings contained herein, each or any combination of the paragraphs in the specific embodiments, each or any combination of the accompanying drawings and / or specific embodiments, or each or any combination of the claims or examples.

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

[0330] In some implementations, a wireless device may include any component or combination of components as described herein in the detailed description and / or accompanying drawings.

[0331] In some embodiments, a non-volatile computer-readable medium may store instructions that, when executed, cause to perform any or a combination of actions as substantially described herein in the detailed description and / or accompanying drawings.

[0332] In some implementations, an integrated circuit may be configured to perform any action or combination of actions as substantially described herein in the detailed description and / or accompanying drawings.

[0333] In some implementations, a mobile station may be configured to perform any action or combination of actions as substantially described herein in the detailed description and / or accompanying drawings.

[0334] In some implementations, a mobile station may include any components or combinations of components as described herein in the detailed description and / or accompanying drawings.

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

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

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

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

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

[0340] In some implementations, a non-access point multilink device may include any component or combination of components as described herein in the detailed description and / or accompanying drawings, as included in a mobile device.

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

[0342] In some implementations, an access point multilink device may include any component or combination of components as described herein in the detailed description and / or accompanying drawings, as included in a mobile device.

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

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

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

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

Claims

1. A non-access point AP multi-link device MLD (non-AP MLD), comprising: Radio components; and A processor, operatively coupled to the radio component and configured to enable the non-APMLD: A first affiliated AP using the AP MLD on the first channel establishes communication with the AP MLD, wherein establishing communication includes: The AP MLD communicates one or more authentication frames; The first affiliated AP is verified at least based on one or more authentication frames; and Receive information associated with a second auxiliary AP of the AP MLD; and The second associated AP of the AP MLD is verified at least based on the received information.

2. The non-AP MLD of claim 1, wherein verifying the second affiliated AP comprises: Data frames are received from the second auxiliary AP on a second channel different from the first channel.

3. The non-AP MLD of claim 2, wherein verifying the second auxiliary AP further includes: Data is transmitted to the AP MLD using the second auxiliary AP on the second channel.

4. The non-AP MLD of claim 1, wherein receiving the information occurs during one of the following: Multi-link configuration; or Rapid multi-link transformation.

5. The non-AP MLD according to claim 1, wherein the information includes a multi-link operation channel information element.

6. The non-AP MLD of claim 5, wherein the multi-link operation channel information element is received in a probe response or association frame.

7. The non-AP MLD of claim 1, wherein the processor is further configured to cause the non-AP MLD to: Receive second information associated with the third affiliated AP of the AP MLD.

8. The non-AP MLD of claim 7, wherein the processor is further configured to cause the non-AP MLD to: The third associated AP of the AP MLD is verified at least based on the second information.

9. An apparatus comprising: The processor is configured to perform operations including the following when executing instructions stored in memory: On the first channel, a first auxiliary AP of the access point AP multi-link device (MLD) AP MLD establishes communication with the AP MLD, wherein establishing communication includes: The AP MLD communicates one or more authentication frames; The first affiliated AP is verified at least based on one or more authentication frames; and Receive information associated with a second auxiliary AP of the AP MLD; and The second associated AP of the AP MLD is verified at least based on the received information.

10. The apparatus of claim 9, wherein the verification of the second auxiliary AP: Data frames are received from the second auxiliary AP on a second channel different from the first channel.

11. The apparatus of claim 10, wherein verifying the second auxiliary AP further comprises: Data is transmitted to the AP MLD using the second auxiliary AP on the second channel.

12. The apparatus of claim 9, wherein receiving the information occurs during one of the following: Multi-link configuration; or Rapid multi-link transformation.

13. The apparatus of claim 9, wherein the information includes a multi-link operation channel information element.

14. The apparatus of claim 13, wherein the multi-link operation channel information element is received in a probe response or association frame.

15. The apparatus of claim 9, wherein the operation further comprises: Receive second information associated with the third affiliated AP of the AP MLD.

16. The apparatus of claim 15, wherein the operation further comprises: The third associated AP of the AP MLD is verified at least based on the second information.

17. A method, the method comprising: On the first channel, a first auxiliary AP of the access point AP multi-link device (MLD) AP MLD establishes communication with the AP MLD, wherein establishing communication includes: The AP MLD communicates one or more authentication frames; The first affiliated AP is verified at least based on one or more authentication frames; and Receive information associated with a second auxiliary AP of the AP MLD; and The second associated AP of the AP MLD is verified at least based on the received information.

18. The method of claim 17, wherein verifying the second auxiliary AP comprises: Data frames are received from the second auxiliary AP on a second channel different from the first channel.

19. The method of claim 18, wherein verifying the second auxiliary AP further comprises: Data is transmitted to the AP MLD using the second auxiliary AP on the second channel.

20. The method of claim 17, wherein receiving the information occurs during one of the following: Multi-link configuration; or Rapid multi-link transformation.

Images