MLD privacy and operational enhancements

Abstract

The present invention discloses methods for performing the following operations: robust discovery of new access points (APs) in AP MLDs, robust link addition to AP MLD associations, AP beacon mode when adding or deleting APs from an AP MLD, and robust BSS handover management (BTM) signaling for steering non-AP MLDs to the best AP MLD and the most suitable AP, as well as privacy improvements for associated non-AP MLDs.

Description

[0001] Priority data

[0002] This patent application claims the benefit of priority to U.S. Provisional Patent Application Serial No. 63 / 116,649, filed on November 20, 2020, entitled “MLD Privacy and Operation Enhancements,” which is hereby incorporated by reference in its entirety as if fully and completely set forth herein. Technical Field

[0003] The present application relates to wireless communications, including techniques for wireless communications between wireless stations in a wireless networking system.

[0004] Related technical description

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

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

[0007] Mobile electronic devices can take the form of smartphones or tablets that users often carry. Wearable devices (also known as accessory devices) are a newer form of mobile electronic device, with smartwatches being an example. Furthermore, low-cost, low-complexity wireless devices designed for static or dynamic deployment are rapidly increasing as part of the development of the "Internet of Things." In other words, the complexity, capabilities, traffic patterns, and other characteristics of the devices required are becoming increasingly broad. Summary of the Invention

[0008] Embodiments described herein relate to systems, methods, and mechanisms for robust discovery of new access points (APs) in AP MLDs, robust link addition to AP MLD associations, AP beacon mode when adding or removing an AP from an AP MLD, and robust BSS handover management (BTM) signaling for steering non-AP MLDs to the best AP MLD and the most suitable AP, as well as privacy improvements for associated non-AP MLDs. It is noted that in the embodiments described herein, "robust" may refer to wireless communications that can withstand intentional or accidental interference, such as technical failures, signal jammers, and / or security threats.

[0009] For example, a wireless station may be configured to associate with an access point, which may be included in and / or associated with a multi-link device (MLD). The wireless station may be configured to transmit a robust query request to the access point and receive a robust query response from the access point. The robust query response may include an integrity-protected broadcast probe response and may use a temporary key and / or a packet number for authentication.

[0010] As another example, a wireless station may be configured to associate with an access point, which may be included in and / or associated with a multi-link device (MLD). The wireless station may be configured to transmit an add link request to the access point. The add link request may request that a new link be added between the wireless station and the access point. Furthermore, the wireless station may be configured to establish security for the new link with the access point, including one or more of the following (e.g., any combination of the following, including at least one and / or all of the following): a Beacon Integrity GTK (BIGTK) Security Architecture (BIGTKSA), an Integrity GTK Security Architecture (IGTKSA), a GTK Security Architecture (GTKSA), or a Peer Transient Key (PTK) Security Architecture (PTKSA) for the added new link.

[0011] As another example, a wireless station may be configured to associate with an access point that may be included in and / or associated with a multi-link device (MLD). The wireless station may be configured to transmit an add-link request to the access point. The add-link request may indicate a MAC address associated with the link, a new MLD MAC address sequence number offset, and an updated timing synchronization function (TSF) for the MAC address. Furthermore, the wireless station may be configured to receive an add-link response from the access point. The add-link response may indicate a MAC address associated with the link, a new MLD MAC address sequence number offset, and an updated TSF for the MAC address.

[0012] As another example, an access point may be configured to receive a MAC protocol data unit (PDU) from a wireless station via a link with the wireless station. The access point may be configured to determine whether a parameter associated with the MAC PDU is a parameter used before a parameter change time or a parameter used after the parameter change time. Furthermore, in response to determining that the parameter is a parameter used before the parameter change time, the access point may be configured to determine whether the MAC PDU was transmitted during a tolerance period associated with the parameter change time. Furthermore, in response to determining that the MAC PDU was transmitted during the tolerance period, the access point may be configured to determine a sequence number of the MAC PDU using a sequence number offset associated with the parameter used before the parameter change time.

[0013] As another example, an access point can be configured to operate in one of multiple operating modes and / or beacon modes. For example, in a first operating and / or beacon mode, the access point can be discovered via any link of the MLD. As another example, in a second operating and / or beacon mode, the access point can be discovered only on its primary channel. As another example, in a third operating and / or beacon mode, the access point can be visible only to selected wireless stations that know the access point's beacon encryption key. As yet another example, in a fourth operating and / or beacon mode, the access point can switch to a shutdown phase and securely shut down the link.

[0014] As yet another example, an access point may be configured to associate with a wireless station. The access point may be included in a multi-link device (MLD). The access point may be configured to receive a BTM query from the wireless station, which may propose adding a second access point to the MLD. Accordingly, the access point may be configured to send (or transmit) a Start New AP in an Access Point (AP) MLD Request to the second access point and receive a New AP Create Response from the second access point. The access point may also be configured to send (or transmit) a BTM request to the wireless station, which includes a candidate BSS list that may include the second access point.

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

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

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

[0018] Figure 1B An exemplary simplified block diagram of a wireless device according to some embodiments is shown.

[0019] Figure 1C An exemplary WLAN communication system is shown in accordance with some embodiments.

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

[0021] Figure 3 An exemplary simplified block diagram of a wireless station (UE) is shown in accordance with some embodiments.

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

[0023] Figure 5A A block diagram illustrating an example of a method for secure multi-link setup according to some embodiments is shown.

[0024] Figure 5B A block diagram illustrating another example of a method for secure multi-link setup according to some embodiments is shown.

[0025] Figure 6A An example of a multi-link entity adding a new AP is shown according to some embodiments.

[0026] Figure 6B An example of secure multi-link scanning is shown according to some embodiments.

[0027] Figure 6C An example of secure multilink addition is shown according to some embodiments.

[0028] Figure 7A An example of an integrity protected broadcast probe response is shown in accordance with some embodiments.

[0029] Figure 7B and Figure 7C An example of a management package element (MME) according to some embodiments is shown.

[0030] Figures 8A to 8C An example of signaling for providing a GTK for a new link is shown according to some embodiments.

[0031] Figure 9 An example of signaling for randomizing MAC addresses of wireless stations is shown according to some embodiments.

[0032] Figure 10 A block diagram illustrating an example of a method for randomizing SN offsets according to some embodiments is shown.

[0033] Figure 11 An example of scheduling parameter changes according to some embodiments is shown.

[0034] Figure 12 A block diagram illustrating an example of a method for selecting an SN offset during a parameter change, according to some embodiments.

[0035] Figure 13 Shown are examples of various operational phases of an AP of an ML entity during AP addition, according to some embodiments.

[0036] 14A to 14D Examples of various AP beacon modes are shown according to some embodiments.

[0037] Figure 15 An example of an AP beacon is shown according to some embodiments.

[0038] Figure 16 Further illustrated are the distinctions among various AP operating modes according to some embodiments.

[0039] Figure 17 An example of BSS handover management usage according to some embodiments is shown.

[0040] Figure 18 The request mode field of a BTM request is shown according to some embodiments.

[0041] Figure 19 Examples of signaling for adding new APs and / or requesting new APs using BTM queries are shown according to some embodiments.

[0042] Figure 20 A block diagram illustrating an example of a method for performing secure multi-link scanning according to some embodiments is shown.

[0043] Figure 21A block diagram illustrating an example of a method for providing a group temporary key (GTK) for a new link according to some embodiments is shown.

[0044] Figure 22 A block diagram illustrating an example of a method for randomizing media access control (MAC) addresses of wireless stations according to some embodiments.

[0045] Figure 23 A block diagram illustrating an example of a method for selecting a sequence number offset for one or more sequence number spaces during an MLD parameter change, according to some embodiments.

[0046] Figure 24 and Figure 25 A block diagram illustrating an example of a method of operating an access point of an MLD according to some embodiments.

[0047] Figure 26 A block diagram illustrating an example of a method for adding a new access point to an MLD using a Basic Service Set (BSS) Handover Management (BTM) query, according to some embodiments.

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

[0049] Acronyms

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

[0051] UE: User Equipment

[0052] AP: Access Point

[0053] STA: wireless station

[0054] TX: Transmit / Transmit

[0055] RX: Receive / Receive

[0056] LAN: Local Area Network

[0057] WLAN: Wireless Local Area Network

[0058] RAT: Radio Access Technology

[0059] ACK: Acknowledgement

[0060] BA: Block Acknowledgement

[0061] NAKC: Negative Acknowledgement

[0062] N-BA: Negative Block Acknowledgement

[0063] TSF: Time synchronization function

[0064] QoS: Quality of Service

[0065] the term

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

[0067] Memory medium - any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include installation media, for example, CD-ROMs, floppy disks, or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, for example, hard drives or optical storage devices; registers or other similar types of memory elements, etc. The memory medium may also include other types of non-transitory memory or a combination thereof. In addition, the memory medium may be located in the first computer system that executes the program, or may be located in a different second computer system that is connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory medium" may include two or more memory media that may reside in different locations in different computer systems connected, for example, via a network. The memory medium may store program instructions (for example, expressed as a computer program) that can be executed by one or more processors.

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

[0069] Computer System—Any of various types of computing or processing systems, including a personal computer system (PC), a mainframe computer system, a workstation, a network appliance, an Internet appliance, a personal digital assistant (PDA), a television system, a grid computing system, or other devices or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (and / or combination of devices) having at least one processor that executes instructions from a memory medium.

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

[0071] Wireless Device (and / or Wireless Station) - Any of various types of computer system devices that perform wireless communications using WLAN communications. As used herein, the term "wireless device" may 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 may be any type of wireless station for an 802.11 system, such as an access point (AP) or a client station (STA or UE). Other examples include televisions, media players (e.g., Apple TV TM , Roku TM , Amazon FireTV TM , Google Chromecast TM etc.), refrigerators, washing machines, thermostats, etc.

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

[0073] Processing Element—refers to various specific implementations of digital circuitry that performs functions in a computer system. Additionally, a processing element may refer to various implementations of analog or mixed-signal (a combination of analog and digital) circuitry that performs a function (and / or multiple functions) in a computer or computer system. Processing elements include, for example, circuits (such as integrated circuits (ICs), ASICs (application-specific integrated circuits), portions or circuits of individual processor cores), entire processor cores, individual processors, programmable hardware devices (such as field-programmable gate arrays (FPGAs)), and / or larger portions of systems that include multiple processors.

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

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

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

[0077] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to." Representing a component as being configured to perform one or more tasks expressly intends that the component not be interpreted under 35 U.S.C. §112(f).

[0078] Figure 1A-1B —Wireless communication system

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

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

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

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

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

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

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

[0086] Figure 1B An exemplary wireless device 100 (e.g., corresponding to wireless device 102 and / or wireless device 104) that can be configured for use in conjunction with various aspects of the present disclosure is shown. Device 100 can be any of a variety of types of devices and can be configured to perform any of a variety of types of functions. Device 100 can be a substantially portable device or a substantially stationary device, potentially including any of a variety of types of devices. Device 100 can be configured to perform one or more ranging wireless communication techniques or features, such as any of the techniques or features subsequently shown and / or described herein with respect to any or all of the figures.

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

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

[0089] It should be noted that in some cases, for example, wireless communication circuitry 130 may include its own processing element (e.g., a baseband processor) in addition to processing element 101. For example, processing element 101 may be an "application processor" whose primary function may be to support application layer operations in device 100, while wireless communication circuitry 130 may be a "baseband processor" whose primary function may be to support baseband layer operations in device 100 (e.g., to facilitate wireless communication between device 100 and other devices). In other words, in some cases, device 100 may include multiple processing elements (e.g., may be a multi-processor device). Other configurations utilizing a multi-processor architecture (e.g., instead of or in addition to an application processor / baseband processor configuration) are also possible.

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

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

[0092] Figure 1C —WLAN system

[0093] Figure 1CAn exemplary WLAN system according to some embodiments is shown. As shown, the exemplary WLAN system includes multiple wireless client stations or devices, or user equipment (UE) 106, which are configured to communicate with an access point (AP) 112 via a wireless communication channel 142. AP 112 can be a Wi-Fi access point. AP 112 can communicate with one or more other electronic devices (not shown) and / or another network 152 (such as the Internet) via a wired and / or wireless communication channel 150. Additional electronic devices, such as remote devices 154, can communicate with components of the WLAN system via network 152. For example, remote device 154 can be another wireless client station. The WLAN system can be configured to operate according to any of a variety of communication standards, such as various IEEE 802.11 standards. In some embodiments, at least one wireless device 106 is configured to communicate directly with one or more neighboring mobile devices without using access point 112.

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

[0095] Figure 2 —Access Point Block Diagram

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

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

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

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

[0100] Figure 3 —Client site diagram

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

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

[0103] As described above, the client station 106 may be configured to communicate wirelessly directly with one or more neighboring client stations. The client station 106 may be configured to communicate according to a WLAN RAT to implement a WLAN network such as Figure 1C ) or Figure 1A Furthermore, in some embodiments,

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

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

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

[0107] Figure 4 —Wireless node block diagram

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

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

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

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

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

[0113] Mobile MLD Privacy and Operation

[0114] Privacy issues have arisen during access point (AP) discovery, link setup, and link maintenance. To improve the privacy of scanning stations, IEEE 802.11aq introduced the transmission of scanning frames using randomized media access control (MAC) addresses. Furthermore, the privacy of initial public scans can be enhanced using the access point's public key. For example, unassociated wireless stations can use a public key and asymmetric cryptography to establish a shared key with the access point. This shared key can be used to encrypt unicast scanning, authentication, and association frames, ensuring privacy for both unassociated stations and the access point. Furthermore, IEEE 802.11be proposes the definition of Robust Multi-Link Device (MLD) Query Request and Query Response frames, as well as Robust Reassociation frames. These frames can be used in the associated state to improve the privacy of wireless stations. Wireless stations can perform virtual link setup and then, in the associated state, perform dedicated discovery and link setup with optimized parameters. Furthermore, IEEE 802.11md introduces an integrity checksum for beacon frames. This allows associated stations to verify that the associated access point transmitted the beacon frame.

[0115] In current implementations, access point (AP) multi-link device (MLD) nodes may need to manage and / or optimize their affiliated APs. Therefore, AP MLD nodes should be able to add more affiliated APs to increase capacity, manage basic service set (BSS) interference and coverage, including switching APs to operate on channels with minimal interference, and / or manipulate associated non-AP MLD nodes to operate on the best-performing AP and / or AP MLD. Therefore, AP MLD nodes may need a mechanism to add affiliated APs to the AP MLD. However, in current implementations, non-AP MLD nodes create all links (e.g., associations between affiliated STAs in the non-AP MLD and affiliated APs in the AP MLD) when associating with an AP MLD, and association request and response signaling is unprotected. This poses a privacy threat to both non-AP MLD nodes and AP MLDs, as the integrity, traceability, and / or privacy of association signaling may be compromised. Furthermore, association resets many parameters, such as the sequence number (SN), packet number (PN), block acknowledgement, and traffic specification (TSPEC) parameters. These parameters are reset for all frame types and traffic identifiers (IDs), such as priority. Thus, if / when a non-AP MLD node uses reassociation to add an AP link to an associated AP MLD, the parameter reset interrupts transmission in all links.

[0116] The embodiments described herein provide systems, methods, and mechanisms for robust discovery of access points (APs) in AP MLD nodes, robust link addition to AP MLD associations, AP beacon mode when adding or removing APs from an AP MLD, robust BSS handover management (BTM) signaling for steering non-AP MLDs to the best AP MLD and the most suitable AP, and improved privacy for associated non-AP MLDs. The embodiments described herein can ease multi-link maintenance. It is noted that in the embodiments described herein, "robust" can refer to wireless communications that can withstand intentional or accidental interference, such as technical failures, signal jammers, and / or security threats.

[0117] For example, protected broadcast probe responses can reduce management frame storms if and / or when an AP in an AP MLD changes its parameter values. As another example, a relaxed parameter change counter can indicate that a parameter has changed, but can allow the new parameter to be acquired on the link. Furthermore, the embodiments described herein can improve the privacy of associated non-AP MLDs. For example, frame sequence numbers can be made to operate within a link-specific range. As another example, when an associated non-AP MLD is (re)associated, the associated non-AP MLD can change its MLD MAC address, link-specific MAC address, sequence number, etc. As a further example, a wireless station can control whether parameter changes are immediate or delayed, or whether there is a sequence of delayed changes. Furthermore, the embodiments described herein can improve the privacy of AP MLDs. For example, an AP MLD can select an AP where the AP MLD is discoverable and that serves legacy wireless stations (e.g., supports up to IEEE 802.11be). Thus, the AP MLD can serve legacy wireless stations on non-discoverable links and can transmit new beacon frame types on links where the AP is not discoverable. Additionally, the AP can improve privacy by changing its parameters and those of the associated wireless stations.

[0118] In some embodiments, a non-AP MLD (e.g., such as wireless station 106) can use default parameters to authenticate and associate to an AP in an AP MLD. After association, the non-AP MLD can securely discover other APs, add more links, and / or optimize its link parameters. Such a scheme can help protect the privacy of both the non-AP MLD and the AP MLD. For example, Figure 5A and Figure 5B A block diagram illustrating an example of a method for secure multi-link setup according to some embodiments is shown. Figure 5A and Figure 5BThe methods shown in the figure can be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. Figure 5A , as shown in the figure, the method can be operated as follows.

[0119] At 502, a wireless station (STA), such as wireless station 106, may perform an initial scan, for example, to discover one or more APs in an AP MLD. The initial scan may include transmitting one or more probe requests and / or receiving one or more probe responses and / or beacons.

[0120] At 504, the STA may (optionally) perform additional scans, eg, to discover one or more additional links.

[0121] At 506, the STA may authenticate with the AP. Authentication may be open, e.g., without a password, or in authentication, the AP and STA may verify that they provide and / or prove possession of a password. For example, the STA may use a Simultaneous Authentication of Equals (SAE) algorithm in authentication.

[0122] At 508, the STA may perform a "virtual" or placeholder MLD setup with the authenticated AP. In other words, when the discovered AP does not have a public key, the STA may need to send its association signaling / MLD setup signaling without encryption. Thus, the STA can minimize the sharing of its private information during MLD setup. The STA can also minimize the information it transmits during discovery. For example, the STA may use passive and / or very simple active scanning. Consequently, MLD setup / association can be simple, and the STA can use default parameter values ​​during MLD setup.

[0123] The STA may perform a 4-way handshake with the discovered AP at 510. The 4-way handshake may then authenticate the discovered AP.

[0124] At 512, the STA may perform robust discovery with associated APs. Thus, the STA may use a robust MLD discovery scheme to discover all APs in the associated AP MLD, including robust discovery MLD probe requests and responses and robust MLD query requests and responses. In some embodiments, robust management frames may be used to protect such communications.

[0125] At 514, the STA may, for example, perform robust reassociation or link addition signaling within the associated AP MLD, as needed and / or as desired. Thus, the STA may use a robust MLD reassociation / link setup scheme to set up a link with capabilities and operating parameters optimized for the AP. Alternatively or additionally, the STA may also change parameter values ​​used in the virtual association. The robust MLD reassociation / link setup scheme may include the use of a robust reassociation request and a robust reassociation response. In some embodiments, robust management frames may be used to protect such communications.

[0126] Go to Figure 5B , as shown in the figure, the method can be operated as follows.

[0127] At 522, a wireless station (STA), such as wireless station 106, may perform an initial scan, for example, to discover one or more APs in an AP MLD. The initial scan may include transmitting one or more probe requests and / or receiving one or more probe responses and / or beacons.

[0128] At 524, the STA may (optionally) set an encryption key to encrypt frames before the STA associates with the AP discovered in the AP MLD. In some embodiments, the discovered AP's public key may be received out-of-band, for example, via a local Quick Response (QR) code, an authentication server, or the like. In some embodiments, the discovered AP's public key may be received during the initial wireless link established between the STA and the discovered AP. The STA uses the AP's public key to encrypt a message used to derive a symmetric key between the STA and the AP. The symmetric key is used to encrypt messages before the STA associates with the AP. If the AP's public key is available, the STA may encrypt authentication and association signaling.

[0129] At 526, the STA may (optionally) perform additional scans, eg, to discover one or more additional links.

[0130] At 528, the STA may perform authentication with the AP to initiate the association process. For example, the authentication may use the SAE authentication protocol. The authentication message may be protected by the symmetric key derived using the AP at 524.

[0131] At 530, the STA may associate with the AP. During association, the STA may establish all links it wishes to use. The association request and response may be protected by the symmetric key derived at 524 using the AP.

[0132] At 532, the STA may perform a 4-way handshake with the AP. The 4-way handshake may then authenticate the associated AP. The 4-way handshake messages may be protected by the symmetric key derived at 524 using the AP.

[0133] At 534, the STA may perform robust discovery with the associated AP. Thus, the STA may use the robust MLD discovery scheme to discover all APs in the associated AP MLD, including robust discovery MLD probe requests and responses and robust MLD query requests and responses. In some embodiments, robust management frames may be used to protect such communications. Note that after the STA establishes keys via the 4-way handshake, the STA may cease using the symmetric key derived with the AP at 524.

[0134] At 536, the STA may, for example, perform robust reassociation or link addition signaling within the associated AP MLD, as needed and / or as desired. Thus, the STA may use a robust MLD reassociation / link setup scheme to set up a link with capabilities and operating parameters optimized for the AP. Alternatively or additionally, the STA may also change parameter values ​​used in the virtual association. The robust MLD reassociation / link setup scheme may include the use of a robust reassociation request and a robust reassociation response. In some embodiments, robust management frames may be used to protect such communications.

[0135] In some embodiments, for example, Figure 6A As shown, when AP MLD adds a new subordinate AP, the new AP may be included in the transmitted Reduce Neighbor Report (RNR) element and multi-link element. In some embodiments, the beacon may contain a set of new AP parameters. In addition, the associated STAs may detect the new AP by receiving beacons from other APs in the AP MLD. In addition, the legacy STAs may find the new AP through passive and / or active scanning. In some embodiments, AP MLD may mitigate link addition storms by delaying the transmission of new AP parameters in beacons. Therefore, Figure 6A As shown, a multi-link (ML) entity 604 may include APs 612a and 612b. APs 612a and 612b may transmit beacons 610a and 610b, respectively. Beacons 610a and 610b may include their respective RNR information and ML element information. Then, when ML entity 604 adds AP 612c (e.g., a new AP), AP 612c may also transmit beacon 610c, which may include RNR information and ML element information for AP 612c.

[0136] In some embodiments, for example, Figure 6BAs shown, an associated non-AP MLD (e.g., such as wireless station 106 and / or wireless node 107) may send a robust ML query request to query the AP MLD for available APs and associated parameters. In other words, the associated non-AP MLD may perform secure multi-link scanning. As shown, non-AP MLD 614 may be associated with ML entity 604 and may include STAs 606a through 606c. STA 606a may send a robust ML query request 620 to AP 612a. AP 612a may respond with a response 622. Response 622 may be a unicast ML query response to STA 606a or a broadcast (ML) probe response in response to request 620 and one or more additional requests (e.g., from other STAs). Additionally, as shown, STA 606b may have a link 624 established with AP 612b.

[0137] In some embodiments, the response 622 may be considered an integrity protected broadcast probe response. The integrity protected broadcast probe response may include a media access control (MAC) management encapsulation element (MME). The MME may be the last element in the frame. Figure 7A As shown, the integrity protected broadcast probe response may include a header, a timestamp, an interval element, and various information elements, including MME. Figure 7B and Figure 7C As shown, the MME may include an element identifier (ID) field, a length field, a key ID field, a beacon integrity packet number (BIPN) field and / or a probe response integrity packet number (PRPN), and a message integrity check (MIC) field. In some embodiments, an integrity checksum may be calculated over the entire probe response, and the timestamp field may be masked (e.g., set to 0) before the integrity checksum is calculated. In some embodiments, the probe response may use the same beacon integrity group temporal key (BIGTK) as used for beacon integrity verification. Additionally, the probe response may use the same BIPN (e.g., as Figure 7B ) as a beacon, or with a separate PRPN (e.g., as Figure 7C In addition, STAs with a BIGTK security association (BIGTKSA) can verify the integrity of the broadcast probe response.

[0138] In some embodiments, for example, Figure 6CAs shown, an associated non-AP MLD (e.g., such as wireless station 106 and / or wireless node 107) may add a new link (e.g., link 628) via a robust add link request (e.g., request 624) and a robust add link response (e.g., response 626) without disrupting the operation of other links. In some embodiments, sequence numbers (SNs), packet numbers (PNs), buffers, block acknowledgements, TSPECs, etc., between the non-AP MLD 614 and the ML entity 604 may not be reset. In some embodiments, a group transient key (GTK) may be provided for the new link. Additionally, once the new link is added, the non-AP STA and MLD parameters may be tuned with the AP MLD. Note that the robust add link request and response may be secure and private, for example, by using a protocol such as that described in reference

[0066] 7A to 7C Integrity protected broadcast probe response as described.

[0139] Figure 8A An example of signaling for providing GTK for a new link according to some embodiments is shown. Figure 8A The signaling shown in the figure can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown can be executed concurrently in an order different from the order shown, or can be omitted. Additional signaling can also be performed as needed. As shown in the figure, the signaling can adopt the following process.

[0140] For example, as described herein, signaling 802 may associate STA 606a with AP 612a. STA 606a may then send an add link request 804 to AP 612a. Add link request 804 may indicate that a link for STA 606b is to be added. For example, as described herein, add link request 804 may be a robust add link request. In some embodiments, a complete set of non-AP STA parameters and AP parameters may be provided for each added link. Note that robust reassociation may include TID-to-link mapping if a non-default TID-to-link mapping is used, otherwise the default mapping (which may use transmission of all TIDs on all links) may be used. Additionally, the power mode (PM) for the link may be provided by the non-AP STA (e.g., STA 606a) for the link. Furthermore, a non-AP MLD (e.g., non-AP MLD 614) may provide a multi-link attribute that may specify its non-STR / STR capabilities for both newly added and existing links (e.g., whether the non-AP MLD can simultaneously transmit / receive on multiple links in a given set of links). AP 612a may respond with an add link response 806. Add link response 806 may indicate that the link for STA 606b is supported by AP 612b. In other words, a new link will be added between STA 606b and AP 612b. For example, as described herein, add link response 806 may be a robust add link response. After adding the new link at 808, STA 606a and AP 612a may exchange EA poll messages 810a-d as part of a 4-way handshake to establish the BIGTK Security Architecture (BIGTKSA), Integrity GTK (IGTK) Security Architecture (IGTKSA), and GTK Security Architecture (GTKSA) for the new link. Note that all links use the same Peer Transient Key Security Architecture (PTKSA), which may have been set up via the initial association of the unicast frame. Upon completion of the 4-way handshake at 812, STA 606a may transmit data 814 to AP 612b. As shown, AP 612b may transmit an acknowledgment 816 of the data.

[0141] Figure 8B Another example of signaling for providing GTK for a new link according to some embodiments is shown. Figure 8B The signaling shown in the figure can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown can be executed concurrently in an order different from the order shown, or can be omitted. Additional signaling can also be performed as needed. As shown in the figure, the signaling can adopt the following process.

[0142] As noted, signaling 802 may associate STA 606a with AP 612a, e.g., as described herein. STA 606a may then send an add link request 804 to AP 612a. Add link request 804 may indicate that a link for STA 606b is to be added. For example, add link request 804 may be a robust add link request, as described herein. In some embodiments, a complete set of non-AP STA parameters and AP parameters may be provided for each added link. Note that robust reassociation may include the TID-to-link mapping if a non-default TID-to-link mapping is used, otherwise the default mapping (which may use transmission of all TIDs on all links) may be used. Additionally, the power mode (PM) for the link may be provided by the non-AP STA (e.g., STA 606a) for the link. In addition, the non-AP MLD (e.g., non-AP MLD 614) may provide a multi-link attribute that may specify its non-STR / STR capabilities for newly added links and existing links (e.g., whether the non-AP MLD can simultaneously transmit / receive on multiple links of a given set of links). AP 612a may respond with an add link response 806. Add link response 806 may indicate that the link for STA 606b is supported by AP 612b. In other words, a new link will be added between STA 606b and AP 612b. For example, as described herein, add link response 806 may be a robust add link response. In some embodiments, STA 606a may use fast MLD handover signaling to reduce the number of frames transmitted in a robust reassociation. Thus, as shown, after receiving add link response 806, STA 606a may transmit a robust reassociation request 818 indicating that a link has been added for STA 606b. The robust reassociation request may use a robust reassociation frame. AP 612a may respond with a robust reassociation response 820 indicating that AP 612b will support adding the link. The reassociation response may use a robust reassociation frame. Note that robust reassociation (e.g., fast MLD handover signaling) may establish the BIGTKSA, IGTKSA, and GTKSA for the new link. Upon completion of adding the new link and the 4-way handshake (completed via fast MLD handover signaling) at 822, STA 606a may transmit data 824 to AP 612b. As shown, AP 612b may transmit an acknowledgment 826 of the data.

[0143] Figure 8C Another example of signaling for providing a GTK for a new link is shown according to some embodiments. Figure 8CThe signaling shown in the figure can be used in conjunction with any of the systems, methods, or devices shown in the figure, as well as other devices. In various embodiments, some of the signaling shown can be executed concurrently in an order different from the order shown, or can be omitted. Additional signaling can also be performed as needed. As shown in the figure, the signaling can adopt the following process.

[0144] As noted, signaling 802 may associate STA 606a with AP 612a, e.g., as described herein. STA 606a may then send an add link request 804 to AP 612a. Add link request 804 may indicate that a link for STA 606b is to be added. For example, add link request 804 may be a robust add link request, as described herein. In some embodiments, a complete set of non-AP STA parameters and AP parameters may be provided for each added link. Note that robust reassociation may include the TID-to-link mapping if a non-default TID-to-link mapping is used, otherwise the default mapping (which may use transmission of all TIDs on all links) may be used. Additionally, the power mode (PM) for the link may be provided by the non-AP STA (e.g., STA 606a) for the link. In addition, the non-AP MLD (e.g., non-AP MLD 614) may provide a multi-link attribute that may specify its non-STR / STR capabilities for newly added links and existing links (e.g., whether the non-AP MLD can simultaneously transmit / receive on multiple links of a given set of links). AP 612a may respond with an add link response 806. Add link response 806 may indicate that the link for STA 606b is supported by AP 612b. In other words, a new link will be added between STA 606b and AP 612b. For example, as described herein, add link response 806 may be a robust add link response. In some embodiments, STA 606a may use modified fast MLD handover signaling to reduce the number of frames transmitted in a robust reassociation. Thus, as shown, after receiving add link response 806, STA 606a may transmit an authentication request 828 to AP 612A. AP 612a may respond with an authentication response 830. Note that authentication (e.g., modified Fast MLD handover signaling) may establish BIGTKSA, IGTKSA, and GTKSA for the new link. Upon completion of adding the new link and the 4-way handshake (completed via modified Fast MLD handover signaling) at 832, STA 606a may transmit data 834 to AP 612b. As shown, AP 612b may transmit an acknowledgment 836 of the data.

[0145] In some embodiments, a STA (such as STA 106 and / or STAs 606a to 606c) may hide its MLD MAC address and use a link-specific address. A non-AP MLD may define a link-specific MAC address and / or a temporary non-AP MLD address during association. The temporary non-AP MLD address may be used for group-addressed frames and A-MSDU transmissions. The actual (e.g., real) non-AP MLD address may only be used for authentication. In some embodiments, for example, Figure 9 As shown, the add link request can be used to randomize the STA MAC address.

[0146] Figure 9 An example of signaling for randomizing the MAC addresses of wireless stations according to some embodiments is shown. Figure 9 The signaling shown in the figure can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown can be executed concurrently in an order different from the order shown, or can be omitted. Additional signaling can also be performed as needed. As shown in the figure, the signaling can adopt the following process.

[0147] For example, as described herein, signaling 902 may associate STA 606a with AP 612a. STA 606a may then send an add link request 904 to AP 612a. Add link request 904 may indicate the MAC address associated with the link, a new MLD MAC address sequence number (SN) offset (including TID, UL, DL), and an updated TSF for the MAC address. For example, as described herein, add link request 904 may be a robust add link request. AP 612a may send an add link response 906 to STA 606a. Add link response 906 may indicate the MAC address associated with the link, a new MLD MAC address sequence number (SN) offset (including TID, UL, DL), and an updated TSF for the MAC address. Upon receipt of add link response 906, the new MAC address may be implemented (e.g., an immediate parameter change), or a delay may occur before the new MAC address is implemented (e.g., a delayed parameter change). Note that multiple future changes to the MAC address may also be scheduled. For example, each STA in a non-AP MLD and the AP in an AP MLD can change their parameters on different schedules and / or on the same schedule. Note that multiple sequence number spaces can be used (e.g., for unicast management frames, there can be a Traffic ID (TID) / priority-specific unicast data sequence number offset). Sequence number offsets can be defined separately for each sequence number space. In some embodiments, when the STA and / or AP-specific address changes, it may be advisable to change the sequence number offsets for all TIDs and frame types.

[0148] In some embodiments, the SN offset (e.g., included in the add link request 904 / add link response 906) can be randomized, for example, to make it more difficult for a third party to detect wireless stations belonging to non-AP MLDs. In some embodiments, the SN offset can be link-specific. Figure 10 A block diagram illustrating an example of a method for randomizing SN offsets according to some embodiments is shown. Figure 10 The method shown can be used in conjunction with any system, method or device shown in the figure and other devices. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0149] At 1002, an application and / or website (e.g., the Internet) may generate data (e.g., one or more MAC PDUs), which may be received into a transmit buffer at 1004. The transmit buffer may map MAC PDUs (MPDUs) to sequence numbers (SNs). The transmit buffer may forward the MAC PDUs to one or more transmit queues, for example, based on the sequence numbers, each transmit queue associated with a link between a non-AP MLD and an ML entity. At 1006, a first transmit queue associated with a first link may receive an MPDU with an associated SN. The first transmit queue may add a link offset (e.g., Offset_link 1) to the SN to generate a link-specific SN, e.g., SN_link1. Similarly, at 1008, a second transmit queue associated with a second link may receive an MPDU with an associated SN. The second transmit queue may add a link offset (e.g., Offset_link 2) to the SN to generate a link-specific SN, e.g., SN_link2. Furthermore, at 1010, a third transmit queue associated with a third link may receive an MPDU with an associated SN. The third transmission queue may add a link offset (e.g., Offset_link3) to the SN to generate a link-specific SN, e.g., SN_link3. At 1010, a first receive buffer may receive an MPDU with a sequence number SN_link1 from the first transmission queue via a first link. The first receive buffer may determine the sequence number associated with the MPDU by removing the SN offset associated with the first link (e.g., Offset_link1). Similarly, at 1012, a second receive buffer may receive an MPDU with a sequence number SN_link2 from the second transmission queue via a second link. The second receive buffer may determine the sequence number associated with the MPDU by removing the SN offset associated with the second link (e.g., Offset_link2). Furthermore, at 1014, a third receive buffer may receive an MPDU with a sequence number SN_link3 from the third transmission queue via a third link. The third receive buffer may determine the sequence number associated with the MPDU by removing the SN offset associated with the third link (e.g., Offset_link3). At 1016 , the reordering buffer may reorder the MPDUs received via the first receive buffer, the second receive buffer, and the third receive buffer based on the determined sequence number of each MPDU. At 1016 , a server of a website and / or application may receive data.

[0150] In some embodiments, MPDUs transmitted after the scheduled MAC address and / or sequence number change time may use the new parameters (e.g., associated with the updated MAC address and / or sequence number). In some embodiments, MPDUs transmitted after the TSF time (e.g., Figure 11 Note that MPDUs transmitted before the TSF time may use the current (e.g., old) parameters. In some embodiments, retransmissions and MPDUs buffered in a link-specific transmit queue (e.g., as of the TSF time) may use the current (e.g., old) values. Note that MPDUs transmitted in a physical PDU (PPDU) may use only the new or old parameter values. Figure 11 As further shown, in some embodiments, the scheduled MAC address and / or sequence number (e.g., parameter) change time may include a tolerance time. As shown, when a transmission opportunity such as TXOP 1102 is initiated during the tolerance time, the receiver may detect from the AID and MAC address whether the transmitted PPDU has a new parameter value or the current parameter value, e.g., as described in reference to FIG. Figure 12 As further described. Thus, PPDUs / MPDUs transmitted during the tolerance time may use either the current parameter values ​​or the new parameter values. However, a TXOP initiated after the tolerance time will only be received if the PPDU / MPDU is transmitted with the new parameter values.

[0151] Figure 12 A block diagram illustrating an example of a method for selecting an SN offset during a parameter change according to some embodiments is shown. Figure 12 The method shown in the figure can also be used together with any one of the systems, methods or devices shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0152] At 1202, a receiver (e.g., an AP such as an ML entity) may receive a MAC PDU (MPDU) via a link with a non-AP MLD (e.g., from a wireless station of the non-AP MLD). At 1204, the receiver may determine whether parameters associated with the MPDU are parameters used before a parameter change time (e.g., old parameters) or parameters used after the parameter change time (e.g., new parameters). At 1206, in response to determining that the parameters associated with the MPDU are old parameters, the receiver may determine whether the MPDU was transmitted during a tolerance time. At 1208, in response to determining that the MPDU was transmitted after the tolerance time, the receiver may discard the MPDU. Alternatively, at 1210, in response to determining that the MPDU was transmitted before and / or during the tolerance time, the receiver may acknowledge the MPDU and determine a sequence number for the MPDU using an SN offset used before the parameter change time (e.g., the old SN offset). The receiver may then add the MPDU to a reordering buffer using the determined sequence number. In addition, in response to determining that the parameter associated with the MPDU is a new parameter, the receiver may confirm the MPDU and determine the sequence number of the MPDU using the SN offset used after the parameter change time (e.g., the new SN offset) at 1212. The receiver may then add the MPDU to the reordering buffer using the determined sequence number.

[0153] In some embodiments, during the addition of an AP to an ML entity, the AP of the ML entity may operate in various stages. For example, Figure 13 An example of various operational phases of an AP for an ML entity during AP addition according to some embodiments is shown. As shown, during AP addition, the AP may be in any of six operational phases. In the open phase (e.g., the default operational mode), the AP may remain in active mode and may be visible to all wireless stations within range. In the hidden phase, the AP may not be included in the ML elements of other APs in reduced neighbor reports (RNR) and AP MLD. Note that when in the hidden phase, the AP may be discoverable only on its primary channel. In the encryption phase, the AP may transmit encrypted beacons and may be visible only to selected wireless stations that know the AP beacon encryption key. In the shutdown phase, the AP may be inoperable. In the shutdown and / or shutdown encryption phases, the AP may be shutting down (e.g., switching to the shutdown phase) and may be in the process of securely terminating links to all wireless stations. As shown in FIG. Figure 13As shown, primary AP 1312a may remain in the open phase of operation while one or more APs (e.g., secondary APs 1312b and 1312c) are added. Upon addition, secondary AP 1312b may switch from the closed phase to the encrypted phase and may be discoverable only to selected wireless stations (e.g., as selected by primary AP 1312a). After a period of time, secondary AP 1312b may decide to switch to the closed phase and may include a closed encrypted phase prior to the closed phase, e.g., to securely terminate links to wireless stations associated with AP 1312b. Upon addition, secondary AP 1312c may switch from the closed phase to the hidden phase before switching to the open phase. The hidden phase may help AP 1312c avoid link signaling storms when entering the open phase. After a period of time in the open phase, AP 1312c may decide to switch to the closed phase and may include a closed phase prior to the closed phase, e.g., to securely terminate links to wireless stations associated with AP 1312c.

[0154] In some embodiments, APs of an ML entity (e.g., APs of an AP MLD) can operate in various beacon modes. In such embodiments, APs broadcasting in hidden beacon mode, dedicated beacon mode, encrypted beacon mode, and / or APs that do not transmit beacons may not be included in the RNR and ML elements of beacons, probe responses, and / or multilink probe responses of other APs in the AP MLD. Therefore, such APs cannot be discovered by beacons received from another AP in the AP MLD. Note that an AP transmitting in hidden beacon mode may transmit normal beacon frames to its RNR and ML elements, which may include other APs in the AP MLD. Further note that an AP transmitting in dedicated beacon mode may transmit normal beacon frames to its RNR and ML elements, which may not include other APs in the AP MLD. Furthermore, an AP transmitting in encrypted beacon mode may not use normal beacon frames. Instead, a receiver may need to detect the content of the beacon frame; for example, the beacon frame may be encrypted with the GTK used for management frames. Such beacon frames may be shorter than normal beacon frames. Additionally, such beacon frames may not include SSIDs, security parameters, and / or BSS performance parameters.Such beacon frames may include other APs in the AP MLD to their RNR and ML elements.

[0155] For example, 14A to 14D 1 shows examples of various beacon modes for an AP attached to an AP MLD according to some embodiments. Figure 14AAs shown, when all APs are in the default beacon mode, the beacon from AP1 1412a may include an ML indicator having values ​​for AP1 1412a, AP2 1412b, and AP3 1412c, and an RNR indicator having values ​​for AP2 1412b and AP3 1412c. Similarly, the beacon from AP2 1412b may include an ML indicator having values ​​for AP1 1412a, AP2 1412b, and AP3 1412c, and an RNR indicator having values ​​for AP1 1412a and AP3 1412c. Furthermore, the beacon from AP3 1412c may include an ML indicator having values ​​for AP1 1412a, AP2 1412b, and AP3 1412c, and an RNR indicator having values ​​for AP1 1412a and AP2 1412b. Figure 14B As shown, AP3 1412c may be in hidden / encrypted beacon mode. Thus, a beacon from AP1 1412a may include an ML indicator having values ​​for AP1 1412a and AP2 1412b, but not AP3 1412c, and an RNR indicator having values ​​for AP2 1412b. Similarly, a beacon from AP2 1412b may include an ML indicator having values ​​for AP1 1412a and AP2 1412b, but not AP3 1412c, and an RNR indicator having values ​​for AP1 1412a. Furthermore, a beacon from AP3 1412c may include an ML indicator having values ​​for AP1 1412a, AP2 1412b, and AP3 1412c, and an RNR indicator having values ​​for AP1 1412a and AP2 1412b. Figure 14C As shown, AP3 1412c may be in dedicated beacon mode. Thus, a beacon from AP1 1412a may include an ML indicator having values ​​for AP1 1412a and AP2 1412b, but not AP3 1412c, and an RNR indicator having a value for AP2 1412b. Similarly, a beacon from AP2 1412b may include an ML indicator having values ​​for AP1 1412a and AP2 1412b, but not AP3 1412c, and an RNR indicator having a value for AP1 1412a. Furthermore, a beacon from AP3 1412c may not include an ML indicator or an RNR indicator. Figure 14DAs shown, AP3 may not transmit a beacon. Therefore, the beacon from AP1 1412a may include an ML indicator having values ​​for AP1 1412a and AP2 1412b, but not for AP3 1412c, and an RNR indicator having a value for AP2 1412b. Similarly, the beacon from AP2 1412b may include an ML indicator having values ​​for AP1 1412a and AP2 1412b, but not for AP3 1412c, and an RNR indicator having a value for AP1 1412a.

[0156] Figure 15 An example of an AP beacon according to some embodiments is shown. As shown, at 1520, while one or more APs (e.g., secondary APs 1512b and 1512c) are added, primary AP 1512a may remain in an open phase of operation. During 1520, APs 1512b and 1512c may be shut down, and AP 1512a may transmit a beacon having only information associated with AP 1512a.

[0157] At 1522, AP 1512c may switch to a hidden mode of operation, while AP 1512b remains off. During 1522, AP 1512a may transmit a beacon having only information associated with AP 1512a (e.g., AP 1512a does not include information such as RNR and ML elements associated with AP 1512c). However, AP 1512c may transmit a beacon having information associated with both AP 1512c and AP 1512a (e.g., RNR and ML elements associated with AP 1512a).

[0158] At 1524, AP 1512c may switch to an open mode of operation, while AP 1512b remains closed. During 1524, AP 1512a may transmit a beacon having information associated with AP 1512a and AP 1512c (e.g., RNR and ML elements associated with AP 1512c). Similarly, AP 1512c may transmit a beacon having information associated with AP 1512c and AP 1512a (e.g., RNR and ML elements associated with AP 1512a).

[0159] At 1526, AP 1512b may switch to an encrypted mode of operation. During 1526, AP 1512a may transmit a beacon with information associated with AP 1512a and AP 1512c (e.g., RNR and ML elements associated with AP 1512c). Similarly, AP 1512c may transmit a beacon with information associated with AP 1512c and AP 1512a (e.g., RNR and ML elements associated with AP 1512a). However, AP 1512b may transmit a beacon with information associated with AP 1512a (e.g., RNR and ML elements associated with AP 1512a) and information associated with AP 1512c (e.g., RNR and ML elements associated with AP 1512c). Note that AP 1512b may not include such information in the probe response.

[0160] At 1528, AP 1512b may switch to an encryption-off mode of operation. During 1528, AP 1512a may transmit a beacon with information associated with AP 1512a and AP 1512c (e.g., RNR and ML elements associated with AP 1512c). Similarly, AP 1512c may transmit a beacon with information associated with AP 1512c and AP 1512a (e.g., RNR and ML elements associated with AP 1512a). However, AP 1512b may transmit a beacon with information associated with AP 1512a (e.g., RNR and ML elements associated with AP 1512a) and information associated with AP 1512c (e.g., RNR and ML elements associated with AP 1512c). Note that AP 1512b may not include such information in the probe response. Additionally, during 1528, AP 1512b may signal that it will shut down.

[0161] At 1530, AP 1512b may switch to off. During 1530, AP 1512a may transmit a beacon having information associated with AP 1512a and AP 1512c (e.g., RNR and ML elements associated with AP 1512c). Similarly, AP 1512c may transmit a beacon having information associated with AP 1512c and AP 1512a (e.g., RNR and ML elements associated with AP 1512a).

[0162] At 1532, AP 1512c may switch to a shutdown mode of operation. During 1532, AP 1512a may transmit a beacon with information associated with AP 1512a and an indication that AP 1512c will be shutting down. Similarly, AP 1512c may transmit a beacon with information associated with AP 1512c and AP 1512a (e.g., RNR and ML elements associated with AP 1512a). Additionally, during 1532, AP 1512c may signal that it will be shutting down.

[0163] At 1534, AP 1512c may transition to OFF. During 1534, AP 1512a may transmit a beacon having only information associated with AP 1512a.

[0164] Figure 16 Further illustrated are the distinctions between various AP operating modes according to some embodiments. As shown, and as described herein, APs operating in default (and / or legacy) operating mode with an AP MLD can be discovered via any AP in the AP MLD. Additionally, AP and link quality assessments can occur across all links or via ML probe requests. Furthermore, when operating in default mode, all links can be set up in a 1-stage setup. Furthermore, as described herein, APs operating in hidden operating mode with an AP MLD can only be discovered on their links (e.g., a hidden AP cannot be discovered via a link to another AP in the AP MLD). Furthermore, AP and link quality assessments can be slower than in default operation and can only be assessed for links to the primary AP, while secondary APs can be set up in a post-association state. Furthermore, APs operating in encrypted mode and / or not transmitting beacons with an AP MLD can be undiscoverable, e.g., only the primary AP can be discovered. AP and link quality assessments can be performed only for the primary AP, while secondary APs can be assessed in a post-association state. Additionally, secondary APs can be set up only in a post-association state.

[0165] In some embodiments, a wireless station in a non-AP MLD may query an AP MLD for available APs via a robust multilink (ML) query procedure. The ML query may identify the requested AP and / or request information for all APs in the AP MLD. The requested AP may transmit hidden, encrypted, and / or proprietary beacons. In this case, the AP in the AP MLD may transmit a unicast robust ML query response to the wireless station and provide AP parameters for the requested AP. Alternatively, if and / or when the AP does not want the wireless station to find the requested AP and add a link to the requested AP, the AP may not respond with a unicast robust ML query response. Furthermore, the AP may not provide any information about the requested AP.

[0166] In some embodiments, a soft AP of an AP MLD may have secondary APs operating in the 5 and / or 6 GHz bands, where a soft AP may be a mobile phone / tablet / laptop that can be switched to operate as an AP. Typically, a soft AP does not operate secondary APs unless the traffic load requires more capacity. However, a soft AP may dynamically add or remove secondary APs. Note that discoverable secondary APs may operate in active mode and may be included in beacons transmitted by other APs, while hidden secondary APs may operate in power save mode and / or have other limitations (e.g., as further described herein). In some embodiments, while all APs of an infrastructure AP MLD may generally be available at all times, the AP MLD may temporarily disable an AP, for example, if the traffic load is high and / or if the AP needs to perform measurements and / or other operations. An infrastructure AP may be independent and may not have a primary AP. Furthermore, an infrastructure AP may have both TX and RX capabilities, for example, an infrastructure AP may transmit and receive independently.

[0167] In some embodiments, an AP serving a legacy wireless station may be required to select a default mode of operation in which beacons are transmitted on all links, the AP is always available, and the AP is capable of both TX and RX. In some embodiments, a hidden AP may transmit selected groups of frames, may be available based on a TWT schedule, and may not be capable of both TX and RX. Note that an AP operating as a hidden AP may operate with any of the above-described features (e.g., may operate as a default AP) if the hidden AP is associated only with non-AP MLDs that support such operation.

[0168] BSS Handoff Management (BTM) signaling allows an AP to propose a BSS handoff to an associated wireless station (STA). A non-AP STA can send a BTM Query to an AP to query its associated APs for candidate APs. The associated AP can send a BTM Request to the STA's AP to propose a handoff. The STA can respond with a BTM Response to accept and / or reject the proposed handoff. In some embodiments, a BTM Request can be sent to a non-AP MLD. For example, an AP MLD can send a BTM Request to an associated non-AP MLD to request an MLD / BSS handoff to another AP / AP MLD, add a new link to the associated AP MLD, and / or disassociate a link / AP from the associated AP MLD. For an MLD / BSS handoff request to another AP / AP MLD, the non-AP MLD can perform a 4-way handshake, delete the current link, and create a new link to the new AP MLD. For the new link added to the associated AP MLD, the AP MLD can signal to the STA that it has a new AP, and the new AP may be undiscoverable to all STAs. Additionally, in at least some embodiments, a BTM request may be the only mechanism for discovering new APs.For a request to disassociate a link / AP from an associated AP MLD, the AP may shut down and the AP MLD may request that the STA stop using the AP.

[0169] Figure 17 An example of BSS handover management usage according to some embodiments is shown. As shown, at 1720, while one or more APs (e.g., secondary APs 1712b and 1712c) are added, primary AP 1712a may remain in an open phase of operation. During 1720, APs 1712b and 1712c may be shut down, and AP 1712a may transmit beacons containing only information associated with AP 1712a. AP 1712a may not transmit BTM frames.

[0170] At 1722, AP 1712c may switch to a hidden mode of operation, while AP 1712b remains off. During 1722, AP 1712a may transmit a BTM request to the selected STA. The BTM request frame may include an indication requesting the legacy STA to switch to AP 1712c. In addition, the BTM frame may include an indication requesting that a non-AP MLD be added to the link of AP 1712c. Furthermore, AP 1712a may transmit a beacon containing only information associated with AP 1712a (e.g., AP 1712a does not include information such as the RNR and ML elements associated with AP 1712c). However, AP 1712c may transmit a beacon containing information associated with both AP 1712c and AP 1712a (e.g., the RNR and ML elements associated with AP 1712a).

[0171] At 1724, AP 1712c may switch to an open mode of operation, while AP 1712b remains closed. During 1724, AP 1712a may transmit a beacon having information associated with AP 1712a and AP 1712c (e.g., RNR and ML elements associated with AP 1712c). Similarly, AP 1712c may transmit a beacon having information associated with AP 1712c and AP 1712a (e.g., RNR and ML elements associated with AP 1712a).

[0172] At 1726, AP 1712b may switch to an encrypted mode of operation. During 1726, APs 1712a and 1712c may transmit a BTM request to the selected station. The BTM frame may be transmitted to the selected non-AP MLD and may include an indication of a request to be added to the link of AP 1712b. In addition, AP 1712a may transmit a beacon with information associated with AP 1712a and AP 1712c (e.g., RNR and ML elements associated with AP 1712c). Similarly, AP 1712c may transmit a beacon with information associated with AP 1712c and AP 1712a (e.g., RNR and ML elements associated with AP 1712a). However, AP 1712b may transmit a beacon with information associated with AP 1712a (e.g., RNR and ML elements associated with AP 1712a), as well as a beacon with information associated with AP 1712c (e.g., RNR and ML elements associated with AP 1712c). Note that AP 1712b may not include such information in the probe response.

[0173] At 1728, AP 1712b may switch to an encryption-off mode of operation. During 1728, APs 1712a, 1712b, and 1712c may transmit BTM requests. The BTM frame may be transmitted to the non-AP MLD that has a link with AP 1712b and may include an indication that AP 1712b is shutting down. In addition, AP 1712a may transmit a beacon with information associated with AP 1712a and AP 1712c (e.g., RNR and ML elements associated with AP 1712c). Similarly, AP 1712c may transmit a beacon with information associated with AP 1712c and AP 1712a (e.g., RNR and ML elements associated with AP 1712a). However, AP 1712b may transmit a beacon with information associated with AP 1712a (e.g., RNR and ML elements associated with AP 1712a), as well as a beacon with information associated with AP 1712c (e.g., RNR and ML elements associated with AP 1712c). Note that AP 1712b may not include such information in the probe response.

[0174] At 1730, AP 1712b may switch to off. During 1730, AP 1712a may transmit a beacon having information associated with AP 1712a and AP 1712c (e.g., RNR and ML elements associated with AP 1712c). Similarly, AP 1712c may transmit a beacon having information associated with AP 1712c and AP 1712a (e.g., RNR and ML elements associated with AP 1712a).

[0175] At 1732, AP 1712c may switch to a shutdown mode of operation. During 1732, APs 1712a and 1712c may transmit BTM requests. BTM frames transmitted to legacy non-AP STAs associated with AP 1712c may include an indication to move to AP 1712a. BTM frames transmitted to non-AP MLDs with a link to AP 1712c may include an indication that AP 1712c will shut down. Furthermore, AP 1712a may transmit a beacon with information associated with AP 1712a and an indication that AP 1712c will shut down. Similarly, AP 1712c may transmit a beacon with information associated with both AP 1712c and AP 1712a (e.g., RNR and ML elements associated with AP 1712a).

[0176] At 1734, AP 1712c may switch to off. During 1734, AP 1712a may transmit a beacon having only information associated with AP 1712a. Note that in each of the above stages 1720-1732, available APs may respond to BTM queries of associated STAs.

[0177] Figure 18 The Request Mode field of a BTM request according to some embodiments is shown. As shown, the Request Mode field may include a field containing a Preferred Candidate List (e.g., to indicate that a Preferred Candidate List is included in the BTM request), a Punctuation field, a To Be Disassociated field, a field containing a BSS Termination field and an ESS To Be Disassociated field, a field containing an AP MLD Termination field, a New APs to Add field, and a Reserved field. In some embodiments, each field may be 1 bit. In some embodiments, when an AP MLD makes a new AP simultaneously discoverable by all STAs, all associated non-AP MLDs may simultaneously add links to the new AP, which may result in a management frame storm. In some embodiments, to mitigate management frame storms, the AP MLD may signal the availability of the new AP only to selected STAs using a BTM Request frame, e.g., as described herein. In some embodiments, the BTM request may propose that the STA create a link to the new AP, e.g., via the New APs to Add field of the Request Mode field. For example, the BTM request may set the New APs to Add field of the Request Mode field to a value of 1, e.g., to request that the STA create a link to the APs listed in the Candidate List. APs in the Candidate List may not be included in the RNR and ML elements to avoid link addition storms. The new AP may send beacons and respond to probe requests. Additionally, the validity interval field of the BTM request may signal multiple TBTTs until the new AP is added to all beacons.

[0178] In some embodiments, a BTM request may indicate AP MLD / BSS termination. In some embodiments, a BTM request may signal the Include BSS Termination field to notify the transmitting AP that it is shutting down. Therefore, when an AP MLD transmits a BTM request with this field set to 1, the APs in the AP MLD may shut down. Additionally, the Include AP MLD Termination field set to a value of 1 may signal that the AP MLD and all its APs will shut down.

[0179] In some embodiments, the non-AP MLD may respond to the BTM request via a BTM response. In the BTM response, the non-AP MLD may indicate acceptance or rejection of the BTM request. In some embodiments, the BTM response does not terminate and / or perform an APMLD handover. In other words, link addition / fast MLD handover / link deletion signaling may require separate signaling.

[0180] In some embodiments, the AP MLD may send a BTM request indicating AP termination to all non-AP MLDs that have links with the terminating AP / BSS and all non-AP STAs that may be associated with the terminating AP / BSS. The AP MLD may receive responses from all associated non-AP STAs and from all non-AP MLDs that have links with the AP / BSS before it terminates the AP / BSS.

[0181] In some embodiments, the AP MLD may signal, for example, in a beacon frame, that the AP in the AP MLD is shutting down. The AP MLD may signal that the AP / BSS will be terminated for a long duration, multiple DTIM beacon intervals, or a beacon interval. The AP may signal the AP termination for at least the longest listen interval of all associated STAs and non-AP MLDs. STAs and / or non-AP MLDs may receive at least one beacon within their listen intervals. The listen interval value may typically be signaled in an associated manner. For example, if the AP has links with many STAs attached to non-AP MLDs, and unicast BTM request / response signaling would result in high signaling overhead, a broadcast termination indication may be useful.

[0182] In some embodiments, different frequency bands may have different minimum durations for the AP / BSS. For example, the UNII-2 band in 5 GHz may signal the BSS to terminate for a shorter period of time. This time may be similar to the duration of the channel switch notification when radar is detected in the band.

[0183] In some embodiments, the beacon transmission mode may define a minimum time that the AP needs to signal the BSS to terminate the duration. For example, if the BSS is transmitting in a hidden or encrypted mode, the minimum duration for signaling the AP to terminate may be shorter than in the default / legacy beacon mode.

[0184] In some embodiments, the AP may transmit a broadcast BTM request frame to signal that the AP / BS in the AP MLD will be terminated. This signaling can be understood by legacy STAs. Note that if a STA receives such a broadcast BTM request but wishes to continue operating in the AP (e.g., objecting to AP termination), the STA may send a unicast BTM response with a status code of "Reject" for AP termination. Furthermore, if AP termination is acceptable to a non-AP MLD, it may send a Link Delete message to terminate the link and / or a unicast BTM response with a status code of "Accept" or "Do Nothing."

[0185] In some embodiments, the AP may be terminated earlier, for example, if the AP does not have any associated STAs or links to the AP MLD. This may occur if all non-AP MLDs delete their links to the AP and legacy STAs disassociate from the AP.

[0186] In some embodiments, the AP MLD may be sent in a beacon frame and send a unicast and / or broadcast BTM request message to signal that it is terminating the AP / BSS. In some embodiments, the AP may perform both signalings in parallel to ensure that the STA does not miss the AP termination indication.

[0187] In some embodiments, for example, if a non-AP MLD is unaware of available APs in the AP MLD and / or if the non-AP MLD wishes to query the network for recommended APs and / or AP MLDs for a STA, the non-AP MLD may transmit a BTM Query frame. For example, if the non-AP MLD is interested in operating with the responding AP MLD, the non-AP MLD may also send an ML Query Request. In other words, if the non-AP MLD does not wish to change its association with another AP or AP-MLD, the non-AP MLD may also send an ML Query Request. The AP MLD may respond with an ML Query Response containing information similar to the BTM Request described above. The AP may not provide all information to all requesting STAs. For example, if the AP MLD does not want the non-AP MLD to know about some of its APs, it may not provide information associated with those APs. The content of the AP ML Query Response may also change over time.

[0188] In some embodiments, the AP MLD may send a BTM request to a specific non-AP MLD and request link termination. Unless the non-AP MLD terminates the link to the AP, the AP may use the To Be Disassociated field to signal that all non-AP MLDs are to be disassociated.

[0189] In some embodiments, the AP may send unicast link termination signaling to the STA to indicate that it has terminated the non-APMLD link. After this indication, the STA may need to add the link or associate with the link in order to use the link to transmit or receive data.

[0190] In some embodiments, the AP may transmit a BTM request to the STA to request that the STA operate on another link and / or the AP may terminate a particular link, for example, if the STA's link performance on that link is very poor (e.g., poor transmission rate, the AP may not receive acknowledgments for its transmitted DL frames, the STA needs to retransmit its frames multiple times, etc.). Alternatively, the AP may terminate a link that uses a significant amount (e.g., a majority) of the transmission time from the STA. For example, a non-AP MLD transmits all of its traffic in 2.4 GHz and does not use the 5 GHz link, which has a much higher transmission capacity.

[0191] In some embodiments, BTM queries may be used to add new APs and / or request new APs. For example, Figure 19 An example of signaling for adding a new AP and / or requesting a new AP using a BTM query is shown according to some embodiments. Figure 19 The signaling shown in the figure can also be used with any of the systems, methods, or devices shown in the figure. In various embodiments, some of the signaling shown can be executed concurrently in an order different from the order shown, or can be omitted. Additional signaling can also be performed as needed. As shown in the figure, the signaling can adopt the following process.

[0192] As shown, STA 606a may associate with AP 612a via signaling 1902, e.g., as described herein. Note that STA 606b may not be associated, and AP 612b may not be operational. STA 606a (e.g., an associated non-AP STA / MLD) may send a BTM query frame 1904 to AP 612a to propose that AP MLD 614 add a new AP (e.g., AP 612b) on a particular channel. BTM query frame 1904 may include an indication of adding a new AP and candidate BSSs. In some embodiments, BTM query frame 1904 may include a request mode field, with the New AP to Add field set to a value of 1 to indicate a request for new AP creation. In some embodiments, STA 606a (e.g., a non-AP MLD) may create an AP and provide its parameters to the STA / non-AP MLD (e.g., AP 612a). AP 612a may send a Start New AP Request 1906 to AP 612b, including the AP MLD parameters, in the AP MLD. AP 612b may send a New AP Create Response 1908 to AP 612a, including the AP MLD parameters. AP 612a may then send a BTM Request 1910 to STA 606a. BTM Request 1910 may include a candidate BSS list that includes AP 612b. STA 606a may send a BTM Response 1912 indicating successful receipt of the BTM Request. STA 606a may then send an Add Link Request 1914 to request the addition of a link between STA 606b and AP 612b. AP 612a may send an Add Link Response 1916 to indicate the addition of a link between STA 606b and AP 612b. At 1918, the link may be added. The STA 602b may then send data (eg, MPDU) 1920 to the AP 612b, and the AP 612b may send an acknowledgment 1922 to the STA 606b.

[0193] In some embodiments, non-AP MLD can delete a link between a STA and an AP. For example, non-AP MLD can delete a link by sending a robust delete link frame to the AP. Note that when a link is deleted, it cannot be used to send data, and non-AP MLD does not maintain link-specific keys and / or parameters.

[0194] Figure 20 A block diagram illustrating an example of a method for performing secure multi-link scanning according to some embodiments is shown. Figure 20The method shown can be used in conjunction with any system, method or device shown in the figure and other devices. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0195] At 2002, a wireless station or wireless device, such as wireless station 106, may associate with an access point, such as access point 112. The access point may be included in and / or associated with a multi-link device (MLD).

[0196] At 2004, the wireless station may transmit a robust query request to the access point. Note that, as used herein, the adjective "robust" may refer to a type of wireless communication that can withstand intentional or accidental interference, such as technical failures, signal interference, and / or security threats. Thus, a robust query request may be considered a query request that can withstand intentional or accidental interference, such as technical failures, signal interference, and / or security threats. In some cases, the robust query request may query available access points within the MLD and / or parameters associated with the MLD.

[0197] At 2006, the wireless station may receive a robust query response from the access point. Note that a robust query response can be considered a query request that can withstand intentional or accidental interference (such as technical failures, signal interference, and / or security threats). In some cases, the robust query response may include an integrity-protected broadcast probe response. The integrity-protected broadcast probe response may include a medium access control (MAC) management encapsulation element (MME). The MME may include at least one of the following (e.g., any combination of the following, including one or more and / or all of the following): an element identifier (ID), a length field, a key ID field, a beacon integrity packet number (BIPN) field, a probe response integrity packet number (PRPN) field, and / or a message integrity check (MIC) field. In some cases, the robust query response may use a transient key and / or packet number for authentication. For example, the robust query response may use a beacon integrity group transient key (BIGTK) for authentication. In such cases, the BIGTK may also be used for beacon integrity authentication. As another example, the robust query response may use a beacon integrity packet number (BIPN). In such cases, the BIPN may also be used for beacon integrity authentication. As another example, the robust query response may use a probe response integrity packet number (PRPN). In such cases, the PRPN may be derived from the PRPN used for the beacon.

[0198] In some cases, the wireless station may calculate an integrity checksum for the entire robust query response. In such cases, the timestamp field included in the robust query response may be masked before calculating the integrity checksum, eg, may not be included in the integrity checksum.

[0199] Figure 21 A block diagram illustrating an example of a method for providing a group temporary key (GTK) for a new link according to some embodiments is shown. Figure 21 The method shown can be used in conjunction with any system, method or device shown in the figure and other devices. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0200] At 2102, a wireless station or wireless device, such as wireless station 106, may associate with an access point, such as access point 112. The access point may be included in and / or associated with a multi-link device (MLD).

[0201] At 2104, the wireless station may transmit an add link request to the access point. The add link request may request that a new link be added between the wireless station and the access point. The add link request may be and / or may include a robust add link request. Note that, as used herein, the adjective "robust" may refer to and / or describe a type of wireless communication that can withstand intentional or accidental interference, such as technical failures, signal interference, and / or security threats. Thus, a robust add link request may be considered an add link request that can withstand intentional or accidental interference, such as technical failures, signal interference, and / or security threats. In some cases, the add link request may include a set of non-access point station (e.g., a group of wireless stations) parameters and a set of access point parameters. In some cases, the add link request may include a power mode (PM) for the new link. In some cases, the add link request may include a multi-link attribute. The multi-link attribute may specify whether the wireless station can transmit / receive on multiple links simultaneously.

[0202] At 2106, the wireless station may establish security for the new link with the access point, including one or more of the following (e.g., any combination of the following, including at least one and / or all of the following): a Beacon Integrity GTK (BIGTK) Security Architecture (BIGTKSA), an Integrity GTK Security Architecture (IGTKSA), a GTK Security Architecture (GTKSA), or a Peer Transient Key (PTK) Security Architecture (PTKSA) for the new link being added. The add link response may be and / or may include a robust add link response. Note that, as used herein, the adjective "robust" may refer to and / or describe a type of wireless communication that can withstand intentional or accidental interference, such as technical failures, signal interference, and / or security threats. Thus, a robust add link response may be considered an add link response that can withstand intentional or accidental interference, such as technical failures, signal interference, and / or security threats. In some cases, the add link response may indicate that a new link between the wireless station and the access point will be added.

[0203] In some cases, to establish security for a new link with an access point, the wireless station may perform a 4-way handshake procedure with the access point. In some cases, to establish security for a new link with an access point, the wireless station may transmit a robust reassociation request to the access point and may receive a robust reassociation response from the access point. In some cases, to establish security for a new link with an access point, the wireless station may transmit an authentication request to the access point and may receive an authentication response from the access point.

[0204] Figure 22 A block diagram illustrating an example of a method for randomizing a media access control (MAC) address of a wireless station according to some embodiments. Figure 22 The method shown in the figure can also be used together with any one of the systems, methods or devices shown in the figure. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0205] At 2202, a wireless station or wireless device, such as wireless station 106, may associate with an access point, such as access point 112. The access point may be included in and / or associated with a multi-link device (MLD).

[0206] At 2204, the wireless station may transmit an add link request to the access point. The add link request may indicate a MAC address associated with the link, a new MLD MAC address sequence number offset, and an updated timing synchronization function (TSF) for the MAC address. The add link request may be and / or may include a robust add link request. It should be noted that, as used herein, the adjective "robust" may refer to and / or describe a type of wireless communication that can withstand intentional or accidental interference (such as technical failures, signal interference, and / or security threats). Therefore, a robust add link request may be considered to be an add link request that can withstand intentional or accidental interference (such as technical failures, signal interference, and / or security threats). In some cases, the add link request may indicate an uplink traffic identifier (ID) and a downlink traffic ID. In some cases, the sequence number offset may be randomized.

[0207] In some cases, the wireless station may receive an add link response from the access point. The add link response may indicate a MAC address associated with the link, a new MLD MAC address sequence number offset, and an updated TSF for the MAC address. The add link response may be and / or include a robust add link response. Note that, as used herein, the adjective "robust" may refer to and / or describe a type of wireless communication that can withstand intentional or accidental interference, such as technical failures, signal interference, and / or security threats. Thus, a robust add link response may be considered an add link response that can withstand intentional or accidental interference, such as technical failures, signal interference, and / or security threats.

[0208] Figure 23 A block diagram illustrating an example of a method for selecting a sequence number offset for one or more sequence number spaces during an MLD parameter change, according to some embodiments. Figure 23 The method shown can be used in conjunction with any system, method or device shown in the figure and other devices. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0209] At 2302, an access point (such as access point 112) may receive a MAC protocol data unit (PDU) from a wireless station (such as wireless station 106) over a link with the wireless station (eg, a non-AP MLD).

[0210] At 2304, the access point may determine whether the parameters associated with the MAC PDU are parameters used before the parameter change time or parameters used after the parameter change time.

[0211] At 2306, in response to determining that the parameter is a parameter used before the parameter change time, the access point may determine whether the MAC PDU is transmitted during a tolerance period associated with the parameter change time.

[0212] At 2308, in response to determining that the MAC PDU was transmitted during the tolerance period, the access point may determine a sequence number of the MAC PDU using a sequence number offset associated with the parameters used prior to the parameter change time.

[0213] In some cases, in response to determining that the MAC PDU was transmitted after the tolerance period, the access point may discard the MAC PDU. In some cases, in response to determining that the parameter is a parameter used after the parameter change time, the access point may determine the sequence number of the MAC PDU using a sequence number offset associated with the parameter used after the parameter change time.

[0214] Figure 24 and Figure 25 A block diagram illustrating an example of a method of operating an access point of an MLD according to some embodiments. Figure 24 and Figure 25 The method shown can be used in conjunction with any system, method or device shown in the figure and other equipment. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed.

[0215] Go to Figure 24 , as shown in the figure, the method can be operated as follows.

[0216] At 2402, an access point (such as access point 112) may determine (e.g., based on a desired discoverability level and / or a desired beacon mode) to operate in one of a plurality of operating modes. For example, in a first operating mode, the access point may be discoverable via any link of the MLD. As another example, in a second operating mode, the access point may be discoverable only on its primary channel. As another example, in a third operating mode, the access point may be visible only to selected wireless stations that know the access point's beacon encryption key. As yet another example, in a fourth operating mode, the access point may switch to a shutdown phase and securely shut down the link.

[0217] At 2404, the access point may operate in a determined operating mode among a plurality of operating modes.

[0218] Go to Figure 25 , as shown in the figure, the method can be operated as follows.

[0219] At 2502, an access point (such as access point 112) may determine (e.g., based on a desired discoverability level and / or a desired operating mode) to operate in one of a plurality of beacon modes. For example, in a first beacon mode, the access point may be discoverable via any link of the MLD. As another example, in a second beacon mode, the access point may be discoverable only on its primary channel. As another example, in a third beacon mode, the access point may be visible only to selected wireless stations that know the access point's beacon encryption key. As yet another example, in a fourth beacon mode, the access point may switch to a shutdown phase and securely shut down the link.

[0220] At 2504, the access point may operate in a determined beacon mode among a plurality of beacon modes.

[0221] Figure 26 A block diagram illustrating an example of a method for adding a new access point to an MLD using a Basic Service Set (BSS) Handover Management (BTM) query, according to some embodiments. Figure 26 The method shown can be used in conjunction with any system, method or device shown in the figure and other devices. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown in the figure, the method can be operated as follows.

[0222] At 2602, an access point, such as access point 112, may associate with a wireless station. The access point may be included in a multi-link device (MLD).

[0223] At 2604, the access point may receive a BTM query from the wireless station. The BTM query may propose to add a second access point to the MLD.

[0224] At 2606, the access point may send (or transmit) a Start New AP in an Access Point (AP) MLD Request to the second access point.

[0225] At 2608, the access point may receive a new AP creation response from the second access point.

[0226] At 2610, the access point may send (or transmit) a BTM request including a candidate BSS list to the wireless station. The candidate BSS list may include the second access point.

[0227] In some cases, the access point may receive an add link request from the wireless device and may send (or transmit) an add link response to the wireless device. The add link response may indicate adding a link to the second access point.

[0228] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

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

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

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

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

Claims

1. A method for multi-link scanning, comprising: Wireless Station, Associating with an access point, wherein the access point is included in a multi-link device MLD; transmitting a robust query request to the access point; and receiving a robust query response from the access point, wherein the robust query response indicates available access points within the MLD and parameters associated with the MLD; transmitting a robust add link request to the access point, the robust add link request indicating a new MLD media access control MAC address sequence number offset, wherein the robust add link request also indicates a MAC address associated with the link and an updated timing synchronization function (TSF) for the MAC address; and A robust add link response is received from the access point, the robust add link response indicating the new MLD MAC address sequence number offset, wherein the robust add link response also indicates the MAC address associated with the link and the updated TSF for the MAC address.

2. The method according to claim 1, The robust query response comprises an integrity-protected broadcast probe response, and the integrity-protected broadcast probe response comprises a medium access control (MAC) management encapsulation element (MME).

3. The method according to claim 2, in, The MME includes at least one of an element identifier ID, a length field, a key ID field, a beacon integrity packet number BIPN field, a probe response integrity packet number PRPN field, or a message integrity check MIC field.

4. The method according to any one of claims 1 to 3, further comprising: The wireless station, An integrity checksum of the robust query response is calculated, wherein a timestamp field included in the robust query response is masked before calculating the integrity checksum.

5. The method according to any one of claims 1 to 3, The robust query response uses at least one of a temporary key or a group number for authentication.

6. The method according to claim 5, The temporary keys include a beacon integrity group temporary key BIGTK, and the BIGTK is further used for beacon integrity verification.

7. The method according to claim 5, The packet number includes a beacon integrity packet number BIPN additionally used for beacons or a probe response integrity packet number PRPN different from a probe response integrity packet number PRPN used for beacons.

8. The method according to any one of claims 1, 2, 3, 6 or 7, The robust query request queries the available access points in the MLD and parameters associated with the MLD.

9. The method according to any one of claims 1, 2, 3, 6 or 7, further comprising: The wireless station, transmitting, to the access point, an add link request for adding a new link between the wireless station and the access point; receiving an add link response from the access point; as well as Establishing security for the new link with the access point.

10. The method according to claim 9, The security of the new link includes one or more of the following: Beacon Integrity GTK BIGTK Security Architecture BIGTKSA, Integrity GTK Security Architecture IGTKSA, GTK Security Architecture GTKSA, or Peer Transient Key PTK Security Architecture PTKSA for the new link.

11. The method according to claim 9, wherein the add link request comprises a robust add link request, wherein the add link request comprises one or more of: a set of non-access point site parameters and a set of access point parameters; a power mode PM for the new link; or A multilink attribute that specifies whether the wireless station can transmit / receive on multiple links simultaneously.

12. The method according to claim 9, wherein said adding a link response comprises a robust adding a link response; and The add link response indicates that the new link between the wireless station and the access point will be added.

13. The method according to claim 9, Wherein establishing security of the new link with the access point includes the wireless station performing at least one of the following: 4-way handshake process with the access point; a robust reassociation process; or Modified Fast MLD Handover Signaling Procedure.

14. The method according to claim 13, The robust reassociation process includes the wireless station: transmitting a robust reassociation request to the access point; and A robust reassociation response is received from the access point.

15. The method according to any one of claims 13 to 14, The modified fast MLD handover signaling process includes the wireless station: transmitting an authentication request to the access point; and An authentication response is received from the access point.

16. The method according to any one of claims 1, 2, 3, 6, 7, 10, 11, 12 or 13, The add link request further indicates an uplink traffic identifier ID and a downlink traffic ID.

17. The method according to any one of claims 1, 2, 3, 6, 7, 10, 11, 12 or 13, The sequence number offset is randomized.

18. A wireless station comprising: one or more processors; as well as A memory having stored thereon instructions which, when executed by the one or more processors, perform the steps of the method according to any one of claims 1 to 17.

19. A computer program product comprising computer instructions which, when executed by one or more processors, perform the steps of the method according to any one of claims 1 to 17.

Images