Association parameter handling for wireless networks

Abstract

In embodiments, AP MLDs participating in the logic AP MLD operation can divide the association identifier (AID) space among them, whereby each AP MLD can then select an AID value only from the part of the AID space assigned to it, and the AP MLDs can dynamically increase the number of bits used for AID representation in order to increase the possible AID values.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more specifically, to, for example, but not limited to, association parameter processing for wireless networks. Background Technology

[0002] Since the late 1990s, Wireless Local Area Network (WLAN) technology has evolved towards increasing data rates and continues to grow in various markets such as homes, businesses, and hotspots. WLAN allows devices to access the Internet in the 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz frequency bands. WLAN is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The IEEE 802.11 standard family aims to improve speed and reliability and extend the operational range of wireless networks.

[0003] WLAN devices increasingly need to support a variety of latency-sensitive or real-time applications, such as augmented reality (AR), robotics, artificial intelligence (AI), cloud computing, and autonomous vehicles. To achieve the extremely low latency and extremely high throughput required for such applications, Multi-Link Operation (MLO) has been proposed for WLANs. A WLAN is formed by WLAN devices within a limited area such as a home, school, apartment, or office building. Each WLAN device can have one or more Stations (STAs), such as Access Point (AP) STAs and Non-Access Point (Non-AP) STAs.

[0004] MLO enables non-AP multi-link devices (MLDs) to establish multiple links with AP MLDs. Each of these links can independently enable channel access and frame switching between the non-AP MLD and the AP MLD, which can reduce latency and increase throughput.

[0005] The descriptions set forth in the Background section should not be assumed to be prior art simply because they are set forth in the Background section. The Background section may describe aspects or embodiments of this disclosure. Summary of the Invention

[0006] One aspect of this disclosure provides a first access point (AP) multilink device (MLD) in a wireless network, comprising: a memory; and a processor coupled to the memory. The processor is configured to send a first frame to a second AP MLD to request a portion of an association identifier (AID), wherein the first AP MLD and the second AP MLD form a seamless roaming domain. The processor is configured to receive from the second AP MLD a second frame in response to the first frame, the second frame assigning the portion of the AID to the first AP MLD. The processor is configured to assign one or more AIDs from the portion of the AID assigned to the first AP MLD to one or more stations (STAs).

[0007] In some examples, the first frame indicates i) a pair of integer values ​​indicating the start and end of the AID that the first AP MLD is requesting, ii) the start and end bits of the AID field from which the first AP MLD is requesting to allow selection of an AID, iii) the number of AIDs that the first AP MLD is requesting, or iv) the AID value that the first AP MLD is requesting.

[0008] In some examples, the second frame indicates i) a pair of integer values ​​indicating the start and end of the AIDs authorized by the first AP MLD, ii) the start bit value and end bit of the AID field from which the first AP MLD can select an AID, iii) the number of AIDs authorized by the first AP MLD, or iv) the AID value authorized by the first AP MLD.

[0009] In some examples, the processor is also configured to send a third frame that increases the number of notification AIDs.

[0010] In some examples, the first AP MLD and the second AP MLD are not co-located.

[0011] In some examples, the two most significant bits of the AID field are used to increase the number of AIDs.

[0012] In some examples, one or more of the two most significant bits of the AID field are set to a value other than 1.

[0013] In some examples, the number of AIDs is increased by assigning additional bits to the AID field.

[0014] One aspect of this disclosure provides a first access point (AP) multilink device (MLD) in a wireless network, comprising: a memory; and a processor coupled to the memory. The processor is configured to receive a first frame from a second AP MLD containing a portion of a request association identifier (AID), wherein the first AP MLD and the second AP MLD form a seamless roaming domain. The processor is configured to send a second frame to the second AP MLD in response to the first frame which assigns the portion of the AID to the second AP MLD.

[0015] In some examples, the first frame indicates i) a pair of integer values ​​indicating the start and end of the AID that the second AP MLD is requesting, ii) the start and end bits of the AID field from which the second AP MLD is requesting to allow selection of an AID, iii) the number of AIDs that the second AP MLD is requesting, or iv) the AID value that the second AP MLD is requesting.

[0016] In some examples, the second frame indicates i) a pair of integer values ​​indicating the start and end of the AIDs authorized by the second AP MLD, ii) the start bit value and end bit of the AID field from which the second AP MLD can select the AIDs, iii) the number of AIDs authorized by the second AP MLD, or iv) the AID value authorized by the second AP MLD.

[0017] In some examples, the processor is also configured to send a third frame that increases the number of notification AIDs.

[0018] In some examples, the first AP MLD and the second AP MLD are not co-located.

[0019] In some examples, the two most significant bits of the AID field are used to increase the number of AIDs.

[0020] One aspect of this disclosure provides a computer-implemented method for wireless communication by a first access point (AP) multilink device (MLD) in a network. The method includes sending a portion of a first frame to a second AP MLD to request an association identifier (AID), wherein the first AP MLD and the second AP MLD form a seamless roaming domain. The method includes receiving a second frame from the second AP MLD in response to the first frame, the second frame assigning said portion of the AID to the first AP MLD. The method includes assigning one or more AIDs from said portion of the AID assigned to the first AP MLD to one or more stations (STAs).

[0021] In some examples, the first frame indicates i) a pair of integer values ​​indicating the start and end of the AID that the first AP MLD is requesting, ii) the start and end bits of the AID field from which the first AP MLD is requesting to allow selection of an AID, iii) the number of AIDs that the first AP MLD is requesting, or iv) the AID value that the first AP MLD is requesting.

[0022] In some examples, the second frame indicates i) a pair of integer values ​​indicating the start and end of the AIDs authorized by the first AP MLD, ii) the start bit value and end bit of the AID field from which the first AP MLD can select an AID, iii) the number of AIDs authorized by the first AP MLD, or iv) the AID value authorized by the first AP MLD.

[0023] In some examples, the method further includes sending a third frame that increases the number of notification AIDs.

[0024] In some examples, the first AP MLD and the second AP MLD are not co-located.

[0025] In some examples, the two most significant bits of the AID field are used to increase the number of AIDs.

[0026] In some examples, one or more of the two most significant bits of the AID field are set to a value other than 1.

[0027] In some examples, the number of AIDs is increased by assigning additional bits to the AID field.

[0028] One aspect of this disclosure provides a computer-implemented method for wireless communication by a first access point (AP) multilink device (MLD) in a network. The method includes receiving a first frame from a second AP MLD containing a portion of a request association identifier (AID), wherein the first AP MLD and the second AP MLD form a seamless roaming domain; and transmitting a second frame to the second AP MLD in response to the first frame which assigns said portion of the AID to the second AP MLD.

[0029] In some examples, the first frame indicates i) a pair of integer values ​​indicating the start and end of the AID that the second AP MLD is requesting, ii) the start and end bits of the AID field from which the second AP MLD is requesting to allow selection of an AID, iii) the number of AIDs that the second AP MLD is requesting, or iv) the AID value that the second AP MLD is requesting.

[0030] In some examples, the second frame indicates i) a pair of integer values ​​indicating the start and end of the AIDs authorized by the second AP MLD, ii) the start bit value and end bit of the AID field from which the second AP MLD can select the AIDs, iii) the number of AIDs authorized by the second AP MLD, or iv) the AID value authorized by the second AP MLD.

[0031] In some examples, the processor is also configured to send a third frame that increases the number of notification AIDs.

[0032] In some examples, the first AP MLD and the second AP MLD are not co-located.

[0033] In some examples, the two most significant bits of the AID field are used to increase the number of AIDs. Attached Figure Description

[0034] Figure 1 An example of a wireless network according to an embodiment is illustrated.

[0035] Figure 2a An example of an AP according to an embodiment is illustrated.

[0036] Figure 2bAn example of a STA according to an embodiment is illustrated.

[0037] Figure 3 An example of multi-link communication operation according to an embodiment is illustrated.

[0038] Figure 4 The illustration shows the stages of the mobility handover process according to an embodiment.

[0039] Figure 5 The illustration shows a logical AP MLD according to an embodiment.

[0040] Figure 6 The illustration shows an increase in AID space according to an embodiment.

[0041] Figure 7 The illustration shows the AID space partitioning according to an embodiment.

[0042] Figure 8 The diagram illustrates a separate AID space according to an embodiment.

[0043] Figure 9 The illustration shows a modified AID element format according to an embodiment.

[0044] Figure 10 The illustration shows a flowchart of an example process for allocating AID space by an AP according to an embodiment.

[0045] In one or more embodiments, not all components depicted in each figure are necessary, and one or more embodiments may include additional components not shown in the figures. Variations in the arrangement and type of components may be made without departing from the scope of this subject matter disclosure. Additional components, different components, or fewer components may be utilized within the scope of this subject matter disclosure. Detailed Implementation

[0046] The detailed description set forth below in conjunction with the accompanying drawings is intended to describe various embodiments and is not intended to represent the only embodiments in which the subject matter can be practiced. Rather, this detailed description includes specific details to provide a thorough understanding of the subject matter of the invention. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the scope of this disclosure. Therefore, the drawings and description are to be considered illustrative rather than restrictive in nature. The same reference numerals denote the same elements.

[0047] The following description pertains to certain implementations for the purpose of describing the innovative aspects of this disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in a variety of different ways. The examples in this disclosure are based on WLAN communication in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, including the IEEE 802.11be standard and any future revisions to the IEEE 802.11 standard. However, the described embodiments can be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals according to the IEEE 802.11 standard, Bluetooth standard, Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunking Radio (TETRA), Wideband CDMA (W-CDMA), Evolved Data Optimized (EV-DO), 1xEV-DO, EV-DO Rev A, EV-DO Rev B, High-Speed ​​Packet Access (HSPA), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Evolved High-Speed ​​Packet Access (HSPA+), Long Term Evolution (LTE), 5G NR (New Radio), AMPS, or other known signals used for communication within wireless, cellular, or Internet of Things (IoT) networks, such as systems utilizing 3G, 4G, 5G, 6G, or further implementations thereof.

[0048] Depending on the network type, other well-known terms may be used instead of "access point" or "AP," such as "router" or "gateway." For convenience, the term "AP" is used in this disclosure to refer to a network infrastructure component that provides wireless access to remote terminals. In a WLAN, assuming that the AP also contends for the wireless channel, the AP may also be referred to as a STA. Furthermore, depending on the network type, other well-known terms may be used instead of "station" or "STA," such as "mobile station," "subscriber station," "remote terminal," "user equipment," "wireless terminal," or "user device." For convenience, the terms "station" and "STA" are used in this disclosure to refer to a remote wireless device that wirelessly accesses an AP or contends for a wireless channel in a WLAN, whether the STA is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer, AP, media player, fixed sensor, television, etc.).

[0049] Multilink Operation (MLO) is a key feature currently being developed by the standards body for next-generation Ultra High Throughput (EHT) Wi-Fi systems in IEEE 802.11be. Wi-Fi devices that support MLO are called Multilink Devices (MLDs). Using MLO, a non-AP MLD can discover, authenticate, associate, and establish multiple links with an AP MLD. Channel access and frame switching can occur on each link between the AP MLD and non-AP MLDs.

[0050] Figure 1 An example of a wireless network 100 according to an embodiment is shown. Figure 1 The illustrated embodiment of the wireless network 100 is for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0051] like Figure 1 As shown, wireless network 100 may include multiple wireless communication devices. Each wireless communication device may include one or more stations (STAs). An STA may be a logical entity that is a separate addressable instance of an interface to the Media Access Control (MAC) layer and Physical (PHY) layer of the wireless medium. STAs may be classified as Access Point (AP) STAs and Non-Access Point (Non-AP) STAs. An AP STA may be an entity that provides access to distribution system services to an associated STA via the wireless medium. A Non-AP STA may be a STA that is not included within an AP-STA. For simplicity, an AP STA may be referred to as an AP, and a Non-AP STA may be referred to as a STA. Figure 1 In the example, APs 101 and 103 are wireless communication devices, each of which may include one or more AP STAs. In such an embodiment, APs 101 and 103 may be AP multilink devices (MLDs). Similarly, STAs 111-114 are wireless communication devices, each of which may include one or more non-AP STAs. In such an embodiment, STAs 111-114 may be non-AP MLDs.

[0052] APs 101 and 103 communicate with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network. AP 101 provides wireless access to network 130 to multiple stations 111-114 in the coverage area 120 of AP 101. APs 101 and 103 can communicate with each other and with STAs using Wi-Fi or other WLAN communication technologies.

[0053] Depending on the network type, other well-known terms may be used instead of "access point" or "AP," such as "router" or "gateway." For convenience, the term "AP" is used in this disclosure to refer to a network infrastructure component that provides wireless access to remote terminals. In a WLAN, assuming that the AP also contends for the wireless channel, the AP may also be referred to as a STA. Furthermore, depending on the network type, other well-known terms may be used instead of "station" or "STA," such as "mobile station," "subscriber station," "remote terminal," "user equipment," "wireless terminal," or "user device." For convenience, the terms "station" and "STA" are used in this disclosure to refer to a remote wireless device that wirelessly accesses an AP or contends for a wireless channel in a WLAN, whether the STA is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer, AP, media player, fixed sensor, television, etc.).

[0054] exist Figure 1 In the diagram, the dashed lines illustrate the approximate extent of the coverage areas 120 and 125 of APs 101 and 103, which are depicted as approximately circular for illustrative and explanatory purposes. It should be clearly understood that, depending on the configuration of the APs, the coverage areas associated with the APs (such as coverage areas 120 and 125) may have other shapes, including irregular shapes.

[0055] As described in more detail below, one or more APs in an AP may include circuitry and / or programming for the management of MU-MIMO and OFDMA channel detection in a WLAN. Although Figure 1 The illustration shows an example of a wireless network 100, but it is possible to... Figure 1 Various modifications can be made. For example, wireless network 100 can include any number of APs and any number of STAs in any suitable arrangement. Furthermore, AP 101 can communicate directly with any number of STAs and provide these STAs with wireless broadband access to network 130. Similarly, each AP 101 and 103 can communicate directly with network 130 and provide STAs with direct wireless broadband access to network 130. Additionally, AP 101 and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0056] Figure 2a An example of AP 101 according to an embodiment is shown. Figure 2a The embodiment of AP 101 shown is for illustrative purposes, and Figure 1 AP 103 can have the same or similar configuration. However, APs have a wide variety of configurations, and Figure 2a This disclosure is not intended to limit the scope to any particular implementation of AP.

[0057] like Figure 2a As shown, AP 101 may include multiple antennas 204a-204n, multiple radio frequency (RF) transceivers 209a-209n, transmit (TX) processing circuitry 214, and receive (RX) processing circuitry 219. AP 101 may also include a controller / processor 224, a memory 229, and a backhaul or network interface 234. RF transceivers 209a-209n receive incoming RF signals from antennas 204a-204n, such as signals transmitted by STAs in network 100. RF transceivers 209a-209n down-convert the incoming RF signals to generate intermediate (IF) or baseband signals. The IF or baseband signals are sent to RX processing circuitry 219, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 219 sends the processed baseband signals to controller / processor 224 for further processing.

[0058] TX processing circuit 214 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from controller / processor 224. TX processing circuit 214 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 209a-209n receive the outgoing processed baseband or IF signal from TX processing circuit 214 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 204a-204n.

[0059] The controller / processor 224 may include one or more processors or other processing devices that control the overall operation of the AP 101. For example, the controller / processor 224 may control the RF transceivers 209a-209n, the RX processing circuitry 219, and the TX processing circuitry 214 to receive uplink signals and transmit downlink signals according to known principles. The controller / processor 224 may also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 224 may support beamforming or directional routing operations, where outgoing signals from multiple antennas 204a-204n are weighted differently to effectively direct outgoing signals to a desired direction. The controller / processor 224 may also support OFDMA operations, where outgoing signals are assigned to different subcarrier subsets for different receivers (e.g., different STAs 111-114). The controller / processor 224 may support a variety of other functions in the AP 101, including combining DLMU-MIMO and OFDMA in the same transmission opportunity. In some examples, controller / processor 224 may include at least one microprocessor or microcontroller. Controller / processor 224 is also capable of executing programs and other processes, such as an operating system, residing in memory 229. Controller / processor 224 is capable of moving data into or out of memory 229 as needed for the execution process.

[0060] The controller / processor 224 is also coupled to a backhaul or network interface 234. The backhaul or network interface 234 allows the AP 101 to communicate with other devices or systems via a backhaul connection or over a network. Interface 234 can support communication via any suitable wired or wireless connection. For example, interface 234 can allow the AP 101 to communicate with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. Interface 234 can include any suitable structure that supports communication via a wired or wireless connection, such as an Ethernet or RF transceiver. Memory 229 is coupled to the controller / processor 224. A portion of memory 229 can include RAM, and another portion of memory 229 can include flash memory or other ROM.

[0061] As described in more detail below, AP 101 may include circuitry and / or procedures for managing the channel detection process in a WLAN. Although Figure 2a An example of AP 101 is illustrated, but it is possible to see... Figure 2a Various changes can be made. For example, AP101 can include any number of... Figure 2aEach component shown. As a specific example, the AP may include multiple interfaces 234, and the controller / processor 224 may support routing functionality to route data between different network addresses. As another example, although illustrated as a single instance including TX processing circuitry 214 and a single instance including RX processing circuitry 219, AP 101 may include multiple instances of each (such as one per RF transceiver). Alternatively, only one antenna and RF transceiver path may be included, as in a conventional AP. Moreover, Figure 2a The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0062] like Figure 2a As shown, in some examples, AP 101 may be an AP MLD comprising multiple APs 202A-202N. Each AP 202a-202n is attached to AP MLD 101 and includes multiple antennas 204a-204n, multiple radio frequency (RF) transceivers 209a-209n, transmit (TX) processing circuitry 214, and receive (RX) processing circuitry 219. Each AP 202a-202n may communicate independently with the controller / processor 224 and other components of AP MLD 101. Figure 2a The diagram illustrates that each AP 202a-202n has its own multiple antennas, but each AP 202a-202n can share multiple antennas 204a-204n without requiring separate multiple antennas. Each AP 202a-202n can represent the physical (PHY) layer and the lower media access control (MAC) layer.

[0063] Figure 2b An example of STA 111 according to an embodiment is shown. Figure 2b The embodiment of STA 111 shown is for illustrative purposes, and Figure 1 STAs 111-114 can have the same or similar configurations. However, STAs appear in a wide variety of configurations, and Figure 2b This disclosure is not intended to limit the scope of any particular implementation of STA.

[0064] like Figure 2b As shown, STA 111 may include one or more antennas 205, an RF transceiver 210, a TX processing circuit 215, a microphone 220, and an RX processing circuit 225. STA 111 may also include a speaker 230, a controller / processor 240, an input / output (I / O) interface (IF) 245, a touchscreen 250, a display 255, and a memory 260. The memory 260 may include an operating system (OS) 261 and one or more applications 262.

[0065] RF transceiver 210 receives incoming RF signals transmitted by the AP of network 100 from antenna 205. RF transceiver 210 down-converts the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to RX processing circuitry 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 225 sends the processed baseband signals to speaker 230 (e.g., for voice data) or to controller / processor 240 for further processing (e.g., for web browsing data).

[0066] TX processing circuitry 215 receives analog or digital voice data from microphone 220, or other outgoing baseband data (such as web data, email, or interactive video game data) from controller / processor 240. TX processing circuitry 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 210 receives the processed outgoing baseband or IF signal from TX processing circuitry 215 and up-converts the baseband or IF signal into an RF signal transmitted via antenna 205.

[0067] The controller / processor 240 may include one or more processors and execute a basic OS program 261 stored in memory 260 to control the overall operation of STA 111. In one such operation, the controller / processor 240 controls the RF transceiver 210, RX processing circuitry 225, and TX processing circuitry 215 to receive downlink signals and transmit uplink signals according to known principles. The controller / processor 240 may also include processing circuitry configured to provide management of the channel detection process in the WLAN. In some examples, the controller / processor 240 may include at least one microprocessor or microcontroller.

[0068] The controller / processor 240 is also capable of executing other processes and programs residing in the memory 260, such as operations for managing channel sensing processes in the WLAN. The controller / processor 240 is capable of moving data into or out of the memory 260 as needed for the execution of processes. In some examples, the controller / processor 240 is configured to execute multiple applications 262, such as applications for channel sensing, including feedback calculations based on received Null Data Packet Advertisements (NDPA) and Null Data Packets (NDP), and sending beamforming feedback reports in response to trigger frames (TF). The controller / processor 240 can operate multiple applications 262 based on the OS program 261 or in response to signals received from the AP. The controller / processor 240 is also coupled to an I / O interface 245, which provides the STA 111 with the ability to connect to other devices such as laptops and handheld computers. The I / O interface 245 is the communication path between these accessories and the main controller / processor 240.

[0069] The controller / processor 240 is also coupled to input 250 (e.g., a touchscreen) and display 255. An operator of STA 111 can use input 250 to input data into STA 111. Display 255 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text and / or at least limited graphics (such as from a website). Memory 260 is coupled to the controller / processor 240. A portion of memory 260 may include random access memory (RAM), and another portion of memory 260 may include flash memory or other read-only memory (ROM).

[0070] although Figure 2b An example of STA 111 is shown, but it is possible to see... Figure 2b Make various changes. For example, Figure 2b The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. In a specific example, STA 111 may include any number of antennas 205 for MIMO communication with AP 101. In another example, STA 111 may not include voice communication, or the controller / processor 240 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although... Figure 2b The illustration shows the STA 111 configured as a mobile phone or smartphone, but the STA can be configured to operate as other types of mobile or fixed devices.

[0071] like Figure 2bAs shown, in some examples, STA 111 may be a non-AP MLD comprising multiple STAs 203A-203N. Each STA 203a-203n is attached to the non-AP MLD 111 and includes an antenna 205, an RF transceiver 210, a TX processing circuit 215, and an RX processing circuit 225. Each STA 203a-203n can independently communicate with the controller / processor 240 and other components of the non-AP MLD 111. Figure 2b It is shown that each STA 203a-203n has a separate antenna, but each STA 203a-203n can share antenna 205 without requiring a separate antenna. Each STA 203a-203n can represent the physical (PHY) layer and the lower media access control (MAC) layer.

[0072] Figure 3 An example of multi-link communication operation according to an embodiment is shown. Multi-link communication operation can be used in the IEEE 802.11be standard and any future revisions of the IEEE 802.11 standard. Figure 3 In the middle, AP MLD 310 can be Figure 1 Wireless communication devices 101 and 103 are included, and the non-AP MLD 220 can be... Figure 1 One of the wireless communication devices 111-114 in the series.

[0073] like Figure 3 As shown, AP MLD 310 may include multiple auxiliary APs, such as AP 1, AP 2, and AP 3. Each auxiliary AP may include a PHY interface to the wireless medium (Link 1, Link 2, or Link 3). AP MLD 310 may include a single MAC Service Access Point (SAP) 318 through which the auxiliary APs of AP MLD 310 communicate with higher layers (Layer 3 or network layer). Each auxiliary AP of AP MLD 310 may have a different MAC address (lower MAC address) than any other auxiliary AP of AP MLD 310. AP MLD 310 may have an MLD MAC address (higher MAC address), and the auxiliary APs share a single MAC SAP 318 to Layer 3. Therefore, the auxiliary APs share a single IP address, and Layer 3 identifies AP MLD 310 by assigning a single IP address.

[0074] A non-AP MLD 320 may include multiple affiliated STAs, such as STA 1, STA 2, and STA 3. Each affiliated STA may include a PHY interface to the wireless medium (Link 1, Link 2, or Link 3). A non-AP MLD 320 may include a single MAC SAP 328, through which affiliated STAs communicate with higher layers (Layer 3 or network layer). Each affiliated STA of a non-AP MLD 320 may have a different MAC address (lower MAC address) than any other affiliated STA of the non-AP MLD 320. A non-AP MLD 320 may have an MLD MAC address (higher MAC address), and the affiliated STAs share the single MAC SAP 328 to Layer 3. Therefore, the affiliated STAs share a single IP address, and Layer 3 identifies the non-AP MLD 320 by assigning this single IP address.

[0075] AP MLD 310 and non-AP MLD 320 can establish multiple links between their associated APs and STAs. In this example, AP 1 and STA 1 can establish Link 1, operating in the 2.4 GHz band. Similarly, AP 2 and STA 2 can establish Link 2, operating in the 5 GHz band, and AP 3 and STA 3 can establish Link 3, operating in the 6 GHz band. Each link can independently enable channel access and frame exchange between AP MLD 310 and non-AP MLD 320, which can increase data throughput and reduce latency. When associated with an AP MLD on a set of links (link establishment), each non-AP device is assigned a unique Association Identifier (AID).

[0076] The following documents are incorporated herein by reference in their entirety, as if fully set forth herein: i) IEEE 802.11-2020, “Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specification”, ii) IEEE 802.11ax-2021, “Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specification”, and ii) IEEE P802.11be / D4.0, “Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specification”.

[0077] When a user moves around the environment while holding the STA device, the signal strength from the STA to its connected AP can change. If the user's movement causes a significant decrease in signal strength, a handover may be necessary. During the handover process, the STA can switch from its currently associated AP to a new AP.

[0078] Figure 4The illustration shows the stages of a mobility handover process according to an embodiment. Figure 4 As shown, in a traditional device without any mobility support, the handover process may involve several steps, including detection phase 401, search phase 403, 802.11 authentication phase 405, 802.11 association phase 407, 802.1X authentication phase 409, and 802.11 resource reservation phase 411.

[0079] During detection phase 401, the STA can determine that a handover is necessary. The process for detecting the need for a handover can be vendor-specific. For example, a particular vendor implementation may choose to trigger a handover when the signal strength to the currently associated AP drops below a certain threshold.

[0080] The detection phase 401 can be followed by the search phase 403. During the search phase 403, the STA can search for new APs to associate with. During the search phase 403, the STA can perform a scan of different channels to identify nearby APs. This can be done passively, for example, by listening to beacons on a specific channel, or actively, for example, by using a probe request and response process.

[0081] After the scanning process is complete, the next step is to perform 802.11 authentication (based on Open Systems / Shared Key) 405. Once the STA is authenticated, the next step is to perform 802.11 association 807. The 802.1X authentication phase 409, introduced in the IEEE 802.1i amendment, can include EAP authentication between the STA and the AAA server with the assistance of the AP. Finally, during the 802.11 resource reservation phase 411, the STA can establish various resources at the new AP. For example, the STA can perform QoS reservations, BA establishment, etc., with the newly associated AP.

[0082] Typically, during handover, connections may be interrupted when the establishment process operates on a drop-before-reconnect basis. This can impact user experience, especially for multimedia services, which may suffer session interruptions due to the high latency encountered during handover.

[0083] To reduce handover latency, several procedures have been introduced into several standards. These procedures focus on eliminating or reducing latency encountered at various steps of the handover process. In 2008, the IEEE 802.11r standard introduced Fast Handover Roaming, which eliminates the need for an authentication step during handover. In 2011, IEEE 802.11k introduced Assisted Roaming, which reduces the search phase by allowing the STA to request the AP to send channel information for candidate neighbor APs. In 2011, IEEE 802.11v also introduced Network Assisted Roaming to assist the search phase. In IEEE 802.11be, the Fast BSS Handover procedure was extended to cover MLO operations. This procedure helps reduce latency encountered due to 802.11 resource reservations. However, the STA may still need to perform association and authentication phases that may take, for example, 10 ms.

[0084] In next-generation WLANs, low latency with high reliability support has become a target. To meet this goal, the concept of Logical Access Point (MAC) MLDs can be considered.

[0085] Figure 5 The illustration shows a logical AP MLD according to an embodiment. (As shown...) Figure 5 As shown, a logical AP MLD 501 can consist of several APs, including AP1 503-1, AP2 503-2, AP3 503-3, AP4 503-4 to APN 503-N, which can be non-coordinated. This may differ from the concept of an AP MLD in IEEE 802.11be, which considers coordinated APs attached to an AP MLD. Furthermore, one or more of these APs may have a common data path to a router or central controller. Figure 5 The APs 503-1 to 503-N shown can form a logical AP MLD 501. This concept of AP MLD can reduce the latency of the aforementioned association and authentication steps, because the STA may not need to perform association and authentication during handover.

[0086] During association, non-AP STAs can be assigned an Association Identifier (AID) value by an AP or AP MLD. This AID value can be used for reference purposes in multiple signaling operations. When multiple non-coordinated APs or AP MLDs form a logical AP MLD, problems can arise regarding AID space handling. Conventional procedures can select AIDs from a limited AID space of up to 2007 or 2006 available AID values. Furthermore, two non-AP STAs associated with an AP MLD should not have the same AID. However, since APs may be non-coordinated, overlap can exist in link IDs used by different APs in a logical AP MLD. Since AIDs can be used in many signaling operations, this can lead to confusion on the non-AP MLD side. Therefore, embodiments of this disclosure provide a process for AID allocation that addresses these problems.

[0087] In some examples, the number of AIDs can be increased by allocating additional bits to the AID field representation, which may be referred to herein as the AID space. In some examples, the AP MLD can have a fixed, higher number of bits used for AID representation. In some embodiments, the AP MLD can dynamically increase the bits used for AID representation to increase the number of feasible AID values. According to existing standards, the two most significant bits (MSBs) of the AID field are set to 1, and the 14 least significant bits (LSBs) of the AID field are used. Therefore, in some examples, one or more of the two MSBs of the AID field can be set to other values ​​(other than 1) to increase the AID space.

[0088] Figure 6 The illustration shows an increase in AID space according to an embodiment. As shown, the AID field comprises two octets. These two MSBs can be used to increase the AID space. Specifically, one or more of the two MSBs of the AID field can be set to other values ​​(excluding 1) to increase the AID space. 14 LSBs can be used in the baseline.

[0089] In some examples, when the AP performs dynamic incrementing of the AID space, the AP MLD is able to announce the change in one or more frames it sends (e.g., beacon frames, etc.).

[0090] In some examples, AP MLDs participating in logical AP MLD operations can divide the AID space among themselves. Each AP MLD can then select AID values ​​only from the portion of the AID space assigned to it.

[0091] Figure 7The diagram illustrates the AID space partitioning according to an embodiment. As shown, AP1, AP2, and AP3 form a Seamless Roaming Domain (SRD). Each AP is allocated a portion of the AID space, as shown: AID space 1 is allocated to the SRD, AID space 2 is allocated to AP1, AID space 3 is allocated to AP2, and AID space 4 is allocated to AP3. The allocated portions together are equal to the baseline AID space.

[0092] Figure 8 The diagram illustrates independent AID spaces according to an embodiment. As shown, AP1, AP2, and AP3 form an SRD. AID space 1 is assigned to the SRD, AID space 2 is assigned to AP1, AID space 3 is assigned to AP2, and AID space 4 is assigned to AP3. Each AID space is an independent AID space. Figure 8 As shown, a seamless roaming domain can also have its own AID space, and each AID space can be an independent AID space.

[0093] In some examples, the partitioning of the AID space can be accomplished based on a negotiation process. This process can involve sending a request frame that may include at least one or more of the information items indicated in Table 1.

[0094] [Table 1]

[0095]

[0096] The aforementioned information items can be sent together or separately. They can be sent as part of any existing frame / element / field / subfield in the standard or as part of a newly defined frame / element / field / subfield.

[0097] It can process request frames to generate response frames, which can include at least one or more of the information items indicated in Table 2.

[0098] [Table 2]

[0099]

[0100] The aforementioned information items can be sent together or separately. They can be sent as part of any existing frame / element / field / subfield in the standard or as part of a newly defined frame / element / field / subfield.

[0101] In some examples, when partitioning the AID space, AP MLDs can select AID values ​​from the portion of the AID space allocated to them. Other values ​​not allocated to an AP MLD can be considered reserved for that AP MLD.

[0102] In some examples, the AID value can be combined with one or more parameters that help distinguish between duplicate AID values. These parameters can be one or more of the parameters provided in Table 3.

[0103] [Table 3]

[0104]

[0105] The aforementioned information items can be added to signaling that includes the AID value by utilizing existing reserved bits, existing unused bits, or by adding additional bits to the frame.

[0106] In some examples, the AID value assigned to a non-AP STA can be used in conjunction with one or more information items indicated in Table 3 for the logical AP MLD. In some examples, a modified AID element can be used when the device is associated with a logical AP MLD.

[0107] Figure 9 The illustration shows a modified AID element format according to an embodiment. The modified AID element includes an element ID field, a length field, an element ID extension field, an AID field, and a roaming ID field. The element ID field may include an identifier for the element. The length field may include length information for the element. The element ID extension field can provide extended information about the element. The AID field can provide the element's AID. The roaming ID field may include information that can be used with the AID for differentiation. In some examples, the roaming ID can be an MLD ID assigned to an AP MLD that is part of a logical AP MLD. When a device is associated with a logical AP MLD, the roaming ID can be the roaming ID of the device through the AP or AP MLD it is associated with. In some examples, the roaming ID can be assigned at association and can remain fixed during the operation of the device with the logical AP MLD. In some examples, the roaming ID can be a unique ID assigned to a seamless roaming domain, such as an ID, MAC address, etc. In some examples, if a MAC address is used, the size can be different (e.g., 6 octets, etc.).

[0108] Figure 10 The illustration shows a flowchart of an example process for allocating a portion of the AID space performed by the AP according to an embodiment. Although one or more operations are described or illustrated in a specific order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations in at least partially overlapping time periods. Figure 10 The flowchart depicted in the diagram illustrates the process in AP MLD (such as...) Figure 3 The operations performed in the AP MLD shown.

[0109] In operation 1001, process 1000 involves the first AP MLD sending a first frame to the second AP MLD requesting an allocation of the Associated Identifier (AID) space. In some examples, the first AP MLD and the second AP MLD form a logical AP multi-link device (MLD). In some examples, the AID field is 16 bits, and the two most significant bits of the AID field are used to increment the AID space by setting one or more of the two MSBs to a value other than 1. In some examples, the first frame indicates a pair of integer values ​​indicating the start and end of the AID space requested by the first AP MLD, or an indication of the start and end bits in the AID field from which the first AP MLD can select the AID value. In some examples, when the first AP MLD performs dynamic incrementing of the AID space, the first AP MLD may announce the change in one or more frames it sends (e.g., beacon frames, etc.).

[0110] In operation 1003, the first AP MLD receives a second frame from the second AP MLD in response to the first frame. This second frame allocates a portion of the AID space to the first AP MLD. In some examples, the second frame indicates the portion of the AID space that the first AP MLD is authorized to use. In some examples, the AP MLDs participating in the logical AP MLD are able to divide the AID space among themselves. Each AP MLD is then able to select AID values ​​only from the portion of the AID space allocated to it.

[0111] In operation 1005, the first AP MLD assigns one or more AID values ​​from a portion of the AID space allocated to the first AP MLD to one or more STAs. In some examples, the AID values ​​can be combined with one or more parameters that can help distinguish between duplicate AID values. Parameters may include an MLD identifier, which includes information items that can be used to represent an AP as part of the logical AP MLD. The information items can be used with the AID for differentiation (e.g., MLD MAC address, MLD ID, etc.). The parameter may include a co-located AP identifier, which can be an information item that can be used to indicate one or more co-located APs as part of the logical AP MLD. For example, there can be co-located AP identifiers that can be assigned to co-located APs as part of the logical AP MLD. This can be used with the AID for differentiation. The parameter may include one or more distinct identifiers, which can be information items that can be any distinct identifier unique to the entity in which all co-located APs exist. For example, identifiers of seamless roaming domains, such as unique IDs, MAC addresses, and other identifiers.

[0112] The embodiments in this disclosure can be applied to other features, such as relay operations, MAP operations, etc., and are therefore not necessarily limited to mobility management. Embodiments of this disclosure provide a process for managing the AID value of a logical AP MLD, which can reduce association and authentication latency during handover processes and improve relay operations between mobility management, multi-AP coordination, and various other wireless network operations.

[0113] Unless otherwise specified, references to elements in the singular form are not intended to indicate one and only one, but rather one or more. For example, a “one” module can refer to one or more modules. In the absence of further constraints, elements preceded by “a,” “an,” “the,” or “the” do not preclude the presence of additional identical elements.

[0114] Titles and subtitles (if any) are used for convenience only and do not limit the invention. The terms "exemplary" are used to indicate that they are intended as examples or illustrations. Within the scope of the use of terms such as "comprising," "having," etc., such terms are intended to be inclusive in a manner similar to the term "comprising," as "comprising" is interpreted when used as a transitional word in the claims. Relational terms such as "first" and "second" may be used to distinguish one entity or action from another without necessarily requiring or implying any actual such relationship or order between these entities or actions.

[0115] Phrases such as aspect, that aspect, on the other hand, some aspects, one or more aspects, implementation, that implementation, another implementation, some implementations, one or more implementations, embodiment, that embodiment, another embodiment, some examples, one or more embodiments, configuration, that configuration, another configuration, some configurations, one or more configurations, subject matter, disclosure, this disclosure, other variations thereof, etc., are used for convenience and do not imply that disclosures associated with such phrases are essential to the subject matter, or that such disclosures apply to all configurations of the subject matter. Disclosures associated with such phrases may apply to all configurations or one or more configurations. Disclosures associated with such phrases may provide one or more examples. Phrases such as aspect or some aspects may refer to one or more aspects, and vice versa, and this similarly applies to other foregoing phrases.

[0116] The phrase "at least one" preceding a series of items, separated by the terms "and" or "or," modifies the list as a whole, rather than each member of the list. The phrase "at least one of..." does not require the selection of at least one item; rather, it allows for the inclusion of at least one of any one item, and / or at least one of any combination of items, and / or at least one of each item. For example, each of the phrases "at least one of A, B, and C" or "at least one of A, B, or C" refers to only A, only B, or only C; any combination of A, B, and C; and / or at least one of each of A, B, and C.

[0117] It should be understood that the specific order or hierarchy of the disclosed steps, operations, or processes is an illustration of exemplary methods. Unless otherwise expressly stated, it should be understood that the specific order or hierarchy of steps, operations, or processes may be performed in a different order. Some steps, operations, or processes may be performed simultaneously, or may be performed as part of one or more other steps, operations, or processes. The appended method claims (if any) present elements of various steps, operations, or processes in a sample order, but this does not imply limitation to the specific order or hierarchy presented. These may be performed serially, linearly, in parallel, or in different orders. It should be understood that the described instructions, operations, and systems can generally be integrated together into a single software / hardware product or packaged into multiple software / hardware products.

[0118] This disclosure is provided to enable any person skilled in the art to practice the various aspects described herein. In some cases, well-known structures and components are illustrated in block diagram form to avoid obscuring the concepts of the subject matter. This disclosure provides various examples of the subject matter, and the subject matter is not limited to these examples. Various modifications to these aspects will be apparent to those skilled in the art, and the principles described herein can be applied to other aspects.

[0119] All elements of the various aspects described herein, and all structural and functional equivalents known now or hereafter to a person skilled in the art, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims. No claim element is to be interpreted pursuant to paragraph 6 of 35 USC §112 unless it is expressly stated using the phrase “means for…” or, in the case of a method claim, using the phrase “steps for…”.

[0120] The title, background information, description of the drawings, abstract, and figures are incorporated herein by reference and are provided as illustrative examples rather than as limiting descriptions. It should be understood at the time of filing that they are not intended to limit the scope or meaning of the claims. Furthermore, in the detailed description, it will become apparent that the description provides illustrative examples and that various features are combined in various embodiments for the purpose of simplifying the disclosure. The approach of this disclosure should not be construed as reflecting an intention to require more features than expressly recited in each claim. Rather, as reflected in the following claims, the inventive subject matter lies in all features of fewer than those in a single disclosure configuration or operation. The appended claims are incorporated herein by reference, wherein each claim is independently claimed as a separate subject matter.

[0121] The claims are not intended to be limited to the aspects described herein, but rather to conform to the full scope consistent with the language claims and to include all legal equivalents. Nevertheless, no claim is intended to include subject matter that does not meet the requirements of applicable patent law, nor should they be interpreted in this manner.

Claims

1. A first access point (AP) multi-link device (MLD) (101) in a wireless network, comprising: Memory (229); as well as Processor (224), coupled to the memory, the processor is configured to: The first frame is sent to the second AP MLD to request the associated identifier (AID), wherein the first AP MLD and the second AP MLD form a seamless roaming domain; A second frame is received from the second AP MLD in response to the first frame, the second frame assigning the aforementioned portion of the AID to the first AP MLD; and One or more AIDs from the portion of the AIDs assigned to the first AP MLD are assigned to one or more stations (STAs).

2. The first AP of claim 1 or claim 2, wherein, The first frame indicates i) a pair of integer values ​​indicating the start and end of the AID that the first AP MLD is requesting, ii) the start and end bits of the AID field from which the first AP MLD is requesting the AID that can be selected, iii) the number of AIDs that the first AP MLD is requesting, or iv) the value of the AID that the first AP MLD is requesting.

3. The first AP according to any one of the preceding claims, wherein, The second frame indicates i) a pair of integer values ​​indicating the start and end of the AIDs authorized by the first AP MLD, ii) the start bit value and end bit of the AID field from which the first AP MLD is allowed to select AIDs, iii) the number of AIDs authorized by the first AP MLD, or iv) the value of the AIDs authorized by the first AP MLD.

4. The first AP according to any one of the preceding claims, wherein, The processor (224) is also configured to send a third frame that increases the number of notification AIDs.

5. The first AP according to any one of the preceding claims, wherein, The first AP MLD and the second AP MLD are not parallel.

6. The first AP according to any one of the preceding claims, wherein, The number of AIDs is increased by using the two most significant bits of the AID field.

7. The first AP according to any one of the preceding claims, wherein, One or more of the two most significant bits of the AID field are set to a value other than 1.

8. The first AP according to any one of the preceding claims, wherein, The number of AIDs is increased by allocating additional bits to the AID field.

9. A first access point (AP) multi-link device (MLD) (101) in a wireless network, comprising: Memory (229); as well as Processor (224), coupled to the memory, the processor is configured to: The first frame is received from the second AP MLD, which is a portion of the request association identifier (AID), wherein the first AP MLD and the second AP MLD form a seamless roaming domain; In response to the first frame, a second frame is sent to the second AP MLD to assign the portion of the AID to the second AP MLD.

10. The first AP according to claim 9, wherein, The first frame indicates: i) a pair of integer values ​​indicating the start and end of the AID that the second AP MLD is requesting, ii) the start and end bits of the AID field from which the second AP MLD is requesting the AID that can be selected, iii) the number of AIDs that the second AP MLD is requesting, or iv) the value of the AID that the second AP MLD is requesting.

11. The first AP according to claim 9 or claim 10, wherein, The second frame indicates: i) a pair of integer values ​​indicating the start and end of the AIDs authorized by the second AP MLD, ii) the start bit value and end bit of the AID field from which the second AP MLD is allowed to select AIDs, iii) the number of AIDs authorized by the second AP MLD, or iv) the value of the AIDs authorized by the second AP MLD.

12. The first AP according to any one of claims 9 to 11, wherein, The processor (224) is also configured to send a third frame that increases the number of notification AIDs.

13. The first AP according to any one of claims 9 to 12, wherein the first AP MLD and the second AP MLD are not juxtaposed.

14. The first AP according to any one of claims 9 to 13, wherein, The number of AIDs is increased by using the two most significant bits of the AID field.

15. A computer-implemented method for wireless communication by a first access point (AP) multilink device (MLD) (101) in a network, comprising: The first frame is sent to the second AP MLD to request the associated identifier (AID), wherein the first AP MLD and the second AP MLD form a seamless roaming domain; Receive a second frame from the second AP MLD in response to the first frame, the second frame assigning the aforementioned portion of the AID to the first AP MLD; and One or more AIDs from the portion of the AIDs assigned to the first AP MLD are assigned to one or more stations (STAs).

Images