Station buffer management for roaming

Abstract

There is provided a method of managing a roaming / transitioning handover wherein a first access point (AP) received from a station (STA), a first frame indicating a transition from the first AP to a second AP; and then transmits to the STA, a second frame indicating a parameter related to transmission to the first AP, prior to the transitioning from the first AP to the second AP, of data buffered at the STA. The first frame may comprise a buffer status report (BSR) indicating one or more traffic identifiers (TIDs) associated with traffic for the first AP buffered at the STA. The in the indication of the transition from the first AP to the second AP may be a request to roam (transition) from the first AP to a second AP, Also, the parameter relating to transmission to the first AP comprises a first TID of the one or more TIDs. Further, the method may comprise receiving, by the first AP from the STA, a third frame comprising data frame associated with the first TID and a second BSR, and based on the second BSR indicating a queue size with a value of zero for the first TID, transmitting, by the first AP to the STA, a fourth frame instructing the STA to transition from the first AP to the second AP.

Description

[0001] STATION BUFFER MANAGEMENT FOR ROAMING

[0002] FIELD OF THE INVENTION

[0003] The present invention relates to wireless networks, particularly those conforming to the IEEE™ 802.11 standard.

[0004] BACKGROUND OF THE INVENTION

[0005] Wireless networks are often required to cater for the mobility of devices connected to them. This mobility may lead to a device distancing itself from the node (such as an access point or base station) with which it has a link (being served by, in other words) and becoming closer to second access point / base station. From a point of view of link bandwidth and reliability, it may be more desirable for it to connect to the second access point i.e. to perform a roaming hand-over.

[0006] Furthermore, it is desirable that the hand-over be executed in a manner that does not disrupt ongoing communications. In general, a device (sometimes referred to as a ‘station’ (STA) or ‘user equipment’ (UE)), prepares the handover by announcing its intention then performing a negotiation. Then, the handover is executed. Roaming may also be referred to as ‘transitioning’.

[0007] SUMMARY OF THE INVENTION

[0008] The present invention is defined by the appended independent claims in which there are provided methods and devices.

[0009] It may be desirable that a STA which is preparing to roam transmit all of its uplink data (drain its uplink data) to the AP to which it is currently connected before transmitting a roaming request to another AP. This has the advantage that that data, which is probably part of an ongoing exchange, is, to some extent, protected from potential disruptions occasioned by the handover.

[0010] To this end, there is provided methods and devices arranged to perform the methods, which may comprise receiving, by a first access point (AP) from a station (STA), a first frame indicating a transition from the first AP to a second AP and transmitting, by the first AP to the STA, a second frame indicating a parameter related to transmission to the first AP, prior to the transitioning from the first AP to the second AP, of data buffered at the STA.

[0011] This enables the AP to provide instructions / information to the STA. Various possibilities exist, and combinations thereof, such as (without limitation) indications of whether to transmit or not, quantities to transmit and types of data concerned by the transmissions.

[0012] These methods have the advantage of avoiding problems discovered by the inventors with this procedure where the STA trying to roam / transition may require a relatively long time in order to drain its uplink data. For example, the STA may not be able to access the channel due to heavy channel contention and / or may have a substantial amount of buffered uplink data. This in turn may delay the sending of the roaming request by the STA and the transition from one AP to the other. Meanwhile, the link between the STA and the first AP may deteriorate and connection may even be lost. Buffered data may then be lost due to the delayed transition.

[0013] BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.

[0015] FIG. 1 illustrates example wireless communication networks in which embodiments of the present disclosure may be implemented.

[0016] FIG. 2 is a block diagram illustrating example implementations of a station (STA) and an access point (AP).

[0017] FIG. 3 illustrates an example multi-AP network.

[0018] FIG. 4 illustrates Enhanced Distributed Channel Access (EDCA) and Coordinated Orthogonal Frequency Division Multiple Access (COFDMA).

[0019] FIG. 5 illustrates an example network that includes a coordinated AP set.

[0020] FIG. 6 illustrates an example multi-AP operation procedure.

[0021] FIG. 7 illustrates an example multi-AP sounding phase.

[0022] FIG. 8 illustrates an example multi-AP downlink data transmission phase.

[0023] FIG. 9 illustrates an example multi-AP uplink data transmission phase.

[0024] FIG. 10 illustrates an example of a STA roaming from a first AP to a second AP.

[0025] FIG. 11 illustrates an example of the Fast Session Transfer protocol using the Over-the- DS method.

[0026] FIG. 12 illustrates an example of a procedure for session transfer via roaming.

[0027] FIG. 13 illustrates an example of a roaming procedure according to an embodiment.

[0028] FIG. 14 illustrates another example of a roaming procedure according to an embodiment. FIG. 15 illustrates another example of a roaming procedure according to an embodiment. FIG. 16 illustrates another example of a roaming procedure according to an embodiment. FIG. 17 illustrates an example process according to an embodiment.

[0029] FIG. 18 illustrates an example process according to an embodiment.

[0030] DETAILED DESCRIPTION

[0031] In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and / or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. After reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments may not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

[0032] Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a station, an access point, a radio environment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and / or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

[0033] In this disclosure, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of’, as used herein, enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of’ provides a complete enumeration of the one or more components of the element being described. The term “based on”, as used herein, may be interpreted as “based at least in part on” rather than, for example, “based solely on”. The term “and / or” as used herein represents any possible combination of enumerated elements. For example, “A, B, and / or C” may represent A; B; C; A and B; A and C; B and C; or A, B, and C.

[0034] If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {STA1, STA2} are: {STA1}, {STA2}, and {STA1, STA2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing / using” (or equally “employing / using at least”) is indicative that the phrase following the phrase “employing / using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

[0035] The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and / or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

[0036] In this disclosure, parameters (or equally called, fields, or Information elements: IES) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages / frames comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages / frames but does not have to be in each of the one or more messages / frames.

[0037] Many features presented are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of the three possible features, with any two of the three possible features or with three of the three possible features.

[0038] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g. hardware with a biological element) or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.

[0039] FIG. 1 illustrates example wireless communication networks in which embodiments of the present disclosure may be implemented.

[0040] As shown in FIG. 1, the example wireless communication networks may include an Institute of Electrical and Electronic Engineers (IEEE) 802.11 (WLAN) infra-structure network 102. WLAN infra-structure network 102 may include one or more basic service sets (BSSs) 110 and 120 and a distribution system (DS) 130.

[0041] BSS 110-1 and 110-2 each includes a set of an access point (AP or AP STA) and at least one station (STA or non-AP STA). For example, BSS 110-1 includes an AP 104-1 and a STA 106-1, and BSS 110-2 includes an AP 104-2 and STAs 106-2 and 106-3. The AP and the at least one STA in a BSS perform an association procedure to communicate with each other.

[0042] DS 130 may be configured to connect BSS 110-1 and BSS 110-2. As such, DS 130 may enable an extended service set (ESS) 150. Within ESS 150, APs 104-1 and 104-2 are connected via DS 130and may have the same service set identification (SSID).

[0043] WLAN infra-structure network 102 may be coupled to one or more external networks.

[0044] For example, as shown in FIG. 1, WLAN infra-structure network 102 may be connected to another network 108 (e.g., 802.X) via a portal 140. Portal 140 may function as a bridge connecting DS 130 of WLAN infra-structure network 102 with the other network 108.

[0045] The example wireless communication networks illustrated in FIG. 1 may further include one or more ad-hoc networks or independent BSSs (IBSSs). An ad-hoc network or IBSS is a network that includes a plurality of STAs that are within communication range of each other. The plurality of STAs are configured so that they may communicate with each other using direct peer-to-peer communication (i.e., not via an AP).

[0046] For example, in FIG. 1, STAs 106-4, 106-5, and 106-6 may be configured to form a first IBSS 112-1. Similarly, STAs 106-7 and 106-8 may be configured to form a second IBSS 112-2. Since an IBSS does not include an AP, it does not include a centralized management entity. Rather, STAs within an IBSS are managed in a distributed manner. STAs forming an IBSS may be fixed or mobile.

[0047] A STA as a predetermined functional medium may include a medium access control (MAC) layer that complies with an IEEE 802. 11 standard. A physical layer interface for a radio medium may be used among the APs and the non-AP stations (STAs). The STA may also be referred to using various other terms, including mobile terminal, wireless device, wireless transmit / receive unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, or user. For example, the term “user” may be used to denote a STA participating in uplink Multi-user Multiple Input, Multiple Output (MU MIMO) and / or uplink Orthogonal Frequency Division Multiple Access (OFDMA) transmission.

[0048] A physical layer (PHY) protocol data unit (PPDU) may be a composite structure that includes a PHY preamble and a payload in the form of a PLCP service data unit (PSDU). For example, the PSDU may include a PHY Convergence Protocol (PECP) preamble and header and / or one or more MAC protocol data units (MPDUs). The information provided in the PHY preamble may be used by a receiving device to decode the subsequent data in the PSDU. In instances in which PPDUs are transmitted over a bonded channel (channel formed through channel bonding), the preamble fields may be duplicated and transmitted in each of the multiple component channels. The PHY preamble may include both a legacy portion (or “legacy preamble”) and a non-legacy portion (or “non-legacy preamble”). The legacy preamble may be used for packet detection, automatic gain control and channel estimation, among other uses. The legacy preamble also may generally be used to maintain compatibility with legacy devices. The format of, coding of, and information provided in the non-legacy portion of the preamble is based on the particular IEEE 802. 11 protocol to be used to transmit the payload.

[0049] A frequency band may include one or more sub-bands or frequency channels. For example, PPDUs conforming to the IEEE 802.1 In, 802. 1 lac, 802. 1 lax and / or 802. 1 Ibe standard amendments may be transmitted over the 2.4 GHz, 5 GHz, and / or 6 GHz bands, each of which may be divided into multiple 20 MHz channels. The PPDUs may be transmitted over a physical channel having a minimum bandwidth of 20 MHz. Larger channels may be formed through channel bonding. For example, PPDUs may be transmitted over physical channels having bandwidths of 40 MHz, 80 MHz, 160 MHz, or 520 MHz by bonding together multiple 20 MHz channels.

[0050] FIG. 2 is a block diagram illustrating example implementations of a STA 210 and an AP 260. As shown in FIG. 2, STA 210 may include at least one processor 220, a memory 230, and at least one transceiver 240. AP 260 may include at least one processor 270, a memory 280, and at least one transceiver 290. Processor 220 / 270 may be operatively connected to memory 230 / 280 and / or to transceiver 240 / 290.

[0051] Processor 220 / 270 may implement functions of the PHY layer, the MAC layer, and / or the logical link control (LLC) layer of the corresponding device (STA 210 or AP 260). Processor 220 / 270 may include one or more processors and / or one or more controllers. The one or more processors and / or one or more controllers may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a logic circuit, or a chipset, for example.

[0052] Memory 230 / 280 may include a read-only memory (ROM), a random-access memory (RAM), a flash memory, a memory card, a storage medium, and / or other storage unit. Memory 230 / 280 may comprise one or more non-transitory computer readable mediums. Memory 230 / 280 may store computer program instructions or code that may be executed by processor 220 / 270 to carry out one or more of the operations / embodiments discussed in the present application. Memory 230 / 280 may be implemented (or positioned) within processor 220 / 270 or external to processor 220 / 270. Memory 230 / 280 may be operatively connected to processor 220 / 270 via various means known in the art.

[0053] Transceiver 240 / 290 may be configured to transmit / receive radio signals. In an embodiment, transceiver 240 / 290 may implement a PHY layer of the corresponding device (STA 210 or AP 260). In an embodiment, STA 210 and / or AP 260 may be a multi -link device (MLD), that is a device capable of operating over multiple links as defined by the IEEE 802.11 standard. As such, STA 210 and / or AP 260 may each implement multiple PHY layers. The multiple PHY layers may be implemented using one or more of transceivers 240 / 290.

[0054] FIG. 3 illustrates an example multi-AP network 300. Example multi-AP network 300 may be a multi-AP network in accordance with the Wi-Fi Alliance standard specification for multi-AP networks. As shown in FIG. 3, multi-AP network 300 may include a multi-AP controller 302 and a plurality of multi-AP groups (or multi-AP sets) 304, 306, and 308.

[0055] Multi-AP controller 302 may be a logical entity that implements logic for controlling the APs in multi-AP network 300. Multi-AP controller 302 may receive capability information and measurements from the APs and may trigger AP control commands and operations on the APs. Multi-AP controller 302 may also provide onboarding functionality to onboard and provision APs onto multi-AP network 300.

[0056] Multi-AP groups 304, 306, and 308 may each include a plurality of APs. APs in a multi- AP group are in communication range of each other and may coordinate their transmissions and / or transmissions from their associated STAs. Coordinated transmissions may involve all or a subset of the APs in a multi-AP group. A multi-AP group may also be referred to as an AP candidate set as APs in a multi-AP group are considered candidates for a coordinated transmission initiated by an AP. The APs in a multi-AP group are not required to have the same primary channel. As used herein, the primary channel for an AP refers to a default channel that the AP monitors for management frames and / or uses to transmit beacon frames. For a STA associated with an AP, the primary channel refers to the primary channel of the AP, which is advertised through the AP’s beacon frames.

[0057] In one approach, a multi-AP group may be established by a coordinator AP in a multi-AP setup phase prior to any multi-AP coordination. APs of the multi-AP group, other than the coordinator AP, may be referred to as the coordinated APs. A coordinator AP may establish one or more multi-AP groups. A coordinated AP may likewise be a member of multiple multi-AP groups. A coordinator AP of a multi-AP group may be a coordinated AP of another multi-AP group, and vice versa. In another approach, a multi-AP group may be established by a network administrator manually by configuring APs as part of the multi-AP group. In yet another approach, a multi-AP group may be established in a distributed manner by APs without a central controller. In this case, an AP may advertise its multi-AP capability in a beacon or other management frame (e.g., public action frame). Other APs that receive the frame with the multi-AP capability information may perform a multi-AP setup with the AP that advertised the multi-AP capability.

[0058] In one approach, one of the APs in a multi-AP group may be designated as a master AP. The designation of the master AP may be done by AP controller 302 or by the APs of the multi-AP group. The master AP of a multi-AP group may be fixed or may change over time between the APs of the multi- AP group. An AP that is not the master AP of the multi-AP group is known as a slave AP.

[0059] In one approach, APs in a multi-AP group may perform coordinated transmissions together. One aspect of coordination may include coordination to perform coordinated transmissions within the multi-AP group. As used herein, a coordinated transmission, also referred to as a multi-AP transmission, is a transmission event in which multiple APs (of a multi-AP group or a multi-AP network) transmit in a coordinated manner over a time period. Coordinated transmissions may involve simultaneous transmissions of a plurality of APs in a multi-AP group. The time period of simultaneous AP transmission may be a continuous period. The multi-AP transmission may use different transmission techniques, such as Coordinated OFDMA (COFDMA), Coordinated Spatial Reuse (CSR), Joint Transmission or Reception (JT / JR), Coordinated Beamforming (CBF), and CTDMA, or a combination of two or more of the aforementioned techniques.

[0060] Multi-AP transmissions may be enabled by the AP controller and / or by the master AP of the multi-AP group. In one approach, the AP controller and / or the master AP may control time and / or frequency sharing in a transmission opportunity (TXOP). For example, when one of the APs (e.g., the master AP) in the multi-AP group obtains a TXOP, the AP controller and / or the master AP may control how time / frequency resources of the TXOP are to be shared with other APs of the multi-AP group. In an implementation, the AP of the multi-AP group that obtains a TXOP becomes the master AP of the multi- AP group. The master AP may then share a portion of its obtained TXOP (which may be the entire TXOP) with one or more other APs of the multi-AP group.

[0061] Different multi-AP transmission schemes may be suitable for different use cases in terms of privacy protection, including whether transmitted data may be shared with other BSSs in the multi-AP group. For example, some multi-AP transmission schemes, such as CSR, CDTMA, coordinated frequency division multiple access (CFDMA), COFDMA, and CBF, enable a master AP to coordinate slave APs by sharing control information among APs, without requiring the sharing of user data among APs. The control information may include BSS information of APs, link quality information of channels between each AP and its associated STAs, and information related to resources to be used to achieve multiplexing in power, time, frequency, or special domains for multi-AP transmission. The control information exchanged among a master AP and slave APs may be used for interference avoidance or nulling to avoid or null co-channel interference introduced to neighboring BSSs in a multi-AP network. Interference avoidance or interference nulling requires that data transmissions between an AP and STAs are only within the same BSS. In other words, each AP transmits or receives data frames to or from its associated STAs, while each STA receives or transmits data frames to or from its associating AP. By contrast, other multi-AP transmission schemes may enable a master AP to coordinate slave APs by sharing both control information and user data among APs in a multi-AP group. Control information may include BSS information related to APs and link quality information of channels between each AP and its associated STAs. By having user data exchanged over backhaul, the master AP and slave APs may perform data transmissions jointly to achieve spatial diversity, e.g., using distributed MIMO, for example joint transmission (JT) for downlink transmissions and joint reception (JR) for uplink transmissions. The data transmissions between APs and STAs may include transmissions within the same BSS and / or across different BSSs. In other words, an AP may transmit or receive data frames to or from its associated STAs as well STAs associated with other APs participating in multi-AP transmission. Similarly, a STA may transmit or receive data frames to or from multiple APs.

[0062] Different multi-AP transmission schemes may be suitable for different use cases in terms of signal reception levels at STAs or APs within a multi-AP group. For example, CBF and JT / JR require that each STA involved in a multi-AP transmission be located within a common area of signal coverage of the APs involved in the multi-AP transmission. Generally, CBF may be suitable when a receiving STA suffers from potential interference from other APs in the multi-AP group. By using channel related information such as channel state information (CSI), channel quality indication (CQI), or compressed beamforming (BF) feedback exchanged among APs, an AP may pre-code a signal to be transmitted to form a beam that increases power toward a target STA while reducing the power that interferes with a STA associated with a neighboring AP. Use cases of JT / JR may require a sufficient received signal power at receiving STAs for JT and a sufficient received signal power at receiving APs for JR. By contrast, CSR may perform multi-AP transmission in an interference coordination manner. The received signal power at a STA associated with an AP transmitting data may be required to be much higher than the received interference power.

[0063] Different multi-AP transmission schemes may require different synchronization levels and may operate with or without a backhaul between a master AP and slave APs in a multi-AP group. For example, CSR may require PPDU-level synchronization, whereas CBF may require symbol-level synchronization. On the other hand, JT / JR may require tight time / frequency / phase -level synchronization as well as a backhaul for data sharing between APs in the multi-AP group.

[0064] Different multi-AP transmission schemes may have different complexity levels with regard to coordination between a master AP and slave APs in a multi-AP group. For example, JT / JR may require very high complexity due to both CSI and user data being shared between APs. CBF may require medium complexity due to the sharing of CSI. CFDMA, COFDMA and CTDMA may require medium or relatively low complexity due to the CSI and time / frequency resources to be shared between APs. CSR may require low complexity as the amount of information related to spatial reuse and traffic that needs to be exchanged between APs may be low.

[0065] A multi-AP group may adopt a static multi-AP operation including a static multi-AP transmission scheme. A multi-AP network may also be dynamic due to various reasons. For example, a STA may join or leave the multi-AP network, a STA may switch to a power save mode, or an AP or a STA may change its location. Such changes may lead to changes in the conditions underlying the selection of the multi-AP transmission scheme and may cause certain requirements (e.g., synchronization, backhaul, coordination, etc.) for the multi-AP transmission scheme to be lost. This results in an inferior quality of transmissions in the multi-AP network.

[0066] In COFDMA, the master AP may share a portion of its TXOP with multiple APs by assigning each of the multiple APs a respective frequency resource (e.g., channel / subchannel) of available frequency resources. COFDMA is illustrated in FIG. 4 as a multi-AP channel access, compared with Enhanced Distributed Channel Access (EDCA). As shown in FIG. 4, in EDCA, channel access by multiple APs (e.g., API, AP2) may occur in consecutive time periods (e.g., TXOPs). During a given channel access, the channel (e.g., 80 MHz) in its entirety may be used by a single AP. In contrast, in COFDMA, access by multiple APs (multi-AP channel access) may take place in a same time period (e.g., same TXOP or same portion of a TXOP) over orthogonal frequency resources. For example, as shown in FIG. 4, an 80 MHz channel may be divided into four non-overlapping 20 MHz channels, each assigned to a respective AP of the multiple APs. The multiple APs may transmit in a coordinated manner, simultaneously in the same time period, to achieve a multi-AP transmission. In the multi-AP transmission, each of the multiple APs may transmit a PPDU to one or more STAs.

[0067] FIG. 5 illustrates an example network 500 that includes a coordinated AP set. As shown in FIG. 5, the coordinated AP set may include two APs - AP 502-1 and AP 502-2. The coordinated AP set may be a subset of an established multi-AP group. At least one STA may be associated with each of APs 502-1 and 502-2. For example, a STA 504-1 may be associated with AP 502-1, and a STA 504-2 may be associated with AP 502-2.

[0068] APs 502-1 and 502-2 may belong to the same ESS as described above in FIG. 1. In such a case, APs 502-1 and 502-2 may be connected by a DS to support ESS features. In addition, as part of a coordinated AP set, APs 502-1 and 502-2 may be connected by a backhaul. The backhaul is used to share information quickly between APs to support coordinated transmissions. The shared information may be channel state information or data to be sent to associated STAs. The backhaul may be a wired backhaul or a wireless backhaul. A wired backhaul is preferred for high-capacity information transfer without burdening the main radios of the APs. However, a wired backhaul may require a higher deployment cost and may place greater constraints on AP placement. A wireless backhaul is preferred for its lower deployment cost and flexibility regarding AP placement. However, because a wireless backhaul relies on the main radios of the APs to transfer information, the APs cannot transmit or receive any data while the wireless backhaul is being used.

[0069] Typically, one of APs 502-1 and 502-2 may act as a Master AP and the other as a Slave AP. The Master AP is the AP that is the owner of the TXOP. The Master AP shares frequency resources during the TXOP with the Slave AP. When there are more than two APs in the coordinated set, a Master AP may share its TXOP with only a subset of the coordinated AP set. The role of the Master AP may change over time. For example, the Master AP role may be assigned to a specific AP for a duration of time. Similarly, the Slave AP role may be chosen by the Master AP dynamically or can be pre-assigned for a duration of time.

[0070] Depending on the capability of APs in a coordinated AP set, the APs may only do certain type of coordinated transmissions. For example, in FIG. 5, if AP 502-1 supports JT and CSR while AP 502-2 supports CSR and CBF, both APs may only perform CSR as a coordinated transmission scheme. An AP may also prefer to perform single AP transmissions for a duration of time if the benefit of coordinated transmission does not outweigh some disadvantages with coordinated transmission such as reduced flexibility and increased computational power required.

[0071] CSR is one type of multi -AP coordination that may be supported by AP 501-1 and AP 502-2 as shown in FIG. 5. Spatial reuse using CSR can be more stable than non-AP coordinated spatial reuse schemes such as OBSS PD-based SR and PSR-based SR. For example, in example network 500, APs 502-1 and 502-2 may perform a joint sounding operation in order to measure path loss (PL) on paths of example network 500. For example, the joint sounding operation may result in the measurement of PL 508 for the path between APs 502-1 and 502-2, path loss 510 for the path between AP 502-1 and STA 504-2, and path loss 512 for the path between AP 502-2 and STA 504-1. The measured path loss information may then be shared between APs 502-1 and 502-2 (e.g., using the backhaul) to allow for simultaneous transmissions by APs 502-1 and 502-2 to their associated STAs 504-1 and 504-2 respectively. Specifically, one of APs 502-1 and 502-2 obtains a TXOP to become the Master AP. The Master AP may then send a CSR announcement frame to the other AP(s). In an embodiment, the Master AP may perform a polling operation, before sending the CSR announcement frame, to poll Slave APs regarding packet availability for transmission. If at least one Slave AP responds indicating packet availability, the Master AP may proceed with sending the CSR announcement frame. In the CSR announcement, the Master AP may limit the transmit power of a Slave AP in order to protect its own transmission to its target STA. The Slave AP may similarly protect its own transmission to its target STA by choosing a modulation scheme that enables a high enough Signal to Interference Ratio (SIR) margin to support the interference due to the transmission of the Master AP to its target STA.

[0072] FIG. 6 illustrates an example 600 of a multi-AP operation procedure. In example 600, the multi-AP operation procedure is illustrated with respect to a multi-AP network that includes APs 602 and 604 and STAs 606 and 608. In an example, APs 602 and 604 may form a multi-AP group. AP 602 may be the master AP and AP 604 may be a slave AP of the multi-AP group. For example, AP 602 may obtain a TXOP making it the master AP of the multi-AP group. Alternatively, AP 602 may be designated as the master AP by a multi-AP controller.

[0073] As shown in FIG. 6, the multi-AP operation procedure may include a series of phases in time, each of which may contain a plurality of frame exchanges within the multi-AP network. Specifically, the multi-AP operation procedure may include a multi-AP selection phase 610, a multi-AP data sharing phase 612, a multi-AP sounding phase 614, and a multi-AP data transmission phase 616. A multi-AP network may carry out a multi-AP operation based on a specific multi-AP transmission scheme. The multi-AP transmission scheme may be chosen by the master AP based on the capabilities of the slave APs in a multi-AP group. Prior to a multi-AP operation, a slave AP may inform the master AP of capability information related to the slave AP, including the capabilities of supporting one or more multi-AP transmission schemes. The slave AP may also inform the master AP of BSS information of the BSS of the slave AP and of link quality information for STAs associated with the slave AP. The master AP may receive information related to all available slave APs. The information related to slave APs may include capability information, BSS information, and link quality information. Based on the information provided by available slave APs, the master AP may determine during a multi-AP selection phase the slave APs to be designated for a multi-AP transmission and a specific multi-AP transmission scheme to be used during the multi-AP transmission.

[0074] Multi-AP selection phase 610 may include procedures for soliciting, selecting, or designating slave AP(s) for a multi-AP group by a master AP. As seen in FIG. 6, the multi-AP selection phase may include transmissions of frame 618 from AP 602 and frame 620 from AP 604. AP 602 may transmit frame 618 to solicit information regarding the buffer status of AP 604. In response, AP 604 may transmit frame 620 to inform AP 602 of its and its associated STAs buffer status and / or whether it intends to join multi-AP operation. Multi-AP selection phase 610 may also be used to exchange information related to multi-AP operation, including BSS information of APs and link quality information between each AP and its associated STAs, for example. The BSS information of an AP may include a BSS ID of the BSS of the AP, identifiers and / or capabilities of STAs belonging to the BSS, information regarding sounding capabilities of the STAs, information regarding MIMO capabilities of the AP, etc. Link quality information may include received signal strength indicator (RSSI), signal-to-noise ratio (SNR), signal-to- interference-plus-noise-ratio (SINR), channel state information (CSI), channel quality indicator (CQI).

[0075] Multi-AP data sharing phase 612 may include procedures for sharing data frames to be transmitted by APs to associated STAs among the master AP and selected slave AP(s) via direct connections between APs. Phase 612 may be optional for some multi-AP data transmission schemes. For example, phase 612 may be required for JT / JR as data frames may be exchanged between APs before or after multi-AP data transmission phase 616.

[0076] Multi-AP data sharing phase 612 may be performed using a wired backhaul, an in- channel wireless backhaul, or an off-channel wireless backhaul. In some cases, multi-AP data sharing phase 612 may be performed over an in-channel backhaul, e.g., using the same wireless channel used to transmit / receive data to / from STAs. For example, as shown in FIG. 6, in phase 612, AP 602 may transmit a frame 622, which may be received by AP 604. Frame 622 may include MPDUs that AP 602 wishes to transmit to associated STAs using a multi-AP operation. Similarly, AP 604 may transmit a frame 624, which may be received by AP 602. Frame 624 may include MPDUs that AP 604 wishes to transmit to associated STAs using a multi-AP operation. Multi -AP sounding phase 614 may include procedures for multi -AP channel sounding, including channel estimation and feedback of channel estimates among the master AP, candidate slave AP(s), and associated STAs. Phase 614 may be optional for some multi-AP transmission schemes, such as COFDMA, CDTMA, and CSR. For example, phase 614 may be performed by the master AP to aid in resource unit allocation when orchestrating a COFDMA transmission.

[0077] Multi-AP data transmission phase 616 may include exchange of data frames between the master AP, slave AP(s), and their associated STAs based on multi-AP transmission scheme(s) determined by the master AP. Depending on the multi-AP transmission scheme(s) to be used, phase 616 may include optional synchronization between APs of the multi-AP group, before exchange of data frames between APs and STAs within the multi-AP group.

[0078] The order of phases 610, 612, 614 and 616 may be different than shown in FIG. 6. For example, in COFDMA, phase 616 may occur immediately after phase 610, whereas, in JT / JR, phase 612 may occur after phase 610. Further, as mentioned above, some phases may be optional and may or may not be present. For example, phase 614 may not be required for COFDMA but may be required for JT / JR.

[0079] FIG. 7 illustrates an example 700 of a multi-AP sounding phase. Multi-AP sounding phase 700 may be an example of multi-AP sounding phase 614. As shown in FIG. 7, example 700 may include a master AP 702 and a slave AP 704 of a multi-AP group. Example 700 may further include a STA 706 associated with AP 702 and a STA 708 associated with AP 704.

[0080] As shown in FIG. 7, multi-AP sounding phase 700 may include frame exchanges to allow AP 702 (the master AP) to acquire channel state information (CSI) of channels in the multi-AP group. In an implementation, phase 700 may include a first subphase 710 and a second subphase 712.

[0081] During the first subphase 710, APs may initiate channel sounding and STAs may estimate channel state information (CSI). For example, AP 702 may transmit a frame 714 to AP 704 (the slave AP) to trigger multi-AP sounding. Frame 714 may comprise a multi-AP trigger frame. Subsequently, APs 702 and 704 may transmit respectively announcement frames 716-1 and 716-2 to their respective associated STAs 706 and 708 to announce the transmission of sounding frames. Frames 716-1 and 716-2 may comprise multi-AP null data packet announcement (NDPA) frames. Frames 716-1 and 716-2 may be transmitted simultaneously. Next, APs 702 and 704 may transmit respectively frames 718-1 and 718-2 to STAs 706 and 708 respectively. Frames 718-1 and 718-2 may comprise multi-AP null data packet (NDP) frames. STAs 706 and 708 receive frames 718-1 and 718-2 respectively and perform channel estimation of the channels from AP 702 to STA 706 and from AP 704 to STA 708, respectively.

[0082] During the second subphase 712, APs may initiate a procedure for STAs to feed back channel estimates to the APs. For example, AP 702 may transmit a frame 720 to trigger STAs 706 and 708 to transmit their channel estimates to APs 702 and 704 respectively. Frame 720 may comprise a multi-AP trigger frame. In response, STAs 706 and 708 may transmit respectively frames 722 and 724 including feedback of channel estimates to APs 702 and 704 respectively. Frames 722 and 724 may comprise NDP feedback frames. The feedback of channel estimates may include NDP feedback, CSI- related information, a beamforming report (BFR), or a channel quality indication (CQI) report.

[0083] FIG. 8 illustrates an example 800 of a multi-AP downlink data transmission phase. Multi- AP downlink data transmission phase 800 may be an example of multi-AP data transmission phase 616. As shown in FIG. 8, example 800 may include a master AP 802 and a slave AP 804 of a multi-AP group. Example 800 may further include a STA 806 associated with AP 802, and a STA 808 associated with AP 804.

[0084] As shown in FIG. 8, multi-AP downlink data transmission phase 800 may include frame exchanges to enable master AP 802 to coordinate with slave AP 804 to perform specific multi-AP transmission schemes with their associated STAs 806 and 808 respectively. The multi-AP transmission schemes may include COFDMA, CTDMA, CSR, CBF, JT / JR, or a combination of two or more of the aforementioned schemes.

[0085] As shown in FIG. 8, master AP 802 may begin phase 800 by transmitting a frame 810 to AP 804. Frame 810 may include information related to AP 804 (e.g., an identifier of AP 804), synchronization information, information related to a specific multi-AP transmission scheme to be used, and / or information related to a resource unit (RU) for use by AP 804 to acknowledge frame 810. Frame 810 may comprise a control frame. For example, frame 810 may comprise a multi-AP trigger frame.

[0086] Slave AP 804 may receive frame 810 and may use the synchronization information to synchronize with master AP 802. Subsequently, APs 802 and 804 may perform data transmission to their associated STAs 806 and 808 respectively. Specifically, AP 802 may transmit a data frame 812 to its associated STA 806, and AP 804 may transmit a data frame 814 to its associated STA 808. Depending on the multi-AP transmission scheme being used, APs 802 and 804 may transmit frames 812 and 814 respectively to STAs in different BSSs. For example, when the multi-AP transmission scheme is JT / JR, AP 802 may also transmit frame 812 to STA 808 associated with slave AP 804, and AP 804 may also transmit frame 814 to STA 808 associated with AP 804. The resources for transmitting and receiving frames 812 and 814 may depend on the specific multi-AP transmission scheme adopted.

[0087] STAs 806 and 808 may acknowledge frames 812 and 814 respectively. For example, STA 806 may transmit a frame 816 to AP 802, and STA 808 may transmit a frame 818 to AP 804. Frames 816 and 818 may comprise block ack (BA) frames. STAs 804 and 814 may also transmit frames 816 and 818 to APs in different BSSs, when required by the used multi-AP transmission scheme. For example, when the multi-AP transmission scheme is JT / JR, STA 806 may also transmit frame 816 to AP 804, and STA 808 may also transmit frame 818 to AP 802. The resources for transmitting and receiving frames 816 and 818 may depend on the specific multi-AP transmission scheme adopted.

[0088] FIG. 9 illustrates an example 900 of a multi-AP uplink data transmission phase. Multi-AP uplink data transmission phase 900 may be an example of multi-AP data transmission phase 616. As shown in FIG. 9, example 900 may include a master AP 902 and a slave AP 904 of a multi-AP group. Example 900 may further include STAs 906 and 908 associated with AP 902, and a STA 910 associated with AP 904.

[0089] As shown in FIG. 9, multi-AP uplink data transmission phase 900 may include frame exchanges to enable master AP 902 to coordinate with slave AP 904 to perform specific multi-AP transmission schemes with STAs 906, 908, and 910910. The multi-AP transmission schemes may include COFDMA, CTDMA, CSR, CBF, JT / JR, or a combination of two or more of the aforementioned schemes.

[0090] As shown in FIG. 9, master AP 902 may begin phase 900 by transmitting a frame 912 to AP 904. Frame 912 may include information related to AP 904 (e.g., an identifier of AP 904), synchronization information, information related to a specific multi-AP transmission scheme to be used, and / or information related to an RU for use by AP 904 to acknowledge frame 912. Frame 912 may comprise a control frame. For example, frame 912 may comprise a multi-AP trigger frame.

[0091] Slave AP 904 may receive frame 912 and may use the synchronization information to synchronize with master AP 902. Subsequently, APs 902 and 904 may solicit uplink data transmissions from their associated STAs 906, 908 and 910 using trigger frames. Specifically, AP 902 may transmit a trigger frame 914 to its associated STAs 906 and 908, and AP 904 may transmit a trigger frame 916 to its associated STA 910. Depending on the multi-AP transmission scheme being used, APs 902 and 904 may also transmit frames 914 and 916 respectively to STAs in different BSSs. For example, when the multi- AP transmission scheme is JT / JR, AP 902 may also transmit frame 914 to STA 910 associated with slave AP 904, and AP 904 may also transmit frame 916 to STAs 906 and 908 associated with AP 902. The resources for transmitting and receiving frames 914 and 916 may depend on the specific multi-AP transmission scheme adopted.

[0092] STAs 906 and 908 may respond to frame 914, STA 910 may respond to frame 916. For example, STAs 906 and 908 may transmit frames 918 and 920 respectively to AP 902, while STA 910 may transmit a frame 922 to AP 904. Frames 918, 920, and / or 922 may be transmitted simultaneously. Frames 918, 920, and 922 may comprise data frames or null data frames. STAs 906, 908, and 910 may also transmit frames 918, 920, and 922 respectively to APs in different BSSs, when required by the used multi-AP transmission scheme. For example, when the multi-AP transmission scheme is JT / JR, STAs 906 and 908 may also transmit respective frames 918 and 920 to AP 904, and STA 910 may also transmit frame 922 to AP 902. The resources for transmitting and receiving frames 918, 920, and 922 may depend on the specific multi-AP transmission scheme adopted. AP 902 may acknowledge frames 918 and 920 by transmitting a multi-STA BA frame 924 to STAs 906 and 908. AP 904 may acknowledge frame 922 by transmitting a BA frame 926 to STA 910.

[0093] FIG. 10 illustrates an example 1000 of a STA 1006 transitioning / roaming from an AP 1002 to an AP 1004. Before the transitioning / roaming from AP 1002 to AP 1004, STA 1006 may be associated with AP 1002. When STA 1006 moves from within a communication range of AP 1002 to a communication range of AP 1004, a communication session of STA 1006 is transferred from AP 1002 to AP 1004. The IEEE 802.11 standard defines a Basic Service Set (BSS) transition process (described in FIG. 11 below) which may be used to transfer the communication session of STA 1006 from AP 1002 to AP 1004.

[0094] FIG. 10 illustrates an example of 1000 of BSS transition according to the IEEE 802.11 standard. As shown in FIG. 10, example 1000 may include APs 1002 and AP 1004 and STA 1006. STA 1006 may be associated with AP 1002 at the beginning of example 1000 and may have established a secure session 1008 with AP 1002.

[0095] STA 1006 starts the transition process by sending an authentication request frame 1010 to AP 1004. IEEE 802.10 authentication operates at the link level between IEEE 802.10 STAs. The IEEE 802.10 standard attempts to control LAN access via the authentication service. IEEE 802.10 authentication is a station service. This service might be used by all STAs to establish their identity to APs with which they communicate. If a mutually acceptable level of authentication has not been established between a STA and an AP, an association is not established.

[0096] If AP 1004 accepts authentication request frame 1010, AP 1004 may send an authentication response frame 1012 to STA 1006. Upon reception of authentication response frame 1012, STA 1006 may send an association request frame 1014 to AP 1004, requesting to start a secure session with AP 1004. If AP 1004 accepts the association request of STA 1006, AP 1004 sends an association response frame 1016 to indicate that the secure session is established.

[0097] A drawback of the BSS transition process illustrated in FIG. 10 is the duration required to exchange authentication request frame 1010 and authentication response frame 1012. To mitigate this problem, the IEEE 802. 10 standard introduced the Fast BSS transition (FT) protocols. The FT protocols seek to reduce the length of time that connectivity is lost between a STA and the distribution system (DS) during a BSS transition. The FT protocols are part of the reassociation service and only apply to STA transitions between APs within the same mobility domain within the same extended service set (ESS). The FT protocols require information to be exchanged during the initial association (or a later reassociation) between a STA (denoted as the FT Originator (FTO)) and an AP. The initial exchange is referred to as the FT initial mobility domain association. Subsequent reassociations to APs within the same mobility domain may make use of the FT protocols.

[0098] The IEEE 802. 11 standard defines two FT protocols: an FT protocol and an FT resource request protocol. The FT protocol is executed when an FTO makes a transition to a target AP and does not require a resource request prior to the transition. The FT resource request protocol is executed when an FTO requires a resource request prior to the transition. For an FTO to move from its current AP to a target AP utilizing the FT protocols, the message exchanges are performed using one of two methods: Over-the-Air or Over-the-DS. Using the Over-the-Air method, the FTO communicates directly with the target AP using IEEE 802.10 authentication with the FT authentication algorithm. Using the Over-the-DS method, the FTO communicates with the target AP via the current AP.

[0099] The communication between the FTO and the target AP is carried in FT Action frames between the FTO and the current AP. Between the current AP and target AP, communication is via an encapsulation. The current AP converts between the two encapsulations. APs advertise both capabilities and policies for supporting the FT protocols and methods.

[0100] FIG. 11 illustrates an example of 1100 of the FT protocol using the Over-the-DS method. As shown in FIG. 11, example 1100 may include APs 1102 and AP 1104 and STA 1106. STA 1106 may be associated with AP 1102 at the beginning of example 1100 and may have established a secure session 1108 with AP 1102. APs 1102 and AP 1104 can communicate through the DS. STA 1106 is the FTO. AP 1104 is the Target AP.

[0101] The Over-the-DS fast BSS transition may begin with STA 1106 (the FTO) sending an FT request 1110 to AP 1104 (the target AP), via AP 1102. FT request 1110 may include an address (e.g., MAC address) of STA 1106 and an address (e.g., BSSID) of AP 1104. AP 1104 may respond to FT request 1110 by sending an FT response 1112 to STA 1106, via AP 1102. FT response 1112 may include an address of STA 1106, an address of AP 1104, and a status. If STA 1106 does not receive a response to FT request 1110, it may reissue the request following the restrictions given for Authentication frames.

[0102] If the status in FT response 1112 indicates SUCCESS, STA1106 may send a reassociation request frame 1114 to AP 1104. AP 1104 may respond with a reassociation response 1116 to STA 1106.

[0103] While the FT protocol eliminates the need for authentication steps, a drawback of the FT protocol is that the FTO and the target AP are still required to perform reassociation steps.

[0104] FIG. 12 illustrates an example 1200 of a procedure for session transfer via roaming. As shown in FIG. 12, example 1200 may include a STA 1202, an AP 1204, an AP 1206, and a controller 1208. Controller 1208 may enable communication between AP 1204 and AP 1206. Controller 1208 may be responsible for authentication and association; thus for a session transfer, it may not necessary to repeat the steps of authentication and association.

[0105] At the beginning of example 1200, STA 1202 may be associated with AP 1204 and may have established a secure session with AP 1204. To initiate a session transfer from AP 1204 to AP 1206, STA 1202 may send one or more uplink data frames 1210 including all the buffered uplink data to AP 1204. Subsequently, STA 1202 may send a roaming announcement indicator (RAI) (or roaming request) frame 1212 to AP 1204. RAI frame 1212 may include the address of AP 1206.

[0106] On receiving frame 1212, AP 1204 may communicate with controller 1208 to determine if the session transfer is approved. If controller 1208 approves the session transfer, AP 1204 transmits frame 1214 to STA 1202. Frame 1212 may be called roaming announcement response (RAR) frame or roaming response frame.

[0107] If controller 1208 approves the session transfer, controller 1208 transfers a context related to STA 1202 from AP 1204 to AP 1206. The context related to STA 1202 may include sequence numbers per traffic identifier for STA 1202. Controller 1208 may also change a data path for data incoming from upper layers from AP 1204 to AP 1206. After transmitting frame 1214, AP 1204 may send one or more downlink data frames 1216 (including all its buffered downlink data for STA 1202) to STA 1202. After AP 1204 sends all data in its buffer for STA 1202, AP 1206 may transmit a link delete frame 1222 to STA 1202 indicating the link between STA 1202 and AP 1204 has been deleted and that STA 1202 may not communicate with AP 1204.

[0108] STA 1202 may start communicating with AP 1206 after receiving frame 1214. Specifically, AP 1206 may transfer packets received from upper layers to STA 1202 via one or more downlink data frames 1218. Conversely, STA 1202 may transmit one or more uplink data frames 1220 AP 1206.

[0109] As described above, the procedure of FIG. 12 requires that STA 1202 transmit all of its uplink data (drain its uplink data) to AP 1204 before transmitting a roaming request to AP 1204. This has the advantage that that data, which is probably part of an ongoing exchange, is, to some extent, protected from potential disruptions occasioned by the handover. However, the inventors have realised that a problem that may arise with this procedure in that STA 1202 may require a relatively long time in order to drain its uplink data (e.g., STA 1202 may not be able to access the channel due to heavy channel contention and / or STA 1202 may have a substantial amount of buffered uplink data). This may delay the sending of the roaming request by STA 1202 and the transition by STA 1202 from AP 1204 to AP 1206. Meanwhile, the link between STA 1202 and AP 1204 may deteriorate and STA 1202 may even lose connection with AP 1204. Buffered data at STA 1202 may be lost due to the delayed transition (roaming) from AP 1204 to AP 1206.

[0110] Embodiments of the present disclosure, as further described below, address the abovediscussed problem of existing technologies. In an aspect, a STA may transmit to a first AP a first frame indicating / requesting a transition (roaming) from the first AP to a second AP. The STA may receive from the first AP a second frame indicating a parameter related to transmission by the STA to the first AP, prior to the transition (roaming) from the first AP to the second AP, of data buffered at the STA. In an embodiment, the parameter may indicate whether the STA is to transmit to the first AP, prior to the transition (roaming) from the first AP to the second AP, an amount of the data buffered at the STA. In an example, the parameter may indicate that the STA is not to transmit to the first AP, prior to the transition (roaming) from the first AP to the second AP, any of the data buffered at the STA. In another embodiment the parameter may indicate an amount of the data buffered at the STA to transmit to the first AP, prior to the transition (roaming) from the first AP to the second AP. In another embodiment, alternatively or additionally, the parameter may indicate a first traffic identifier (TID) (or a first access category) of first data, of the data buffered at the STA, to transmit to the first AP, prior to the transition (roaming) from the first AP to the second AP. In another embodiment, alternatively or additionally, the parameter may indicate a first duration for transmission to the first AP, prior to the transition (roaming) from the first AP to the second AP, of a portion of the data buffered at the STA.

[0111] The parameter may be based on a signal strength. In an embodiment, the signal strength may comprise a received signal strength of a frame transmitted by the first AP and received by the STA. In another embodiment, the signal strength may comprise a received signal strength of a frame transmited by the second AP and received by the STA. In a further embodiment, the signal strength may comprise a received signal strength of a frame transmited by the STA and received by the first AP. In a further embodiment, the signal strength may comprise a received signal strength of a frame transmited by the STA and received by the second AP.

[0112] The STA may transmit to the AP first data, of the data buffered at the STA, based on the parameter, before transitioning from the first AP to the second AP. As such, the AP may control the amount / type of data to be transmited by the STA to the AP before transitioning from the first AP to the second AP. This may reduce the amount of data transmited to the first AP before the transition from the first AP to the second AP and may accelerate the transition from the first AP to the second AP.

[0113] FIG. 13 illustrates an example 1300 of a roaming procedure according to an embodiment. Example 1300 is provided for the purpose of illustration only and is not limiting of embodiments of the present disclosure. As shown in FIG. 13, example 1300 may include a STA 1302, APs 1304 and 1306, and a device 1308. In an embodiment, each of AP 1304, AP 1306, and STA 1302 may be a multi-link device (MLD), that is a device capable of operating over multiple links as defined by the IEEE 802. 11 standard.

[0114] Device 1308 may be a controller. Device 1308 may be connected (e.g., through a wired / wireless backhaul) to each of APs 1304 and 1306. As such, device 1308 may enable communication between APs 1304 and 1306. For example, device 1308 may enable context transfer between APs 1304 and 1306 as a STA associated with one of APs 1304 and 1306 roams / transitions to another one of APs 1304 and 1306. As such, association and authentication of the STA may not need to be performed again when the STA roams / transitions between APs 1304 and 1306.

[0115] At the beginning of example 1300, STA 1302 may be associated with AP 1304 and may have established a secure session with AP 1304. In an embodiment, STA 1302 may have an established link with AP 1304. In an example, STA 1302 may determine to initiate a session transfer from AP 1304. When STA 1302 initiates the session transfer, STA 1302 may have buffered data for transmission to AP 1304. To initiate session transfer from AP 1304 to another AP, STA 1302 may transmit a frame 1310 to AP 1304. Frame 1310 may indicate a transition (roaming) from AP 1304 to AP 1306. Frame 1310 may comprise a roaming request.

[0116] Frame 1310 may comprise a link reconfiguration notify frame, a roaming announcement notify frame, a roaming announcement request frame, a roaming request frame, a roaming notify frame, or a probe request frame.

[0117] On receiving frame 1310, AP 1304 may transmit a frame 1312 to STA 1302. Frame 1312 may comprise a roaming response. Frame 1312 may indicate a parameter related to transmission by STA 1302 to AP 1304, prior to the transition (roaming) from AP 1304 to AP 1306, of data buffered at STA 1302 for AP 1304.

[0118] In an embodiment, the parameter may indicate whether STA 1302 is to transmit to AP 1304, prior to the transition (roaming) from AP 1304 to AP 1306, an amount of the data buffered at the STA1302. For example, the parameter may indicate that STA 1302 is not to transmit to the AP 1304, prior to the transition (roaming) from AP 1304 to AP 1306, any of the data buffered at STA 1302. In another example, the parameter may indicate that STA 1302 is to transmit to AP 1304, prior to the transition (roaming) from AP 1304 to AP 1306, all of the data buffered at the STA. In another embodiment, the parameter may indicate an amount of the data buffered at the STA to transmit to AP 1304, prior to the transition (roaming) from AP 1304 to AP 1306. The amount may be indicated as a number of bits, bytes, or octets, for example. In an example, the amount may be equal to zero.

[0119] In another embodiment, alternatively or additionally, the parameter may indicate a first traffic identifier (TID) (or a first access category) of first data, of the data buffered at STA 1302, to be transmitted to AP 1304, prior to the transition (roaming) from AP 1304 to AP 1306. In an embodiment, frame 1310 may indicate one or more TIDs (or one or more ACs) associated with the data buffered at STA 1302. In an implementation, frame 1310 may comprise a buffer status report (BSR) that indicates the one or more TIDs. The one or more TIDs (or one or more ACs) may comprise the first TID (or first AC).

[0120] In a further embodiment, alternatively or additionally, the parameter may indicate a first duration for transmission to AP 1304, prior to the transition (roaming) from AP 1304 to AP 1306, of a portion of the data buffered at STA 1302. In an embodiment, the first duration comprises a duration of a transmission opportunity (TXOP) initiated by frame 1312. In an embodiment, frame 1310 indicates a second duration. The first duration may be based on the second duration. In an embodiment, the first duration is less than or equal to the second duration. In an embodiment, the second duration comprises a duration of a TXOP initiated by frame 1310.

[0121] In an embodiment, the parameter may be based on a signal strength. In an embodiment, the signal strength may comprise a received signal strength of a frame transmitted by AP 1304 and received by STA 1302. Examples of such a frame may include a beacon frame transmitted by AP 1304 or an ack frame transmitted by AP 1304 to STA 1302. In an embodiment, where the received signal strength is lower than a threshold, the parameter may indicate a smaller amount (e.g., zero) of the buffered data to transmit by STA 1302 to AP 1304 prior to transitioning from AP 1304 to AP 1306, one or more TIDs associated with low latency traffic, or a shorter duration for transmission to AP 1304 prior to the transition from AP 1304 to AP 1306.

[0122] In another embodiment, the signal strength may comprise a received signal strength of a frame transmitted by AP 1306 and received by STA 1302. An example of such a frame may include a beacon frame transmitted by AP 1306. In an embodiment, where the received signal strength is greater than or equal to a threshold, the parameter may indicate a smaller amount (e.g., zero) of the buffered data to transmit by STA 1302 to AP 1304 prior to transitioning from AP 1304 to AP 1306, one or more TIDs associated with low latency traffic, or a shorter duration for transmission to AP 1304 prior to the transition from AP 1304 to AP 1306. In another embodiment, the signal strength may comprise a received signal strength of a frame transmitted by STA 1302 and received by AP 1304. Examples of such a frame may include a data frame transmitted by STA 1302 to AP 1304. In an embodiment, where the received signal strength is lower than a threshold, the parameter may indicate a smaller amount (e.g., zero) of the buffered data to transmit by STA 1302 to AP 1304 prior to transitioning from AP 1304 to AP 1306, one or more TIDs associated with low latency traffic, or a shorter duration for transmission to AP 1304 prior to the transition from AP 1304 to AP 1306.

[0123] In another embodiment, the signal strength may comprise a received signal strength of a frame transmitted by STA 1302 and received by AP 1306. Examples of such a frame may include a data frame transmitted by STA 1302 to AP 1304 and received by AP 1306. In an embodiment, where the received signal strength is greater than or equal to a threshold, the parameter may indicate a smaller amount (e.g., zero) of the buffered data to transmit by STA 1302 to AP 1304 prior to transitioning from AP 1304 to AP 1306, one or more TIDs associated with low latency traffic, or a shorter duration for transmission to AP 1304 prior to the transition from AP 1304 to AP 1306.

[0124] Returning to FIG. 13, upon receiving frame 1312, STA 1302 may transmit to AP 1304 a frame 1314. In an embodiment, STA 1302 may transmit frame 1314 based on the parameter indicated in frame 1312. For example, frame 1314 may be a data frame comprising an amount of the buffered data based on the parameter indicated in frame 1312. In another example, alternatively or additionally, frame 1314 may be a data frame comprising a TID (or AC) based on the parameter indicated in frame 1312. In another example, alternatively or additionally, STA 1302 may transmit frame 1314 within a duration indicated by the parameter indicated in frame 1312.

[0125] Upon reception frame 1314, AP 1304 may communicate with device 1308 for transition / roaming. Device 1308 transfers a context related to STA 1302 from AP 1304 to AP 1306. The context related to STA 1302 may include sequence numbers per traffic identifier for STA 1302. Device 1308 may also change a data path for data incoming from upper layers from AP 1304 to AP 1306. AP 1304 may send one or more downlink data frames 1316 (including all its buffered downlink data for STA 1302) to STA 1302. After AP 1304 sends all data in its buffer for STA 1302, AP 1306 may transmit a link delete frame 1318 to STA 1302 indicating the link between STA 1302 and AP 1304 has been deleted and that STA 1302 may not communicate with AP 1304.

[0126] FIG. 14 illustrates an example 1400 of a roaming procedure according to an embodiment. Example 1400 is provided for the purpose of illustration only and is not limiting of embodiments of the present disclosure. As shown in FIG. 14, example 1400 may include a STA 1402, APs 1404 and 1406, and a device 1408. In an embodiment, each of AP 1404, AP 1406, and STA 1402 may be a multi-link device (MLD), that is a device capable of operating over multiple links as defined by the IEEE 802. 11 standard.

[0127] Device 1408 may be a controller. Device 1408 may be connected (e.g., through a wired / wireless backhaul) to each of APs 1404 and 1406. As such, device 1408 may enable communication between APs 1404 and 1406. For example, device 1408 may enable context transfer between APs 1404 and 1406 as a STA associated with one of APs 1404 and 1406 roams / transitions to another one of APs 1404 and 1406. As such, association and authentication of the STA may not need to be performed again when the STA roams / transitions between APs 1404 and 1406.

[0128] At the beginning of example 1400, STA 1402 may be associated with AP 1404 and may have established a secure session with AP 1404. In an embodiment, STA 1402 may have an established link with AP 1404. In an example, STA 1402 may determine to initiate a session transfer from AP 1404. When STA 1402 initiates the session transfer, STA 1402 may have buffered data for transmission to AP 1404. To initiate session transfer from AP 1404 to another AP, STA 1402 may transmit a frame 1410 to AP 1404. Frame 1410 may indicate atransition (roaming) from AP 1404 to AP 1406. Frame 1410 may comprise a roaming request.

[0129] Frame 1410 may comprise a link reconfiguration notify frame, a roaming announcement notify frame, a roaming announcement request frame, a roaming request frame, a roaming notify frame, or a probe request frame.

[0130] On receiving frame 1410, AP 1404 may transmit a frame 1412 to STA 1402. Frame 1412 may comprise a roaming response. Frame 1412 may indicate a parameter related to transmission by STA 1402 to AP 1404, prior to the transition (roaming) from AP 1404 to AP 1406, of data buffered at STA 1402 for AP 1404. In example 1400, the parameter indicates an amount (X) of the data buffered at STA 1402 to transmit to AP 1404, prior to the transition (roaming) from AP 1404 to AP 1406. The amount (X) may be indicated as a number of bits, bytes, octets, etc.

[0131] Upon receiving frame 1412, STA 1402 may transmit to AP 1404 a frame 1414, based on the parameter indicated in frame 1412. Frame 1414 may be a data frame comprising the amount (X) of the buffered data based on the parameter indicated in frame 1412. In another example, STA 1402 may transmit to AP 1404 a plurality of frames comprising data with a total size equal to the amount (X) indicated by the parameter indicated in frame 1412.

[0132] In an embodiment, based on receiving frame 1414, AP 1404 may transmit to STA 1402 a frame 1416 instructing STA 1402 to roam / transition from AP 1404 to AP 1406. Based on receiving frame 1416, STA 1402 may begin transmitting uplink data to AP 1406.

[0133] In another embodiment, upon receiving frame 1414, AP 1404 may further communicate with device 1408 to initiate context transfer to AP 1406. Device 1408 transfers a context related to STA 1402 from AP 1404 to AP 1406. The context related to STA 1402 may include sequence numbers per traffic identifier for STA 1402. Device 1408 may also change a data path for data incoming from upper layers from AP 1404 to AP 1406. AP 1404 may send one or more downlink data frames (not shown in FIG. 14) (e.g., including all its buffered downlink data for STA 1402) to STA 1402. In an embodiment, after AP 1404 sends all data in its buffer for STA 1402, AP 1404 transmits frame 1416 to STA 1402. In another embodiment, after AP 1404 sends all data in its buffer for STA 1402, AP 1406 may transmit a link delete frame 1418 to STA 1402 indicating the link between STA 1402 and AP 1404 has been deleted and that STA 1402 may not communicate with AP 1404.

[0134] FIG. 15 illustrates an example 1500 of a roaming procedure according to an embodiment. Example 1500 is provided for the purpose of illustration only and is not limiting of embodiments of the present disclosure. As shown in FIG. 15, example 1500 may include a STA 1502, APs 1504 and 1506, and a device 1508. In an embodiment, each of AP 1504, AP 1506, and STA 1502 may be a multi-link device (MLD), that is a device capable of operating over multiple links as defined by the IEEE 802. 11 standard.

[0135] Device 1508 may be a controller. Device 1508 may be connected (e.g., through a wired / wireless backhaul) to each of APs 1504 and 1506. As such, device 1508 may enable communication between APs 1504 and 1506. For example, device 1508 may enable context transfer between APs 1504 and 1506 as a STA associated with one of APs 1504 and 1506 roams / transitions to another one of APs 1504 and 1506. As such, association and authentication of the STA may not need to be performed again when the STA roams / transitions between APs 1504 and 1506.

[0136] At the beginning of example 1500, STA 1502 may be associated with AP 1504 and may have established a secure session with AP 1504. In an embodiment, STA 1502 may have an established link with AP 1504. In an example, STA 1502 may determine to initiate a session transfer from AP 1504. When STA 1502 initiates the session transfer, STA 1502 may have buffered data for transmission to AP 1504. To initiate session transfer from AP 1504 to another AP, STA 1502 may transmit a frame 1510 to AP 1504. Frame 1510 may indicate a transition (roaming) from AP 1504 to AP 1506. Frame 1510 may comprise a roaming request. Frame 1510 may comprise a link reconfiguration notify frame, a roaming announcement notify frame, a roaming announcement request frame, a roaming request frame, a roaming notify frame, or a probe request frame. In an embodiment, frame 1510 may comprise a buffer status report (BSR) that indicates one or more TIDs (or one or more ACs) of data buffered at STA 1502 for AP 1504.

[0137] On receiving frame 1510, AP 1504 may transmit a frame 1512 to STA 1502. Frame 1512 may comprise a roaming response. Frame 1512 may indicate a parameter related to transmission by STA 1502 to AP 1504, prior to the transition (roaming) from AP 1504 to AP 1506, of data buffered at STA 1502 for AP 1504. In example 1500, the parameter indicates a first traffic identifier (TID) (TID 1) of the one or more TIDs (or a first access category of the one or more ACs) of first data, of the data buffered at STA 1502, to be transmitted to AP 1504, prior to the transition (roaming) from AP 1504 to AP 1506. For example, the first TID (TID 1) may correspond to low latency traffic, and the first data may correspond to the low latency data among the data buffered at STA 1502 for AP 1504.

[0138] Upon receiving frame 1512, STA 1502 may transmit to AP 1504 a frame 1514, based on the parameter indicated in frame 1512. Frame 1514 may be a data frame comprising a TID (or AC) based on the parameter indicated in frame 1512. Specifically, as shown in FIG. 15, frame 1514 may be a data frame associated with the first TID (TID 1). In an embodiment, frame 1514 may further comprise a BSR that indicates one or more TIDs (or one or more ACs) of data buffered at STA 1502 for AP 1504. In an embodiment, based on the BSR indicating a queue size with a value of zero for the first TID (TID 1), AP 1504 may transmit to STA 1502 a frame 1516 instructing STA 1502 to roam / transition from AP 1504 to AP 1506. Based on receiving frame 1516, STA 1502 may begin transmitting uplink data to AP 1506.

[0139] In an embodiment, upon receiving frame 1514, AP 1504 may communicate with device 1508 to initiate context transfer to AP 1506. Device 1508 transfers a context related to STA 1502 from AP 1504 to AP 1506. The context related to STA 1502 may include sequence numbers per traffic identifier for STA 1502. Device 1508 may also change a data path for data incoming from upper layers from AP 1504 to AP 1506. In an embodiment, AP 1504 may send one or more downlink data frames (not shown in FIG. 15) (including all its buffered downlink data for STA 1502) to STA 1502. In an embodiment, after AP 1504 sends all data in its buffer for STA 1502, AP 1504 transmits frame 1516 to STA 1502. In another embodiment, after AP 1504 sends all data in its buffer for STA 1502, AP 1506 may transmit a link delete frame 1518 to STA 1502 indicating the link between STA 1502 and AP 1504 has been deleted and that STA 1502 may not communicate with AP 1504.

[0140] FIG. 16 illustrates an example 1600 of a roaming procedure according to an embodiment. Example 1600 is provided for the purpose of illustration only and is not limiting of embodiments of the present disclosure. As shown in FIG. 16, example 1600 may include a STA 1602, APs 1604 and 1606, and a device 1608. In an embodiment, each of AP 1604, AP 1606, and STA 1602 may be a multi -link device (MLD), that is a device capable of operating over multiple links as defined by the IEEE 802. 11 standard.

[0141] Device 1608 may be a controller. Device 1608 may be connected (e.g., through a wired / wireless backhaul) to each of APs 1604 and 1606. As such, device 1608 may enable communication between APs 1604 and 1606. For example, device 1608 may enable context transfer between APs 1604 and 1606 as a STA associated with one of APs 1604 and 1606 roams / transitions to another one of APs 1604 and 1606. As such, association and authentication of the STA may not need to be performed again when the STA roams / transitions between APs 1604 and 1606.

[0142] At the beginning of example 1600, STA 1602 may be associated with AP 1604 and may have established a secure session with AP 1604. In an embodiment, STA 1602 may have an established link with AP 1604. In an example, STA 1602 may determine to initiate a session transfer from AP 1604. When STA 1602 initiates the session transfer, STA 1602 may have buffered data for transmission to AP 1604. To initiate session transfer from AP 1604 to another AP, STA 1602 may transmit a frame 1610 to AP 1604. Frame 1610 may indicate atransition (roaming) from AP 1604 to AP 1606. Frame 1610 may comprise a roaming request. Frame 1610 may comprise a link reconfiguration notify frame, a roaming announcement notify frame, a roaming announcement request frame, a roaming request frame, a roaming notify frame, or a probe request frame. In an embodiment, frame 1610 may comprise a parameter indicating a first duration (equal to x) for STA 1602 to transmit to AP 1604 buffered data for AP 1604. In an embodiment, the first duration comprises a duration of a TXOP initiated by frame 1610. In an embodiment, the first duration may correspond to a requested / preferred / recommended duration by STA 1602.

[0143] On receiving frame 1610, AP 1604 may transmit a frame 1612 to STA 1602. Frame 1612 may comprise a roaming response. Frame 1612 may indicate a parameter related to transmission by STA 1602 to AP 1604, prior to the transition (roaming) from AP 1604 to AP 1606, of data buffered at STA 1602 for AP 1604. In example 1600, the parameter indicates a second duration (equal to y) for transmission by STA 1602 to AP 1604, prior to the transition (roaming) from AP 1604 to AP 1606, of a portion of the data buffered at STA 1602 for AP 1604. The second duration may comprise a duration of a transmission opportunity (TXOP) initiated by frame 1612. The second duration may be based on the first duration. The second duration may be less than or equal to the first duration.

[0144] Upon receiving frame 1612, STA 1602 may transmit to AP 1604 one or more frames during the second duration indicated by the parameter. For example, STA 1602 may transmit frames 1614 and 1616 comprising data for AP 1604 during the second duration indicated by the parameter. AP 1604 may respond to frames 1614 and 1616 by transmitting respective BA frames (not shown in FIG. 16) to STA 1602.

[0145] In an embodiment, after the end of the second duration, AP 1604 may transmit to STA 1602 a frame 1618 instructing STA 1602 to roam / transition from AP 1604 to AP 1606. Based on receiving frame 1618, STA 1602 may begin transmitting uplink data to AP 1606.

[0146] In an embodiment, after receiving frames 1614 and 1616 and / or after the end of the second duration, AP 1604 may communicate with device 1608 to initiate context transfer to AP 1606. Device 1608 transfers a context related to STA 1602 from AP 1604 to AP 1606. The context related to STA 1602 may include sequence numbers per traffic identifier for STA 1602. Device 1608 may also change a data path for data incoming from upper layers from AP 1604 to AP 1606. In an embodiment, AP 1604 may send one or more downlink data frames (not shown in FIG. 16) (including all its buffered downlink data for STA 1602) to STA 1602. In an embodiment, after AP 1604 sends all data in its buffer for STA 1602, AP 1604 transmits frame 1618 to STA 1602. In another embodiment, after AP 1604 sends all data in its buffer for STA 1602, AP 1606 may transmit a link delete frame 1620 to STA 1602 indicating the link between STA 1602 and AP 1604 has been deleted and that STA 1602 may not communicate with AP 1604.

[0147] FIG. 17 illustrates an example process 1700 according to an embodiment. Example process 1700 is provided for the purpose of illustration only and is not limiting embodiments. Process 1700 may be performed by a first AP, such as AP 1304, AP 1404, AP 1504, or AP 1604. As shown in FIG. 17, process 1700 may comprise steps 1702 and 1704.

[0148] Step 1702 comprises receiving, by the first AP from a STA, a first frame indicating a transition (roaming) from the first AP to a second AP. The first frame may comprise a roaming request. The STA may be associated with the first AP. Step 1704 comprises transmitting, by the first AP to the STA, a second frame indicating a parameter related to transmission to the first AP, prior to the transition (roaming) from the first AP to the second AP, of data buffered at the STA. in an embodiment, the second frame may comprise a roaming response.

[0149] In an embodiment, the parameter may indicate whether the STA is to transmit to the first AP, prior to the transition (roaming) from the first AP to the second AP, an amount of the data buffered at the STA.

[0150] In another embodiment, the parameter may indicate that the STA is not to transmit to the first AP, prior to the transition (roaming) from the first AP to the second AP, any of the data buffered at the STA.

[0151] In another embodiment, the parameter indicates that the STA is to transmit to the first AP, prior to the transition (roaming) from the first AP to the second AP, all of the data buffered at the STA.

[0152] In another embodiment, the parameter may indicate an amount of the data buffered at the STA to transmit to the first AP, prior to the transition (roaming) from the first AP to the second AP. In an embodiment, the amount may indicate bits, bytes, octets. In another embodiment, the amount may be zero. In an embodiment, process 1700 may further comprise receiving, by the first AP from the STA, one or more third frames comprising first data for the first AP with a total size equal to the amount indicated by the parameter.

[0153] In an embodiment, process 1700 may further comprise based on the receiving of the first data, transmitting, by the first AP to the STA, a fourth frame instructing the STA to roam / transition from the first AP to the second AP.

[0154] In an embodiment, the parameter may indicate a first traffic identifier (TID) (or a first access category (AC)) of first data, of the data buffered at the STA, to be transmitted to the first AP, prior to the transition (roaming) from the first AP to the second AP.

[0155] In an embodiment, the first frame may indicate one or more TIDs (one or more ACs) associated with the data buffered at the STA. In an embodiment, the first frame may comprise a buffer status report (BSR) that indicates the one or more TIDs. The one or more TIDs (one or more ACs) may comprise the first TID (or first AC).

[0156] In an embodiment, process 1700 may further comprise receiving, by the first AP from the STA, a third frame comprising: a data frame associated with the first TID; and a second BSR.

[0157] In an embodiment, process 1700 may comprise based on the second BSR indicating a queue size with a value of zero for the first TID, transmitting, by the first AP to the STA, a fourth frame instructing the STA to roam / transition from the first AP to the second AP.

[0158] In another embodiment, the parameter may indicate a first duration for transmission to the first AP, prior to the transition (roaming) from the first AP to the second AP, of a portion of the data buffered at the STA. In an embodiment, the first duration may comprise a duration of a transmission opportunity (TXOP) initiated by the second frame. In an embodiment, the first frame may indicate a second duration. The first duration may be based on the second duration. In an embodiment, the first duration may be less than or equal to the second duration. In an embodiment, the second duration may comprise a duration of a transmission opportunity (TXOP) initiated by the first frame.

[0159] In an embodiment, process 1700 may comprise receiving, by the first AP from the STA, one or more third frames comprising data for the first AP during the first duration indicated by the parameter.

[0160] In an embodiment, process 1700 may further comprise, after an end of the first duration, transmitting, by the first AP to the STA, a fourth frame instructing the STA to roam / transition from the first AP to the second AP.

[0161] In an embodiment, the parameter may be based on a signal strength. In an embodiment, the signal strength may comprise a received signal strength of a frame transmitted by the first AP and received by the STA. In another embodiment, the signal strength may comprise a received signal strength of a frame transmitted by the second AP and received by the STA. In another embodiment, the signal strength may comprise a received signal strength of a frame transmitted by the STA and received by the second AP.

[0162] FIG. 18 illustrates an example process 1800 according to an embodiment. Example process 1800 is provided for the purpose of illustration only and is not limiting embodiments. Process 1800 may be performed by a STA, such as STA 1302, STA 1402, STA 1502, or STA 1602. As shown in FIG. 18, process 1800 may comprise steps 1802 and 1804.

[0163] Step 1802 comprises transmitting, by the STA to a first AP, a first frame indicating a transition (roaming) from the first AP to a second AP. The STA may be associated with the first AP.

[0164] Step 1804 comprises receiving, by the STA from the first AP, a second frame indicating a parameter related to transmission by the STA to the first AP, prior to the transition (roaming) from the first AP to the second AP, of data buffered at the STA.

[0165] In an embodiment, the parameter may indicate whether the STA is to transmit to the first AP, prior to the transition (roaming) from the first AP to the second AP, an amount of the data buffered at the STA.

[0166] In another embodiment, the parameter may indicate that the STA is not to transmit to the first AP, prior to the transition (roaming) from the first AP to the second AP, any of the data buffered at the STA.

[0167] In another embodiment the parameter indicates that the STA is to transmit to the first AP, prior to the transition (roaming) from the first AP to the second AP, all of the data buffered at the STA.

[0168] In another embodiment, the parameter may indicate an amount of the data buffered at the STA to transmit to the first AP, prior to the transition (roaming) from the first AP to the second AP. In an embodiment, the amount may indicate bits, bytes, octets. In another embodiment, the amount may be zero. In an embodiment, process 1800 may further comprise transmitting, by the STA to the first AP, one or more third frames comprising first data for the first AP with a total size equal to the amount indicated by the parameter.

[0169] In an embodiment, process 1800 may further comprise receiving, by the STA from the first AP a fourth frame instructing the STA to roam / transition from the first AP to the second AP.

[0170] In an embodiment, the parameter may indicate a first traffic identifier (TID) (or a first access category (AC)) of first data, of the data buffered at the STA, to be transmitted to the first AP, prior to the transition (roaming) from the first AP to the second AP.

[0171] In an embodiment, the first frame may indicate one or more TIDs (one or more ACs) associated with the data buffered at the STA. In an embodiment, the first frame may comprise a buffer status report (BSR) that indicates the one or more TIDs (one or more ACs). The one or more TIDs (or one or more ACs) may comprise the first TID (first AC).

[0172] In an embodiment, process 1800 may further comprise transmitting, by the STA to the first AP, a third frame comprising a data frame associated with the first TID and a second BSR.

[0173] In an embodiment, process 1800 may comprise based on the second BSR indicating a queue size with a value of zero for the first TID, receiving, by the STA from the first AP, a fourth frame instructing the STA to roam / transition from the first AP to the second AP.

[0174] In another embodiment, the parameter may indicate a first duration for transmission to the first AP, prior to the transition (roaming) from the first AP to the second AP, of a portion of the data buffered at the STA. In an embodiment, the first duration may comprise a duration of a transmission opportunity (TXOP) initiated by the second frame.

[0175] In an embodiment, the first frame may indicate a second duration. The first duration may be based on the second duration. In an embodiment, the first duration may be less than or equal to the second duration. In an embodiment, the second duration may comprise a duration of a transmission opportunity (TXOP) initiated by the first frame.

[0176] In an embodiment, process 1800 may further comprise transmitting, by the STA to the first AP, one or more third frames comprising traffic for the first AP during the first duration indicated by the parameter.

[0177] In an embodiment, process 1800 may comprise, after an end of the first duration, receiving, by the STA from the first AP, a fourth frame instructing the STA to roam / transition from the first AP to the second AP.

[0178] In an embodiment, the parameter may be based on a signal strength. In an embodiment, the signal strength may comprise a received signal strength of a frame transmitted by the first AP and received by the STA. In another embodiment, the signal strength may comprise a received signal strength of a frame transmitted by the second AP and received by the STA. In another embodiment, the signal strength may comprise a received signal strength of a frame transmitted by the STA and received by the second AP.

Claims

29CLAIMS:

1. A method, comprising: receiving, by a first access point (AP) from a station (STA), a first frame indicating a transition from the first AP to a second AP; and transmitting, by the first AP to the STA, a second frame indicating a parameter related to transmission to the first AP, prior to the transitioning from the first AP to the second AP, of data buffered at the STA.

2. The method of claim 1 wherein the first frame comprises a buffer status report (BSR) indicating one or more traffic identifiers (TIDs) associated with traffic for the first AP buffered at the STA, wherein the indication of the transition from the first AP to the second AP is a request to roam (transition) from the first AP to a second AP, and wherein the parameter relating to transmission to the first AP comprises a first TID of the one or more TIDs, the method comprising receiving, by the first AP from the STA, a third frame comprising: a data frame associated with the first TID; and a second BSR, and based on the second BSR indicating a queue size with a value of zero for the first TID, transmitting, by the first AP to the STA, a fourth frame instructing the STA to transition from the first AP to the second AP.

3. A method, comprising: transmitting, by a station (STA) to a first access point (AP), a first frame indicating a transition from the first AP to a second AP; and receiving, by the STA from the first AP, a second frame indicating a parameter related to transmission by the STA to the first AP, prior to the transition from the first AP to the second AP, of data buffered at the STA.

4. The method of claim 330 wherein the first frame comprises a buffer status report (BSR) indicating one or more traffic identifiers (TIDs) associated with traffic for the first AP buffered at the STA, wherein the indication of the transition from the first AP to the second AP is a request to roam (transition) from the first AP to a second AP, and wherein the parameter relating to transmission to the first AP comprises a first TID of the one or more TIDs, the method comprising transmitting, by the STA to the first AP, a second frame comprising: a data frame associated with the first TID; and a second BSR, and based on the second BSR indicating a queue size with a value of zero for the first TID, receiving, by the STA grom the first AP, a fourth frame instructing the STA to roam / transition from the first AP to the second AP.

5. The method of any preceding claim, wherein the parameter indicates whether the STA is to transmit to the first AP, prior to the transition from the first AP to the second AP, an amount of the data buffered at the STA.

6. The method of claim 5, wherein the parameter indicates that the STA is not to transmit to the first AP, prior to the transition from the first AP to the second AP, any of the data buffered at the STA.

7. The method of claim 5, wherein the parameter indicates that the STA is to transmit to the first AP, prior to the transition from the first AP to the second AP, all of the data buffered at the STA.

8. The method of any preceding claim, wherein the parameter indicates an amount of the data buffered at the STA to transmit to the first AP, prior to the transition from the first AP to the second AP.

9. The method of claim 8, wherein the amount indicates a number bits, bytes, octets.

10. The method of any of claims 8 or 9, wherein the amount is equal to zero.

11. The method of any of claims 8 or 9 further comprising: transmitting, by the STA to the first AP, one or more third frames comprising first data for the first AP with a total size equal to the amount indicated by the parameter.

12. The method of claim 11, further comprising, receiving, by the STA from the first AP a fourth frame instructing the STA to roam / transition from the first AP to the second AP.

13. The method of any of claims any preceding, wherein the parameter indicates a first traffic identifier (TID) (or a first access category (AC)) of first data, of the data buffered at the STA, to be transmitted to the first, prior to the transition from the first AP to the second AP.

14. The method of claim 13, wherein the first frame indicates one or more TIDs (one or more ACs) associated with the data buffered at the STA.

15. The method of claim 14, wherein the first frame comprises a buffer status report (BSR) that indicates one or more TIDs.

16. The method of any of claims 14 or 15, wherein the one or more TIDs (one or more ACs) comprise the first TID (or first AC).

17. The method of any of claims 13 - 16, further comprising transmitting, by the STA to the first AP, a third frame comprising: a data frame associated with the first TID; and a second BSR.

18. The method of claim 17, further comprising based on the second BSR indicating a queue size with a value of zero for the first TID, receiving, by the STA from the first AP, a fourth frame instructing the STA to roam / transition from the first AP to the second AP.

19. The method of any preceding claim, wherein the parameter indicates a first duration for transmission to the first AP, prior to the transition from the first AP to the second AP, of a portion of the data buffered at the STA.

20. The method of claim 19, wherein the first duration comprises a duration of a transmission opportunity (TXOP) initiated by the second frame.

21. The method of any of claims 19 or 20, wherein the first frame indicates a second duration.

22. The method of claim 21, wherein the first duration is based on the second duration.

23. The method of claim 22, wherein the first duration is less than or equal to the second duration.

24. The method of any of claims 20 - 22, wherein the second duration comprises a duration of a transmission opportunity (TXOP) initiated by the first frame.

25. The method of any of claims 19 - 24, further comprising transmitting, by the STA to the first AP, one or more third frames comprising traffic for the first AP during the first duration indicated by the parameter.

26. The method of claim 25, further comprising after an end of the first duration receiving, by the STA from the first AP, a fourth frame instructing the STA to roam / transition from the first AP to the second AP.

27. The method of any preceding claim, wherein the parameter is based on a signal strength.

28. The method of claim 27, wherein the signal strength comprises a received signal strength of a frame transmitted by the first AP and received by the STA.

29. The method of claim 27, wherein the signal strength comprises a received signal strength of a frame transmitted by the second AP and received by the STA.

30. The method of claim 27 wherein the signal strength comprises a received signal strength of a frame transmitted by the STA and received by the first AP.

31. The method of claim 27, wherein the signal strength comprises a received signal strength of a frame transmitted by the STA and received by the second AP.

32. The method of any preceding claim, wherein the first frame comprises a roaming request.

33. The method of any preceding claim, wherein the second frame comprises a roaming response.

34. An apparatus arranged to operate in an access point (AP) and comprising a processor and a transceiver, wherein, the processor is arranged to:33 receive, via the transceiver, from a station (STA), a first frame indicating a transition from the first AP to a second AP; and transmit, via the transceiver to the STA, a second frame indicating a parameter related to transmission to the first AP, prior to the transition from the first AP to the second AP, of data buffered at the STA.

35. The apparatus of claim 34 wherein the first frame comprises a buffer status report (BSR) indicating one or more traffic identifiers (TIDs) associated with traffic for the first AP buffered at the STA, wherein the indication of the transition from the first AP to the second AP is a request to roam (transition) from the first AP to a second AP, and wherein the parameter relating to transmission to the first AP comprises a first TID of the one or more TIDs, the processor being arranged to receive, via the transceiver from the STA, a third frame comprising: a data frame associated with the first TID; and a second BSR; and based on the second BSR indicating a queue size with a value of zero for the first TID, transmit, via the transceiver, to the STA, a fourth frame instructing the STA to roam / transition from the first AP to the second AP.

36. An apparatus, arranged to operate in a stations (STA) and comprising a processor and a transceiver, the apparatus being arranged to: transmit, via the transceiver, to a first access point (AP), a first frame indicating a transition from the first AP to a second AP; and receive, via the transceiver, from the first AP, a second frame indicating a parameter related to transmission by the STA to the first AP, prior to the transition from the first AP to the second AP, of data buffered at the STA.

37. The apparatus of claim 36 wherein the first frame comprises a buffer status report (BSR) indicating one or more traffic identifiers (TIDs) associated with traffic for the first AP buffered at the STA, wherein the indication of the transition from the first AP to the second AP is a request to roam (transition) from the first AP to a second AP, and2024P00710WG34 wherein the parameter relating to transmission to the first AP comprises a first TID of the one or more TIDs, the processor being arranged to: transmit, via the transceiver, to the first AP, a second frame comprising: a data frame associated with the first TID; and a second BSR; and based on the second BSR indicating a queue size with a value of zero for the first TID, receive, via the transceiver, from the first AP, a fourth frame instructing the STA to roam / transition from the first AP to the second AP.

38. A computer program product, storable on a computer readable medium and arranged, when run on a computer, to execute the method of any of claims 1 - 33.

Images