Multi-Access Point Association

Abstract

To provide systems, apparatuses and methods for devices for multi-access point association in a wireless local area network architecture.SOLUTION: This disclosure relates to methods for multi-access point association in a WLAN. Multiple access point wireless devices establish a multi-access point system. Other access point wireless devices join the multi-access point system. Non-access point wireless devices form association with the multi-access point system by linking to multiple different access point wireless devices in the multi-access point system.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] This application relates to wireless communications, including techniques and devices for multi-access point association in wireless local area network architectures. [Background technology]

[0002] 2. Description of the Related Art The use of wireless communication systems is growing rapidly. Furthermore, wireless communication technology has evolved from voice-only communications to also include the transmission of data, such as Internet and multimedia content.

[0003] A mobile electronic device or user equipment device (UE) may take the form of a smartphone or tablet typically carried by a user. One aspect of wireless communication that may be typically performed by a UE may include wireless networking over a wireless local area network (WLAN), which may include devices operating according to one or more communication standards, for example, the IEEE 802.11 family of standards. Although a UE may be capable of transitioning between access points in such a system, such transitions between access points in a WLAN configuration may involve signaling overhead and delays in data communication, as well as possible failures or ping-ponging between access points, which may further interrupt data communication. Thus, improvements in this area are desirable. Summary of the Invention

[0004] Among other things, embodiments of a system, apparatus, and method for devices for multi-access point association in a wireless local area network architecture are presented herein.

[0005] The wireless device may include one or more antennas, one or more radios operably coupled to the one or more antennas, and a processor operably coupled to the one or more radios. The wireless device may be configured to establish a connection with an access point through a wireless local area network (WLAN) over one or more wireless links, or may be an access point configured to establish a connection with one or more other wireless devices through a WLAN over one or more wireless links. The wireless device may operate in each of multiple wireless links using a separate one of the one or more radios.

[0006] According to the techniques described herein, access point wireless devices can perform discovery and join together to form a multi-access point system. Non-access point wireless devices joining the multi-access point system may be capable of forming simultaneous associations with multiple access point wireless devices in the system, which, according to at least some embodiments, can help reduce delays and overhead from transitioning between access point wireless devices in the system and / or support improved reliability and performance in the system.

[0007] The techniques described herein may be implemented in and / or used in conjunction with many different types of devices, including, but not limited to, cellular telephones, tablet computers, accessory and / or wearable computing devices, portable media players, cellular base stations and other cellular network infrastructure equipment, servers, unmanned aerial vehicles, unmanned flight controllers, automobiles and / or powered vehicles, and any of a variety of other computing devices.

[0008] This Summary is intended to provide a brief overview of some of the subject matter described in this document. It should therefore be understood that the above features are merely examples and should not be construed as narrowing the scope or spirit of the subject matter described herein. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, drawings, and claims. [Brief description of the drawings]

[0009] The subject matter of the present invention can be better understood when the following detailed description of the embodiments is considered in conjunction with the following drawings, in which:

[0010] [Figure 1] 1 illustrates an exemplary wireless communication system including a user equipment device (UE) according to some embodiments.

[0011] [Diagram 2] 1 is a block diagram illustrating an example UE according to some embodiments.

[0012] [Diagram 3] 1 is a block diagram illustrating an exemplary network element or access point according to some embodiments.

[0013] [Figure 4] 1 is a flow chart diagram illustrating an example method for supporting multi-access point (MAP) association in a wireless local area network according to some embodiments. [Diagram 5] 1 is a flow chart diagram illustrating an example method for supporting multi-access point (MAP) association in a wireless local area network according to some embodiments.

[0014] [Figure 6] 1 is a flow chart diagram illustrating example signaling aspects of possible fast BSS transition according to some embodiments.

[0015] [Figure 7] 1 illustrates example aspects of possible scenarios in which a wireless device may associate with a multi-access point system, according to some embodiments.

[0016] [Figure 8] 1 illustrates aspects of an example extended service set and mobility domain deployment scenario in which one or more MAP APs may be deployed, according to some embodiments.

[0017] [Figure 9] 1 is a table comparing various features of different Wi-Fi generations according to one possible evolution.

[0018] [Figure 10] 1 illustrates aspects of an exemplary link switching scenario in a MAP system in a post-association state, according to some embodiments.

[0019] [Figure 11] 1 illustrates aspects of an example link switching scenario in which multiple AP Multi-Link Devices (MLDs) in an AP MAP are at the coverage edge of a non-AP MAP, according to some embodiments.

[0020] [Figure 12] 1 is a table illustrating examples of possible link operation modes that may be used for a MAP system, according to some embodiments.

[0021] [Figure 13] 1 illustrates an example aspect of a possible AP MAP architecture according to some embodiments.

[0022] [Figure 14] 1 illustrates aspects of an example MAP system capable of implementing multiple downlink frame transmission buffering and uplink frame reordering buffering options according to some embodiments.

[0023] [Figure 15] 1 illustrates an example aspect of a possible non-AP MAP architecture, according to some embodiments.

[0024] [Figure 16] 1 illustrates further exemplary aspects of a possible MAP system architecture according to some embodiments.

[0025] [Figure 17] 1 illustrates an example aspect of an alternative system architecture with mobility domain extension according to some embodiments.

[0026] [Figure 18] 1 illustrates an example aspect of a possible extended service set in which such a mobility domain extension may be deployed, according to some embodiments.

[0027] [Figure 19] 1 illustrates an example aspect of a possible initiation operation of a new AP MLD joining AP MAP according to some embodiments. [Figure 20] 1 illustrates an example aspect of a possible initiation operation of a new AP MLD joining AP MAP according to some embodiments.

[0028] [Figure 21] 1 illustrates an example aspect of a possible easy mesh AP MAP network backbone deployment according to some embodiments.

[0029] [Figure 22] 1 illustrates an example embodiment of a possible NAN topology that can be used for a MAP system, according to some embodiments.

[0030] [Diagram 23] 4 is a signal flow diagram illustrating examples of possible AP MAP discovery and association features according to some embodiments.

[0031] [Figure 24-01] 1 is an exemplary signal flow diagram illustrating possible association process features for an AP MAP according to some embodiments. [Figure 24-02] 1 is an exemplary signal flow diagram illustrating possible association process features for an AP MAP according to some embodiments.

[0032] [Diagram 25] 1 illustrates further example aspects and features of possible AP MLD transitions within a multi-AP association, according to some embodiments.

[0033] [Figure 26] 1 illustrates an example of a possible signal flow for adding a link to a MAP association according to some embodiments.

[0034] [Figure 27] 1 illustrates an example scenario illustrating various possible TID-to-link mapping features for MLD management according to some embodiments.

[0035] [Figure 28] 1 is a table illustrating examples of possible features for TID-to-link mapping in a MAP association, according to some embodiments.

[0036] [Figure 29] 1 illustrates aspects of example scenarios in which a roaming TID mapping mode may be used, according to some embodiments.

[0037] [Diagram 30] 13 illustrates further examples of possible features for an AP MAP implementation in roaming mode, according to some embodiments. [Diagram 31] 13 illustrates further examples of possible features for an AP MAP implementation in roaming mode, according to some embodiments.

[0038] [Diagram 32] 1 illustrates example aspects of possible multi-AP operation modes according to some embodiments.

[0039] [Diagram 33] 1 illustrates example aspects of possible power management usage in conjunction with MAP association, according to some embodiments.

[0040] [Diagram 34] 1 illustrates an example aspect of a possible two-level address hierarchy framework for non-AP STAs in a MAP system, according to some embodiments.

[0041] [Diagram 35] 1 illustrates an example embodiment of a possible fast transition key hierarchy that may be used in a MAP system, according to some embodiments.

[0042] [Diagram 36] 1 illustrates an example embodiment of a possible MAP system including multiple locations where transmit buffer and reordering buffer implementations can occur, according to some embodiments.

[0043] [Figure 37] 1 illustrates further details of possible example scenarios in which the transmit buffer and reordering buffer implementations can be implemented in multiple locations, according to some embodiments. [Figure 38] 1 illustrates further details of possible example scenarios in which the transmit buffer and reordering buffer implementations can be implemented in multiple locations, according to some embodiments.

[0044] [Figure 39] 1 illustrates an exemplary embodiment of a possible data encryption and decryption architecture in a MAP system, according to some embodiments.

[0045] [Diagram 40]1 is a table illustrating examples of possible data transmission flow features within an AP MAP and possible implementation locations for those features, according to some embodiments.

[0046] [Diagram 41] 1 illustrates example aspects of possible frame encryption and decryption alternatives in an AP MAP, according to some embodiments.

[0047] [Diagram 42] 1 is a table illustrating examples of possible sequence number processing rules for such various SN spaces in a MAP system, according to some embodiments.

[0048] [Diagram 43] 1 illustrates example aspects of possible EMLSR operations in MAP association, according to some embodiments.

[0049] [Diagram 44] 1 illustrates examples of possible characteristics of a multi-AP element that can be used to provide information about a MAP system, according to some embodiments.

[0050] [Diagram 45] 1 illustrates example aspects of possible MAP probe request and probe response use cases according to some embodiments.

[0051] [Figure 46] A signal flow diagram showing an example of such possible MAP probe request and probe response signal flows according to some embodiments.

[0052] [Figure 47] 1 is a table illustrating examples of possible variations on information that may be requested / included in a probe request / response according to some embodiments.

[0053] [Figure 48]1 is a table illustrating examples of possible AP MAP signaling aspects in reduced neighbor reporting (RNR), according to some embodiments.

[0054] [Figure 49] 1 illustrates aspects of possible exemplary RNR format options that may be used for an AP MAP, according to some embodiments. [Figure 50] 1 illustrates aspects of possible exemplary RNR format options that may be used for an AP MAP, according to some embodiments.

[0055] 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 described in detail herein. It should be understood, however, that the drawings and detailed description are not intended to limit the invention to the particular forms disclosed, but rather to cover all modifications, equivalents, and alternatives within the spirit and scope of the present subject matter as defined by the appended claims. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0056] Terminology Below are definitions of terms used in this disclosure.

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

[0058] Carrier Medium - memory media as described above, as well as physical transmission media such as a bus, network, and / or other physical transmission medium that carries signals, such as electrical, electromagnetic, or digital signals.

[0059] Programmable Hardware Element - includes a variety of hardware devices with multiple programmable function blocks connected via programmable interconnects. Examples include Field Programmable Gate Arrays (FPGAs), Programmable Logic Devices (PLDs), Field Programmable Object Arrays (FPOAs), and Complex PLDs (CPLDs). Programmable function blocks can range from fine-grained (combinational logic or look-up tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements are also sometimes referred to as "reconfigurable logic."

[0060] 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 any other device or combination of devices. In general, the term "computer system" may be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0061] User Equipment (UE) (or "UE device") - any of various types of computer systems or devices that are mobile or portable and perform wireless communications. Examples of UE devices include mobile phones or smartphones (e.g., iPhone™, Android™ based phones), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices (e.g., smart watches, smart glasses), PDAs, portable Internet devices, music players, data storage devices or other handheld devices, automobiles and / or motor vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), and the like. In general, the term "UE" or "UE device" can be broadly defined to encompass any electronic, computing, and / or telecommunications device (or combination of devices) that is easily carried by a user and capable of wireless communications.

[0062] Wireless Device or Station (STA) - Any of various types of computer systems or devices that perform wireless communications. A wireless device can be portable (or mobile) or may be stationary or fixed to a location. The terms "station" and "STA" are used interchangeably. A UE is an example of a wireless device.

[0063] Communications Device - Any of various types of computer systems or devices that perform communications, which may be wired or wireless. A communications device may be portable (or mobile) or may be stationary or fixed to a particular location. A wireless device is one example of a communications device. A UE is another example of a communications device.

[0064] Base Station or Access Point (AP) - The term "base station" (also referred to as "eNB") has the full scope of its ordinary meaning and includes at least a wireless communication station that is installed at a fixed location and used to communicate as part of a wireless communication system. The term "access point" (or "AP") is used similarly.

[0065] Processing Element (or Processor) - refers to various elements or combinations of elements capable of performing functions within a device, e.g., within a user equipment device or within a network infrastructure device. A processor may include, for example, a processor and associated memory, a circuit such as an application specific integrated circuit (ASIC), a portion or circuitry of an individual processor core, an entire processor core, a processor array, a programmable hardware device such as a field programmable gate array (FPGA), and / or a larger portion of a system including multiple processors, as well as various combinations of any of the foregoing.

[0066] Automatically - refers to an action or operation being performed by a computer system (e.g., software executed by a computer system) or device (e.g., circuit mechanisms, programmable hardware elements, ASICs, etc.) without user input directly specifying or executing the action or operation. Thus, the term "automatically" is in contrast to an operation that is manually performed or specified by a user, where the user provides input to directly perform the operation. An automatic procedure may be initiated by input provided by a user, but the subsequent actions that are performed "automatically" are not specified by the user; that is, they are not performed "manually" with the user specifying 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, selecting radio selections, etc.) is considered to be manually filling out the form, even though the computer system must update the form in response to the user actions. A form may be filled out automatically by a computer system, where the computer system (e.g., software executed by the computer system) analyzes the fields of the form and fills out the form without user input specifying answers to the fields. As noted above, a user can invoke automatic filling of a form, but is not involved in the actual filling of the form (e.g., the user does not manually specify answers in fields, but rather the answers are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions taken by a user.

[0067] Refers to technology based on IEEE 802.11 wireless standards, such as IEEE 802.11-802.11a, 802.11b, 802.11g, 802.11n, 802.11-2012, 802.11ac, 802.11ad, 802.11ax, 802.11ay, 802.11be, and / or other IEEE 802.11 standards. IEEE 802.11 technology is sometimes referred to as "Wi-Fi" or "Wireless Local Area Network (WLAN)" technology.

[0068] Configured to - Various components may be described as "configured to" perform a task. In such contexts, "configured to" is a broad description that generally means "having a structure" to perform a task or tasks during operation. Thus, a component may be configured to perform a task even when the component is not currently performing the task (e.g., a set of conductors may be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, "configured to" may be a broad description of a structure that generally means "having circuitry" to perform a task or tasks during operation. Thus, a component may be configured to perform a task even when the component is not currently on. In general, the circuitry that forms the structure corresponding to "configured to" may include hardware circuitry.

[0069] In the description herein, for convenience, various components may be described as performing a task or tasks. Such descriptions should be construed to include the phrase "configured to." It is expressly intended that the description of a component as being configured to perform one or more tasks does not apply to the interpretation of that component under 35 U.S.C. § 112, sixth paragraph. Figure 1-Figure 2: Wireless communication system

[0070] FIG. 1 illustrates an example of a wireless communication system. It should be noted that FIG. 1 represents one possibility among many, and that the features of the present disclosure may be implemented in any of a variety of systems, as appropriate. For example, the embodiments described herein may be implemented in any type of wireless device. The wireless embodiment described below is one exemplary embodiment.

[0071] As shown, the exemplary wireless communication system includes a cellular base station 102 that communicates over a transmission medium with one or more wireless devices 106A, 106B, etc. The wireless devices 106A and 106B may be user devices and may be referred to herein as “user equipment” (UE), UE, or UE devices.

[0072] The UE 106 may be a device with wireless network connectivity, such as a mobile phone, a handheld device, a wearable device, a computer or tablet, an unmanned aerial vehicle (UAV), an unmanned flight controller (UAC), or virtually any type of wireless device. The UE 106 may include a processor (processing element) configured to execute program instructions stored in a memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or in addition, the UE 106 may include a programmable hardware element, such as a field programmable gate array (FPGA), an integrated circuit, and / or any of a variety of other possible hardware components configured to perform (e.g., individually or in combination) any of the method embodiments described herein, or any portion of any of the method embodiments described herein.

[0073] The base station 102 may be a base transceiver station (BTS) or cell site and may include hardware enabling wireless communication with the UE devices 106A and 106B. The base station 102 may also be equipped to communicate with the network 100 (e.g., a cellular service provider's core network, a telecommunications network such as the public switched telephone network (PSTN), and / or the Internet, among other possibilities). The base station 102 may thus facilitate communication between the UE devices 106 and / or between the UE devices 106 and the network 100. In other implementations, the base station 102 may be configured to provide communication via one or more WLAN protocols, such as 802.11a, b, g, n, ac, ad, ax, ay, be, and / or other 802.11 versions, or one or more other wireless technologies, such as an access point supporting LTE in an unlicensed band (LAA).

[0074] A communication area (or coverage area) of a base station 102 may also be referred to as a “cell.” The base station 102 and the UEs 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs) or wireless communication technologies, such as LTE, LTE-Advanced (LTE-A), 5G NR, Wi-Fi, ultra-wideband (UWB), etc.

[0075] The base station 102 and other similar base stations (not shown) operating according to one or more cellular communication technologies may therefore be provided as a network of cells that can provide continuous or near-continuous overlapping service to UE devices 106A-B and similar devices across a geographic area via one or more cellular communication technologies.

[0076] It should be noted that, at least in some cases, the UE device 106 may be capable of communicating using any of multiple wireless communication technologies. For example, the UE device 106 may be configured to communicate using one or more of LTE, LTE-A, 5G NR, WLAN, Bluetooth, UWB, one or more Global Navigation Satellite Systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H), etc. Other combinations of wireless communication technologies (including three or more wireless communication technologies) are possible. Similarly, in some cases, the UE device 106 may be configured to communicate using only a single wireless communication technology.

[0077] As shown, the exemplary wireless communication system also includes a WLAN access point (AP) 104 that communicates with the wireless device 106B over a transmission medium. The WLAN access point, which may be a Wi-Fi AP, also provides communication connectivity to the network 100. Thus, according to some embodiments, a wireless device may be able to connect to either or both of the base station 102 (or another cellular base station) and the access point 104 (or another access point) in order to access the network 100 at a given time.

[0078] The UEs 106A and 106B may include handheld devices such as smartphones or tablets, wearable devices such as smart watches or smart glasses, and / or any of various types of devices having cellular communication capabilities. For example, one or more of the UEs 106A and 106B may be wireless devices intended for stationary or nomadic deployment, such as appliances, measuring devices, control devices, etc.

[0079] The UE 106B may also be configured to communicate with the UE 106A. For example, the UE 106A and the UE 106B may be capable of performing direct device-to-device (D2D) communication. The D2D communication may be supported by the cellular base station 102 (e.g., the BS 102 may facilitate discovery, among various possible forms of assistant), or may be performed in a manner not supported by the BS 102.

[0080] The UE 106 may include one or more devices or integrated circuits for facilitating wireless communication, potentially including a cellular modem and / or one or more other wireless modems. The wireless modem(s) may include one or more processors (processing elements) and various hardware components as described herein. The UE 106 may perform any of the method embodiments described herein by executing instructions on one or more programmable processors. Alternatively or in addition, the one or more processors may be one or more programmable hardware elements, such as a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other circuitry configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein. The wireless modem(s) described herein may be used in a UE device as defined herein, a wireless device as defined herein, or a communication device as defined herein. The wireless modem(s) described herein may also be used in a base station or other similar network side device.

[0081] The UE 106 may include one or more antennas for communicating using two or more wireless communication protocols or radio access technologies. In some embodiments, the UE device 106 may be configured to communicate using a single shared radio. The shared radio may be coupled to a single antenna or may be coupled to multiple antennas (e.g., for MIMO) to perform wireless communication. Alternatively, the UE device 106 may include two or more radios, each of which may be configured to communicate over a separate wireless link. Other configurations are possible. Figure 2 - Example block diagram of a UE device

[0082] 2 illustrates one possible block diagram of a UE device, such as the UE device 106. In some cases (e.g., in the context of 802.11 communications), the UE device 106 may alternatively be referred to as a station (STA) 106, and in some cases more specifically as a non-AP STA 106. As shown, the UE device 106 may include a system-on-chip (SOC) 300, which may include portions for various purposes. For example, as shown, the SOC 300 may include a processor(s) 302 that may execute program instructions for the UE device 106, and a display circuit 304 that may perform graphics processing and provide display signals to a display 360. The SOC 300 may also include a motion sensing circuit 370 that may detect motion of the UE 106, for example, using a gyroscope, an accelerometer, and / or any of a variety of other motion sensing components. The processor(s) 302 may also be coupled to a memory management unit (MMU) 340, which may be configured to receive addresses from the processor(s) 302 and translate those addresses to locations in memory (e.g., memory 306, read-only memory (ROM) 350, flash memory 310). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor(s) 302.

[0083] As shown, the SOC 300 may be coupled to various other circuits of the UE 106. For example, the UE 106 may include various types of memory (including, e.g., NAND flash 310), a connector interface 320 (e.g., for coupling to a computer system, a dock, a charging station, etc.), a display 360, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, 5G NR, Bluetooth, Wi-Fi, NFC, GPS, UWB, etc.).

[0084] The UE device 106 may include at least one antenna, and in some embodiments multiple antennas 335a and 335b, for performing wireless communications with base stations and / or other devices. For example, the UE device 106 may perform wireless communications using the antennas 335a and 335b. As mentioned above, the UE device 106 may be configured to communicate wirelessly using multiple wireless communication standards or radio access technologies (RATs) in some embodiments.

[0085] The wireless communication circuitry 330 may include Wi-Fi logic 332, a cellular modem 334, and Bluetooth logic 336. The Wi-Fi logic 332 is for enabling the UE device 106 to perform Wi-Fi or other WLAN communications over an 802.11 network. The Bluetooth logic 336 is for enabling the UE device 106 to perform Bluetooth communications. The cellular modem 334 may be a cellular modem capable of performing cellular communications according to one or more cellular communication technologies.

[0086] As described herein, the UE 106 may include hardware and software components for implementing embodiments of the present disclosure. For example, one or more components of the wireless communication circuitry 330 (e.g., Wi-Fi logic 332, cellular modem 334, BT logic 336) of the UE device 106 may be configured to perform some or all of the methods described herein, for example, by a processor executing program instructions stored in a memory medium (e.g., a non-transitory computer-readable memory medium), 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). Figure 3 - Access Point Block Diagram

[0087] FIG. 3 illustrates an example block diagram of an access point (AP) 104, according to some embodiments. In some cases (e.g., in the context of 802.11 communications), the AP 104 may also be referred to as a station (STA), and in some cases more specifically, an AP STA. It should be noted that the AP of FIG. 3 is merely one example of a possible access point. As shown, the AP 104 may include a processor(s) 404 that may execute program instructions for the AP 104. The processor(s) 404 may also be coupled to a memory management unit (MMU) 440, which may be configured to receive addresses from the processor(s) 404 and translate those addresses to locations in memory (e.g., memory 460 and read-only memory (ROM) 450), or other circuits or devices.

[0088] The AP 104 may include at least one network port 470. The network port 470 may be configured to couple to a telephone network to provide multiple devices, such as the UE device 106, access to the telephone network as described above in FIG.

[0089] Network port 470 (or additional network ports) may also or alternatively be configured to couple to a cellular network, for example, of a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 470 may couple to a telephone network through the core network and / or the core network may provide telephone services (e.g., between other UE devices serviced by the cellular service provider).

[0090] The AP 104 may include one or more radios 430A-N, each of which may be coupled to a separate communication chain and at least one antenna 434, possibly multiple antennas. The antenna(s) 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with the UE device 106 / 107 via the radio 430. The antenna(s) 434A-N communicate with their respective radios 430A-N via communication chains 432A-N. The communication chains 432 may be receive chains, transmit chains, or both. The radios 430A-N may be configured to communicate via various wireless communication standards, including, but not limited to, LTE, LTE-A, 5G NR, UWB, Wi-Fi, etc. The UE 104 may be configured to operate in multiple wireless links using one or more radios 430A-N, each radio used to operate in a separate wireless link.

[0091] The AP 104 may be configured to communicate wirelessly using multiple wireless communication standards. In some cases, the AP 104 may include multiple radios, which may enable a network entity to communicate according to multiple wireless communication technologies. For example, in one possibility, the AP 104 may include an LTE or 5G NR radio for performing communication according to LTE, as well as a Wi-Fi radio for performing communication according to Wi-Fi. In such a case, the AP 104 may be capable of operating as both an LTE base station and a Wi-Fi access point. In another possibility, the AP 104 may include a multi-mode radio, which may perform communication according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, 5G NR and LTE, etc.). In yet another possibility, the AP 104 may be configured to operate exclusively as a Wi-Fi access point, for example, without cellular communication capabilities.

[0092] As described further herein below, the AP 104 may include hardware and software components for implementing or supporting the implementation of the features described herein. The processor 404 of the access point 104 may be configured to implement or support some or all of the methods described herein, for example, by executing program instructions stored in a memory medium (e.g., a non-transitory computer-readable memory medium) to operate multiple wireless links using multiple respective radios. Alternatively, the processor 404 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array), or as an ASIC (application specific integrated circuit), or as a combination thereof. Alternatively (or in addition), the processor 404 of the AP 104 may be configured to implement or support some or all of the features described herein in conjunction with one or more of the other components 430, 432, 434, 440, 450, 460, 470. Multi-link communication and multi-AP association over WLAN

[0093] A wireless local area network (WLAN) may utilize multiple links during communication between a wireless station (STA), such as a UE 106 as shown in Figure 2, and a wireless access point (AP), such as the AP 104 as shown in Figure 3, in either or both uplink and downlink communications. The STA may be any of a variety of types of wireless stations, including, but not limited to, a UE 106, a smartphone, a tablet, a personal computer, a smart watch, an accessory device, an unmanned aerial vehicle (UAV), an unmanned aircraft controller (UAC), an automobile, or any other type of wireless device capable of communicating over a WLAN.

[0094] While the 802.11ax standard allows STAs and APs to communicate according to either a 5 GHz link or a 2.4 GHz link, for example, 802.11be may allow STAs and APs to communicate simultaneously over multiple links, potentially including 2.4 GHz, 5 GHz, and / or 6 GHz links, which may, at least in some cases, improve throughput and reduce communication latency. For example, a single connection between a STA and an AP may utilize multiple wireless links, each of which operates within the same or different frequency bands.

[0095] Operating on multiple links can reduce transmission delays because associated APs and STAs can communicate simultaneously on multiple links and perform transmissions over the first available link (e.g., rather than having to wait for a particular link, which may be temporarily congested or otherwise unavailable, to become available). Thus, a single congested link can be prevented from significantly increasing transmission delays, and the duration of transmission delays can be reduced. In addition, multiple link operation introduces power consumption considerations, since STA power consumption can vary depending on the number of spatial streams and the size of the operating bandwidth. Depending on the STA configuration, operation over multiple links can consume more power than operation over a single link.

[0096] Such concepts can be extended to include the possibility for a STA to establish simultaneous wireless links with multiple APs. Supporting multi-AP association can have the further potential benefit of reducing the number of basic service set (BSS) transitions, thereby avoiding at least some communication overhead and delays. In some cases, such features can potentially result in reduced BSS transition failure cases and a lower likelihood of ping-ponging between different APs, for example in scenarios when the link performance of one or more available APs experiences significant variability over time. The embodiments described herein include devices and mechanisms for supporting multi-AP association. Figure 4 - Figure 5 - Flowchart

[0097] 4-5 are flow chart diagrams illustrating a method of using a WLAN to support a multi-access point (AP) system between one or more wireless stations (STAs), such as UE 106, and multiple wireless APs, such as AP 104, according to some embodiments. In various embodiments, some of the method elements illustrated in the figures may be performed simultaneously, may be performed in a different order than that illustrated in the figures, may be replaced by other method elements, or may be omitted. Additional method elements may be performed as desired.

[0098] Aspects of the methods of Figures 4-5 may be performed by a wireless device such as the AP 104 or UE 106 illustrated and described with respect to Figures 1-3, or more generally, in conjunction with, among other things, any of the computer circuits, systems, devices, elements, or components shown in the figures, as appropriate. For example, the processor (and / or other hardware) of such a device may be configured to cause the device to perform any combination of the method elements shown in the figures and / or other method elements.

[0099] It should be noted that, although at least some elements of the methods of Figures 4-5 are described as relating to the use of communication techniques and / or features associated with the IEEE 802.11 specification, such description is not intended to limit the disclosure and aspects of the methods of Figures 4-5 may be used in any suitable wireless communication system, as desired. As shown, the methods may operate as follows.

[0100] One aspect of the method can include mutual AP discovery and formation of a multi-AP system. As part of such discovery, a first access point (AP) wireless device can provide (e.g., via over-the-air transmission) beacon information indicating multi-AP parameters for the first AP wireless device (452). It should be noted that, according to various embodiments, the beacon information for the first AP wireless device can also include AP parameters for the first AP wireless device, and / or any of a variety of other types of information.

[0101] The first AP wireless device may receive (e.g., via over-the-air transmission) beacon information from the second AP wireless device that may indicate multi-AP parameters for the second AP wireless device (454). It should be noted that, according to various embodiments, like the beacon information for the first AP wireless device, the beacon information for the second AP wireless device may also include AP parameters for the second wireless device and / or any of a variety of other types of information.

[0102] The first AP wireless device and the second AP wireless device may establish a multi-AP system with at least the first AP wireless device and the second AP wireless device (456). The multi-AP system may be established based at least in part on multi-AP parameters exchanged in beacon transmissions for the first AP wireless device and the second AP wireless device. For example, the first AP wireless device and the second AP wireless device may perform handshake signaling to negotiate or agree on multi-AP parameters for the multi-AP system. The handshake signaling may include, for example, exchanging a multi-AP creation request and a multi-AP creation response. The multi-AP system establishment may also include mutual authentication and establishment of a pairwise master key (PMK) and / or providing information indicative of APs and / or AP multi-link devices (and their parameters) in the established multi-AP system.

[0103] Once a multi-AP system is established, other AP wireless devices may also perform discovery to determine that a multi-AP system exists and potentially join the multi-AP system. For example, discovery may include receiving beacon information provided by one or more AP wireless devices that have joined the multi-AP system, where the beacon information may include multi-AP system parameter information. An AP wireless device may be capable of transmitting a request to join the multi-AP system (e.g., to an AP wireless device that has received a beacon frame from it that includes the multi-AP system parameter information) and then receiving a response accepting the request to join the multi-AP system. Join signaling to join the multi-AP system may include authentication, key setup, and / or capability signaling, among other possibilities.

[0104] The multi-AP system parameters may be updated after the multi-AP system is initially established. This may include, as one possibility, updating the list of APs and AP multi-link devices that have joined the multi-AP system based on the APs or AP multi-link devices that join the multi-AP system. Additionally or alternatively, any of a variety of other multi-AP parameters may be modified, for example, in a variety of circumstances. In such a case, the updated multi-AP parameters may be provided to the AP wireless devices that have joined the multi-AP system. Those AP wireless devices may then provide the updated multi-AP parameters (e.g., including a different list of APs and / or AP multi-link devices that have joined the multi-AP system and / or other different multi-AP parameters) in beacon information transmitted in beacon frames and / or in other transmissions (e.g., probe response frames, multi-link probe response frames, reduced neighbor report frames, etc.) performed by the AP wireless devices in the multi-AP system.

[0105] A non-AP wireless device may establish a wireless association with an AP wireless device in such a multi-AP system. For example, the non-AP wireless device may establish a first wireless association with a first AP wireless device in the multi-AP system (552). The non-AP wireless device may also establish a second wireless association with a second AP wireless device in the multi-AP system (554). Wireless associations with different AP devices in the multi-AP system may be active simultaneously. In other words, according to at least some embodiments, the non-AP wireless device may not need to release an association with one AP wireless device in the multi-AP system to establish an association with another AP wireless device in the multi-AP system. The non-AP wireless device may be capable of performing wireless data communications with both the first AP wireless device and the second AP wireless device.

[0106] The wireless communication may, according to at least some embodiments, include IEEE 802.11-based wireless communication. Beacon frames and / or wireless links established between devices in a multi-AP system may operate within one or more separate frequency bands (e.g., 2.4 GHz links, 5 GHz links, 6 GHz links, and / or other wireless links).

[0107] Each wireless device operating in a multi-AP system may be assigned a multi-AP address for use by the wireless device in the multi-AP system. Thus, the first AP wireless device, the second AP wireless device, any other AP wireless devices, and any non-AP wireless devices in the system may each determine their individual multi-AP addresses for use for identification within the multi-AP system. Such addresses may be separate from a multi-link device (MLD) level address and / or a STA level address, according to at least some embodiments.

[0108] An AP wireless device in a multi-AP system may provide multi-AP system information about the multi-AP system to non-AP wireless devices in the multi-AP system (or that may potentially join the multi-AP system). Various types and amounts of multi-AP system information may be provided in any or all of one or more beacon frames, probe response frames, multi-link probe response frames, and / or reduced neighbor report frames. For example, the multi-AP system information may include information indicative of all APs in the multi-AP system. Alternatively, the multi-AP system information may include information indicative of a subset of APs in the multi-AP system. For example, an AP wireless device in a multi-AP system may receive a probe request from a non-AP wireless device, and depending on the specificity of the probe request, the AP wireless device may respond with AP information for a corresponding specific subset of APs in the multi-AP system, which may include information at any or all of the AP, AP multi-link device, or multi-AP system levels.

[0109] According to various embodiments, it may be possible to perform traffic identifier (TID)-to-link mapping for non-AP wireless devices in a multi-AP system in any of a variety of ways. At least in some cases, it may be possible that some or all TIDs can be limited to links between non-AP wireless devices and a single AP wireless device in the multi-AP system (e.g., at most one AP per TID). Alternatively, it may be possible that some or all TIDs can be assigned to multiple links across associations between non-AP wireless devices and multiple AP wireless devices in the multi-AP system. Other approaches or modes of operation are also possible.

[0110] In some embodiments, an AP wireless device (e.g., a first AP wireless device, a second AP wireless device, or another AP wireless device) or another wireless device (e.g., a dedicated network controller device) can operate as a network controller for a multi-AP system. The network controller can store various bookkeeping information for various multi-AP associations in the multi-AP system, according to at least some embodiments. For example, for each association in the multi-AP system, the network controller can store any or all of station (STA) and AP parameters for each link for the association, non-AP multi-link device and AP multi-link device parameters for each multi-link device for the association, and / or non-AP multi-access point parameters and AP multi-access point parameters for the association.

[0111] In some cases, the network controller may additionally or alternatively have a role in performing non-AP association with the multi-AP system. For example, when an association request is received from a non-AP wireless device by an AP wireless device in the multi-AP system, the request may be forwarded to the network controller. The network controller may send queries to one or more APs and / or AP multilink devices in the multi-AP system to determine which links are available (e.g., setup). The network controller may also determine whether the link(s) requested in the association request are to be created with the joining AP (potentially including combining responses from APs / AP multilink devices in the system and / or further reducing the link or rejecting the association entirely) and may create an association response that is sent to the non-AP wireless device (e.g., via the AP wireless device that received the association request from the non-AP wireless device).

[0112] In some cases, either or both of downlink data buffering and / or uplink data buffering and reordering for non-AP wireless device data communication in a multi-AP system may be performed by a network controller. Thus, as one possibility, downlink data for non-AP wireless devices in a multi-AP system may be buffered until the downlink data is requested by an AP wireless device in the multi-AP system (e.g., for transmission to an associated non-AP wireless device). As another possibility, uplink data for non-AP wireless devices in a multi-AP system may be received from an AP wireless device in the multi-AP system, and the network controller may, for example, buffer the uplink data for non-AP wireless devices in the multi-AP system and perform uplink data reordering before providing the data onward (e.g., to the Internet or otherwise to a higher layer for processing). Alternatively, either or both of downlink data buffering and / or uplink data buffering and reordering for non-AP wireless devices may be performed in an AP wireless device currently serving the non-AP wireless device in the multi-AP system.

[0113] Similarly, in some embodiments, one or more of downlink frame encryption or uplink frame decryption for non-AP wireless devices in a multi-AP system may be performed by a network controller. For example, in some cases, an encryption block may be co-located with a device that operates a transmit buffer and a decryption block may be co-located with a device that operates a reordering buffer.

[0114] In some cases, a non-AP wireless device may be capable of establishing wireless associations with multiple AP wireless devices in a multi-AP system via control signaling with a single AP wireless device in the multi-AP system. For example, the first wireless association and the second wireless association may be established via control signaling with a first AP device as one possibility. It should be noted that, according to various embodiments, it may be possible for a non-AP wireless device to establish links with multiple AP wireless devices in a multi-AP system when it first forms an association with the multi-AP system, and / or, according to various embodiments, for a non-AP wireless device to establish one or more additional links with an AP wireless device in a multi-AP system after the non-AP wireless device has already associated with the multi-AP system. Once an association has already been established, it may be possible to send a link addition request (which may be sent, for example, to an AP wireless device to which the non-AP wireless device is requesting to add a link, or to another AP wireless device in the multi-AP system, such as an AP wireless device to which the non-AP wireless device has already established one or more links) and then receive a link addition response to form one or more additional links. As mentioned above, in some embodiments, the association request is ultimately processed by a network controller for the multi-AP system, and the signaling may in some embodiments be performed by the first AP device. The link addition request / response may in some embodiments be similarly processed by the network controller for the multi-AP system (e.g., with signaling performed by the AP wireless device receiving the link addition request).

[0115] There may be cases where at least some communication parameters for performing communication between a non-AP wireless device and any AP wireless device in a multi-AP system are unified. For example, as one possibility, unicast frames communicated between a non-AP wireless device and an AP wireless device (such as a first AP wireless device and / or a second AP wireless device) in a multi-AP system may be encrypted using the same Peer-wise Temporal Key (PTK).

[0116] According to at least some embodiments, it may be possible to enable / disable various wireless links between a non-AP wireless device in a multi-AP system and any AP wireless device with which the non-AP wireless device has established a wireless association. In some cases, it may be possible that only a subset of the wireless links between a non-AP wireless device and a single AP wireless device may be active / enabled at any given time. Thus, at one time, one or more links for a first wireless association may be enabled and one or more links for a second wireless association may be disabled, while at another time (e.g., based on wireless device mobility in a multi-AP system as one possibility), one or more links for the first wireless association may be disabled and one or more links for the second wireless association may be enabled. In this example, it may be the case that the wireless device maintains both the first and second wireless associations at both times (e.g., regardless of which link set is enabled / disabled). Because both associations are maintained, link enabling / disabling to transition from one actively used association to another actively used association may be able to dramatically reduce delays, overhead, and risk of association failure, even compared to, for example, high speed basic service set (BSS) transitions where links to only a single physical device are maintained at any given time.

[0117] In some embodiments, it may further be possible for a non-AP wireless device to have links enabled simultaneously with multiple AP wireless devices in a multi-AP system. For example, in such a scenario, a non-AP wireless device may simultaneously enable at least one link for a first wireless association and at least one link for a second wireless association. Thus, the non-AP wireless device may be capable of performing data communications with both the first AP wireless device and the second AP wireless device. Supporting such a configuration may help improve reliability, for example, in coverage edge scenarios, since links with all such devices may be available simultaneously, data may be communicated over both links, and ping-pong transitions between available AP wireless devices may be avoided.

[0118] Multi-AP may support any of a variety of possible power saving features. As one such possibility, it may be possible to put some or all enabled links for a multi-AP association of a non-AP wireless device into a power saving mode. Traffic may not be carried on such links. According to at least some embodiments, since a link may remain enabled while in a power saving mode, a non-AP wireless device and / or a corresponding AP wireless device for such a link may be able to quickly resume use of the link if traffic arrives that was buffered for transmission, for example, due to changing wireless medium conditions (e.g., due to device mobility, as one possibility) and / or for any of a variety of other reasons.

[0119] It should be noted that in some embodiments, the TID-to-link mapping (and potentially, more generally, link enablement) may be separate / independent for the uplink and downlink data transmission directions. Thus, for a non-AP wireless device, among other possibilities, there may be cases where at least one link for a first wireless association and at least one link for a second wireless association are simultaneously enabled in the downlink direction (e.g., one or more downlink TIDs may be mapped to each of these links), but only one or more links for the first association are enabled in the uplink direction (e.g., one or more uplink TIDs may be mapped to these links, but no uplink TIDs are mapped to any links for the second wireless association), or where at least one link for a first wireless association and at least one link for a second wireless association are simultaneously enabled in the uplink direction, but only one or more links for the first association are enabled in the downlink direction.

[0120] In some embodiments, it may be possible that the TID mapping mode used for multi-AP association can affect where certain multi-AP system management operations are performed for the association. For example, in some cases, in the case of a roaming mode where uplink and downlink frames (at least a subset of) can be transmitted on any AP wireless device in the multi-AP system, uplink reordering buffering and downlink transmit buffering may be performed in the network controller. In a TID mapping mode where uplink and downlink frames can be transmitted on a link with only one AP wireless device in the multi-AP system at a time, uplink reordering buffering and downlink transmit buffering may be performed in that AP wireless device. In a TID mapping mode where traffic in one direction can be transmitted on a link with only one AP wireless device in the multi-AP system at a time and traffic in the other direction can be transmitted on a link with any of multiple AP wireless devices in the multi-AP system, a hybrid approach may be used. For example, in the case where uplink frames can be transmitted on any link while downlink frames are restricted to transmission via one AP wireless device, uplink reordering buffering may be performed in the network controller and downlink transmit buffering may be performed in the AP wireless device. It should be noted that other correlations between TID mapping modes and management operation implementation options are possible, and embodiments are envisioned in which the TID mapping mode is not directly tied to other multi-AP system management operations.

[0121] 4-5, it may be possible to establish a multi-AP system in which a wireless device may associate with multiple AP devices of the multi-AP system. Such techniques, according to at least some embodiments, may improve any or all of throughput, reliability, and / or power consumption, among other possible benefits. Figures 6 to 50 and additional information

[0122] 6-50 illustrate and describe further aspects that can be used in conjunction with the methods of FIGS. 4-5, if desired. However, it should be noted that the exemplary details shown in and described with respect to FIGS. 6-50 are not intended to limit the disclosure as a whole, and numerous variations and alternatives to the details provided herein below are possible and should be considered within the scope of the disclosure. Thus, terms such as "must," "necessary," "always," "must," "should," and other similar such terms used in the following examples should be understood as being used in the context of specific exemplary scenarios and embodiments, and not necessarily applicable to all possible scenarios and embodiments within the scope of the disclosure.

[0123] In IEEE 802.11 wireless communication systems, BSS transitions may cause interruptions in data transmission. For example, at least some BSS transition mechanisms may require as many as 30 message transmissions, which may result in delays and overhead. Block Acknowledgements (BAs) may be sent separately for each traffic identifier (TID) and direction (uplink / downlink), stream classification service (SCS) setup, target wake time (TWT) setup, new keys, etc. This may make it difficult to maintain a transmission delay of 5-10 ms for BSS transitions.

[0124] Furthermore, it is possible that a BSS transition may fail. For example, a reassociation request may be rejected by an access point (AP), in which case the transition station (STA) may not have any association. If a link to only a single physical device is maintained, the STA may perform a ping-pong BSS transition between two APs, for example, if the performance of the link fluctuates.

[0125] Supporting multi-AP association may, in some embodiments, reduce the number of BSS transitions performed in an IEEE 802.11 wireless communication system. For example, in at least some embodiments, a residential network having such capability may be able to operate without BSS transitions and / or an enterprise network may be able to operate with a 90% reduction in the number of BSS transitions compared to, for example, a Wi-Fi 7 network.

[0126] FIG. 6 is a flow chart diagram illustrating an example signaling aspect of a possible Fast BSS Transition, according to some embodiments. Fast BSS Transition can reset all existing keys, Block ACK (BA), TWT setup, and SCS stream setup. The STA can start operating from scratch in the new AP. Note that BA setup may require the transmission of about 30 messages and acknowledgments. All of this signaling may add delay before the STA can start transmitting new data. In addition, as mentioned before, if the target AP rejects reassociation signaling from the STA, the STA may not have any association and may not be able to transmit any data, which may add further delay to data transmission.

[0127] As shown, in an exemplary scenario, at 608, the STA 602 may be initially associated with AP1 604 and may be performing a handover to AP2 606. The transition signaling may include a four-way handshake and association. Note that link setup preparation may not be possible in this scenario. At 610, the STA 602 may be associated with AP2 606. After the handover, the STA may set up BA, SCS signaling, and TWT flows. BA may be direction and TID specific. One BA may be set up in a single BA request. SCS and QoS characteristic signaling may aggregate requests for multiple flows. Note that not all BA setups are shown in FIG. 6. Since each direction carrying traffic and user priority (UP) may be set up, two BAs may be set up. * 8 * 2=32 messages and 32 ACKs can be exchanged. At 612, the BA is set up, the SCS stream is set up, the TWT flow is set up, and the transition can be completed.

[0128] To reduce BSS transitions, it may be possible to support STAs that are associated with a group of APs, sometimes referred to as AP Multi-Access Points (AP MAPs). Figure 7 illustrates an example aspect of one such possible scenario, according to some embodiments. As shown, a multi-AP STA (e.g., a single physical device) can have one or more links with one or more AP Multi-Link Devices (MLDs) (e.g., each of which may be a separate physical device operating within a MAP AP).

[0129] STAs can operate in a post-associated state and data transmission can continue without interruption as STAs move within the AP MAP. Multi-AP association can be built on Wi-Fi 7 rules. STA and AP capabilities can be configured per link. Unicast frames can be sent over any link and all links can use the same BA setup and the same Peer-Wise Temporal Key (PTK) (encryption). STAs can receive group data frames from any link. Each AP / link can have a different group key and group frames can have joint sequence numbering. In some embodiments, possible updates to Wi-Fi 7 rules can include non-AP link management rules.

[0130] FIG. 8 illustrates aspects of an exemplary extended service set and mobility domain deployment scenario in which one or more MAP APs may be deployed, according to some embodiments. As illustrated, such an extended service set (ESS) may include one or more APs, potentially including zero or more AP MLDs and zero or more MAP APs. Each MAP AP may include one or more AP MLDs, and each AP MLD may include one or more APs. A MAP STA may be associated with a MAP AP, AP MLD, or AP in an ESS at a time. An ESS may have one or more mobility domains. There may be cases where fast BSS transitions are supported within an AP / AP MLD / AP MAP in a mobility domain.

[0131] FIG. 9 is a table showing a comparison of various features of different Wi-Fi generations with one possible evolution. In the illustrated scenario, the association can define the links and APs to which the STA can transmit data. The unicast data can have the following joint parameters on each link: joint sequence number (SN) and packet number (PN), PTK, and BA. With regard to Enhanced Multi-Link Single Radio (EMLSR) support, it is noted that in at least some embodiments, the MAP can separately define the EMLSR in use for each AP MLD. In the case of TWT, there may be cases where signaling can set up the TWT to any enabled link.

[0132] FIG. 10 illustrates aspects of an exemplary link switching scenario in a post-association state, according to some embodiments. As illustrated, a non-AP MAP ("non-AP MAP 1") moving at a certain speed ("X") may decide to switch links from one AP MLD ("AP MLD 1") in its MAP to another AP MLD ("AP MLD 2") in the same AP MAP. After discovering AP MLD 2, non-AP MAP 1 may create a new link with AP MLD 2. All links may be created in association, or non-AP MAP may add links 4, 5, and 6 using a link addition message via an existing link (e.g., with AP MLD 1). After links 4, 5, 6 are created, non-AP MAP may enable these links 4, 5, 6 with AP MLD 1 and disable links 1, 2, and 3 with AP MLD 1.

[0133] 11 illustrates aspects of an example link switching scenario where multiple AP MLDs in an AP MAP are at the coverage edge of a non-AP MAP, according to some embodiments. In the illustrated scenario, it may be possible to avoid ping-pong transitions since links with multiple AP MLDs in the AP MAP may be available to the non-AP MAP. This may also potentially provide improved reliability and may allow data to be transmitted over both links.

[0134] FIG. 12 is a table showing possible link operation modes that can be used for a MAP system, according to some embodiments. Such operation modes can be used to support the possibility that a STA can create multiple links, but not necessarily operate on all links. Links may be virtual, in which case it is possible that no data may be transmitted on those links. However, links can be quickly changed to be able to carry data frames. In Wi-Fi 7, it may be the case that each setup link is configured for a different mode.

[0135] According to at least some embodiments, there may be a number of potential advantages to reducing the number of handovers in an IEEE 802.11 based wireless communication system. Handover delays may be reduced, resulting in more reliable data transmission delays, and as mentioned above, transitions between AP MAP links may be relatively fast. For non-AP MAPs (e.g., STAs), power savings may be increased, and STAs may receive beacons from multiple APs (e.g., from a larger area) and have less signaling. The best link may be used quickly without setup signaling overhead. Multiple links and operating channels may be available for use, and STAs may operate on the most appropriate channel. STAs may have multiple links available to find an available link for data transmission. It may further be possible that multi-AP association may enable more complex transmission schemes. Association may create encryption keys, AIDs, and configure STA and AP capabilities for each link. Such bookkeeping and information sharing may be a first step toward multi-AP transmission, which may enable multiple APs to transmit or receive simultaneously to or from a STA. The AP may also be able to transmit all traffic more reliably: frames may be forwarded to the sending AP within the AP MAP.

[0136] FIG. 13 illustrates an exemplary aspect of a possible AP MAP architecture, according to some embodiments. As illustrated, a transmission buffer can be maintained at the transmitter side, which can provide downlink frames to a receiver via multiple links between multiple STAs. Frames received at the receiver side via multiple STAs can be provided to a reordering buffer for decoding, duplicate detection, and reordering. Note that, at least in some cases, the approach illustrated in FIG. 13 can be applied to either or both uplink (e.g., from non-AP STAs to AP STAs) or downlink (e.g., from AP STAs to non-AP STAs) transmissions.

[0137] In the case of an AP MAP that includes multiple physical devices (e.g., AP MLDs), it may be useful to identify and set guidelines or requirements for downlink frame transmit buffering (e.g., which device on the AP side should implement downlink frame transmit buffering) and / or uplink frame reordering buffering (e.g., where on the AP side the received uplink frames are reordered). Some possibilities may include a router device (e.g., that may implement an AP MAP function to support the inclusion of multiple physical devices in the AP MAP), or an AP MLD that is closest to the corresponding STA (e.g., in the context of the network architecture). FIG. 14 illustrates an aspect of an example system that may implement any of such possibilities. As shown as "Case 1," the transmit buffer and reordering buffer may be maintained in a router device that may provide downlink data to an AP MLD ("AP MLD 1") for downlink transmission to the STA associated with AP MLD 1 as requested by AP MLD 1. The router device may also obtain uplink data and receive block acknowledgments from the STA via AP MLD 1 so that uplink reordering buffering may be performed at the router device. In "Case 2," the transmit and reordering buffers may be maintained in an AP MLD device ("AP MLD 3") that is a physically separate device from the router. In this case, all downlink data for STAs associated with AP MLD 3 may be immediately delivered to AP MLD 3, which may perform the transmit buffering function. Similarly, AP MLD 3 may perform uplink frame reordering for STAs and may pass already reordered uplink data to the router.

[0138] FIG. 15 illustrates an exemplary aspect of a possible non-AP MAP architecture, according to some embodiments. As previously mentioned, the non-AP MAP may be one physical device. The non-AP MAP may have one or more chips operating in different bands. The chips may implement lower MAC operations, e.g., TXOP acquisition, BA scoreboard, etc. The non-AP MAP layer may implement higher MAC operations. For example, for uplink frames, the higher MAC may assign SN, encrypt, and transmit buffer the frame, while for downlink frames, the higher MAC may decode and reorder and buffer the frame.

[0139] Another possibility is to note that an architecture may implement mobility domain operation supporting multiple associations, as compared to an architecture where association to a MAP AP is supported, for example. Note that according to at least some embodiments, a mobility domain may be different from a multi-AP coverage. It may not be necessary to have the same fast transition device set as the devices in a multi-AP joint link set. A mobility domain may include legacy STAs and MLDs in some embodiments. There may be cases where the AP identifier of the association for association to a multi-AP AP is the multi-AP AP address, while for multiple associations in a mobility domain, the mobility domain ID and AP MLD address(es) may be used. There may be cases where the MAP STA address may be used as the STA identifier, and IP address maintenance and fast BSS transition may be possible within the mobility domain, both for association to a MAP AP and multiple associations in a mobility domain. There may be cases where MAP STAs in a MAP AP system may have joint links. There may be cases where AP MLDs in mobility domain 2 (which may be a mobility domain separate from a fast transition (FT) mobility domain or "mobility domain 1") may have joint links. Fast transition to other devices may be possible in (FT) mobility domain for both association to MAP AP and multiple association in mobility domain. To support association to MAP AP, new MAP AP and MAP STA types may be defined. To support multiple association in mobility domain, it may be necessary that two mobility domains can exist in the same area, including new mobility domain for STAs creating joint links. MAP AP, AP MLD, and legacy AP may all be supported in the architecture framework that supports association to MAP AP.In some cases, only AP MLD may be supported in a new mobility domain for an architecture framework supporting multiple associations in a mobility domain, and legacy and AP MLD may be supported on a FT mobility domain. For an architecture framework supporting association to a MAP AP, no changes to the mobility domain operation may be required and one mobility domain for FT protocols may be deployed. For an architecture framework supporting multiple associations in a mobility domain, a mobility domain for AP MLD that can participate in a multi-AP link may be required as well as a mobility domain for FT transition of legacy STAs.

[0140] FIG. 16 illustrates further exemplary aspects of a possible MAP system architecture, according to some embodiments. As illustrated, there can be multiple identifiers on each of the AP side and STA side at various layers of the system. In addition to the multi-AP association scope between the MAP AP and the MAP STA using the MAP address, the MAP AP may also support Wi-Fi 7 AP MLD level association (e.g., by multi-link association scope using the MLD address) and Wi-Fi 6 single-link association (e.g., by single-link association scope using the AP link address (BSSID)).

[0141] FIG. 17 illustrates an example aspect of an alternative system architecture with mobility domain extension, according to some embodiments. As shown, in the illustrated example architecture, the mobility domain identifier (MDID), which may be a two-octet value defined in 802.11r, may be used as the AP MLD group identifier, which may provide the ability to set up links to all AP MLDs (e.g., those with the same MDID) in the AP MLD group. STAs and APs may continue to have a two-level hierarchy for their MAC addresses. Thus, in addition to mobility domain association scope between a group of MLD APs and STAs using MDIDs, Wi-Fi 7 AP MLD level association (e.g., by multi-link association scope using MLD addresses) and Wi-Fi 6 single-link association (e.g., by single-link association scope using AP link addresses (BSSIDs)) may also be supported in this example scenario.

[0142] FIG. 18 illustrates an example aspect of a possible extended service set in which such mobility domain extensions are deployed, according to some embodiments. An ESS can include one or more APs, zero or more of which may be AP MLDs, and an AP MLD can include one or more APs. As shown, the ESS can include an FT mobility domain ("Mobility Domain 2") in which fast BSS transitions may be possible. The ESS can further include another mobility domain ("Mobility Domain 1") in which link creation may be possible, meaning that a multi-AP STA can be associated with multiple AP MLDs at the same time.

[0143] The following sections include possible similarities and differences in management operations and characteristics between AP MAP operations and AP MLD (e.g., legacy AP) operations, according to some embodiments. In the case of MLME-AP-START (e.g., when a new AP MLD or AP MAP starts), for AP MLD, AP operation parameters can be configured and the AP can start beaconing. AP MAP parameters can be configured and the configured device can scan for available AP MAP, and if a suitable AP MAP is found, the device can become part of the AP MAP. If a suitable AP MAP is not found, the device can establish a new AP MAP. For discovery, the AP (MLD) can send beacons, probe responses, ML probe responses, and reduced neighbor reports to be discoverable. For AP MAP, the AP MAP parameters can be included in existing elements and management frames. For association, the STA (MLD) can associate with the AP (MLD) and the STA and AP parameters can be configured for the setup link. The non-AP MAP can associate with the AP MAP. The STA and AP parameters can be configured for the setup link. In case of authentication and 4-way key exchange, a single PTK can encrypt all unicast frames for both AP MLD and AP MAP operations. Unicast frames can be sent on any link. Group frames may be encrypted by a link-specific key. All group keys can be shared to associated STAs. Adding a link to an association may not be supported for AP MLP, and non-AP MLD may need to re-associate and redo all signaling to add a link to an association. Adding a link to an association may be supported for AP MAP, and non-AP MLD can add a new link to an association without re-association and re-setup of all parameters.In the case of TID-to-link mapping, for AP MLD operation, the STA and AP may configure a link(s) that can carry traffic from the TID. In addition, in the case of AP MAP operation, further TID-to-link mapping modes may be available. For power savings, in both scenarios, the STA may be available on the enabled link by sending a power management (PM) field with a value of 1. In the case of legacy AP operation, fast BSS transition may enable transition between APs and / or AP MLDs. In the case of AP MAP operation, fast BSS transition may enable transition between APs, AP MLDs, and / or AP MAPs.

[0144] 19-20 illustrate exemplary aspects of possible start operations of a new AP MLD joining AP MAP, according to some embodiments. As shown in FIG. 19, the new AP MLD ("AP MLD 2") can be started, including, for example, performing an MLME-START primitive. AP, AP MLD, and AP MAP parameters can be configured for AP MLD 2, and the AP may start sending beacons. AP MLD 2 can perform discovery and join available AP MAP. Signaling to join discovered AP MAP can include authentication, key setup, and capability signaling. The new AP and AP MLD can be added to beacons, probe responses, RNRs, etc. for AP MAP.

[0145] FIG. 20 illustrates a possible MLME-Start signaling flow for discovery and joining of AP1 2002 and AP2 2004 to form AP MAP 1, according to some embodiments. At 2006, the APs are not yet present and are not transmitting beacons. The APs may be started and then can set up the AP MAP that can discover each other and associate with STAs. At 2008, the APs can perform SAE authentication to establish a PMK. After SAE authentication, the MAPs can associate and set up keys in a 4-way handshake that may be similar to 802.11s link setup signaling.

[0146] There may be multiple possible backbone network alternatives to support AP MAP operation. Such a choice of backbone architecture may be left as an implementation choice, according to at least some embodiments. Some such options may include wired backbone, Wi-Fi Easy Mesh, Neighbor Aware Networking (NAN), and / or IEEE 802.11s (MESH). Wired backbone options may include wired Ethernet or fiber connections, which may be outside the scope of the 802.11 specification. In this option, only wired transmissions may be supported in the network backbone, and the 802.11 specification may not define the backbone operation (e.g., it may be left to the device vendor to implement). The Wi-Fi Eash Mesh option, in some embodiments, may have a hierarchical structure with only transmissions to / from the Internet. In this case, the backbone AP may have multiple BSSs, and the ingress AP may host a BSS with an associated egress node similar to the non-AP STAs. The other BSSs may serve end devices (e.g., non-AP STAs). In some embodiments, single user (SU), multi-user (MU), and triggered transmissions may be supported in such a network backbone. MU physical layer protocol data units (PPDUs) or trigger-based (TB) PPDUs may carry frames to the backbone and associated non-AP STAs. It may be the case that the backbone only operates towards APs. Infrastructure BSS features (triggering, TWT, etc.) may be relatively simple to add to the ingress BSS, for example, for the backbone. The NAN option may have a non-hierarchical structure. Any NAN device may communicate with any NAN STA. In this option, it may be the case that the backbone device is a NAN STA. SU transmissions may be supported in such a network backbone.The MAC and PHY supported P2P transmission modes can be targeted to non-AP STA capabilities. In some embodiments, end devices can also get their transmissions through the NAN. The 802.11s options can also have a non-hierarchical structure. A mesh STA can create a mesh link with another mesh STA. Transmissions can be performed over the mesh link. Each STA may be a mesh STA. There may be cases where SU transmissions are supported in such a network backbone. Note that mesh may not currently support features introduced after 802.11ac, so that it may require changes to introduce Wi-Fi 6 and 7 features.

[0147] FIG. 21 illustrates an exemplary aspect of a possible Easy Mesh deployment, according to some embodiments. The Easy Mesh specification may specify onboarding and setup procedures. Support for QoS and transmission may be provided. Eash Mesh may be able to provide a standardized AP-to-AP interface within the AP MAP. It may be possible that the AP MAP internal operation is not defined in the 802.11 specification. There may be cases where a STA is associated with one AP at a time. This AP may manage all UL and DL traffic to this STA. It may be possible that AP-to-AP communication at the same hierarchical level is not supported. Alternatively, support for such communication may be added, according to some embodiments.

[0148] FIG. 22 illustrates an example aspect of a possible NAN topology, according to some embodiments. In at least some embodiments, NAN-enabled STAs can directly participate in backbone operations. This can be useful for D2D link transmissions and Internet transmissions. There may be cases where all NAN devices can communicate directly with each other. The NAN may include support for scheduling signaling for power saving and time division multiple access (TDMA). Triggering support and MU PPDU transmissions may not be supported, at least in some cases, which may increase the latency of forwarded traffic.

[0149] FIG. 23 is a signal flow diagram illustrating possible AP MAP discovery and association features, according to some embodiments. As shown, the signal flow can be performed between a STA 2302 and an AP 2304 in a multi-AP system. Beacon and probe response frames can have a multi-AP element that includes multi-AP parameters and capabilities. Other AP MLD and AP parameters may not be present to reduce overhead. Reduced Neighbor Reports (RNRs) can include available AP MLD and APs that belong to the AP MAP. For a non-AP MAP 2302 to associate with an AP MAP 2304, the non-AP MAP 2302 can signal MLD and MAP parameters and provide STA capabilities for each requested link. The AP MAP 2304 can signal its MLD and MAP parameters and provide AP parameters for each setup link. After successful association, the non-AP MAP 2302 can be associated and have one or more setup links. The 4-way handshake may set up multiple keys, namely, the PTK used on all links in the MAP, as well as link-specific GTK, IGTK, and BIGTK. All keys may be distributed to the STA and AP. One link may carry the association request, association response, and 4-way handshake frames. The link carrying the frame may be included as the setup link. There may be cases where a non-AP MAP cannot operate on all links simultaneously. In some embodiments, a non-AP MAP may choose to operate only on a subset of links. After successful association, the setup link with the AP MLD that delivered the association signaling may be enabled. All TIDs may be mapped with these enabled links. Links with other AP MLDs may be disabled. After association, the STA may be in a power save state for all links except the link that carried the association signaling. The STA may transmit UL frames and receive DL frames on any enabled link.A STA can switch to active mode on an enabled link.

[0150] 24-01 and 24-02 are signal flow diagrams illustrating possible association process features for AP MAP, according to some embodiments. As shown, the signal flow can be performed between STA1 2402 in the non-AP MAP, AP1 2404 in the AP MAP, AP MLD1 2406 in the AP MAP, AP MLD2 2408 in the AP MAP, controller 2410 in the AP MAP, and authenticator 2412 in the AP MAP. At 2414, the non-AP MAP can authenticate and associate with the AP MAP, which can include AP MAP internal signaling to perform authentication with an authentication server. At 2416, the non-AP MAP authentication can be successful, and the authenticator can configure the network controller to enable link creation with the non-AP MAP. As shown, the association request frame provided by STA1 2402 to AP1 2404 can be forwarded to the network controller 2410. At 2418, the non-AP MAP can request the creation of multiple links. The network controller can determine whether links can be created and can signal the AP MLD in the AP MAP to indicate the STA parameters and the created links. The network controller can organize a query to the AP MLD to clarify which links are being set up. The AP MLD can determine whether the requested links are created with its subscribing AP. The AP MLD can send a response to the AP MAP query. The network controller can combine the responses from the AP MLD, possibly further reduce the links or deny the association, and can create an association response that is sent to the STA.

[0151] Associations, established links, and STA parameters for links may require specific bookkeeping. Each device in the AP MAP (AP MLD and AP) may maintain parameters related to its operation. The AP MAP / network controller may have a database that stores all non-AP MAP parameters. As an example, in some embodiments, as part of the bookkeeping for all non-AP MAP associations, the AP MAP (network controller) may store, for each MAP association, the STA and AP parameters for each link, the non-AP MLD and AP MLD parameters to each MLD, and the AP MAP and non-AP MAP parameters. As part of the bookkeeping of non-AP MAP parameters related to the AP MLD, the AP MLD may store the STA and AP parameters for each link of the AP MLD, the non-AP MLD and AP MLD parameters for the association, and the AP MAP parameters related to the AP MLD. As part of the bookkeeping for link-specific STA parameters, the AP may store the AP MLD settings for the AP MLD to which the STA belongs.

[0152] FIG. 25 illustrates further aspects and features of possible AP MLD transitions in a multi-AP association, according to some embodiments. In the illustrated scenario, AP MAP 1 may have a restriction that allows a non-AP MAP device to operate with only one AP MLD at a time, but in some cases, it may be possible for a non-AP MAP device to have the operational capability to operate for multiple AP MLDs simultaneously. A non-AP MLD may be moving at a certain speed such that after a certain time, it may be desirable to transition from an active link with the associated AP MLD 1 (which is part of AP MAP 1) to a link with a discovered new AP MLD 2 (which is also part of AP MAP 1). A non-AP MAP may perform the following steps to change the AP MLD it operates on. As a first step, the non-AP MAP may discover AP MLD 2 with links 1-3 between the non-AP MAP and AP MLD 1 enabled (at this starting point, the non-AP MAP may be close to AP MLD 1). Note that the default TID-to-link mapping may be appropriate for these links. As a second step, the non-AP MAP can create new virtual STAs 4-6. As a third step, the non-AP MAP can add links 4-6 between the non-AP MAP and the AP MLD 2. Initially, these links can be disabled, but links 1-3 may remain enabled. As a fourth step, the non-AP MAP can enable links 4-6 and disable links 1-3. The TID-to-link mapping for the AP MLD transition can be used after the link transition.

[0153] FIG. 26 illustrates a possible signal flow for adding a link to a MAP association, according to some embodiments. The signal flow may be performed between STA1 2602 in a non-AP MAP, AP1 2604 in an AP MAP, STA2 2606 in a non-AP MAP, and AP2 2608 in an AP MAP. At 2610, STA1 2602 may be associated with AP1 2604 and have a link with AP1 2604. Link Add Requests and Link Add Responses may be exchanged between STA1 2602 and AP1 2604. Link Add Requests and Link Add Responses may be robust action frames (encrypted). Thus, the link add request may be sent over an existing link or may request a new link creation in the AP MAP association. The link add request may maintain the existing link and key, and thus only need to add one or more new links to the MAP association. After the link addition, STA2 2606 may be associated with AP2 2608 at 2612, and the non-AP MAP may have two links.

[0154] FIG. 27 illustrates an example scenario showing various possible TID-to-link mapping features for MLD management, according to some embodiments. In the illustrated scenario, a first link between a transmitter and a receiver may be disabled (no TIDs can be mapped to the first link), TIDs 1-3 can be mapped to a second link between the transmitter and the receiver, and TIDs 2-4 can be mapped to a third link between the transmitter and the receiver. The TID-to-link mapping can define which traffic is transmitted on the link. Each TID and UL / DL direction can be separately mapped to a link. The TID-to-link mapping can also define whether the link can transmit traffic or not. For example, for a disabled link (e.g., in the illustrated scenario, link 1), no traffic may be transmitted, and for an enabled link (e.g., in the illustrated scenario, links 2 and 3), traffic may be allowed to / from at least one TID and management frame. In some embodiments, a non-AP MAP can transition between AP MLDs using TID-to-link mapping signaling. In some embodiments, a non-AP MAP can exchange data with one AP MLD at a time. When a non-AP MAP transitions to a new AP MLD, it can map a TID to the new AP MLD.

[0155] FIG. 28 is a table illustrating possible characteristics of TID-to-link mapping in a MAP association, including details of both MLD-level (e.g., Wi-Fi 7) TID mapping support and MAP-level (e.g., at least potentially Wi-Fi 8) TID mapping operation. As shown in the figure, according to various embodiments, there can be a variety of possible required and optionally supported modes that can potentially be used, depending, for example, on any of device capabilities and / or various other considerations. Note that other TID mapping modes and / or variations of the illustrated TID mapping modes are also possible.

[0156] FIG. 29 illustrates aspects of an example scenario in which roaming mode may be used, according to some embodiments. In the illustrated scenario, a non-AP MAP may have six links all enabled. When there is no buffered traffic, all links may be in power saving mode. When there is buffered traffic, the link with AP MLD 2 may carry traffic. Note that in some embodiments, a non-AP MAP in roaming mode may have rules that allow STA(s) in one non-AP MLD to operate in active mode at one time. For example, there may be cases where a non-AP MLD does not set links with more than one AP MLD in active mode. Roaming mode may be based on fast link activation and deactivation. The operating mode may not be suitable for continuous low latency traffic transmission, in some embodiments. An AP MAP may limit the subscribed AP MLDs that can operate in roaming mode.

[0157] 30-31 show further possible features for AP MAP implementation in roaming mode, according to some embodiments. As shown in FIG. 30, the router / AP MAP can store downlink frames addressed to non-AP MLD in roaming mode. The AP MAP can instruct the AP to signal to the non-AP MAP in roaming mode whether the AP has buffered the traffic. When the non-AP MAP activates the STA in the link to active mode, the router can forward the buffered frames to the AP. After transmitting the frames, the router can return to buffering frames for the non-AP MAP. As shown in FIG. 31, in 3110, STA MAP1 can have a first link between STA1 3102 of STA MAP1 and AP1 3104 of AP MAP1, and a second link between STA2 3106 of STA MAP1 and AP2 3108 of AP MAP1. STA MAP1 may have been using the first link and may wish to use the second link instead (e.g., using AP2). To do so, STA1 3102 may indicate to AP1 3104 to enter a power save mode, and STA2 3106 may indicate to AP2 3108 to enter an active mode. After this signaling, at 3112, STA1 3102 may be in a power save state and may not transmit any further data, while STA2 3106 may be in an active mode and may transmit and receive data. Note that in at least some embodiments, the same block acknowledgment, SCS, and TWT settings may be used in both links.

[0158] FIG. 32 illustrates an exemplary aspect of a possible multi-AP operation mode, according to some embodiments. In the illustrated scenario, the AP MAP and non-AP MAP can support more flexible UL and DL transmission modes. Such an operation mode can further reduce the BSS transition delay in the AP MAP and provide more data transmission alternatives, at least in some cases. As shown in the figure, one such possibility can include a scenario in which the uplink can be performed on any link (e.g., including those associated with multiple different AP MLDs), while the downlink can be performed on a specific AP MLD. In this scenario, the UL TID can be mapped to all links, including both links with AP MLD 1 and links with AP MLD 2, but all DL TIDs can be mapped to links with AP MLD 1, and no DL TID can be mapped to links with AP MLD 1. Also as shown in the figure, another such possibility can include a scenario in which the uplink and downlink can be performed on any link (e.g., including links associated with multiple different AP MLDs). In this scenario, both UL and DL TIDs can be mapped to all links, including both links with AP MLD 1 and links with AP MLD 2.

[0159] In some embodiments, a setup link may be defined as valid if at least one TID is mapped to the link, and invalid if no TID is mapped to the link. If a link is valid, it may be used for frame exchange, but limited to data frames corresponding to the mapped TID and management frames. Measurement MMPDUs may be transmitted only on a particular link, at least in some embodiments. If a link is invalid, it may not be used for frame exchanges, including management frame exchanges. Power management modes may not be maintained. S-APSD and TWT schedules may be deleted. Ongoing exchanges that were initiated before the link invalidation may send responses on the invalidated link.

[0160] Unless admission control is used, a TID may always be mapped to at least one setup link. TID-to-link mapping may be unidirectional, e.g., the TID mapped to a UL link may not be the same TID mapped to the corresponding DL link. By default, all TIDs may be mapped to all setup links, both UL and DL. Thus, in this case, all setup links may be enabled. If the AP MLD and non-AP MLD do not negotiate different mappings, or if the AP MLD and non-AP MLD cannot agree on any alternative mappings, or if the AP MLD and non-AP MLD break agreement, the default TID-to-link mapping mode may be used. TID-to-link mapping negotiation may take place during ML setup, e.g., via association frames or via a TID-to-link mapping handshake. Either the AP MLD or the non-AP MLD may be able to initiate the negotiation. Either the AP or the non-AP MLD may accept or reject a TID-to-link mapping request from a peer. If the TID-to-link mapping is not acceptable, the peer may propose a preferred mapping.

[0161] FIG. 33 illustrates an exemplary aspect of possible power management usage in conjunction with MAP association, according to some embodiments. In the illustrated example, a non-AP MAP may be able to control its power management mode on an enabled link. There may be cases where traffic is not permitted to be transmitted on a disabled link, and thus a STA cannot set itself to active mode on a disabled link. A power management field in the MAC header can set the STA to active mode or power save mode. An AP can expect not to transmit frames to a STA when it is in power save mode. Note that this behavior may be similar to Wi-Fi 7 behavior. Thus, in the illustrated scenario where a non-AP MAP has links 1-3 with AP MLD 1 disabled (hence no power save mode option) and links 4-6 with AP MLD 2 enabled, the non-AP MAP can set any combination of active and power save modes for enabled links 4-6, in this case including PS mode for link 4 and active modes for links 5 and 6.

[0162] FIG. 34 illustrates an exemplary aspect of a possible two-level address hierarchy framework for non-AP STAs in a MAP system, according to some embodiments. The two-level address hierarchy may include a link level address for each link, as well as a STA MAP address to identify the STA. The MAP STA address may be used similarly to the STA MLD address in 802.11be (e.g., the STA MLD address may be used to identify the STA in a BSS transition), and may identify the MAP STA to a MAP AP, an AP MLD, or an AP. As shown in the figure, in certain scenarios, it may be possible for this address hierarchy to be compressed. For example, when interacting with a legacy AP using a single link, the MAP STA address may be used to identify the non-AP STA at both the link level and the MAP level. Also as shown in the figure, according to at least some embodiments, the address hierarchy may also be re-expanded after such compression, for example, when transitioning from such a legacy AP to a MAP AP in a MAP system.

[0163] More specifically, in at least some embodiments, the STA link address may be the STA identifier in the link and may be present in the over-the-air (OTA) frame. This address may be associated and changed. The non-AP MAP address may identify the non-AP MAP in authentication and association. This address may be a long-term identifier and may be used in key derivation. The AP link address may be the AP identifier in the link and may be present in the OTA frame. This address may serve as the AP identifier in legacy authentication and association (note that legacy association does not have multi-link support). The AP MLD address may be the AP MLD identifier in multi-link authentication and association. This address may identify the AP MLD when the non-AP STA MLD associates. The AP MAP address may be the AP MAP identifier in MAP authentication and association. This address may identify the AP MAP when the non-AP STA MAP associates.

[0164] 35 illustrates an example aspect of a possible fast transition key hierarchy that may be used for a MAP system, according to some embodiments. As shown, in the illustrated example, a separate PMK-R1 key may be used for each AP in the mobility domain, the AP MLD, and the AP MAP.

[0165] Referring again to FIG. 13, an exemplary aspect of a possible block acknowledgement (BA) framework that can be used for a MAP system, according to some embodiments, is also shown. In the illustrated example, a BA can be set up for all links, i.e., all links can have the same BA in use. Each link-specific AP can perform link-specific data transmission and BA scoreboarding, for example, according to Wi-Fi 7 principles. Thus, at least in some respects, a BA implementation in a non-AP MAP may be similar to a non-AP MLD implementation. An AP MAP can have multiple alternatives for arranging transmit and reordering buffers.

[0166] FIG. 36 illustrates an exemplary aspect of a possible MAP system including multiple locations where transmit and reordering buffer implementations can occur, according to some embodiments. As one option, the DL TX buffer and / or UL reordering buffer can be located in a router (e.g., an AP MAP controller). If this is a DL TX buffer location, the transmitting AP may need to fetch DL frames from the router, which may add delay. If this is a UL reordering buffer location, all UL frames can be forwarded to the router. The router can perform reordering buffering and remove duplicate frames. The router can release the reordered packets to the Internet. As another option, the DL TX buffer and / or UL reordering buffer can be located in an AP MLD that has an active link with the STA. If this is a DL TX buffer location, DL packets can be delivered directly to the AP MLD. This can reduce DL frame transmission delays. If this is a UL reordering buffer location, the non-AP MAP can send UL frames to a single AP MLD that performs UL reordering buffering. The AP MLD can immediately send the reordered frames to the Internet.

[0167] 37-38 show further details of these possible example scenarios. In FIG. 37, possible DL frame transmit buffer alternatives in the AP MAP are further shown, including a scenario where the transmit buffer is located in the router ("Case 1"), and a scenario where the transmit buffer is located in the AP MLD ("Case 2"). In some embodiments, the first scenario may be more suitable for serving roaming non-AP MAPs that may receive downlink data from different MLDs at different times, while the second scenario may be more suitable for low latency / high bit rate data transmission, at least in some cases. In FIG. 38, possible UL reordering buffer alternatives in the AP MAP are further shown, including a scenario where the reordering buffer is located in the router ("Case 1"), and a scenario where the reordering buffer is located in the AP MLD ("Case 2"). As shown, in the first scenario, all UL data may be forwarded to the router as soon as it is received, while in the second scenario, at least in some cases, the reordered, buffered, and decoded UL data may be sent directly from the AP MLD to the Internet.

[0168] FIG. 39 illustrates an exemplary embodiment of a possible data encryption and decryption architecture in a MAP system, according to some embodiments. In Wi-Fi 7, the MLD address can be used for data encryption and decryption. The OTA transmission frame can include a link-specific address so that the MLD address is not transmitted OTA. The MLD address can be used as the OTA address in encryption. The OTA address is set to be the link address, but the receiver replaces this address with the MLD address. Wi-Fi 8 can use a similar principle, where the MLD address is replaced with the MAP address. Encryption / decryption may be performed by a separate block in the cloud or AP MLD. In some embodiments, the encryption block can be co-located with the device that operates the transmission buffer. Similarly, the decryption block can be co-located with the device that operates the reordering buffer in some embodiments.

[0169] Figure 40 is a table showing possible data transmission flow features and possible implementation locations for those features in the AP MAP, according to some embodiments. Note that in at least some embodiments, packet number assignment and encryption (shaded in the transmitter operation) may be the operation of the encryption unit. In some embodiments, it may be possible that decryption and replay detection (shaded in the receiver operation) can be located in an external unit.

[0170] FIG. 41 illustrates aspects of possible frame encryption and decryption alternatives in the AP MAP, according to some embodiments. Note that the encryption and decryption alternatives may follow, at least in some cases, alternatives for the transmit and reordering buffer implementations. As shown in the figure, the options may include a first option in which the router decrypts the UL frame and encrypts the DL frame, a second option in which the last AP MLD decrypts the UL frame and encrypts the DL frame, and a third (hybrid) option in which the AP MLD encrypts the DL frame while the router decrypts the UL frame. Note that other options may also be possible.

[0171] A WLAN can have several possible sequence number (SN) spaces. QoS data can have a SN for each TID and direction (UL / DL). AP MAP wide SN can enable BA usage on all links. Group addressed data frames can have unique SNs in all links. Thus, non-AP MAPs can receive group data frames on any link. Figure 42 is a table illustrating possible sequence number handling rules for such various SN spaces in a MAP system, according to some embodiments.

[0172] FIG. 43 illustrates an example aspect of possible EMLSR operation in MAP association, according to some embodiments. In Wi-Fi 7, EMLSR can operate on links in AP MLD. In Wi-Fi 8, it may be the case that EMLSR can operate on links in one AP MLD. Thus, if an AP MAP has multiple AP MLDs, it may be the case that each AP MLD can set up EMLSR links independently from other AP MLDs. In some embodiments, one EMLSR setup may not operate on links in different AP MLDs. Optionally, it may be the case that a Wi-Fi 8 device can have the capability to operate EMLSR on links belonging to different AP MLDs.

[0173] In some embodiments, various features may be possible for association maintenance MAP power management. Such features may include "listen interval" and "max idle period" parameters, which may be exchanged during MAP association and both may apply to the MAP entity. The listen interval may indicate how often the non-AP MAP wakes at least one of its STAs to receive beacons. The AP MAP may expect to buffer the unicast bus for the non-AP MAP for a period longer than the listen interval. The max idle period may indicate a period during which the AP MAP expects at least one frame from the non-AP MAP on any setup link. If not, the AP MAP may disassociate the non-AP MAP. The 802.11 specification may define a MAP max idle value to signal this MAP specific parameter. Alternatively, a legacy BSS max idle variable may signal this idle period. During this period, the AP MAP may not disassociate the non-AP MAP because no frames are received from the non-AP MAP on any setup link.

[0174] In AP MAP, all APs can transmit beacons, so STAs can receive beacons from any AP. Frames from STAs must be received on enabled links. The network controller or AP MAP can control AP MLD and check whether the listen interval and / or maximum idle period is met for all APs in the MLD.

[0175] FIG. 44 illustrates possible features of a multi-AP element that can be used to provide information about the MAP system, according to some embodiments. The MAP element can include AP MAP common parameters and ML elements of other AP MLD(s) and AP(s) in the AP MAP. Information of other AP MLD(s) and AP(s) may be present in the association response frame. The MAP element in the beacon and probe response frames can carry only common AP MAP parameters, which may be similar to the Wi-Fi 7 principle of ML element usage in some embodiments. Non-AP MLDs can send a MAP element in an association request frame. The MAP element can include parameters of other non-AP MLDs and non-AP(s) for non-AP MAPs of the non-AP MLD. The MAP element can use inheritance, and the element value can be inherited from the value of the first element sent in the frame, at least in some embodiments.

[0176] FIG. 45 illustrates aspects of possible MAP probe request and probe response use cases, according to some embodiments. STAs may need to have a mechanism to query all links and information about the AP MAP. STAs may need the information to be able to set up links with the AP MLD. Thus, a probe request may be provided from a scanning STA to the AP in a MAP system. The query may be specific, for example, to request information about a particular AP. In some embodiments, the AP MAP may be able to use such a mechanism to provide details of the APs and AP MLDs it operates on. In at least some embodiments, this information may be made available prior to the association request to facilitate the setup of an association link with the correct parameters.

[0177] FIG. 46 is a signal flow diagram illustrating an example of such a possible MAP probe request and probe response signal flow, according to some embodiments. The signal flow may be performed between STA1 4602 in a non-AP MLD operating in the 2.4 GHz frequency band and AP1 4604 in AP MLD1 of AP MAP1 also operating in the 2.4 GHz frequency band. At 4606, AP MAP1 may have four AP MLDs. STA1 4602 may have discovered AP1 4604 in the 2.4 GHz frequency band. Each AP MLD may have three links, one link each in the 2.4, 5, and 6 GHz bands. STA1 4602 may send a MAP probe request to inquire about more information about the AP MLDs and APs in the AP MAP. At 4608, a probe request may be provided requesting information about all APs in the AP MAP system, and the probe response may include an AP MAP element with complete information about the AP MLDs in the system and their joined APs. At 4610, a probe request can be provided requesting information about specific AP MLDs in the AP MAP system, and the probe response can include an AP MAP element with information about these specific AP MLDs. Figure 47 is a table illustrating possible variations on information that can be requested / included in a probe request / response, according to some embodiments.

[0178] FIG. 48 is a table illustrating possible AP MAP signaling aspects in reduced neighbor reporting (RNR), according to some embodiments. RNRs can potentially be used for out-of-band discovery of other APs belonging to the same AP MAP, and / or link maintenance to update AP operational parameters. RNRs sent by APs subscribing to an AP MAP can, in some embodiments, include information about APs in the reporting AP MLD and neighboring AP MLDs that are part of the AP MAP. As shown, identifier values ​​that can be included in such RNRs can include, at least in some embodiments, a MAP ID and one or more AP IDs, link IDs, and / or MLD IDs.

[0179] 49-50 illustrate aspects of possible exemplary RNR format options that may be used for AP MAP, according to some embodiments. As shown, the RNR element may include Neighbor AP Information fields for (potentially) multiple neighboring APs. Each Neighbor AP Information element may include a TBTT Information Header, an Operation Class, a Channel Number, and a TBTT Information Set (which may include multiple TBTT Information Fields). In some embodiments, the TBTT Information Header may include a TBTT Information Field Type, which may identify whether the TBTT Information Header is for MLD or MAP STAs, or for legacy 802.11ac or 802.11ax STAs for AP discovery. As shown, the length and fields present in the TBTT Information Field may vary depending on the TBTT Information Field Type value.

[0180] Note that the MLD ID (e.g., in the MLD parameters field of the TBTT information field) can be generated by the reporting AP to identify a list of reported APs that subscribe to the same AP MLD. The Link ID can indicate the link identifier of the reported AP in the AP MLD to which the reported AP subscribes. The Change Sequence can be incremented when a significant update to the beacon of the reported AP occurs. If the beacon transmitted by the reported BSS includes all parameters whose values ​​were changed in the last Change Sequence value update, all included update fields can be set to 1. Thus, by receiving a beacon from the reported BSS, in this case, the STA can obtain all updated parameter values, at least according to some embodiments.

[0181] It is understood that use of personally identifiable information should comply with privacy policies and practices generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of permitted uses should be clearly indicated to users.

[0182] In addition to the exemplary embodiments described above, further embodiments of the present disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as a computer-implemented method, a computer-readable memory medium, or a computer system. Other embodiments may be implemented using one or more custom-designed hardware devices, such as an ASIC. Still other embodiments may be implemented using one or more programmable hardware elements, such as an FPGA.

[0183] In some embodiments, a non-transitory computer readable memory medium may be configured to store program instructions and / or data that, when executed by a computer system, cause the computer system to perform the method, e.g., any of the method embodiments described herein, or a combination of the method embodiments described herein, or a subset of the method embodiments described herein, or a combination of such subsets.

[0184] In some embodiments, a device (e.g., AP 104 or UE 106) can be configured to include a processor (or set of processors) and a memory medium, where the memory medium stores program instructions and the processor is configured to read and execute the program instructions from the memory medium. The program instructions are executable to perform any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets). The device may be realized in any of a variety of forms.

[0185] 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, and it is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims

1. by a first access point (AP) wireless device, providing beacon information indicative of one or more multi-AP parameters associated with the first AP wireless device; receiving beacon information from a second AP wireless device, the beacon information indicating one or more second multi-AP parameters associated with the second AP wireless device; establishing a multi-AP system with at least the second AP wireless device based at least in part on the one or more multi-AP parameters associated with the first AP wireless device and the one or more second multi-AP parameters associated with the second AP wireless device; determining a traffic identifier (TID)-to-link mapping for a non-AP wireless device in the multi-AP system having one or more enabled wireless links with one or more AP wireless devices in the multi-AP system; A method comprising:

2. The method of claim 1 , wherein establishing the multi-AP system includes determining a multi-AP address used to identify the first AP wireless device in the multi-AP system.

3. The method further comprising:

2. The method of claim 1, further comprising: providing multi-AP system information to one or more non-AP wireless devices in one or more of a beacon frame, a probe response frame, a multilink probe response frame, or a reduced neighbor report frame.

4. The first AP wireless device acts as a network controller for the multi-AP system, and the method comprises: For each association in the multi-AP system, Station (STA) and AP parameters for a link corresponding to the association; one or more non-AP multilink device and one or more AP multilink device parameters for a multilink device corresponding to the association; or one or more non-AP multi-access point parameters and one or more AP multi-access point parameters corresponding to the association; The method of claim 1 , further comprising: storing one or more of:

5. The method further comprising:

5. The method of claim 4, further comprising: buffering the downlink data for one or more non-AP wireless devices in the multi-AP system until downlink data is requested by an AP wireless device in the multi-AP system.

6. The method further comprising: receiving uplink data for one or more non-AP wireless devices in the multi-AP system from one or more AP wireless devices in the multi-AP system; buffering the uplink data and performing uplink data reordering; The method of claim 4 further comprising:

7. The method further comprising: The method of claim 4 , further comprising: performing one or more of downlink frame encryption or uplink frame decryption for non-AP wireless devices in the multi-AP system.

8. A first access point (AP) wireless device, comprising: A radio and a processor communicatively connected to the radio; The processor executes the instructions stored in the memory to providing, via the radio, beacon information indicative of one or more multi-AP parameters associated with the first AP wireless device; receiving, via the radio, beacon information from a second AP wireless device, the beacon information indicating one or more second multi-AP parameters associated with the second AP wireless device; establishing a multi-AP system with at least the second AP wireless device over the radio based at least in part on the one or more multi-AP parameters associated with the first AP wireless device and the one or more second multi-AP parameters associated with the second AP wireless device; determining a traffic identifier (TID)-to-link mapping for a non-AP wireless device in the multi-AP system having one or more enabled wireless links with one or more AP wireless devices in the multi-AP system; A first AP wireless device performing the method, comprising:

9. The first AP wireless device of claim 8, wherein establishing the multi-AP system includes determining a multi-AP address used to identify the first AP wireless device in the multi-AP system.

10. The method of claim 1, 10. The first AP wireless device of claim 8, further comprising: providing multi-AP system information to one or more non-AP wireless devices via the radio in one or more of a beacon frame, a probe response frame, a multi-link probe response frame, or a reduced neighbor report frame.

11. The method according to claim 10, wherein the first AP wireless device acts as a network controller for the multi-AP system, the method comprising: For each association in the multi-AP system, Station (STA) and AP parameters for a link corresponding to the association; one or more non-AP multilink device and one or more AP multilink device parameters for a multilink device corresponding to the association; or one or more non-AP multi-access point parameters and one or more AP multi-access point parameters corresponding to the association; The first AP wireless device of claim 8 , further comprising: storing one or more of:

12. The method according to claim 1, The first AP wireless device of claim 11 , further comprising: buffering the downlink data for one or more non-AP wireless devices in the multi-AP system until downlink data is requested by an AP wireless device in the multi-AP system.

13. The method according to claim 1, receiving uplink data for one or more non-AP wireless devices in the multi-AP system from one or more AP wireless devices in the multi-AP system via the radio; buffering the uplink data and performing uplink data reordering; The first AP wireless device of claim 11 further comprising:

14. The method according to claim 1, The first AP wireless device of claim 11 , further comprising: performing one or more of downlink frame encryption or uplink frame decryption for non-AP wireless devices in the multi-AP system.

15. An apparatus comprising: A processor is included. The processor executes the instructions stored in the memory to providing beacon information indicative of one or more multi-AP parameters associated with a first (access point) AP wireless device; receiving beacon information from a second AP wireless device, the beacon information indicating one or more second multi-AP parameters associated with the second AP wireless device; establishing a multi-AP system with at least the second AP wireless device based at least in part on the one or more multi-AP parameters associated with the first AP wireless device and the one or more second multi-AP parameters associated with the second AP wireless device; determining a traffic identifier (TID)-to-link mapping for a non-AP wireless device in the multi-AP system having one or more enabled wireless links with one or more AP wireless devices in the multi-AP system; 23. An apparatus configured to perform the operations including:

16. The apparatus of claim 15, wherein establishing the multi-AP system includes determining a multi-AP address used to identify the first AP wireless device in the multi-AP system.

17. The operation 20. The apparatus of claim 15, further comprising: providing multi-AP system information to one or more non-AP wireless devices in one or more of a beacon frame, a probe response frame, a multilink probe response frame, or a reduced neighbor report frame.

18. The method of claim 17, wherein the first AP wireless device acts as a network controller for the multi-AP system, and the operation comprises: For each association in the multi-AP system, Station (STA) and AP parameters for a link corresponding to the association; one or more non-AP multilink device and one or more AP multilink device parameters for a multilink device corresponding to the association; or one or more non-AP multi-access point parameters and one or more AP multi-access point parameters corresponding to the association; The apparatus of claim 15 , further comprising: storing one or more of:

19. The operation 20. The apparatus of claim 18, further comprising: buffering the downlink data for one or more non-AP wireless devices in the multi-AP system until downlink data is requested by an AP wireless device in the multi-AP system.

20. The operation receiving uplink data for one or more non-AP wireless devices in the multi-AP system from one or more AP wireless devices in the multi-AP system; buffering the uplink data and performing uplink data reordering; 20. The apparatus of claim 18, further comprising:

21. The operation 20. The apparatus of claim 18, further comprising: performing one or more of downlink frame encryption or uplink frame decryption for non-AP wireless devices in the multi-AP system.

Images