NON-COLLOCATION AFFILIATION INDICATION FOR WIRELESS NETWORKS

Abstract

In an embodiment, an access point (AP) may provide an indication regarding whether an AP whose information is provided to a station (STA) is a part of the seamless roaming domain with its current physical AP or AP MLD or not, which signaling may be useful for the STA to know when roaming to a new AP or AP MLD.

Description

TECHNICAL FIELD

This disclosure relates generally to a wireless communication system, and more particularly to, for example, but not limited to, non-collocation affiliation indication for wireless networks.

BACKGROUND

Wireless local area network (WLAN) technology has evolved toward increasing data rates and continues its growth in various markets such as home, enterprise and hotspots over the years since the late 1990s. WLAN allows devices to access the internet in the 2.4 GHZ, 5 GHZ, 6 GHz or 60 GHz frequency bands. WLANs are based on the Institute of Electrical and Electronic Engineers (IEEE) 802.11 standards. IEEE 802.11 family of standards aims to increase speed and reliability and to extend the operating range of wireless networks.

WLAN devices are increasingly required to support a variety of delay-sensitive applications or real-time applications such as augmented reality (AR), robotics, artificial intelligence (AI), cloud computing, and unmanned vehicles. To implement extremely low latency and extremely high throughput required by such applications, multi-link operation (MLO) has been suggested for the WLAN. The WLAN is formed within a limited area such as a home, school, apartment, or office building by WLAN devices. Each WLAN device may have one or more stations (STAs) such as the access point (AP) STA and the non-access-point (non-AP) STA.

The MLO may enable a non-AP multi-link device (MLD) to set up multiple links with an AP MLD. Each of multiple links may enable channel access and frame exchanges between the non-AP MLD and the AP MLD independently, which may reduce latency and increase throughput.

The description set forth in the background section should not be assumed to be prior art merely because it is set forth in the background section. The background section may describe aspects or embodiments of the present disclosure.

SUMMARY

One aspect of the present disclosure provides a first access point (AP) in a wireless network, comprising: a memory; and a processor coupled to the memory. The processor is configured to transmit, to a station (STA), a frame that includes an indication of whether a particular AP is a part of a seamless roaming domain and an identifier of the seamless roaming domain when the particular AP is a part of the seamless roaming domain.

In some embodiments, the identifier media access control (MAC) address.

In some embodiments, the particular AP is the first AP or a second AP.

In some embodiments, the particular AP is a second AP, wherein the frame includes an indication that indicates if the first AP is a part of the same seamless roaming domain as the second AP

In some embodiments, the frame is a management frame.

In some embodiments, the frame includes a reduced neighbor report (RNR) element that includes one or more of the indication of whether the particular AP is a part of the seamless roaming domain or the identifier of the seamless roaming domain when the particular AP is a part of the seamless roaming domain.

In some embodiments, the identifier of the seamless roaming domain is set to a basic service set (BSS) identifier.

In some embodiments, the seamless roaming domain provides seamless roaming between APs that are a part of the seamless roaming domain.

In some embodiments, the first AP and the particular AP are non-collocated.

In some embodiments, the identifier of the seamless roaming domain is the same as an identifier for the first AP.

One aspect of the present disclosure provides a computer-implemented method for communication by a first access point (AP) in a wireless network. The method comprises transmitting, to a station (STA), a frame that includes an indication of whether a particular AP is a part of a seamless roaming domain and an identifier of the seamless roaming when the particular AP is a part of the seamless roaming domain.

In some embodiments, the identifier is a media access control (MAC) address.

In some embodiments, the particular AP is the first AP or a second AP.

In some embodiments, the particular AP is a second AP, wherein the frame includes an indication that indicates if the first AP is a part of the same seamless roaming domain as the second AP.

In some embodiments, the frame is a management frame.

In some embodiments, the frame includes a reduced neighbor report (RNR) element that includes one or more of the indication of whether the particular AP is a part of the seamless roaming domain or the identifier of the seamless roaming domain when the particular AP is a part of the seamless roaming domain.

In some embodiments, the identifier of the seamless roaming domain is set to a basic service set (BSS) identifier.

In some embodiments, the seamless roaming domain provides seamless roaming between APs that are a part of the seamless roaming domain.

In some embodiments, the first AP and the particular AP are non-collocated.

In some embodiments, the identifier of the seamless roaming domain is the same as an identifier for the first AP.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a wireless network in accordance with an embodiment.

FIG. 2A illustrates an example of AP in accordance with an embodiment.

FIG. 2B illustrates an example of STA in accordance with an embodiment.

FIG. 3 illustrates an example of multi-link communication operation in accordance with an embodiment.

FIG. 4 illustrates stages of a mobility handover procedure in accordance with an embodiment.

FIG. 5 illustrates a logical AP MLD in accordance with an embodiment.

FIG. 6 illustrates a seamless roaming domain (SRD) in accordance with an embodiment.

FIG. 7 illustrates a logical AP MLD indication in accordance with an embodiment.

FIG. 8 illustrates a logical AP MLD identifier in accordance with an embodiment.

FIG. 9 illustrates a same logical AP MLD affiliation indication in accordance with an embodiment.

FIG. 10 illustrates a logical AP MLD indication element in accordance with an embodiment.

FIG. 11 illustrates a format of a logical AP MLD information field in accordance with an embodiment.

FIG. 12 illustrates a modified target beacon transmission time (TBTT) information field in accordance with an embodiment.

FIG. 13 illustrates a logical AP MLD parameters subfield format in accordance with an embodiment.

FIG. 14 illustrates a modified BSSID Information field in accordance with an embodiment.

FIG. 15 illustrates a flow chart of an example process performed by a first AP of providing an indication of whether a particular AP is part of a logical AP MLD in accordance with an embodiment.

In one or more implementations, not all of the depicted components in each figure may be required, and one or more implementations may include additional components not shown in a figure. Variations in the arrangement and type of the components may be made without departing from the scope of the subject disclosure. Additional components, different components, or fewer components may be utilized within the scope of the subject disclosure.

DETAILED DESCRIPTION

The detailed description set forth below, in connection with the appended drawings, is intended as a description of various implementations and is not intended to represent the only implementations in which the subject technology may be practiced. Rather, the detailed description includes specific details for the purpose of providing a thorough understanding of the inventive subject matter. As those skilled in the art would realize, the described implementations may be modified in various ways, all without departing from the scope of the present disclosure. Accordingly, the drawings and description are to be regarded as illustrative in nature and not restrictive. Like reference numerals designate like elements.

The following description is directed to certain implementations for the purpose of describing the innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. The examples in this disclosure are based on WLAN communication according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, including IEEE 802.11be standard and any future amendments to the IEEE 802.11 standard. However, the described embodiments may be implemented in any device, system or network that is capable of transmitting and receiving radio frequency (RF) signals according to the IEEE 802.11 standard, the Bluetooth standard, Global System for Mobile communications (GSM), GSM/General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband-CDMA (W-CDMA), Evolution Data Optimized (EV-DO), 1×EV-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 that are used to communicate within a wireless, cellular or internet of things (IoT) network, such as a system utilizing 3G, 4G, 5G, 6G, or further implementations thereof, technology.

Depending on the network type, other well-known terms may be used instead of “access point” or “AP,” such as “router” or “gateway.” For the sake of convenience, the term “AP” is used in this disclosure to refer to network infrastructure components that provide wireless access to remote terminals. In WLAN, given that the AP also contends for the wireless channel, the AP may also be referred to as a STA. Also, 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 the sake of convenience, the terms “station” and “STA” are used in this disclosure to refer to remote wireless equipment 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 telephone or smartphone) or is normally considered a stationary device (such as a desktop computer, AP, media player, stationary sensor, television, etc.).

Multi-link operation (MLO) is a key feature that is currently being developed by the standards body for next generation extremely high throughput (EHT) Wi-Fi systems in IEEE 802.11be. The Wi-Fi devices that support MLO are referred to as multi-link devices (MLD). With MLO, it is possible for a non-AP MLD to discover, authenticate, associate, and set up multiple links with an AP MLD. Channel access and frame exchange is possible on each link between the AP MLD and non-AP MLD.

FIG. 1 shows an example of a wireless network 100 in accordance with an embodiment. The embodiment of the wireless network 100 shown in FIG. 1 is for illustrative purposes only. Other embodiments of the wireless network 100 could be used without departing from the scope of this disclosure.

As shown in FIG. 1, the wireless network 100 may include a plurality of wireless communication devices. Each wireless communication device may include one or more stations (STAs). The STA may be a logical entity that is a singly addressable instance of a medium access control (MAC) layer and a physical (PHY) layer interface to the wireless medium. The STA may be classified into an access point (AP) STA and a non-access point (non-AP) STA. The AP STA may be an entity that provides access to the distribution system service via the wireless medium for associated STAs. The non-AP STA may be a STA that is not contained within an AP-STA. For the sake of simplicity of description, an AP STA may be referred to as an AP and a non-AP STA may be referred to as a STA. In the example of FIG. 1, APs 101 and 103 are wireless communication devices, each of which may include one or more AP STAs. In such embodiments, APs 101 and 103 may be AP multi-link device (MLD). Similarly, STAs 111-114 are wireless communication devices, each of which may include one or more non-AP STAs. In such embodiments, STAs 111-114 may be non-AP MLD.

The 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. The AP 101 provides wireless access to the network 130 for a plurality of stations (STAs) 111-114 with a coverage are 120 of the AP 101. The APs 101 and 103 may communicate with each other and with the STAs using Wi-Fi or other WLAN communication techniques.

Depending on the network type, other well-known terms may be used instead of “access point” or “AP,” such as “router” or “gateway.” For the sake of convenience, the term “AP” is used in this disclosure to refer to network infrastructure components that provide wireless access to remote terminals. In WLAN, given that the AP also contends for the wireless channel, the AP may also be referred to as a STA. Also, 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 the sake of convenience, the terms “station” and “STA” are used in this disclosure to refer to remote wireless equipment 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 telephone or smartphone) or is normally considered a stationary device (such as a desktop computer, AP, media player, stationary sensor, television, etc.).

In FIG. 1, dotted lines show the approximate extents of the coverage area 120 and 125 of APs 101 and 103, which are shown as approximately circular for the purposes of illustration and explanation. It should be clearly understood that coverage areas associated with APs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the APs.

As described in more detail below, one or more of the APs may include circuitry and/or programming for management of MU-MIMO and OFDMA channel sounding in WLANs. Although FIG. 1 shows one example of a wireless network 100, various changes may be made to FIG. 1. For example, the wireless network 100 could include any number of APs and any number of STAs in any suitable arrangement. Also, the AP 101 could communicate directly with any number of STAs and provide those STAs with wireless broadband access to the network 130. Similarly, each AP 101 and 103 could communicate directly with the network 130 and provides STAs with direct wireless broadband access to the network 130. Further, the APs 101 and/or 103 could provide access to other or additional external networks, such as external telephone networks or other types of data networks.

FIG. 2A shows an example of AP 101 in accordance with an embodiment. The embodiment of the AP 101 shown in FIG. 2A is for illustrative purposes, and the AP 103 of FIG. 1 could have the same or similar configuration. However, APs come in a wide range of configurations, and FIG. 2A does not limit the scope of this disclosure to any particular implementations of an AP.

As shown in FIG. 2A, the 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. The AP 101 also may include a controller/processor 224, a memory 229, and a backhaul or network interface 234. The RF transceivers 209a-209n receive, from the antennas 204a-204n, incoming RF signals, such as signals transmitted by STAs in the network 100. The 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 the RX processing circuitry 219, which generates processed baseband signals by filtering, decoding, and/or digitizing the baseband or IF signals. The RX processing circuitry 219 transmits the processed baseband signals to the controller/processor 224 for further processing.

The TX processing circuitry 214 receives analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller/processor 224. The TX processing circuitry 214 encodes, multiplexes, and/or digitizes the outgoing baseband data to generate processed baseband or IF signals. The RF transceivers 209a-209n receive the outgoing processed baseband or IF signals from the TX processing circuitry 214 and up-converts the baseband or IF signals to RF signals that are transmitted via the antennas 204a-204n.

The controller/processor 224 can include one or more processors or other processing devices that control the overall operation of the AP 101. For example, the controller/processor 224 could control the reception of uplink signals and the transmission of downlink signals by the RF transceivers 209a-209n, the RX processing circuitry 219, and the TX processing circuitry 214 in accordance with well-known principles. The controller/processor 224 could support additional functions as well, such as more advanced wireless communication functions. For instance, the controller/processor 224 could support beam forming or directional routing operations in which outgoing signals from multiple antennas 204a-204n are weighted differently to effectively steer the outgoing signals in a desired direction. The controller/processor 224 could also support OFDMA operations in which outgoing signals are assigned to different subsets of subcarriers for different recipients (e.g., different STAs 111-114). Any of a wide variety of other functions could be supported in the AP 101 by the controller/processor 224 including a combination of DL MU-MIMO and OFDMA in the same transmit opportunity. In some embodiments, the controller/processor 224 may include at least one microprocessor or microcontroller. The controller/processor 224 is also capable of executing programs and other processes resident in the memory 229, such as an OS. The controller/processor 224 can move data into or out of the memory 229 as required by an executing process.

The controller/processor 224 is also coupled to the backhaul or network interface 234. The backhaul or network interface 234 allows the AP 101 to communicate with other devices or systems over a backhaul connection or over a network. The interface 234 could support communications over any suitable wired or wireless connection(s). For example, the interface 234 could allow the AP 101 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface 234 may include any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or RF transceiver. The memory 229 is coupled to the controller/processor 224. Part of the memory 229 could include a RAM, and another part of the memory 229 could include a Flash memory or other ROM.

As described in more detail below, the AP 101 may include circuitry and/or programming for management of channel sounding procedures in WLANs. Although FIG. 2A illustrates one example of AP 101, various changes may be made to FIG. 2A. For example, the AP 101 could include any number of each component shown in FIG. 2A. As a particular example, an AP could include a number of interfaces 234, and the controller/processor 224 could support routing functions to route data between different network addresses. As another example, while shown as including a single instance of TX processing circuitry 214 and a single instance of RX processing circuitry 219, the AP 101 could include multiple instances of each (such as one per RF transceiver). Alternatively, only one antenna and RF transceiver path may be included, such as in legacy APs. Also, various components in FIG. 2A could be combined, further subdivided, or omitted and additional components could be added according to particular needs.

As shown in FIG. 2A, in some embodiment, the AP 101 may be an AP MLD that includes multiple APs 202a-202n. Each AP 202a-202n is affiliated with the 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 APs 202a-202n may independently communicate with the controller/processor 224 and other components of the AP MLD 101. FIG. 2A shows that each AP 202a-202n has separate multiple antennas, but each AP 202a-202n can share multiple antennas 204a-204n without needing separate multiple antennas. Each AP 202a-202n may represent a physical (PHY) layer and a lower media access control (MAC) layer.

FIG. 2B shows an example of STA 111 in accordance with an embodiment. The embodiment of the STA 111 shown in FIG. 2B is for illustrative purposes, and the STAs 111-114 of FIG. 1 could have the same or similar configuration. However, STAs come in a wide variety of configurations, and FIG. 2B does not limit the scope of this disclosure to any particular implementation of a STA.

As shown in FIG. 2B, the STA 111 may include antenna(s) 205, a RF transceiver 210, TX processing circuitry 215, a microphone 220, and RX processing circuitry 225. The STA 111 also may 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.

The RF transceiver 210 receives, from the antenna(s) 205, an incoming RF signal transmitted by an AP of the network 100. The RF transceiver 210 down-converts the incoming RF signal to generate an IF or baseband signal. The IF or baseband signal is sent to the RX processing circuitry 225, which generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuitry 225 transmits the processed baseband signal to the speaker 230 (such as for voice data) or to the controller/processor 240 for further processing (such as for web browsing data).

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

The controller/processor 240 can include one or more processors and execute the basic OS program 261 stored in the memory 260 in order to control the overall operation of the STA 111. In one such operation, the controller/processor 240 controls the reception of downlink signals and the transmission of uplink signals by the RF transceiver 210, the RX processing circuitry 225, and the TX processing circuitry 215 in accordance with well-known principles. The controller/processor 240 can also include processing circuitry configured to provide management of channel sounding procedures in WLANs. In some embodiments, the controller/processor 240 may include at least one microprocessor or microcontroller.

The controller/processor 240 is also capable of executing other processes and programs resident in the memory 260, such as operations for management of channel sounding procedures in WLANs. The controller/processor 240 can move data into or out of the memory 260 as required by an executing process. In some embodiments, the controller/processor 240 is configured to execute a plurality of applications 262, such as applications for channel sounding, including feedback computation based on a received null data packet announcement (NDPA) and null data packet (NDP) and transmitting the beamforming feedback report in response to a trigger frame (TF). The controller/processor 240 can operate the plurality of applications 262 based on the OS program 261 or in response to a signal received from an AP. The controller/processor 240 is also coupled to the I/O interface 245, which provides STA 111 with the ability to connect to other devices such as laptop computers and handheld computers. The I/O interface 245 is the communication path between these accessories and the main controller/processor 240.

The controller/processor 240 is also coupled to the input 250 (such as touchscreen) and the display 255. The operator of the STA 111 can use the input 250 to enter data into the STA 111. The display 255 may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and/or at least limited graphics, such as from web sites. The memory 260 is coupled to the controller/processor 240. Part of the memory 260 could include a random access memory (RAM), and another part of the memory 260 could include a Flash memory or other read-only memory (ROM).

Although FIG. 2B shows one example of STA 111, various changes may be made to FIG. 2B. For example, various components in FIG. 2B could be combined, further subdivided, or omitted and additional components could be added according to particular needs. In particular examples, the STA 111 may include any number of antenna(s) 205 for MIMO communication with an AP 101. In another example, the STA 111 may not include voice communication or the controller/processor 240 could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Also, while FIG. 2B illustrates the STA 111 configured as a mobile telephone or smartphone, STAs could be configured to operate as other types of mobile or stationary devices.

As shown in FIG. 2B, in some embodiment, the STA 111 may be a non-AP MLD that includes multiple STAs 203a-203n. Each STA 203a-203n is affiliated with the non-AP MLD 111 and includes an antenna(s) 205, a RF transceiver 210, TX processing circuitry 215, and RX processing circuitry 225. Each STAs 203a-203n may independently communicate with the controller/processor 240 and other components of the non-AP MLD 111. FIG. 2B shows that each STA 203a-203n has a separate antenna, but each STA 203a-203n can share the antenna 205 without needing separate antennas. Each STA 203a-203n may represent a physical (PHY) layer and a lower media access control (MAC) layer.

FIG. 3 shows an example of multi-link communication operation in accordance with an embodiment. The multi-link communication operation may be usable in IEEE 802.11be standard and any future amendments to IEEE 802.11 standard. In FIG. 3, an AP MLD 310 may be the wireless communication device 101 and 103 in FIG. 1 and a non-AP MLD 220 may be one of the wireless communication devices 111-114 in FIG. 1.

As shown in FIG. 3, the AP MLD 310 may include a plurality of affiliated APs, for example, including AP 1, AP 2, and AP 3. Each affiliated AP may include a PHY interface to wireless medium (Link 1, Link 2, or Link 3). The AP MLD 310 may include a single MAC service access point (SAP) 318 through which the affiliated APs of the AP MLD 310 communicate with a higher layer (Layer 3 or network layer). Each affiliated AP of the AP MLD 310 may have a MAC address (lower MAC address) different from any other affiliated APs of the AP MLD 310. The AP MLD 310 may have a MLD MAC address (upper MAC address) and the affiliated APs share the single MAC SAP 318 to Layer 3. Thus, the affiliated APs share a single IP address, and Layer 3 recognizes the AP MLD 310 by assigning the single IP address.

The non-AP MLD 320 may include a plurality of affiliated STAs, for example, including 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). The non-AP MLD 320 may include a single MAC SAP 328 through which the affiliated STAs of the non-AP MLD 320 communicate with a higher layer (Layer 3 or network layer). Each affiliated STA of the non-AP MLD 320 may have a MAC address (lower MAC address) different from any other affiliated STAs of the non-AP MLD 320. The non-AP MLD 320 may have a MLD MAC address (upper MAC address) and the affiliated STAs share the single MAC SAP 328 to Layer 3. Thus, the affiliated STAs share a single IP address, and Layer 3 recognizes the non-AP MLD 320 by assigning the single IP address.

The AP MLD 310 and the non-AP MLD 320 may set up multiple links between their affiliate APs and STAs. In this example, the AP 1 and the STA 1 may set up Link 1 which operates in 2.4 GHz band. Similarly, the AP 2 and the STA 2 may set up Link 2 which operates in 5 GHZ band, and the AP 3 and the STA 3 may set up Link 3 which operates in 6 GHz band. Each link may enable channel access and frame exchange between the AP MLD 310 and the non-AP MLD 320 independently, which may increase date throughput and reduce latency. Upon associating with an AP MLD on a set of links (setup links), each non-AP device is assigned a unique association identifier (AID).

The following documents are hereby incorporated by reference in their entirety into the present disclosure as if fully set forth herein: i) IEEE 802.11-2020, “Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications,” ii) IEEE 802.11ax-2021, “Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications,” and ii) IEEE P802.11bc/D4.0, “Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications.”

As users move around an environment while holding an STA device, a signal strength of the STA to its connected AP can vary. If a user movement causes a significant decrease in a signal strength, a handover may be necessary. During the process of handover, an STA may switch from its current associated AP to a new AP.

FIG. 4 illustrates stages of a mobility handover procedure in accordance with an embodiment. As shown in FIG. 4, in legacy devices without any mobility support, the handover procedure may involve several steps, including a detection phase 401, a search phase 403, an 802.11 authentication phase 405, an 802.11 association phase 407, an 802.1X authentication phase 409, and a 802.11 resource reservation phase 411.

During the detection phase 401, an STA may determine that there is a need for a handover. The procedures to detect a need for handover may be vendor specific. For instance, a particular vendor implementation can choose to trigger handover when the signal strength to the currently associated AP drops below a certain threshold.

The detection phase 401 may be followed by a search phase 403. During the search phase 403, the STA may search for new APs to associate with. During the search phase 403, the STA may perform a scan of different channels to identify APs in the vicinity. This can be done cither passively, for example, by listening to beacons on a particular channel, or actively, for example, by the use of probe request and response procedure.

After the scanning procedure is complete, the next step is to perform 802.11 authentication (open system/shared key based) 405. Once the STA is authenticated, the next step is to perform 802.11 association 807. Introduced in IEEE 802.1i amendment, the 802.1X authentication phase 409 may include an EAP authentication between the STA and a AAA server with the assistance of the AP. Finally, during the 802.11 resource reservation phase 411, the STA may set up various resources at the new AP. For example, the STA can perform QoS reservation, BA setup, among other operations with the newly associated AP.

Typically, during a handover, there can be a disruption in the connection as the setup procedure operates in a break-before-make manner. This can cause an impact on user experience especially with multimedia services which can suffer from session disruptions due to the high delay encountered during handover procedure.

In order to reduce the handover delay, a number of procedures have been introduced in several standards. The focus of these procedures may be to remove or reduce the delay encountered in various steps of the handover procedure. In 2008, IEEE 802.11r standard introduced a fast transition roaming which may eliminate the need for the authentication step during the 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 of 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 transition procedure was extended to cover the case of MLO operation. This procedure helps to reduce the delays encountered due to 802.11 resource reservation. However, the STA may still need to perform the association and authentication phases which can take e.g., 10 s of ms.

In next generation WLANs, low-latency with high reliability support has been targeted. In order to meet this goal, the concept of a logical AP MLD can be considered.

FIG. 5 illustrates a logical AP MLD in accordance with an embodiment. As illustrated in FIG. 5, a logical AP MLD 501 can be made up of several APs, including AP1 503-1, AP2 503-2, AP3 503-3, AP4 503-4 to APN 503-N, which can be non-collocated. This may be different from the concept of AP MLD in IEEE 802.11be which considers collocated APs affiliated with an AP MLD. Further, one or more of these APs can have a common data path to a router or a central controller. The APs 503-1 to 503-N shown in FIG. 5 can form a logical AP MLD 501. This concept of AP MLD may reduce the delays of association and authentication steps mentioned above as the STA may not need to perform association and authentication during handover.

A logical AP MLD can also be used for a number of purposes including mobility management, multi-AP coordination, relay operations, among others. As described herein, the term logical AP MLD may refer to a coordination that may be established between APs to achieve a seamless roaming (e.g., seamless roaming domain, enhancement to baseline FT procedures, non-collocated AP MLD, among others).

Embodiments in accordance with this disclosure may provide an indication regarding whether an AP whose information is provided to the STA is a part of the logical AP MLD with its current physical AP or AP MLD or not. This signaling may be useful for the STA to know the procedure to use when roaming to a new AP or AP MLD. Embodiments in accordance with this disclosure may provide information regarding the non-collocation based affiliation which can be useful for the non-AP MLD. As described herein, an AP may refer to an AP or an AP MLD.

FIG. 6 illustrates a seamless roaming domain (SRD) in accordance with an embodiment. As illustrated, the SRD 1 includes several APs, including AP1, AP2, AP3 and AP4. The SRD 2 includes AP5 and AP6. As illustrated, STA communicates with the SRD1, whereby AP1 provides information on AP2-AP6. Several side issues may include, for example, whether all the APs are part of the same seamless domain and which APs are collocated with which other APs.

Accordingly, in some embodiments, the information that is reported about a particular AP can be tagged with an information item that can indicate if the reported AP is a part of a logical AP MLD. If the reported AP is part of a logical AP MLD, information can be provided regarding whether the AP is a part of the same logical AP MLD that the reporting AP is a part of.

In some embodiments, an AP can transmit a message that can include at least one or more of the information items as indicated in Table 1.

TABLE 1
Information
item       Description
Logical AP An information item that can indicate that the AP is a
MLD        part of a logical AP MLD. e.g., a flag/bit that can take
indication a predetermined value to make the indication.
Logical AP An information item that can serve as an identifier for
MLD        the logical AP MLD that the AP is a part of. e.g.,
identifier logical AP MLD MAC address, logical AP MLD ID,
           among others.

The above information items can be transmitted together or separately. They can be transmitted as a part of any existing frame/element/field/subfield in the standard or can be a part of newly defined ones. In some embodiments, there can be two fields to carry the above information set forth in Table 1.

FIG. 7 illustrates a logical AP MLD indication in accordance with an embodiment. The logical AP MLD indication field can be set to 1 if the reported AP or the reporting AP is a part of a logical AP MLD. Otherwise, the logical AP MLD indication field can be set to 0.

FIG. 8 illustrates a logical AP MLD identifier in accordance with an embodiment. The logical AP MLD identifier field can carry the MLD ID of the logical AP MLD. In some embodiments, the logical AP MLD identifier field can be the MAC address of the logical AP MLD and can have a size of, for example, 6 octets. Based on the information indication, the non-AP MLD can determine whether a particular AP can be a part of a logical AP MLD and which logical AP MLD the AP can be affiliated with.

In some embodiments, to indicate if a reported AP is a part of the same logical AP MLD that the reporting AP is a part of, the reporting AP can transmit a message that can include at least one or more of the information items as indicated in Table 2.

TABLE 2
Information item Description
Logical AP MLD   An information item that can indicate that the AP is a
indication       part of a logical AP MLD. e.g., a flag/bit that can take
                 a predetermined value to make the indication.
Same Logical AP  An information item that can indicate if the reported
MLD affiliation  AP is a part of the same logical AP MLD as the
indication       reporting AP. e.g., a flag/bit that can take a
                 predetermined value to make the indication.
Logical AP MLD   An information item that can serve as an identifier for
identifier       the logical AP MLD that the AP is a part of. e.g.,
                 logical AP MLD MAC address, AP MLD ID, among
                 others.

The above information items can be transmitted together or separately. They can be transmitted as a part of any existing frame/element/field/subfield in the standard or can be a part of newly defined ones. Example formats for the logical AP MLD indication and identifier can be similar to those illustrated in FIG. 7 and FIG. 8.

FIG. 9 illustrates a same logical AP MLD affiliation indication in accordance with an embodiment. The same logical AP MLD affiliation indication bit field can be set to 1 if the reported AP is a part of the same logical AP MLD as the reporting AP. Otherwise, the same logical AP MLD affiliation indication bit field can be set to 0.

In some embodiments, there can be an element that can be carried in management frames (e.g., beacons, probe responses, among others) which can indicate whether the reporting AP is a part of a logical AP MLD and/or an indication of which logical AP MLD the reporting AP is a part of.

FIG. 10 illustrates a logical AP MLD indication element in accordance with an embodiment. The logical AP MLD indication element may include an element ID field, a length field, a clement ID extension field, and a logical AP MLD information field. The element ID field may include identification information for the element. The length field may provide length information for the element. The element ID extension field may provide extension information for the element. The logical AP MLD information field may provide information regarding whether an AP is a part of a logical AP MLD and/or an indication of which logical AP MLD the AP is a part of. In some embodiments, the logical AP MLD information field can include several subfields as illustrated in FIG. 11.

FIG. 11 illustrates a format of a logical AP MLD information field in accordance with an embodiment. The logical AP MLD information field can include a logical AP MLD indication field, a reserved field, and a logical AP MLD identifier field. The logical AP MLD indication field may provide an indication regarding whether the AP is a part of a logical AP MLD. The reserved field may be reserved. The logical AP MLD identifier field may provide information regarding the logical AP MLD that the AP is a part of.

In some embodiments, when the information about an AP affiliated with a logical AP MLD is carried in a reduced neighbor report (RNR) element, the RNR element can have a modified target beacon transmission time (TBTT) information field.

FIG. 12 illustrates a modified target beacon transmission time (TBTT) information field in accordance with an embodiment. The TBTT information field can include a neighbor AP TBTT offset field, a BSSID (optional) field, a short SSID (optional) field, a BSS parameters field, a 20 MHz PSD field, a MLD parameters field, and a logical AP MLD parameters field.

The neighbor AP TBTT offset field may indicate the offset in time unit (TU) and may be rounded to a nearest TU (255 offsets indicate unknown values).

The BSSID field may provide a basic service set identifier. The short SSID field may provide a hash of an SSID. The 20 MHz PSD field may provide a maximum power transmit for the 20 MHz primary channel. The MLD parameters field may provide information regarding parameters of the MLD. The logical AP MLD parameters field may provide information regarding parameters of the logical AP MLD and can include various subfields as illustrated in FIG. 13 in accordance with an embodiment.

FIG. 13 illustrates a logical AP MLD parameters subfield format in accordance with an embodiment. The logical AP MLD parameters subfield can include a logical AP MLD indication field, a same logical AP MLD affiliation indication field, a reserved field, and a logical AP MLD identifier field. The logical AP MLD indication may provide an indication regarding whether the AP is a part of a logical AP MLD. The same logical AP MLD affiliation indication bit field can be set to 1 if the reported AP is a part of the same logical AP MLD as the reporting AP. Otherwise, the same logical AP MLD affiliation indication bit field can be set to 0. The reserved field may be reserved. The logical AP MLD identifier may provide information regarding the logical AP MLD that the AP is a part of

In some embodiments, the logical AP MLD identifier sub-field can be absent. In some embodiments, the receiving non-AP MLD can infer the information regarding the logical AP MLD identifier from other messages that the reporting AP can transmit. For example, based on the first two subfields, if the non-AP MLD determines that the reported AP is a part of a logical AP MLD and the same logical AP MLD as the reporting AP, then the logical AP MLD identifier can be the same as that which is advertised by the reporting AP in one or more of the same or other frames (e.g., beacons). In some embodiments, the logical AP MLD identifier can be 6 octets long (e.g., if it is a MAC address). The information described herein can be carried in other frames in the standards (e.g., BTM messages such as query/request/response frames, neighbor report messages, among others).

FIG. 14 illustrates a modified BSSID Information field in accordance with an embodiment. The BSSID information field can include an AP reachability field, a security field, a key scope field, a capabilities field, a mobility domain field, a high throughput field, a very high throughput field, a fine time measurement (FTM) field, a high efficiency field, an Extended Range (ER) BSS field, a collocated AP field, an unsolicited probe responses active field, a members of extended service set (ESS) with 2.4/5 GHz collocated AP field, a OCT supported with reporting AP field, a collocated with 6 GHz AP field, a extremely high throughput field, a directional multi-gigabit (DMG) positioning field, a logical AP MLD indication field, a same logical AP MLD affiliation indication field, a logical AP MLD identified field, and a reserved field. The logical AP MLD indication field, the same logical AP MLD affiliation indication field, and the logical AP MLD identified field may provide similar and/or the same information as described herein in the embodiments illustrated in, for example, FIG. 11 and FIG. 13.

The AP reachability field may provide information regarding whether the AP identified by this BSSID is reachable by an STA that requested the neighbor report. The security field may indicate that the AP identified by this BSSID supports all of the security capabilities of the AP with which the STA is currently associated with. The key scope field may indicate the AP represented by this BSSID has the same authenticator as the AP sending the report. The capabilities field may include selected capability information for the AP represented by this BSSID. The mobility domain field may provide information regarding a group of APs that a STA may roam between. The high throughput field may provide information to enable or disable high throughput. The very high throughput field may provide information to enable or disable very high throughput.

The fine timing measurement (FTM) field may indicate that the AP represented by this BSSID is an AP that has set the Fine Timing Measurement Responder field of the Extended Capabilities element to 1 or not. The high efficiency field may indicate whether the AP represented by this BSSID is an HE AP.

The extended range (ER) basic service set (BSS) field may indicate if the BSS corresponding to the high efficiency (HE) AP representing this BSSID is an ER BSS transmitting beacon frames using an HE ER single user (SU) physical layer protocol data unit (PPDU) or not.

The unsolicited probe responses active field may provide an indication whether the reported AP is part of an extended service set (ESS) where all the APs that operate in the same channel as the reported AP and that might be detected by a STA receiving this frame are transmitting unsolicited probe response frames every 20 time units (TUs) or less.

The members of ESS with 2.4/5 Ghz collocated AP field may indicated if the reported AP is part of an ESS where each AP in the ESS and operating in the same band as the reported AP that might be detected by a STA receiving this frame has a corresponding AP operating in the 2.4 GHz or 5 GHz bands that is in the same co-located AP set as that AP.

The OCT supported with reporting AP field may indicate that OCT is supported to exchange Management MAC Protocol Data Unit (MMPDUs) with the AP reported in the Neighbor Report clement through over-the-air transmissions with the AP sending the Neighbor Report element.

The Collocated with 6 GHZ AP field may provide an indication regarding whether the AP reported by the Neighbor Report element is in the same co-located AP set as a 6 GHZ AP and the 6 GHZ AP can be discovered by receiving management frames sent by the reported AP.

The extremely high throughput field may indicate that the AP represented by this BSSID is an EHT AP or not. The directional multi-gigabit (DMG) positioning field may provide DMG positioning information.

An example signaling for including the information in neighbor report element can be as follows. In some embodiments, when the AP being described in the neighbor report element has the logical AP MLD indication bit set to 1 and the same logical AP MLD affiliation indication bit set to 1, then the identifier of the seamless roaming domain for the reporting AP can be the same as the reported AP. The information on the seamless roaming domain can be either obtained via other frames of the reporting AP (e.g., management frame such as beacons, probe responses, among others) or via inclusion of logical AP MLD indication element in the optional sub-elements of the neighbor report element.

In some embodiments, when the AP being described in the neighbor report element has a logical AP MLD indication bit set to 1 but the same logical AP MLD affiliation indication bit is set to 0, the information of the corresponding seamless roaming domain can be obtained by inclusion of an element that describes the seamless roaming domain in the neighbor report element (e.g., in the optional sub-elements) or in other management frames transmitted by the reporting AP. In some embodiments, the STA can obtain the information of the corresponding seamless roaming domain directly from the frames being advertised by the AP being reported.

In some embodiments, the logical AP MLD indication field, the same logical AP MLD affiliation indication field, and the logical AP MLD identified field illustrated in FIG. 14 may be present in one or more of the other fields of a neighbor report element.

In some embodiments, the modified neighbor report element and/or the logical AP MLD indication field, the same logical AP MLD affiliation indication field, and the logical AP MLD identified field can be carried in BTM messages (e.g., BTM query, request, response frames, among others).

In some embodiments, a BSSID can be set to the logical AP MLD identifier. For example, if the logical AP MLD identifier is a MAC address. In some embodiments, APs that have the same BSSID can be assumed to be a part of the same logical AP MLD or seamless roaming domain.

FIG. 15 illustrates a flow chart of an example process performed by a first AP of providing an indication of whether a particular AP is part of a logical AP MLD in accordance with an embodiment. Although one or more operations are described or shown in particular sequential order, in other embodiments the operations may be rearranged in a different order, which may include performance of multiple operations in at least partially overlapping time periods. The flowchart depicted in FIG. 15 illustrates operations performed in an AP, such as the AP illustrated in FIG. 3.

The process 1500, in operation 1501, the first AP determines whether a particular AP is a part of a logical AP MLD. If in operation 1501, the first AP determines that the particular AP is a part of a logical AP MLD, then the process proceeds to operation 1503. If in operation 1501, the first AP determines that the particular AP is not a part of a logical AP MLD, then the process proceeds to operation 1505. In some embodiments, the particular AP is the first AP or a second AP. In some embodiments, when the particular AP is a second AP, the frame includes an indication that indicates if the first AP is a part of the same logical AP MLD as the second AP. In some embodiments, the frame is a beacon frame or a probe response frame. In some embodiments, the first AP and the particular AP are non-collocated.

In operation 1503, the first AP transmits, to a STA, a frame that includes an indication that the particular AP is a part of a logical AP MLD and an identifier of the logical AP MLD. In some embodiments, the identifier of the logical AP MLD is the same as an identifier of the first AP. In some embodiments, the identifier is a logical AP MLD media access control (MAC) address. In some embodiments, the identifier of the logical AP MLD is set to a basic service set (BSS) identifier.

In operation 1505, the first AP transmits, to a STA, a frame that includes an indication that the particular AP is not a part of a logical AP MLD.

Embodiments in accordance with this disclosure provide a STA with information regarding whether an AP is part of a logical AP MLD, which may be useful for the STA to know when roaming to a new AP and can improve network operations and reduce latency during handover procedures while roaming.

A reference to an element in the singular is not intended to mean one and only one unless specifically so stated, but rather one or more. For example, “a” module may refer to one or more modules. An element proceeded by “a,” “an,” “the,” or “said” does not, without further constraints, preclude the existence of additional same elements.

Headings and subheadings, if any, are used for convenience only and do not limit the invention. The word exemplary is used to mean serving as an example or illustration. To the extent that the term “include,” “have,” or the like is used, such term is intended to be inclusive in a manner similar to the term “comprise” as “comprise” is interpreted when employed as a transitional word in a claim. Relational terms such as first and second and the like may be used to distinguish one entity or action from another without necessarily requiring or implying any actual such relationship or order between such entities or actions.

Phrases such as an aspect, the aspect, another aspect, some aspects, one or more aspects, an implementation, the implementation, another implementation, some implementations, one or more implementations, an embodiment, the embodiment, another embodiment, some embodiments, one or more embodiments, a configuration, the configuration, another configuration, some configurations, one or more configurations, the subject technology, the disclosure, the present disclosure, other variations thereof and alike are for convenience and do not imply that a disclosure relating to such phrase(s) is essential to the subject technology or that such disclosure applies to all configurations of the subject technology. A disclosure relating to such phrase(s) may apply to all configurations, or one or more configurations. A disclosure relating to such phrase(s) may provide one or more examples. A phrase such as an aspect or some aspects may refer to one or more aspects and vice versa, and this applies similarly to other foregoing phrases.

A phrase “at least one of” preceding a series of items, with the terms “and” or “or” to separate any of the items, modifies the list as a whole, rather than each member of the list. The phrase “at least one of” does not require selection of at least one item; rather, the phrase allows a meaning that includes at least one of any one of the items, and/or at least one of any combination of the items, and/or at least one of each of the items. By way of 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.

It is understood that the specific order or hierarchy of steps, operations, or processes disclosed is an illustration of exemplary approaches. Unless explicitly stated otherwise, it is understood that the specific order or hierarchy of steps, operations, or processes may be performed in different order. Some of the steps, operations, or processes may be performed simultaneously or may be performed as a part of one or more other steps, operations, or processes. The accompanying method claims, if any, present elements of the various steps, operations or processes in a sample order, and are not meant to be limited to the specific order or hierarchy presented. These may be performed in serial, linearly, in parallel or in different order. It should be understood that the described instructions, operations, and systems can generally be integrated together in a single software/hardware product or packaged into multiple software/hardware products.

The disclosure is provided to enable any person skilled in the art to practice the various aspects described herein. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts of the subject technology. The disclosure provides various examples of the subject technology, and the subject technology is not limited to these examples. Various modifications to these aspects will be readily apparent to those skilled in the art, and the principles described herein may be applied to other aspects.

All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. § 112, sixth paragraph, unless the element is expressly recited using a phrase means for or, in the case of a method claim, the element is recited using the phrase step for.

The title, background, brief description of the drawings, abstract, and drawings are hereby incorporated into the disclosure and are provided as illustrative examples of the disclosure, not as restrictive descriptions. It is submitted with the understanding that they will not be used to limit the scope or meaning of the claims. In addition, in the detailed description, it can be seen that the description provides illustrative examples and the various features are grouped together in various implementations for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed subject matter requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed configuration or operation. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separately claimed subject matter.

The claims are not intended to be limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims and to encompass all legal equivalents. Notwithstanding, none of the claims are intended to embrace subject matter that fails to satisfy the requirements of the applicable patent law, nor should they be interpreted in such a way.

Claims

1. A first access point (AP) in a wireless network, comprising: a memory; anda processor coupled to the memory, the processor configured to: transmit, to a station (STA), a frame that includes an indication of whether a particular AP is a part of a seamless roaming domain and an identifier of the seamless roaming domain when the particular AP is a part of the seamless roaming domain.

2. The first AP of claim 1, wherein the identifier is a media access control (MAC) address.

3. The first AP of claim 1, wherein the particular AP is the first AP or a second AP.

4. The first AP of claim 1, wherein the particular AP is a second AP, wherein the frame includes an indication that indicates if the first AP is a part of the same seamless roaming domain as the second AP.

5. The first AP of claim 1, wherein the frame is a management frame.

6. The first AP of claim 1, wherein the frame includes a reduced neighbor report (RNR) element that includes one or more of the indication of whether the particular AP is a part of the seamless roaming domain or the identifier of the seamless roaming domain when the particular AP is a part of the seamless roaming domain.

7. The first AP of claim 1, wherein the identifier of the seamless roaming domain is set to a basic service set (BSS) identifier.

8. The first AP of claim 1, wherein the seamless roaming domain provides seamless roaming between APs that are a part of the seamless roaming domain.

9. The first AP of claim 1, wherein the first AP and the particular AP are non-collocated.

10. The first AP of claim 1, wherein the identifier of the seamless roaming domain is the same as an identifier for the first AP.

11. A computer-implemented method for communication by a first access point (AP) in a wireless network, comprising: transmitting, to a station (STA), a frame that includes an indication of whether a particular AP is a part of a seamless roaming domain and an identifier of the seamless roaming when the particular AP is a part of the seamless roaming domain.

12. The computer-implemented method of claim 11, wherein the identifier is a media access control (MAC) address.

13. The computer-implemented method of claim 11, wherein the particular AP is the first AP or a second AP.

14. The computer-implemented method of claim 11, wherein the particular AP is a second AP, wherein the frame includes an indication that indicates if the first AP is a part of the same seamless roaming domain as the second AP.

15. The computer-implemented method of claim 11, wherein the frame is a management frame.

16. The computer-implemented method of claim 11, wherein the frame includes a reduced neighbor report (RNR) element that includes one or more of the indication of whether the particular AP is a part of the seamless roaming domain or the identifier of the seamless roaming domain when the particular AP is a part of the seamless roaming domain.

17. The computer-implemented method of claim 11, wherein the identifier of the seamless roaming domain is set to a basic service set (BSS) identifier.

18. The computer-implemented method of claim 11, wherein the seamless roaming domain provides seamless roaming between APs that are a part of the seamless roaming domain.

19. The computer-implemented method of claim 11, wherein the first AP and the particular AP are non-collocated.

20. The computer-implemented method of claim 11, wherein the identifier of the seamless roaming domain is the same as an identifier for the first AP.