CN117692990A

CN117692990A - Multi-access point association

Info

Publication number: CN117692990A
Application number: CN202311157335.XA
Authority: CN
Inventors: J·L·克内科特; 江津菁; 刘勇; 伍天宇; L·维尔马; S·K·勇; 王�琦; A·R·希达亚特; S·R·撒库
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2022-09-09
Filing date: 2023-09-08
Publication date: 2024-03-12

Abstract

The present disclosure relates to a method for multiple access point association in a wireless local area network. Multiple access point wireless devices may establish a multiple access point system. Other access point wireless devices may then join the multiple access point system. The non-access point wireless devices may form an association with the multi-access point system, which may include links with a plurality of different access point wireless devices in the multi-access point system.

Description

Multi-access point association

Technical Field

The present application relates to wireless communications, including techniques and apparatus for multiple access point association in a wireless local area network architecture.

Background

The use of wireless communication systems is growing rapidly. In addition, wireless communication technologies have evolved from voice-only communication to also include transmission of data such as the internet and multimedia content.

A mobile electronic device or user equipment device (UE) may take the form of a smart phone or tablet that a user typically carries. One aspect of wireless communications that may be generally performed by a UE may include wireless networking, for example, through a Wireless Local Area Network (WLAN), which may include devices operating in accordance with one or more communication standards in the IEEE 802.11 family of standards. The UE may be able to transition between access points in such a system, but such transitions between access points in WLAN settings may involve not only signaling overhead and data communication delays, but also the possibility of failure or ping-pong repetition between access points, which may further disrupt data communication. Accordingly, improvements in this area are desired.

Disclosure of Invention

Embodiments of systems, apparatuses, and methods are presented herein, particularly for devices for multi-access point association in a wireless local area network architecture.

A wireless device may include: one or more antennas; one or more radio components operatively coupled to the one or more antennas; and a processor operatively coupled to the one or more radio components. The wireless device may be configured to establish a connection with an access point over one or more wireless links through a Wireless Local Area Network (WLAN), or may be an access point configured to establish a connection with one or more other wireless devices over one or more wireless links through a WLAN. The wireless device may operate in each of the plurality of wireless links using a respective radio of the one or more radios.

In accordance with the techniques described herein, access point wireless devices may perform discovery and join together to form a multi-access point system. In accordance with at least some embodiments, a non-access point wireless device joining the multi-access point system may be able to form simultaneous associations with multiple access point wireless devices in the system, which may help reduce delay and overhead from transitions between access point wireless devices within the system, and/or may support improved reliability and performance of the system.

The techniques described herein may be implemented in and/or used with a number of 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 aerial controllers, automobiles and/or motor vehicles, and any of a variety of other computing devices.

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

Drawings

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

Fig. 1 illustrates an exemplary wireless communication system including a user equipment device (UE) in accordance with some embodiments;

Fig. 2 is a block diagram illustrating an exemplary UE in accordance with some embodiments;

fig. 3 is a block diagram illustrating an exemplary network element or access point in accordance with some embodiments;

fig. 4-5 are flowcharts illustrating exemplary methods for supporting Multiple Access Point (MAP) association in a wireless local area network, according to some embodiments;

fig. 6 is a flow chart illustrating exemplary signaling aspects of a possible fast BSS transition in accordance with some embodiments;

fig. 7 illustrates exemplary aspects of a possible scenario in which a wireless device may be associated with a multi-access point system, according to some embodiments;

FIG. 8 illustrates aspects of an exemplary extended service set and mobile domain deployment scenario in which one or more MAP APs may be deployed, according to some embodiments;

FIG. 9 is a table showing a comparison of various features for different Wi-Fi generations according to one possible evolution;

FIG. 10 illustrates aspects of an exemplary link handoff scenario in a MAP system in a post-association state, according to some embodiments;

FIG. 11 illustrates aspects of an exemplary link handoff scenario in which multiple AP multilink devices (MLDs) in an AP MAP are located at the coverage edge of a non-AP MAP, according to some embodiments;

FIG. 12 is a table illustrating examples of possible link operation modes that may be used in a MAP system according to some embodiments;

FIG. 13 illustrates exemplary aspects of a possible AP MAP architecture in accordance with some embodiments;

FIG. 14 illustrates aspects of an exemplary MAP system in which multiple downlink frame transmission buffering and uplink frame reordering buffering options may be implemented, according to some embodiments;

FIG. 15 illustrates exemplary aspects of a possible non-AP MAP architecture in accordance with some embodiments;

FIG. 16 illustrates further exemplary aspects of a possible MAP system architecture in accordance with some embodiments;

FIG. 17 illustrates an exemplary aspect of an alternative system architecture with mobility domain enhancements in accordance with some embodiments;

FIG. 18 illustrates exemplary aspects of a possible extended service set in which such mobile domain enhancements are deployed, according to some embodiments;

FIGS. 19-20 illustrate exemplary aspects of possible startup operations of a new AP MLD joining an AP MAP according to some embodiments;

FIG. 21 illustrates exemplary aspects of a possible simple mesh AP MAP network backbone deployment in accordance with some embodiments;

fig. 22 illustrates exemplary aspects of a possible NAN topology that may be used in a MAP system, in accordance with some embodiments;

Fig. 23 is a signal flow diagram illustrating an example of possible AP MAP discovery and association features in accordance with some embodiments;

FIG. 24 is an exemplary signal flow diagram illustrating possible association process features of an AP MAP according to some embodiments;

FIG. 25 illustrates further exemplary aspects and features of possible AP MLD transitions within a multi-AP association according to some embodiments;

FIG. 26 illustrates an example of a possible signal flow for adding links to MAP associations, according to some embodiments;

FIG. 27 illustrates an exemplary scenario illustrating various possible TID-to-link mapping features for MLD management, in accordance with some embodiments;

FIG. 28 is a table showing examples of possible features of TID to link mapping in MAP associations according to some embodiments;

FIG. 29 illustrates aspects of an exemplary scenario in which a roaming TID mapping mode may be used, according to some embodiments;

FIGS. 30-31 illustrate additional examples of possible features of AP MAP implementations of roaming modes in accordance with some embodiments;

fig. 32 illustrates exemplary aspects of possible multi-AP modes of operation according to some embodiments;

FIG. 33 illustrates exemplary aspects of possible power management use in connection with MAP association, in accordance with some embodiments;

Fig. 34 illustrates exemplary aspects of a possible level 2 address hierarchy framework for non-AP STAs in a MAP system, according to some embodiments;

FIG. 35 illustrates exemplary aspects of a possible fast transition key hierarchy that may be used in a MAP system according to some embodiments;

FIG. 36 illustrates exemplary aspects of a possible MAP system including a plurality of locations in which transport buffer and reorder buffer implementations may be implemented, according to some embodiments;

FIGS. 37 through 38 illustrate additional details of possible exemplary scenarios in which a transport buffer and a reorder buffer implementation may be implemented in multiple locations, according to some embodiments;

FIG. 39 illustrates exemplary aspects of a possible data encryption and decryption architecture in a MAP system according to some embodiments;

FIG. 40 is a table showing examples of possible data transport stream features and possible implementation locations of those features in an AP MAP according to some embodiments;

FIG. 41 illustrates exemplary aspects of possible frame encryption and decryption alternatives in an AP MAP according to some embodiments;

FIG. 42 is a table showing examples of possible sequence number processing rules for such various SN spaces in a MAP system, according to some embodiments;

FIG. 43 illustrates exemplary aspects of possible EMLSR operation in MAP association according to some embodiments;

FIG. 44 illustrates an example of possible features of a multi-AP element that may be used to provide information about a MAP system according to some embodiments;

FIG. 45 illustrates exemplary aspects of possible MAP probe request and probe response usage in accordance with some embodiments;

fig. 46 is a signal flow diagram illustrating an example of such possible MAP probe request and probe response signal flows in accordance with some embodiments;

FIG. 47 is a table showing examples of possible variations on information that may be requested/included in a probe request/response, according to some embodiments;

FIG. 48 is a table illustrating an example of aspects of reducing possible AP MAP signaling in a neighbor report (RNR) according to some embodiments; and

fig. 49-50 illustrate aspects of possible exemplary RNR format options available for an AP MAP according to some embodiments.

While the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims.

Detailed Description

Terminology

The following are definitions of terms used in this disclosure:

memory medium-any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include mounting media such as CD-ROM, floppy disk, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, rambus RAM, etc.; nonvolatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. The memory medium may also include other types of non-transitory memory or combinations thereof. Furthermore, the memory medium may be located in a first computer system executing the program or may be located in a different second computer system connected to the first computer system through a network such as the internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory medium" may include two or more memory media that may reside at different locations in different computer systems connected by, for example, a network. The memory medium may store program instructions (e.g., as a computer program) that are executable by one or more processors.

Carrier medium-a memory medium as described above, and physical transmission media such as buses, networks, and/or other physical transmission media that transmit signals such as electrical, electromagnetic, or digital signals.

Programmable hardware elements-include a variety of hardware devices that include a plurality of programmable functional blocks connected via programmable interconnects. Examples include FPGAs (field programmable gate arrays), PLDs (programmable logic devices), FPOA (field programmable object arrays), and CPLDs (complex PLDs). The programmable function blocks may range from fine granularity (combinatorial logic or look-up tables) to coarse granularity (arithmetic logic units or processor cores). The programmable hardware elements may also be referred to as "configurable logic elements".

Computer system-any of various types of computing systems or processing systems, including Personal Computer Systems (PCs), mainframe computer systems, workstations, network appliances, internet appliances, personal Digital Assistants (PDAs), television systems, grid computing systems, or other devices or combinations 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.

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 smart phones (e.g., iphones ^TM Android-based ^TM A telephone of (a)), a portable game device (e.g., a Nintendo DS ^TM 、PlayStation Portable ^TM 、Gameboy Advance ^TM 、iPhone ^TM ) Laptop computers, wearable devices (e.g., smart watches, smart glasses), PDAs, portable internet devices, music players, data storage or other handheld devices, automobiles and/or motor vehicles, unmanned Aerial Vehicles (UAVs) (e.g., unmanned aerial vehicles), UAV controllers (UAVs), and the like. Generally, the term "A UE "or" UE device "may be broadly defined to encompass any electronic, computing, and/or telecommunications device (or combination of such devices) that is easily transportable by a user and capable of wireless communication.

Wireless device or Station (STA) -any of various types of computer systems or devices that perform wireless communications. The wireless device may be portable (or mobile) or may be stationary or fixed at a location. The terms "station" and "STA" are used similarly. A UE is one example of a wireless device.

Communication device-any of various types of computer systems or devices that perform communications, where the communications may be wired or wireless. The communication device may be portable (or mobile) or may be stationary or fixed at a location. A wireless device is one example of a communication device. A UE is another example of a communication device.

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

Processing element (or processor) -refers to various elements or combinations of elements capable of performing the functions in a device (e.g., in a user equipment device or a network infrastructure device). The processor may include, for example: processors and associated memory, circuits such as an ASIC (application specific integrated circuit), portions or circuits of individual processor cores, an entire processor core, a processor array, a larger portion of a programmable hardware device such as a Field Programmable Gate Array (FPGA) and/or a system comprising multiple processors, and any combination of the various above elements.

By automatically, it is meant that an action or operation is performed by a computer system (e.g., software executed by a computer system) or device (e.g., circuitry, programmable hardware elements, ASIC, etc.) without the need to directly specify or perform the action or operation by user input. Thus, the term "automatically" is in contrast to operations being performed or specified manually by a user, where the user provides input to directly perform the operation. The automated process may be initiated by input provided by the user, but subsequent actions performed "automatically" are not specified by the user, i.e., are not performed "manually", where the user specifies each action to be performed. For example, a user fills in an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting check boxes, radio selections, etc.) to manually fill in the form, even though the computer system must update the form in response to user actions. The form may be automatically filled in by a computer system that (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user entering an answer to the specified fields. As indicated above, the user may refer to the automatic filling of the form, but not participate in the actual filling of the form (e.g., the user does not manually specify answers to the fields, but they do so automatically). The present description provides various examples of operations that are automatically performed in response to actions that a user has taken.

IEEE 802.11-refers to technologies based on IEEE 802.11 wireless standards (such as 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 may also be referred to as "Wi-Fi" or "Wireless Local Area Network (WLAN)" technology.

Configured-various components may be described as "configured to" perform a task or tasks. In such environments, "configured to" is a broad expression that generally means "having" a structure that "performs one or more tasks during operation. Thus, even when a component is not currently performing a task, the component can be configured to perform the task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module, even when the two modules are not connected). In some contexts, "configured to" may be a broad expression of structure generally meaning "having" circuitry "that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently on. In general, the circuitry forming the structure corresponding to "configured to" may comprise hardware circuitry.

For ease of description, various components may be described as performing one or more tasks. Such descriptions should be construed to include the phrase "configured to". The expression component configured to perform one or more tasks is expressly intended to not refer to the component for explanation in section 112 of the 35 th heading of the american code.

Fig. 1-2-wireless communication system

Fig. 1 illustrates an example of a wireless communication system. It should be noted that fig. 1 represents one of many possibilities, and that features of the present disclosure may be implemented by any of a variety of systems as desired. For example, the embodiments described herein may be implemented in any type of wireless device. The wireless embodiment described below is an exemplary embodiment.

As shown, an exemplary wireless communication system includes a cellular base station 102 that communicates with one or more wireless devices 106A, 106B, etc. over a transmission medium. Wireless devices 106A and 106B may be user devices, which may be referred to herein as "user equipment" (UE), UEs, or UE devices.

The UE 106 may be a device with wireless network connectivity, such as a mobile phone, handheld device, wearable device, computer or tablet, unmanned Aerial Vehicle (UAV), unmanned flight controller (UAC), automobile, or almost any type of wireless device. The UE 106 may include a processor (processing element) configured to execute program instructions stored in 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 programmable hardware elements such as FPGAs (field programmable gate arrays), integrated circuits, 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.

Base station 102 may be a Base Transceiver Station (BTS) or a cell site and may include hardware capable of wireless communication with UE devices 106A and 106B. The base station 102 may also be equipped to communicate with a network 100 (e.g., a core network of a cellular service provider, a telecommunications network such as the Public Switched Telephone Network (PSTN), and/or the internet, as well as various possible networks). Thus, the base station 102 may facilitate communication between the UE devices 106 and/or communication between the UE devices 106 and the network 100. In other implementations, the base station 102 may be configured to provide communication through one or more other wireless technologies, such as an access point or LTE in an unlicensed frequency band (LAA) that supports one or more WLAN protocols, such as 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ad, 802.11ax, 802.11ay, 802.11be, and/or other 802.11 versions.

The communication area (or coverage area) of a base station 102 may be referred to as a "cell. The base station 102 and the UE 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.

Thus, base station 102 and other similar base stations (not shown) operating in accordance with one or more cellular communication technologies may be configured as a network of cells that may provide continuous or nearly continuous overlapping services to UE devices 106A-B and similar devices within a geographic area via one or more cellular communication technologies.

Note that in at least some cases, the UE device 106 may be capable of communicating using any of a variety of wireless communication techniques. 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), and/or the like. Other combinations of wireless communication technologies are also possible, including more than two wireless communication technologies. Likewise, in some cases, the UE device 106 may be configured to communicate using only a single wireless communication technology.

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

The UEs 106A and 106B may include handheld devices such as smartphones or tablets, wearable devices such as smartwatches or smart glasses, and/or may include any of a variety of types of devices having cellular communication capabilities. For example, one or more of UEs 106A and 106B may be wireless devices intended for fixed or nomadic deployment, such as appliances, measurement devices, control devices, and the like.

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

The UE 106 may include one or more devices or integrated circuits for facilitating wireless communications, potentially including a cellular modem and/or one or more other wireless modems. The wireless modem may include one or more processors (processor 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 an FPGA (field programmable gate array), an Application Specific Integrated Circuit (ASIC), or other circuitry configured to perform any of the method embodiments described herein or any portion of the method embodiments described herein. The wireless modems described herein may be used for UE devices as defined herein, wireless devices as defined herein, or communication devices as defined herein. The wireless modems described herein may also be used for base stations or other similar network-side devices.

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) for performing wireless communications. Alternatively, the UE device 106 may include two or more radios, each of which may be configured to communicate via a respective wireless link. Other configurations are also possible.

FIG. 2-exemplary block diagram of a UE device

Fig. 2 illustrates one possible block diagram of a UE device, such as UE device 106. In some cases (e.g., in an 802.11 communication context), the UE 106 may alternatively be referred to as a Station (STA) 106, and may more particularly be referred to as a non-AP STA 106. As shown, the UE device 106 may include a system on a chip (SOC) 300, which may include portions for various purposes. For example, as shown, SOC 300 may include a processor 302 that may execute program instructions for UE device 106 and display circuitry 304 that may perform graphics processing and provide display signals to display 360. The SOC 300 may also include a motion sensing circuit 370, which 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 one or more processors 302 may also be coupled to a Memory Management Unit (MMU) 340, which may be configured to receive addresses from the one or more processors 302 and translate the addresses to locations in memory (e.g., memory 306 and Read Only Memory (ROM) 350, flash memory 310). MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, MMU 340 may be included as part of processor 302.

As shown, the SOC 300 may be coupled to various other circuitry of the UE 106. For example, the UE 106 may include various types of memory (e.g., including NAND flash memory 310), a connector interface 320 (e.g., for coupling to a computer system, docking station, 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.).

The UE device 106 may include at least one antenna and in some embodiments may include multiple antennas 335a and 335b for performing wireless communications with a base station and/or other devices. For example, UE device 106 may perform wireless communications using antennas 335a and 335 b. As described above, the UE device 106 may be configured in some embodiments to communicate wirelessly using a plurality of wireless communication standards or Radio Access Technologies (RATs).

The wireless communication circuitry 330 may include Wi-Fi logic 332, cellular modem 334, and bluetooth logic 336.Wi-Fi logic 332 is to enable UE device 106 to perform Wi-Fi or other WLAN communications over an 802.11 network. Bluetooth logic 336 is used to enable UE device 106 to perform bluetooth communications. Cellular modem 334 may be a cellular modem capable of performing cellular communications in accordance with one or more cellular communication techniques.

As described herein, the UE 106 may include hardware components and software components for implementing embodiments of the present disclosure. For example, one or more components of the wireless communication circuitry 330 (e.g., wi-Fi logic 332, cellular modem 334, BT logic 336) of the UE device 106 may be configured to implement a portion or all of the methods described herein, e.g., by a processor executing program instructions stored on 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).

FIG. 3-block diagram of an access point

Fig. 3 illustrates an exemplary block diagram of an Access Point (AP) 104, according to some embodiments. In some cases (e.g., in an 802.11 communication context), the AP 104 may also be referred to as a Station (STA), and may be more specifically referred to as an AP STA. Note that the AP of fig. 3 is only one example of a possible access point. As shown, the AP 104 may include a processor 404 that may execute program instructions for the AP 104. The processor 404 may also be coupled to a Memory Management Unit (MMU) 440 or other circuit or device, which may be configured to receive addresses from the processor 404 and translate the addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

The AP 104 may include at least one network port 470. Network port 470 may be configured to couple to a telephone network and provide access to a plurality of devices, such as UE device 106, of the telephone network as described above in fig. 1.

The network port 470 (or additional network ports) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and/or other services to a plurality of devices, such as UE device 106. In some cases, the network port 470 may be coupled to a telephone network via a core network, and/or the core network may provide a telephone network (e.g., in other UE devices served by a cellular service provider).

The AP 104 may include one or more radios 430A-430N and at least one antenna 434 (and possibly multiple antennas), each of which may be coupled to a respective communication chain. The one or more antennas 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. Antennas 434A-N communicate with their respective radio components 430A-N via communication links 432A-N. Communication link 432 may be a receive link, a transmit link, or both. The radio 430A-N may be configured to communicate via various wireless communication standards including, but not limited to, LTE-A, 5G NR, UWB, wi-Fi, and the like. The UE 104 may be configured to operate in a plurality of wireless links using one or more radios 430A-N, each for operating in a respective wireless link.

The AP 104 may be configured to wirelessly communicate using a plurality of wireless communication standards. In some cases, the AP 104 may include multiple radios that may enable a network entity to communicate in accordance with multiple wireless communication techniques. For example, as one possibility, the AP 104 may include LTE or 5G NR radio components for performing communications according to LTE, and Wi-Fi radio components for performing communications according to Wi-Fi. In such cases, the AP 104 may be able to operate as both an LTE base station and a Wi-Fi access point. As another possibility, the AP 104 may include a multimode radio capable of performing communications in accordance with any of a variety of wireless communication technologies (e.g., 5G NR and Wi-Fi,5G NR and LTE, etc.). As another possibility, the AP 104 may be configured to exclusively function as a Wi-Fi access point, e.g., without cellular communication capabilities.

As described further herein below, the AP 104 may include hardware and software components for implementing or supporting the features described herein. The processor 404 of the access point 104 may be configured to implement or support implementing some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer readable memory medium) to operate a plurality of wireless links using a plurality of respective radio components. 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 a combination thereof. Alternatively (or in addition), in combination with one or more of the other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of the AP 104 may be configured to implement or support implementation of some or all of the features described herein.

Multilink communication and multiple AP association through WLAN

A Wireless Local Area Network (WLAN) may utilize multiple links in either or both of uplink and downlink communications during communications between a wireless Station (STA), such as UE 106 shown in fig. 2, and a wireless Access Point (AP), such as AP 104 shown in fig. 3. The STA may be any of a variety of types of wireless stations including, but not limited to, a UE 106, a smart phone, a tablet, a personal computer, a smart watch, an accessory device, an Unmanned Aerial Vehicle (UAV), an unmanned aerial vehicle controller (UAC), an automobile, or any other type of wireless device capable of communicating over a WLAN.

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

Operating in multiple links may shorten transmission delay because the associated AP and STA communicate on multiple links simultaneously and may perform transmission over the first available link (e.g., rather than having to wait for a particular link to become available that may be temporarily congested or otherwise unavailable). Accordingly, a single congested link can be prevented from seriously increasing the transmission delay, and the duration of the transmission delay can be shortened. In addition, multilink operation introduces power consumption considerations because STA power consumption may vary depending on the number of spatial streams and the size of the operating bandwidth. Depending on the STA configuration, operations on multiple links may consume more power than operations on a single link.

This concept can be extended to include the possibility of STAs establishing simultaneous wireless links with multiple APs. Supporting multi-AP association may have additional potential benefits: the number of Basic Service Set (BSS) transitions is reduced, which may avoid at least some communication overhead and delay. In some cases, such as in scenarios where the link performance of one or more available APs experiences significant variability over time, such a feature may potentially result in reduced instances of BSS transition failure and reduced likelihood of ping-pong iterations between different APs. Embodiments described herein include devices and mechanisms to support multi-AP association.

FIGS. 4 to 5-flow diagrams

Fig. 4-5 are flowcharts illustrating methods for supporting a multiple Access Point (AP) system between one or more wireless Stations (STAs), such as UE 106, and a plurality of wireless APs, such as AP 104, using a WLAN, according to some embodiments. In various embodiments, some of the elements of the illustrated methods may be performed concurrently in a different order than illustrated, may be replaced by other method elements, or may be omitted. Additional method elements may also be performed as desired.

Aspects of the methods of fig. 4-5 may be implemented by a wireless device, such as the AP 104 or UE 106 shown in fig. 1-3 and described with respect to these figures, or more generally, may be implemented in connection with any of the computer circuits, systems, devices, elements or components, etc., shown in the figures, as desired. For example, a processor (and/or other hardware) of such a device may be configured to cause the device to perform any combination of the illustrated method elements and/or other method elements.

It is noted that while at least some elements of the methods of fig. 4-5 are described in a manner that relates to the use of communication techniques and/or features associated with IEEE 802.11 specification documents, such description is not intended to limit the present disclosure, and aspects of the methods of fig. 4-5 may be used in any suitable wireless communication system as desired. As shown, these methods may operate as follows.

One aspect of these methods may include mutual AP discovery and formation of a multi-AP system. As part of such discovery, a first Access Point (AP) wireless device may provide (e.g., via wireless transmission) beacon information indicating multi-AP parameters for the first AP wireless device (452). Note that according to various embodiments, the beacon information for the first AP wireless device may also include AP parameters for the first AP wireless device and/or any of various other types of information.

The first AP wireless device may receive (e.g., via wireless transmission) beacon information from the second AP wireless device that may indicate multi-AP parameters for the second AP wireless device (454). Note that, according to various embodiments, similar to 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.

The first AP wireless device and the second AP wireless device may establish a multi-AP system (456) having at least the first AP wireless device and the second AP wireless device. The multi-AP system may be established based at least in part on multi-AP parameters exchanged in beacon transmissions of 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 to multi-AP parameters for a multi-AP system. The handshake signaling may include, for example, exchanging multi-AP creation requests and multi-AP creation responses. The multi-AP system setup may also include mutual authentication and setup of a Pairwise Master Key (PMK) and/or provision of information indicating that APs and/or AP multi-link devices (and their parameters) in the multi-AP system are being setup.

Once the multi-AP system is established, other AP wireless devices may also perform discovery to determine that the multi-AP system exists and may potentially join the multi-AP system. For example, the discovery may include receiving beacon information provided by one or more AP wireless devices affiliated with the multi-AP system, which may include multi-AP system parameter information. The AP wireless device may be able to transmit a request to join the multi-AP system (e.g., to the AP wireless device from which the AP wireless device receives the beacon frame including the multi-AP system parameter information) and then receive a response accepting the request to join the multi-AP system. The joining signaling attached to the multi-AP system may include various possibilities of authentication, key set-up and/or capability signaling, among others.

It may be the case that the multiple AP system parameters may be updated after the multiple AP system is initially established. As a possibility, this may include updating the list of APs and AP multilink devices attached to the multi-AP system based on the AP or AP multilink devices joining the multi-AP system. Additionally or alternatively, any of a variety of other multi-AP parameters may be modified, for example, in various circumstances. In such cases, the updated multi-AP parameters may be provided to AP wireless devices affiliated with the multi-AP system. Those AP wireless devices may then provide updated multi-AP parameters (e.g., including different lists and/or other different multi-AP parameters of APs and/or AP multi-link devices attached to the multi-AP system) in beacon information transmitted in beacon frames and/or other transmissions performed by AP wireless devices in the multi-AP system (e.g., probe response frames, multi-link probe response frames, reduced neighbor report frames, etc.).

The non-AP wireless device may establish a wireless association with an AP wireless device in such a multi-AP system. For example, a non-AP wireless device may establish a first wireless association with a first AP wireless device in a 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 association with different AP devices in a multi-AP system may be active simultaneously; in other words, at least in accordance with some embodiments, a non-AP wireless device may not need to release an association with one AP wireless device in a 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.

The wireless communication may comprise IEEE 802.11 based wireless communication, in accordance with at least some embodiments. Beacon frames and/or wireless links established between devices in a multi-AP system may operate in one or more separate frequency bands (e.g., 2.4GHz link, 5GHz link, 6GHz link, and/or other wireless links).

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

An AP wireless device in a multi-AP system may provide multi-AP system information for the multi-AP system to a non-AP wireless device in the multi-AP system (or potentially joining 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 indicating all APs in the multi-AP system. Alternatively, the multi-AP system information may include information indicating 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 particular subset of APs in the multi-AP system, which may include information at any or all of the APs, AP multi-link devices, or multi-AP system levels.

According to various embodiments, traffic Identifier (TID) to link mapping for non-AP wireless devices in a multi-AP system may be performed in any of a variety of ways. In at least some cases, some or all TIDs may be limited to links between non-AP wireless devices and single AP wireless devices in a multi-AP system (e.g., at most one AP per TID). Alternatively, some or all TIDs may be assigned to multiple links spanning the association between a non-AP wireless device and multiple AP wireless devices in a multi-AP system. Other methods or modes of operation are also possible.

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) may operate as a network controller for a multi-AP system. In accordance with at least some embodiments, the network controller may store various bookkeeping information for various multi-AP associations in a multi-AP system. For example, for each association in a multi-AP system, the network controller may store any or all of Station (STA) and AP parameters for each link of the association, non-AP multi-link device parameters and AP multi-link device parameters for each multi-link device of the association, and/or non-AP multi-access point parameters and AP multi-access point parameters for the association.

In some cases, the network controller may additionally or alternatively function in performing non-AP association with a multi-AP system. For example, when an association request is received by an AP wireless device in a multi-AP system from a non-AP wireless device, it may be the case that the request is forwarded to a network controller. The network controller may send a query to one or more APs in the multi-AP system and/or AP multi-link devices to determine which links are available (e.g., set up). The network controller may also decide whether to create a link requested in the association request with the affiliated AP (potentially including combining responses from AP/AP multi-link devices in the system and/or further reducing the link or rejecting the association entirely) and may create an association response to be sent to the non-AP wireless device (e.g., by the AP wireless device receiving the association request from the non-AP wireless device).

In some cases, either or both of downlink data buffering and/or uplink data buffering and reordering for non-AP wireless device data communications in a multi-AP system may be performed by a network controller. Thus, as one possibility, downlink data for a non-AP wireless device in a multi-AP system may be buffered until the downlink data is requested by the 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 the multi-AP system may be received from AP wireless devices in the multi-AP system, and the network controller may buffer and perform uplink data reordering for uplink data for non-AP wireless devices in the multi-AP system, e.g., before continuing to provide data (e.g., to the internet or otherwise to higher processing layers). Alternatively, it may be the case that either or both of the downlink data buffering and/or the uplink data buffering and reordering for the non-AP wireless device is performed at the AP wireless device currently serving the non-AP wireless device in the multi-AP system.

Similarly, in some implementations, 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, it may be the case that the encryption block is located with the device operating the transport buffer and the decryption block is located with the device operating the reorder buffer.

In some cases, a non-AP wireless device may be able to establish 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, as one possibility, the first wireless association and the second wireless association may be established via control signaling with the first AP device. It is noted that, according to various embodiments, a non-AP wireless device may establish links with multiple AP wireless devices in a multi-AP system when initially forming an association with the multi-AP system, and/or, according to various embodiments, after the non-AP wireless device has been associated with the multi-AP system, the non-AP wireless device may establish one or more additional links with the AP wireless devices in the multi-AP system. To form one or more additional links once the association has been established, an add link request may be transmitted (e.g., the add link request may be transmitted to an AP wireless device with 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 with which the non-AP wireless device has established one or more links), and then an add link response is received. As previously described, in some embodiments, it may be the case that the association request is ultimately handled by the network controller of the multi-AP system, with signaling being performed by the first AP device in some embodiments. In some embodiments, the add link request/response may be similarly processed by a network controller of the multi-AP system (e.g., where signaling is performed by the AP wireless device receiving the add link request).

It may be the case that at least some of the communication parameters used to perform communication between the non-AP wireless device and any AP wireless device in the multi-AP system are uniform. For example, as one possibility, unicast frames transmitted 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-to-Peer Transient Key (PTK).

In accordance with at least some embodiments, various wireless links between a non-AP wireless device in a multi-AP system and any AP wireless devices with which the non-AP wireless device has established a wireless association may be enabled/disabled. In some cases, it may be the case that only a subset of the wireless links between the non-AP wireless device and a single AP wireless device may be in an active/enabled state at any given time. Thus, it may be the case that one or more links for a first wireless association are enabled and one or more links for a second wireless association are disabled at one time, but one or more links for the first wireless association are disabled and one or more links for the second wireless association are enabled at another time (e.g., as a possibility based on wireless device movement within a multi-AP system). In this example, it may be the case that the wireless device retains both the first wireless association and the second wireless association at two times (e.g., regardless of which link set is enabled/disabled). Since both associations are reserved, link enabling/disabling to transition from one actively used association to another, the delay, overhead, and risk of association failure may be significantly reduced even compared to fast Basic Service Set (BSS) transitions (e.g., where only links to a single physical device are maintained at any given time).

In some embodiments, the non-AP wireless device may also enable links with multiple AP wireless devices in a multi-AP system at the same time. For example, in such a scenario, the non-AP wireless device may enable at least one link for the first wireless association and at least one link for the second wireless association simultaneously. Thus, the non-AP wireless device may be able to perform data communications with both the first AP wireless device and the second AP wireless device. Supporting such an arrangement may help improve reliability, for example, in a coverage edge scenario, because data may be communicated over two links, and ping-pong transitions between available AP wireless devices may be avoided, as links with all such devices may be available at the same time.

Multiple APs may support any of a variety of possible power saving features. As one such possibility, some or all of the enabled links for multi-AP association of the non-AP wireless device may be placed in a power save mode. It may be the case that traffic is not carried on such links. At least in accordance with some embodiments, it may be the case that a non-AP wireless device and/or a corresponding AP wireless device of such a link is able to quickly resume use of the link, e.g., in case buffer traffic arrives for transmission due to a change in wireless medium conditions (e.g., as a possibility, due to device movement) and/or for any of a variety of other reasons, as the link may remain enabled while in a power save mode.

Note that in some embodiments, TID-to-link mapping (and potentially link enablement, more generally) may be separate/independent for uplink and downlink data transmission directions. Thus, for a non-AP wireless device, it may be the case that at least one link for a first wireless association and at least one link for a second wireless association are enabled simultaneously in the downlink direction (e.g., one or more downlink TIDs may be mapped to each of these links), but for the uplink direction, only one or more links for the first association are enabled (e.g., one or more uplink TIDs may be mapped to these links without an uplink TID being mapped to any link for the second wireless association), or at least one link for the first wireless association and at least one link for the second wireless association are enabled simultaneously in the uplink direction, but for the downlink direction, only one or more links for the first association are enabled, etc.

In some embodiments, the TID mapping pattern for a multi-AP association may affect the location at which certain multi-AP system management operations are performed for that association. For example, in some cases, for roaming modes where (at least a subset of) uplink and downlink frames may be transmitted on any AP wireless device in a multi-AP system, it may be the case that uplink reorder buffering and downlink transmission buffering are performed at the network controller. In a TID mapping mode where uplink and downlink frames may be transmitted on links with only one AP wireless device in a multi-AP system at a time, it may be the case that uplink reorder buffering and downlink transmission buffering are performed at the AP wireless device. For TID mapping mode where traffic in one direction may be transmitted on links with only one AP wireless device in the multi-AP system at a time and traffic in the other direction may be transmitted on links with any AP wireless device in the plurality of AP wireless devices in the multi-AP system, a hybrid approach may be used. For example, if an uplink frame may be transmitted on any link while a downlink frame is limited to transmission via one AP wireless device, then it may be the case that uplink reordering buffering is performed at the network controller while downlink transmission buffering is performed at the AP wireless device. It should be noted that other correlations between TID mapping patterns and management operation implementation options are also possible, and embodiments are also contemplated in which TID mapping patterns are not directly tied to other multi-AP system management operations.

Thus, according to the methods of fig. 4-5, a multi-AP system may be established in which a wireless device may be associated with multiple AP devices of the multi-AP system. Such techniques, at least in accordance with some implementations, may improve any or all of a variety of possible benefits of throughput, reliability, and/or power consumption.

Fig. 6 to 50 and additional information

Fig. 6-50 illustrate and describe additional aspects that may be used in connection with the methods of fig. 4-5 if desired. It should be noted, however, that the exemplary details shown in fig. 6-50 and described with respect to these drawings are not intended to limit the disclosure as a whole: many variations and alternatives to the details provided herein below are possible and should be considered within the scope of the disclosure. Thus, terms used in the following examples, such as "mandatory," "required," "always," "must," "should," and other similar such terms should be understood as being used in the context of certain exemplary scenarios and embodiments and not necessarily applicable to all possible scenarios and embodiments within the scope of the present disclosure.

In an IEEE 802.11 wireless communication system, it may be the case that BSS transitions cause interruption of data transmission. For example, at least some BSS transition mechanisms may require about 30 message transmissions, which may create delay and overhead. Block Acknowledgements (BAs) may be sent separately for each Traffic Identifier (TID) and direction (uplink/downlink), flow classification service (SCS) settings, target Wake Time (TWT) settings, new keys, etc. This can make it challenging to maintain a 5ms-10ms transmission delay for BSS transitions.

In addition, BSS transition may fail. For example, an Access Point (AP) may reject a reassociation request, in which case the transition Station (STA) may not have any association. In the case where a link to only a single physical device is maintained, for example if the performance of the link changes, the STA may perform a ping-pong BSS transition between the two APs.

In some embodiments, supporting multiple AP association may reduce the number of BSS transitions performed in an IEEE 802.11 wireless communication system. For example, in at least some embodiments, residential networks with such capability may operate without BSS switches, e.g., as compared to Wi-Fi 7 networks, and/or for enterprise networks may operate with a 90% reduction in the number of BSS switches.

Fig. 6 is a flow chart illustrating exemplary signaling aspects of a possible fast BSS transition, according to some embodiments. The fast BSS transition may reset all existing keys, block ACK (BA), TWT settings, and SCS flow settings; the STA may operate from zero in the new AP. Note that BA settings may require transmission of approximately 30 messages and acknowledgements. All of this signaling may add a delay before the STA can begin transmitting new data. In addition, as previously described, if the target AP refuses re-association signaling from the STA, the STA may not have any association and may not be able to send any data, which may add further delay to the data transmission.

As shown, in an exemplary scenario, in 608, STA 602 may be initially associated with AP1 604 and may perform a handoff to AP2 606. The transition signaling may include a 4-way handshake and association. Note that in this scenario, the link settings may not be ready. In 610, STA 602 may be associated with AP2 606. After the handoff, the STA may set BA, SCS signaling, and TWT flows. The BA may be direction and TID specific. One BA may be set in a single BA request. SCS and QoS feature signaling may aggregate requests to multiple flows. Note that not all BA settings are shown in fig. 6; it may be the case that each direction of bearer traffic and User Priority (UP) are set so that 2×8×2=32 messages and 32 ACKs can be exchanged. In 612, the BA is set, the SCS stream is set, and the TWT stream is set, and the conversion may be completed.

To reduce BSS transitions, STAs associated with an AP group, which may also be referred to as an AP multi-access point (AP MAP), may be supported. Fig. 7 illustrates exemplary aspects of one such possible scenario, according to some embodiments. As shown, a multi-AP STA (e.g., a single physical device) may have one or more links with one or more AP multi-link devices (MLDs) (e.g., each of these AP multi-link devices may be separate physical devices operating within a MAP AP).

The STA may operate in the post-association state and data transmission may continue without interruption while the STA moves in the AP MAP. The multiple AP association may be constructed based on Wi-Fi 7 rules. STA and AP capabilities may be configured for each link. Unicast frames may be transmitted over any link: all links may use the same BA settings and the same peer-to-Peer Transient Key (PTK) (encryption). The STA may receive a group data frame from any link; each AP/link may have a different group key and the framing may have a joint sequence number. In some implementations, possible updates to Wi-Fi 7 rules may include non-AP link management rules.

Fig. 8 illustrates aspects of an exemplary extended service set and mobile domain deployment scenario in which one or more MAP APs may be deployed, according to some embodiments. As shown, such an Extended Service Set (ESS) may contain one or more APs, potentially including zero or more AP MLDs and zero or more MAP APs. Each MAP AP may contain one or more AP MLDs, and each AP MLD may contain one or more APs. The MAP STA may associate with a MAP AP, an AP MLD, or an AP in the ESS at a time. The ESS may have one or more mobility domains. It may be the case that fast BSS transitions are supported within the AP/AP MLD/AP MAP in the mobile domain.

Fig. 9 is a table showing a comparison of various features for different Wi-Fi generations according to one possible evolution. In the illustrated scenario, the association may define an AP to/from which the link and STA may transmit data. Unicast data may have the following joint parameters in each link: joint Sequence Number (SN) and Packet Number (PN), PTK and BA. Regarding enhanced multi-link single radio (EMLSR) support, it is noted that, at least in some embodiments, the MAP may define the EMLSR for each AP MLD separately. For a TWT, it may be the case that signaling may set the TWT to any enabled link.

Fig. 10 illustrates aspects of an exemplary link handoff scenario in a post-association state, according to some embodiments. As shown, a non-AP MAP ("non-AP MAP 1") moving at a certain speed ("X") may determine 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 the non-AP MAP may add links 4, 5 and 6 using an add link message over the existing link (e.g., with AP MLD 1). After links 4, 5, 6 have been created, the non-AP MAP may enable those links 4, 5, 6 with AP MLD 1 and disable links 1, 2, and 3 with AP MLD 1.

Fig. 11 illustrates aspects of an exemplary link switching scenario in which multiple AP MLDs in an AP MAP are located at a coverage edge of a non-AP MAP, according to some embodiments. In the scenario shown, ping-pong transitions may be avoided since links with multiple ones of the AP MLDs are available for the non-AP MAP. This may also potentially provide improved reliability and may transmit data on both links.

Fig. 12 is a table illustrating possible link operation modes that may be used in a MAP system according to some embodiments. Such modes of operation may be used to support the possibility that a STA may create multiple links but need not operate on all of these links. Links may be virtual, in which case non-data may be transmitted over the links. However, the link may be changed quickly to be able to carry data frames. In Wi-Fi 7, it may be the case that each setup link is configured to a different mode.

There may be a number of potential benefits to reducing the number of handoffs in an IEEE 802.11 based wireless communication system, at least in accordance with some embodiments. It may be the case that the handover delay is reduced, resulting in a more reliable data transfer delay; as previously described, it may be the case that the transition between AP MAP links may be relatively fast. For non-AP MAPs (e.g., STAs), power savings may be improved; the STA may receive beacons from multiple APs (e.g., from a larger area) and have less signaling. The best link can be put into use quickly without setting up the signaling overhead. Multiple links and operating channels are available and STAs may operate on the most appropriate channel. The STA may have multiple links available for searching for available links for data transmission. Multiple AP association may also enable more complex transmission schemes. The association may create encryption keys, AID, and configure STA and AP capabilities for each link. Such bookkeeping and information sharing may be a first step towards multi-AP transmissions that may allow multiple APs to transmit to or receive from a STA at the same time. The AP may also be able to more reliably transmit all traffic; these frames may be forwarded within the AP MAP to the transmitting AP.

Fig. 13 illustrates exemplary aspects of a possible AP MAP architecture according to some embodiments. As shown, a transmission buffer may be maintained at the transmitter side, which may provide downlink frames to the receiver via multiple links between multiple STAs. Frames received at the receiver side via multiple STAs may be provided to a reorder buffer for decryption, duplicate detection, and reordering. It is noted that the method shown in fig. 13 may be applied to either or both of uplink (e.g., from a non-AP STA to an AP STA) or downlink (e.g., from an AP STA to a non-AP STA) transmissions, at least in some cases.

For an AP MAP that includes multiple physical devices (e.g., AP MLD), it may be useful to identify and set criteria or requirements for downlink frame transmission buffers (e.g., which devices on the AP side should implement downlink frame transmission buffers) and/or uplink frame reordering buffers (e.g., where received uplink frames are ordered on the AP side). Some possibilities may include a router device (e.g., which may implement an AP MAP function to support including multiple physical devices in an AP MAP) or an AP MLD closest to the corresponding STA (e.g., in a network architecture context). Fig. 14 illustrates aspects of an exemplary system in which both possibilities may be implemented. As shown, as "case 1", the transmission buffer and the reorder buffer may be maintained in a router device that may provide downlink data to the AP MLD ("AP MLD 1") for downlink transmission to STAs associated with the AP MLD 1 as requested by the AP MLD 1. The router device may also obtain uplink data via the AP MLD 1 and receive block acknowledgements from STAs so that uplink reorder buffering can be performed at the router device. In case 2, the transmission buffer and the reorder buffer may be maintained in an AP MLD device ("AP MLD 3"), which is a physically different device than the router. In this case, all downlink data of STAs associated with the AP MLD 3 may be delivered to the AP MLD 3 immediately, which may perform a transmission buffer function. Similarly, the AP MLD 3 may perform uplink frame reordering for STAs and may pass uplink data that has been reordered to the router.

Fig. 15 illustrates exemplary aspects of a possible non-AP MAP architecture according to some embodiments. As previously described, the non-AP MAP may be a physical device. The non-AP MAP may have one or more chips operating in different frequency bands. The chip may implement lower MAC operations such as TXOP acquisition, BA scoreboards, etc. The non-AP MLD layer may implement upper MAC operations. For example, for uplink frames, the upper MAC may allocate SNs, encrypt, and transmit buffer the frames, while for downlink frames, the upper MAC may decrypt the frames and reorder buffer the frames.

Note that as another possibility, for example, an architecture in which a mobile domain operation supports a plurality of associations may be implemented as compared to an architecture in which association with a MAP AP is supported. Note that, at least in accordance with some embodiments, the mobile domain may be different from the multi-AP coverage. It may not be necessary to have the same set of fast switching devices as the devices in the multi-AP joint link set. In some implementations, the mobile domain may include legacy STAs and MLDs. It may be the case that the AP identifier for the association with the association of the multi-AP is a multi-AP address, whereas for multiple associations in the mobile domain, a mobile domain ID and an AP MLD address may be used. For both association with MAP AP and multiple associations in the mobile domain, it may be the case that MAP STA addresses may be used as STA identifiers, and IP address maintenance and fast BSS transitions are possible in the mobile domain. It may be the case that MAP STAs within a MAP AP system may have a joint link. It may be the case that the AP MLD within mobile domain 2 (which may be a separate mobile domain from the Fast Transition (FT) mobile domain or "mobile domain 1") may have a joint link. For both association with MAP AP and multiple associations in the mobile domain, fast transitions to other devices are possible in the (FT) mobile domain. To support association with a MAP AP, it may be the case that a new MAP AP and MAP STA types are defined. In order to support multiple associations in a mobile domain, it may be desirable that two mobile domains (including a new mobile domain for STAs creating a joint link) may exist in the same area. It may be the case that all of the MAP AP, the AP MLD, and the legacy AP may be supported in an architecture framework supporting association with the MAP AP. It may be the case that for an architecture framework supporting multiple associations in the mobile domain, only AP MLD is supported in the new mobile domain, whereas legacy and AP MLD may be supported on the FT mobile domain. For an architecture framework supporting association with a MAP AP, there may be no need to change the mobility domain operation, and one mobility domain for the FT protocol may be deployed. For an architecture framework that supports multiple associations in the mobile domain, a mobile domain for AP MLD that can participate in multi-AP links, and a mobile domain for legacy STA FT transitions may be required.

Fig. 16 illustrates further exemplary aspects of a possible MAP system architecture according to some embodiments. As shown, there may be multiple identifiers on each of the AP side and STA side at various layers of the system. It may be the case that, in addition to the multi-AP association range between the MAP AP and the MAP STA using the MAP address, the MAP AP also supports Wi-Fi 7AP MLD level association (e.g., with a multi-link association range using the MLD address) and Wi-Fi 6 single link association (e.g., with a single link association range using the AP link address (BSSID)).

Fig. 17 illustrates an exemplary aspect of an alternative system architecture with mobility domain enhancements, in accordance with some embodiments. As shown, in the illustrated exemplary architecture, a Mobility Domain Identifier (MDID), which may be a 2 octet group value defined in 802.11r, may be used as an AP MLD group identifier that may provide the ability to set links to all AP MLDs in the AP MLD group (e.g., those AP MLDs having the same MDID). The STA and AP may continue to have a 2-level hierarchical structure for their MAC addresses. Thus, in addition to the range of mobile domain associations between MLD AP groups and STAs using MDIDs, wi-Fi 7AP MLD level associations (e.g., with a range of multi-link associations using MLD addresses) and Wi-Fi 6 single-link associations (e.g., with a range of single-link associations using AP link addresses (BSSIDs)) may also be supported in this exemplary scenario.

Fig. 18 illustrates exemplary aspects of a possible extended service set in which such mobile domain enhancements are deployed, according to some embodiments. The ESS may contain one or more APs, zero or more of which may be AP MLDs; the AP MLD may include one or more APs. As shown, the ESS may include an FT mobility domain ("mobility domain 2") within which fast BSS transitions may be possible. The ESS may also include another mobility domain ("mobility domain 1") that may have link creation capabilities, meaning that a multi-AP STA may be associated with multiple AP MLDs simultaneously.

According to some embodiments, the following sections include possible similarities and differences in management operations and features between AP MAP operations and AP MLD (e.g., legacy AP) operations. For MLME-AP-START (e.g., when a new AP MLD or AP MAP STARTs), AP operating parameters may be configured for AP MLD and the AP may START sending beacons. The AP MAP parameters may be configured, the configured device may scan for available AP MAPs, and if a suitable AP MAP is found, the device may become part of the AP MAP. If no suitable AP MAP is found, the device may establish a new AP MAP. For discovery, an AP (MLD) may send beacons, probe responses, ML probe responses, and reduced neighbor reports to be able to be discovered. For the AP MAP, the AP MAP parameters may be included to existing elements and management frames. For association, a STA (MLD) may be associated with an AP (MLD), and STA and AP parameters may be configured to set up a link. The non-AP MAP may be associated with an AP MAP. The STA and AP parameters may be configured to set up the link. For authentication and 4 key exchanges, a single PTK may encrypt all unicast frames for both AP MLD operation and AP MAP operation. Unicast frames may be transmitted in any link. The framing may be encrypted by a link specific key. All group keys may be shared to the associated STAs. For AP MLP, adding links to associations may not be supported; the non-AP MLD may need to re-associate and re-do all signaling to add the link to the association. For an AP MAP, adding links to the association may be supported; the non-AP MLD may add a new link to the association without having to re-associate and reset all parameters. For TID-to-link mapping, for AP MLD operation, the STA and AP may configure a link that may carry traffic from the TID. Further, additional TID-to-link mapping modes may be available for AP MAP operation. For power saving, in two scenarios, a STA may be available on an enabled link by sending a Power Management (PM) field with a value of 1. For legacy AP operation, fast BSS transitions may enable transitions between APs and/or AP MLDs. For AP MAP operation, fast BSS transitions may enable transitions between APs, AP MLDs, and/or AP MAPs.

Fig. 19-20 illustrate exemplary aspects of possible startup operations of a new AP MLD joining an AP MAP according to some embodiments. As shown in fig. 19, a new AP MLD ("AP MLD 2") may be started, including, for example, executing an MLME-START primitive. The AP, AP MLD, and AP MAP parameters may be configured for AP MLD 2, and the AP may begin transmitting beacons. AP MLD 2 may perform discovery and join available AP MAPs; the signaling for joining the discovered AP MAP may include authentication, key set-up, and capability signaling. New APs and AP MLDs may be added to beacons, probe responses, RNRs, etc. for the AP MAP.

Fig. 20 illustrates a possible MLME-Start signaling flow for discovering and joining AP1 2002 and AP22004 to form AP MAP 1, according to some embodiments. In 2006, the AP is not already present and is not transmitting a beacon. The APs may be activated and may then discover each other and set an AP MAP that can be associated with the STA. In 2008, the AP may perform SAE authentication to establish the PMK. After SAE authentication, the MAP may associate and set keys in a 4-way handshake, which may be similar to 802.11s link setup signaling.

There may be a number of possible backbone network alternatives for supporting AP MAP operation. Such selection of backbone architecture may be left as an implementation choice, at least in accordance with some embodiments. Some such options may include a wired backbone, wi-Fi simple MESH, neighbor Aware Networking (NAN), and/or IEEE 802.11s (MESH). The wired backbone options may include wired ethernet or fiber optic connections that may be outside the scope of the 802.11 specification. In this option, it may be the case that only wired transmission is supported in the network backbone, and the 802.11 specification may not define backbone operation (e.g., it may be left to the device vendor to implement). In some embodiments, wi-Fi simple mesh options may have a hierarchical structure with transmissions to/from the internet only. In this case, the backbone AP may have multiple BSSs: the ingress AP may host a BSS with an associated egress node similar to a non-AP STA. Other BSSs may serve terminal 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. A MU physical layer protocol data unit (PPDU) or a trigger-based (TB) PPDU may carry frames to the backbone and associated non-AP STAs. It may be the case that the backbone operates only for APs. Infrastructure BSS features (triggers, TWTs, etc.) may be added relatively simply to an ingress BSS, e.g., 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. It may be the case that SU transmissions are supported in such a network backbone. The MAC and PHY supported P2P transmission modes may be for non-AP STA capabilities. In some embodiments, the terminal devices may also obtain their transmissions via the NAN. The 802.11s option may also have a non-hierarchical structure; a mesh STA may create a mesh link with another mesh STA. The transmission may be performed over a mesh link. Each STA may be a mesh STA. It may be the case that SU transmissions are supported in such a network backbone. Note that the mesh may not currently support features introduced after 802.11ac, so that changes may be required to introduce Wi-Fi 6 and 7 features.

Fig. 21 illustrates exemplary aspects of a possible simple grid deployment according to some embodiments. The simple grid specification may specify configuration networking and setup procedures. Support for QoS and transmission may be provided. The simple mesh may be able to provide a standardized AP-to-AP interface within the AP MAP; the AP MAP internal operation may not be defined in the 802.11 specification. It may be the case that a STA is associated with 1 AP at a time; the AP may manage all UL and DL traffic to the STA. inter-AP communication at the same hierarchical level may not be supported; alternatively, according to some embodiments, support for such communication may be added.

Fig. 22 illustrates exemplary aspects of a possible NAN topology, according to some embodiments. In at least some embodiments, NAN-capable STAs may participate directly in backbone operations. This may facilitate D2D link transmission and internet transmission. It may be the case that all NAN devices may communicate directly with each other. NAN may include support for scheduling signaling for power saving and Time Division Multiple Access (TDMA). At least in some cases, trigger support and MU PPDU transmissions may not be supported, which may increase forwarding traffic delay.

Fig. 23 is a signal flow diagram illustrating possible AP MAP discovery and association features in accordance with some embodiments. As shown, signal flow may be performed between a STA 2302 and an AP 2304 in a multi-AP system. The beacon frame and probe response frame may have multiple AP elements that contain multiple AP parameters and capabilities. Other AP MLD and AP parameters may not be present to reduce overhead. The Reduced Neighbor Report (RNR) may include available AP MLDs and APs belonging to the AP MAP. To associate the non-AP MAP 2302 with the AP MAP 2304, the non-AP MAP 2302 may signal the MLD and MAP parameters and provide STA capability for each requested link. The AP MAP 2304 may signal its MLD and MAP parameters and provide AP parameters for each set link. After successful association, the non-AP MAP 2302 may be associated and have one or more setup links. The 4-way handshake may set multiple keys: PTKs for all links in the MAP, and link specific GTKs, IGTKs, and BIGTKs. All keys may be distributed to STAs and APs. One link may carry an association request, an association response, and a 4-way handshake frame. The link carrying the frames may be included as a setup link. It may be the case that the non-AP MAP is not able to operate on all links simultaneously; in some embodiments, the non-AP MAP may choose to operate on only a subset of links. After successful association, a setup link with the AP MLD delivering 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 carrying association signaling. The STA may transmit UL frames and receive DL frames on any enabled link. The STA may switch to active mode on the enabled link.

Fig. 24 is a signal flow diagram illustrating possible association process features of an AP MAP according to some embodiments. As shown, signal flow may 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. In 2414, the non-AP MAP may authenticate and be associated with the AP MAP, which may include AP MAP internal signaling to perform authentication with an authentication server. In 2416, the non-AP MAP authentication may be successful and the authenticator may configure the network controller to enable link creation of the non-AP MAP. As shown, association request frames provided by STA1 2402 to AP1 2404 may be forwarded to network controller 2410. In 2418, the non-AP MAP may request to create a plurality of links. The network controller may decide whether these links may be created and may signal the AP MLD within the AP MAP to indicate STA parameters and the created links. The network controller may plan a query to the AP MLD to ascertain which links are set. The AP MLD may decide whether to create a requested link with its affiliated AP. The AP MLD may send a response to the AP MAP query. The network controller may combine the responses from the AP MLD, may further reduce links or reject associations, and may create association responses that are sent to the STAs.

Association, established link, and STA parameters on the link may require some 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 for storing all non-AP MAP parameters. As an example, in some embodiments, an AP MAP (network controller) may store STA and AP parameters for each link, non-AP MLD and AP MLD parameters for each MLD, and AP MAP and non-AP MAP parameters for each MAP association as part of bookkeeping for all non-AP MAP associations. As part of bookkeeping of the non-AP MAP parameters associated with the AP MLD, the AP MLD may store STA and AP parameters for each link of the AP MLD, the non-AP MLD and AP MLD parameters for association, and the AP MAP parameters associated with the AP MLD. As part of bookkeeping for link-specific STA parameters, the AP may store AP MLD settings for the AP MLD to which the STA belongs.

Fig. 25 illustrates further aspects and features of possible AP MLD conversions within a multi-AP association according to some embodiments. In the illustrated scenario, the AP MAP 1 may have limitations that allow the non-AP MAP device to operate with only one AP MLD at a time in some cases, but the non-AP MAP device may also have the operating capability to operate on multiple AP MLDs at the same time. The non-AP MLD may move at a rate such that after a certain time, a transition from an active link with the associated AP MLD 1 (which is part of AP MAP 1) to a link with the new AP MLD 2 found (which is also part of AP MAP 1) may be desired. The non-AP MAP may perform the following steps to change the operated AP MLD. As a first step, the non-AP MAP may discover AP MLD 2 (at which point the non-AP MAP may be close to AP MLD 1), with links 1-3 between the non-AP MAP and AP MLD 1 enabled. Note that the default TID-to-link mapping may be in place for these links. As a second step, the non-AP MAP may create a new virtual STA 4-6. As a third step, the non-AP MAP may add links 4-6 between the non-AP MAP and the AP MLD 2. Initially, these links may be disabled, while links 1-3 may remain enabled. As a fourth step, the non-AP MAP may enable links 4-6 and disable links 1-3. The TID-to-link mapping may be converted after the link conversion using AP MLD.

Fig. 26 illustrates a possible signal flow for adding a link to a MAP association, in accordance with some embodiments. The signal flow may be performed between STA1 2602 in the non-AP MAP, AP12604 in the AP MAP, STA2 2606 in the non-AP MAP, and AP2 2608 in the AP MAP. In 2610, STA1 2602 may be associated with AP12604 and have a link with AP 1. The add link request and the add link response may be exchanged between STA1 2602 and AP1 2604. The add link request and the add link response may be robust action frames (encrypted). Thus, an add link request may be sent over an existing link and may request a new link creation to the AP MAP association. The add link request may maintain an existing link and key and may therefore only add one or more new links to the MAP association. After the link addition, in 2612, STA2 2606 may be associated with AP2 2608 and the non-AP MAP may have two links.

Fig. 27 illustrates an exemplary scenario illustrating various possible TID-to-link mapping features for MLD management, according to some embodiments. In the scenario shown, a first link between the transmitter and the receiver may be disabled (no TID may be mapped to the first link), TID 1-3 may be mapped to a second link between the transmitter and the receiver, and TID 2-4 may be mapped to a third link between the transmitter and the receiver. The TID-to-link mapping may define traffic transmitted in the link. Each TID and UL/DL direction may be mapped to these links separately. The TID-to-link mapping may also define whether the link may transmit traffic. For example, for a deactivated link (e.g., link 1 in the illustrated scenario), the case may be that traffic is not transmitted, and for an activated link (e.g., links 2 and 3 in the illustrated scenario), traffic may be admitted to/from at least one TID and management frame. In some embodiments, the non-AP MAP may use TID-to-link mapping signaling to transition between AP MLDs. In some embodiments, the non-AP MAP may exchange data with one AP MLD at a time. When a non-AP MAP transitions to a new AP MLD, the non-AP MAP may MAP the TID to the new AP MLD.

Fig. 28 is a table showing possible features of TID-to-link mapping in 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, there may be a variety of possible mandatory and optional support modes that may potentially be used according to various embodiments, e.g., depending on any of a variety of other considerations and/or device capabilities. It should be noted that other TID mapping patterns and/or variations on the TID mapping patterns shown are possible.

Fig. 29 illustrates aspects of an exemplary scenario in which a roaming mode may be used, according to some embodiments. In the scenario shown, the non-AP MAP may have 6 links all enabled. When there is no buffered traffic, all links may be in a power save mode. When there is buffered traffic, the link with the AP MLD 2 may carry the traffic. Note that in some embodiments, the non-AP MAP in roaming mode may have rules that allow STAs in one non-AP MLD to operate once in active mode. For example, it may be the case that a non-AP MLD does not set links with 2 or more AP MLDs to active mode. Roaming mode may be based on fast link activation and deactivation. In some embodiments, this mode of operation may not be suitable for continuous low delay traffic transmission. The AP MAP may limit the accessory AP MLD that can operate in roaming mode.

Fig. 30-31 illustrate additional possible features of an AP MAP implementation of roaming mode according to some embodiments. As shown in fig. 30, the router/AP MAP may store downlink frames directed to the non-AP MLD in the roaming mode. The AP MAPs may command the APs to signal whether they have buffered traffic to non-AP MAPs in roaming mode. When the non-AP MAP activates the STA in the link in active mode, the router may forward the buffered frame to the AP. After transmitting these frames, the router may re-buffer the frames for the non-AP MAP. As shown in fig. 31, in 3110, STA MAP1 may 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 MAP 1. STA MAP1 may be always using the first link and may want to instead use the second link (e.g., put AP2 into use). To do so, STA1 3102 may instruct AP1 3104 to enter a power save mode, and STA2 3106 may instruct AP2 3108 to enter an active mode. After this signaling, in 3112, STA1 3102 may be in a power saving state and may not transmit any additional 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 for both links.

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

In some embodiments, if at least one TID is mapped to a set link, the link may be defined as enabled, and if no TID is mapped to the link, the link may be defined as disabled. If a link is enabled, the link may be used for frame exchanges, but these frame exchanges may be limited to data frames and management frames corresponding to the mapped TID. In at least some embodiments, the measurement MMPDU can be transmitted only in specific links. If the link is disabled, it may be the case that the link is not used for frame exchange, including management frame exchange. The power management mode may not be maintained. The S-APSD and TWT schedules may be deleted. An ongoing exchange initiated prior to the deactivation of the link may transmit a response over the deactivated link.

It may be that the TID is always mapped to at least one set link unless admission control is used. The TID-to-link mapping may be unidirectional, e.g., such that the TID mapped to the UL link may not be the same as the TID mapped to the corresponding DL link. By default, it may be the case that all TIDs are mapped to all setup links for both UL and DL; thus, in this case, all setup links may be enabled. It may be the case that if the AP MLD and the non-AP MLD do not negotiate different mappings, or the AP MLD and the non-AP MLD cannot agree on any alternative mapping, or the AP MLD and the non-AP MLD have torn down the agreement, then the default TID to link mapping mode is used. TID-to-link mapping negotiations may occur during multi-ML setup, e.g., via an association frame or via TID-to-link mapping handshakes. Either the AP MLD or the non-AP MLD may be able to initiate the negotiation. The AP or non-AP MLD may accept or reject TID-to-link mapping requests from the peer. If the TID-to-link mapping is not accepted, the peer may propose a preferred mapping.

Fig. 33 illustrates exemplary aspects of possible power management use in connection with MAP association, in accordance with some embodiments. In the example shown, the non-AP MAP may be able to control its power management mode in the enabled link. It may be the case that traffic is not allowed to be sent in the deactivated link, so the STA cannot set itself to active mode on the deactivated link. The power management field in the MAC header may set the STA to an active mode or a power save mode. When the AP is in the power save mode, it may be desirable for the AP not to transmit frames to the STA. Note that this operation may be similar to Wi-Fi 7 operation. Thus, in the illustrated scenario in which the non-AP MAP disables links 1-3 with AP MLD 1 (and thus has no power saving mode option) and enables links 4-6 with AP MLD 2, the non-AP MAP may set any combination of active mode and power saving mode for the enabled links 4-6 (in this case, including PS mode for link 4 and active mode for links 5 and 6).

Fig. 34 illustrates exemplary aspects of a possible level 2 address hierarchy framework for non-AP STAs in a MAP system, according to some embodiments. The level 2 address hierarchy may include a link level address for each link and an STA MAP address identifying STAs. The MAP STA address may be similarly used as the STA MLD address in 802.11be (e.g., where the STA MLD address may be used to identify STAs in a BSS transition): it may identify the MAP STA as a MAP AP, an AP MLD, or an AP. As shown, in some scenarios, the address hierarchy may be compressed; for example, when interacting with a legacy AP with a single link, it may be the case that the MAP STA address is used to identify non-AP STAs in both the link and MAP levels. Also as shown, the address hierarchy may also be re-expanded after such compression, at least in accordance with some embodiments, e.g., when transitioning from such a legacy AP to a MAP AP in a MAP system.

In more detail, in at least some embodiments, the STA link address may be an STA identifier in the link and may be present in an over-the-air (OTA) frame. The address may change in association. The non-AP MAP address may identify the non-AP MAP in the authentication and association. The address may be a long-term identifier and may be used for key derivation. The AP link address may be an AP identifier in the link and may be present in the OTA frame. This address may be used as an AP identifier in legacy authentication and association (note that legacy association does not have multi-link support). The AP MLD address may be an AP MLD identifier in the multi-link authentication and association. When non-AP STA MLD associates, the address may identify the AP MLD. The AP MAP address may be an AP MAP identifier in the MAP authentication and association. The address may identify an AP MAP when a non-AP STA MAP associates.

Fig. 35 illustrates exemplary aspects of a possible fast transition key hierarchy that may be used in a MAP system, according to some embodiments. As shown, in the illustrated example, a separate PMK-R1 key may be used for each AP, AP MLD, and AP MAP in the mobile domain.

Referring back to fig. 13, exemplary aspects of a possible Block Acknowledgement (BA) framework that may be used for the MAP system are also shown, according to some embodiments. In the example shown, the BA may be set to all links, i.e., all links may use the same BA. Each link-specific AP may perform link-specific data transmission and BA scoreboards, for example, following Wi-Fi 7 principles. Thus, in at least some aspects, the BA implementation in the non-AP MAP may be similar to the non-AP MLD implementation. The AP MAP may have a number of alternatives for locating the transmission buffer and the reorder buffer.

Fig. 36 illustrates exemplary aspects of a possible MAP system including multiple locations in which transport buffer and reorder buffer implementations may be implemented, according to some embodiments. As an option, the DL TX buffer and/or UL reorder buffer may 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 take the DL frame from the router, which may add delay. If this is the UL reorder buffer location, all UL frames may be forwarded to the router. The router may perform reorder buffering and delete duplicate frames. The router may release the reordered packets to the internet. As another option, the DL TX buffer and/or UL reorder buffer may be located in an AP MLD with an active link with the STA. If this is the DL TX buffer location, the DL packet may be delivered directly to the AP MLD. This may reduce DL frame transmission delay. If this is a UL reorder buffer location, the non-AP MAP may send UL frames to a single AP MLD performing UL reorder buffering. The AP MLD may immediately send the reordered frame to the internet.

Fig. 37-38 show additional details of these possible exemplary scenarios. In fig. 37, possible DL frame transmission buffer alternatives in the AP MAP are further shown, including a scenario in which the transmission buffer is located in the router ("case 1") and a scenario in which the transmission buffer is located in the AP MLD ("case 2"). In some implementations, 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 transmissions. In fig. 38, possible UL reorder buffer alternatives in the AP MAP are further shown, including scenarios where the reorder buffer is located in the router ("case 1") and scenarios where the reorder buffer is located in the AP MLD ("case 2"). As shown, in at least some cases, in a first scenario, all UL data is forwarded to the router immediately as it is received, while in a second scenario, the reordered buffered and decrypted UL data may be sent directly from the AP MLD to the internet.

Fig. 39 illustrates exemplary aspects 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 frame of the OTA transmission may include a link-specific address such that the MLD address is not transmitted through the OTA. The MLD address may be used as an OTA address in encryption; the OTA address is set to the link address but the receiver replaces this address with the MLD address. Wi-Fi 8 may use a similar principle, where the MLD address is replaced by a MAP address. Encryption/decryption may be performed by a separate block in the cloud or in the AP MLD. In some implementations, the encryption block may be located with the device operating the transmission buffer. Similarly, in some implementations, the decryption block may be located with the device that operates the reorder buffer.

Fig. 40 is a table showing possible data transport stream features and possible implementation locations of those features in an AP MAP according to some embodiments. It is noted that, at least in some embodiments, the packet number assignment and encryption (indicated by shading in transmitter operation) may be the operation of the encryption unit. In some embodiments, decryption and playback detection (shown shaded in receiver operation) may be located in the external unit.

Fig. 41 illustrates aspects of possible frame encryption and decryption alternatives in an AP MAP according to some embodiments. It should be noted that in at least some cases, the encryption and decryption alternatives may follow the transport buffer and reorder buffer implementation alternatives. As shown, these options may include a first option where the router decrypts the UL frame and encrypts the DL frame, a second option where the final AP MLD decrypts the UL frame and encrypts the DL frame, and a third (hybrid) option where the AP MLD encrypts the DL frame and the router decrypts the UL frame. Note that other options may also be possible.

A WLAN may have several possible Sequence Number (SN) spaces. The QoS data may have SN for each TID and direction (UL/DL). The AP MAP wide SN may enable the BA to be used for all links. The group-addressed data frame may have a unique SN within all links. Thus, the non-AP MAP may receive the group data frame on any link. Fig. 42 is a table illustrating possible sequence number processing rules for such various SN spaces in a MAP system, according to some embodiments.

Fig. 43 illustrates exemplary aspects of possible EMLSR operation in MAP association according to some embodiments. In Wi-Fi 7, EMLSR may operate in links within the AP MLD. In Wi-Fi 8, it may be the case that EMLSR may operate in a link within one AP MLD. Thus, if the AP MAP has multiple AP MLDs, it may be the case that each AP MLD may set up the EMLSR link independently of the other AP MLDs. In some embodiments, one EMLSR setting may not operate on a link in a different AP MLD. Optionally, it may be the case that a Wi-Fi 8 device may have the ability to operate EMLSR in links belonging to different AP MLDs.

In some embodiments, various features may be possible for association maintenance MAP power management. Such features may include "listening interval" and "maximum idle period" parameters that may be exchanged during MAP association and both may be applied to the MAP entity. The listening interval may indicate a frequency at which the non-AP MAP wakes up at least one of its STAs to receive the beacon. The AP MAP may be expected to buffer the unicast bus of the non-AP MAP for a longer period than the listening interval. The maximum idle period may indicate a period of time during which the AP MAP expects at least one frame from the non-AP MAP on any set link; otherwise, the AP MAP may be disassociated with the non-AP MAP. The 802.11 specification may define a MAP maximum idle value to signal the MAP specific parameter. Alternatively, the legacy BSS maximum idle variable may signal the idle period. During this period, it may be the case that the AP MAP will not be disassociated from the non-AP MAP because no frames are received from the non-AP MAP on any set link.

In the AP MAP, all APs may transmit beacons, so STAs may receive beacons from any AP. Frames from STAs must be received on the enabled link. The network controller or the AP MAP may control the AP MLD and check whether the listening interval and/or the maximum idle period satisfy all APs in the MLD.

Fig. 44 illustrates possible features of a multi-AP element that may be used to provide information about a MAP system, according to some embodiments. The MAP elements may include AP MAP generic parameters and other AP MLDs in the AP MAP and ML elements of the AP. Other AP MLDs and AP information may be present in the association response frame. In some embodiments, the MAP elements in the beacon and probe response frames may carry only generic AP MAP parameters, which may be similar to Wi-Fi 7ML element usage principles. The non-AP MLD may transmit the MAP element in an association request frame. The MAP element may include other non-AP MLD and non-AP parameters of the non-AP MAP for the non-AP MLD. The MAP element may use inheritance: in at least some embodiments, the element value may be inherited from the value of the first element transmitted in the frame.

Fig. 45 illustrates aspects of possible MAP probe request and probe response usage according to some embodiments. The STA may need to have a mechanism to query all links and information for the AP MAP. The STA may need this information to be able to set up a link with the AP MLD. Accordingly, a probe request may be provided from a scanning STA to an AP in a MAP system. The query may be specific, such as being able to request information about a particular AP. In some embodiments, the AP MAP may be able to use this mechanism to provide details of the APs and AP MLDs that are operated. In at least some embodiments, this information may be made available prior to the association request in order to set up the relevant links with the correct parameters.

Fig. 46 is a signal flow diagram illustrating an example of such a possible MAP probe request and probe response signal flow in accordance with some embodiments. Signal flow may be performed between STA1 4602 operating in the 2.4GHz band in the non-AP MLD and AP1 4604 also operating in the 2.4GHz band in AP MLD1 of AP MAP 1. In 4606, AP MAP1 may have 4 AP MLDs. STA1 4602 may have found AP1 4604 in the 2.4GHz band. Each AP MLD may have 3 links, one in each of the 2.4GHz, 5GHz, and 6GHz frequency bands. STA1 4602 may transmit a MAP probe request to query for more information about AP MLD and AP in the AP MAP. In 4608, a probe request may be provided requesting information for all APs in the AP MAP system, and the probe response may include an AP MAP element with complete information for the AP MLD and its affiliated APs in the system. In 4610, a probe request may be provided requesting information for specific AP MLDs in the AP MAP system, and the probe response may include AP MAP elements with information for those specific AP MLDs. Fig. 47 is a table showing possible variations on information that may be requested/included in a probe request/response, according to some embodiments.

Fig. 48 is a table illustrating aspects of reducing possible AP MAP signaling in a neighbor report (RNR) according to some embodiments. In some cases, the RNR may be used for out-of-band discovery of other APs belonging to the same AP MAP and/or link maintenance to update AP operating parameters. In some embodiments, the RNR transmitted by the AP affiliated with the AP MAP may include information reporting the AP of the AP MLD and neighboring AP MLD as part of the AP MAP. As shown, the identifier values that may be included in such RNRs may include a MAP ID and one or more AP IDs, link IDs, and/or MLD IDs, in accordance with at least some embodiments.

Fig. 49-50 illustrate aspects of possible exemplary RNR format options available for an AP MAP according to some embodiments. As shown, the RNR element may include neighbor AP information fields of (potentially) multiple neighbor 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 a plurality of TBTT information fields). In some embodiments, the TBTT information header may include a TBTT information field type that may identify whether the TBTT information header is for an MLD or MAP STA or for a legacy 802.11ac or 802.11ax STA for AP discovery. As shown, the length and fields present in the TBTT information field may be different depending on the TBTT information field type value.

Note that the MLD ID (e.g., in the MLD parameter field of the TBTT information field) may be generated by the reporting AP to identify a list of reported APs affiliated with the same AP MLD. The link ID may indicate a link identifier of the reported AP within the AP MLD to which the reported AP is affiliated. The change sequence may be incremented upon a critical update of the beacon of the reported AP. If the beacon transmitted by the reported BSS contains all parameters whose values have changed at the last change sequence value update, then the field including all updates may be set to 1; thus, at least in accordance with some embodiments, by receiving a beacon from the reported BSS, the STA may in this case obtain all updated parameter values.

It is well known that the use of personally identifiable information should follow privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use, and the nature of authorized use should be specified to the user.

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. Other embodiments may be implemented using one or more programmable hardware elements, such as FPGAs.

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

In some embodiments, a device (e.g., AP 104 or UE 106) may be configured to include a processor (or set of processors) and a memory medium, wherein the memory medium stores program instructions, wherein the processor is configured to read and execute the program instructions from the memory medium, wherein the program instructions may be executed to implement any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset of the method embodiments described herein, or any combination of such subsets). The device may be implemented in any of various forms.

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

Claims

1. A method, comprising:

a wireless device via a first Access Point (AP):

providing beacon information indicating one or more multi-AP parameters associated with the first AP wireless device;

receiving beacon information from a second AP wireless device, wherein the beacon information indicates one or more second multi-AP parameters associated with the second AP wireless device; and

a multi-AP system having at least the second AP wireless device is established 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.

2. The method according to claim 1,

wherein establishing the multi-AP system includes determining a multi-AP address for identifying the first AP wireless device in the multi-AP system.

3. The method of claim 1, wherein the method further comprises:

The multi-AP system information is provided to one or more non-AP wireless devices in one or more of a beacon frame, a probe response frame, a multi-link probe response frame, or a reduced neighbor report frame.

4. The method of claim 1, wherein the method further comprises:

a Traffic Identifier (TID) to link map is determined for a non-AP wireless device in the multi-AP system, wherein one or more wireless links with one or more AP wireless devices in the multi-AP system are enabled.

5. The method of claim 1, wherein the first AP wireless device acts as a network controller for the multi-AP system, wherein the method further comprises:

for each association in the multi-AP system, one or more of the following is stored:

station (STA) parameters and AP parameters for a link corresponding to the association;

one or more non-AP multilink device parameters and one or more AP multilink device parameters for corresponding to the associated multilink device; or alternatively

One or more non-AP multi-access point parameters and one or more AP multi-access point parameters corresponding to the association.

6. The method of claim 5, wherein the method further comprises:

Downlink data of one or more non-AP wireless devices in the multi-AP system is buffered until the downlink data is requested by an AP wireless device in the multi-AP system.

7. The method of claim 5, wherein the method further comprises:

receiving uplink data from one or more AP wireless devices in the multi-AP system; and

and buffering the uplink data and executing uplink data reordering.

8. The method of claim 5, wherein the method further comprises:

one or more of downlink frame encryption or uplink frame decryption for non-AP wireless devices in the multi-AP system is performed.

9. An apparatus, comprising:

a processor configured to cause a non-Access Point (AP) wireless device in a AP system to:

establishing a first wireless association with a first AP device in the multi-AP system;

establishing a second wireless association with a second AP device in the multi-AP system, wherein the first wireless association and the second wireless association are simultaneously active; and

wireless data communication with the first AP device and with the second AP device is performed when the first wireless association and the second wireless association are in an active state.

10. An apparatus according to claim 9,

wherein the first wireless association and the second wireless association are each established via control signaling with the first AP device.

11. The apparatus of claim 9, wherein the processor is further configured to cause the non-AP wireless device to:

a multi-AP address to be used to identify the non-AP wireless device in the multi-AP system is determined.

12. The apparatus of claim 9, wherein the processor is further configured to cause the non-AP wireless device to:

multi-AP system information is received from one or more AP wireless devices in one or more of a beacon frame, a probe response frame, a multi-link probe response frame, or a reduced neighbor report frame.

13. An apparatus according to claim 9,

wherein unicast frames communicated via the wireless association with the first AP device and unicast frames communicated via the wireless association with the second AP device are encrypted using the same peer-to-Peer Transient Key (PTK).

14. An apparatus according to claim 9,

wherein at a first time, one or more links corresponding to the first wireless association are enabled, and one or more links corresponding to the second wireless association are disabled,

Wherein the processor is further configured to cause the non-AP wireless device to, at a second time:

disabling one or more links corresponding to the first wireless association; and

one or more links corresponding to the second wireless association are enabled,

wherein both the first wireless association and the second wireless association are reserved at both the first time and the second time.

15. The apparatus of claim 9, wherein the processor is further configured to cause the non-AP wireless device to:

at least one link for the first wireless association and at least one link for the second wireless association are simultaneously enabled.

16. The apparatus of claim 15, wherein the processor is further configured to cause the non-AP wireless device to:

a Traffic Identifier (TID) to link map for the non-AP wireless device is determined for the at least one link for the first wireless association and the at least one link for the second wireless association.

17. A first Access Point (AP) wireless device, comprising:

one or more antennas;

a radio operably coupled to the one or more antennas; and

A processor operably coupled to the radio;

wherein the first AP wireless device is configured to:

transmitting beacon information indicating one or more multi-AP parameters for a multi-AP system of which the first AP wireless device is a member;

receiving a multi-AP association request from a non-AP wireless device, wherein the multi-AP association request indicates a request to establish a first wireless association with the first AP device in the multi-AP system and a request to establish a second wireless association with a second AP device in the multi-AP system; and

a multi-AP association response is transmitted to the non-AP wireless device, wherein the multi-AP association response indicates whether to establish the first wireless association and the second wireless association.

18. The first AP of claim 17, wherein the first AP wireless device is further configured to:

providing the multi-AP association request to a network controller of the multi-AP system; and

a multiple AP association response is received from the network controller.

19. The first AP of claim 17, wherein the first AP wireless device is further configured to:

receiving beacon information from the second AP wireless device, the beacon information indicating one or more multi-AP parameters corresponding to the multi-AP system;

Transmitting a request to join the multi-AP system to the second AP wireless device; and

receiving a response from the second AP wireless device accepting the request to join the multi-AP system,

wherein the first AP wireless device is a member of the multi-AP system based at least in part on the request to join the multi-AP system and the response to accept the request to join the multi-AP system.

20. The first AP of claim 17, wherein the first AP wireless device is further configured to:

receiving information indicative of updated multi-AP parameters corresponding to the multi-AP system of which the first AP wireless device is a member, wherein the updated multi-AP parameters include at least an addition of one or more AP wireless devices to the multi-AP system; and

and transmitting updated beacon information indicating the updated multi-AP parameters.