Patent ID: 12192891

DETAILED DESCRIPTION

Embodiments can include a distributed, high-efficiency approach to associating wireless devices (i.e., STAs) with network controller devices (i.e., APs) in dense operating environments. According to embodiments, APs can broadcast received power value (e.g., RSSI), air time, and data rates of associated STAs information. A newly arrived STA can scan for such broadcasts, measure received power, and generate estimated data rates and thus the needed air time that would result were the STA to associate with an AP, for every AP. The STA can then select an AP for association according to such estimates.

In some embodiments, a STA can establish a subset of AP candidates for association by selecting those APs with the least remaining air time that can satisfy the STA's throughput requirement. A STA can then select one AP from the subset for association. In some embodiments, such a selection can be random.

In some embodiments, a STA can exclude an AP from consideration if a received power value (e.g., RSSI) of a broadcast from the AP is below a predetermined threshold.

In some embodiments, a STA can exclude an AP from consideration if, by associating with the AP, the traffic load of the AP exceeds a predetermined threshold.

In some embodiments, if an AP does not have sufficient air time left (i.e., the AP's traffic load is full or near full), a STA can generate an estimated data rate for itself, based on a received power value from broadcasts by an AP, in referencing the power values of all associated STAs in the broadcasts, multiplying a factor less than one, which is estimated by squeezing all associated STA's air time to make room for the air time needed by the newly arrived STA (all associated STAs will proportionally slow down as the newly arrived STA associates with the AP due to competing air time).

In some embodiments, APs can operate with air time fairness, allocating the amount of air time equal to, or proportionally less than, the air time needed to achieve the expected throughput for each associated STA. If a STA needs much bigger throughput than indicated when the STA associates with the AP, the AP can put a limit on its expected throughput.

FIGS.1A to1Care diagrams showing operations in a wireless environment according to an embodiment. A wireless environment100can include multiple APs102- to102-2and a newly arrived STA104. Newly arrived STA104can seek association with one of APs102-0to -2.

Referring toFIG.1A, each of APs102-0to -2can issue broadcast transmissions108-0to -2. Broadcast transmissions (108-0to -2) can be detected by any compatible STA in range of the originating AP. In some embodiments, broadcast transmissions (108-0to -2) can be periodic beacons transmitted by APs (102-0to -2). In some embodiments, broadcast transmissions (108-0to -2) can be beacon frames compatible with one or more IEEE 802.11 wireless standards. Broadcast transmissions (108-0to -2) can each include communication information110-0to -2corresponding to the APs (102-0to -2). Communication information (110-0to -2) can take any suitable form that can enable a newly arrived STA104to estimate its own data rate with respect to each AP (102-0to -2), as well as available air time for each AP (102-0to -2). In some embodiments, communication information can include any of: receive power for each associated STA, a modulation scheme and/or coding rate for each associated STA, and/or air time for each associated STA at its AP.

Referring toFIG.1B, a newly arrived STA104can extract the communication information (110-0to -2) from broadcast transmissions (108-0to -2). STA104can execute a selection process112to select one of the APs (102-0to -2) for association based on communication information (110-0to -2). In some embodiments, a selection process can include selecting from one or more APs having a lowest available air time, however, alternate embodiments can include processes based on other AP traffic metrics.

Referring toFIG.1C, after selecting an AP, a STA104can execute an association process114with the selected AP. In the embodiment shown, STA104selects AP1, which is one of the APs having a lowest available throughput106-0. Once newly arrived STA104is associated with AP1102-0, AP1its available air time106-0will grow smaller, as a new portion of throughput116is dedicated to STA104.

FIGS.2A to2Care diagram showing operations for a wireless environment according to additional embodiments. In some embodiments, the operations ofFIGS.2A to2Ccan be versions of those shown inFIGS.1A to1C. A wireless environment200can include APs202-0to -3, a joining STA204, and various other STAs (not shown). A total air time of APs (202-0to -3) is represented by a rectangle, and includes dedicated air time (206-0D to206-3D) and available air time (206-0A to206-3A).

FIGS.2A to2Cshow an arrangement in which APs can operate with air time fairness. With air time fairness, an AP can allocate air time based on a STAs expected throughput. Thus, AP1202-0is shown associated with STA11, STA12and STA13(not shown), and allocates air time sufficient to enable equal throughput among the STAs. Similarly, AP2202-1allocates equal throughput to STA21, STA22, STA23, STA24(not shown). AP3202-2is associated with only one station device, STA31(not shown). AP4202-3is associated with STA41, STA42, STA43(not shown).

In some embodiments, newly joining STAx204can have its own throughput value216.

FIG.2Ashows a status of the various devices before STAx204has selected an AP for association. STAx204can detect wireless broadcasts messages from each AP (202-0to -3) which can include information for STAs associated with that AP. AP information can take any suitable form, as described herein or equivalents. From such information, STAx204can estimate its air time for each AP (202-0to -3) based on its throughput value216and determine the available throughput (206-0A to -3A) for all APs (202-0to -3).

FIG.2Bshows operations following STAx204receiving broadcast transmissions. STAx204can generate estimated air time values and select AP candidates for association. STAx204can estimate its effect were it to associate with each AP (202-0to -2). Such operations are represented inFIG.2Bby estimated STA air time values218-0to218-3added to the dedicated air time for each AP (202-0to -3).

Referring still toFIG.2B, a STA can select AP candidates for association according to throughput metrics for the APs. In some embodiments, selection can be based, at least in part, on lowest available air time. It is understood that if the addition of the air time of a STA would exceed the available air time of an AP, the AP can be excluded as a candidate for association. This is represented by AP4202-3inFIG.2B. Because the association of STAx with AP2202-3is estimated to exceed the available air time of AP4202-3, STAx can exclude the AP2202-3from consideration for association. In the embodiment shown, AP1202-0and AP2202-1have a lowest estimated available air time220-0A/220-1A, and so are considered candidates for association (shown by short list222). AP3202-2can be excluded from consideration as its estimated available air time can be determined to be too large. Exclusion of a high available throughput/air time AP, like AP3202-2, can advantageously reserve the AP for other (possibly high throughput) STAs that may arrive in the future.

Selection of AP candidates based on lowest estimated available air time (or greatest estimated aggregate air time) can take any suitable form. In some embodiments, a STA can select some minimum number of APs for consideration (e.g., two). However, alternate embodiments can include other considerations, including but not limited to: a relative difference between estimated air time values (i.e., if there are three AP candidates, but one has an available air time substantially greater than the others, the larger available air time AP is excluded); number of STAs already associated with the AP (an AP with fewer associated STAs may be preferred for association over those with more associated STAs). In some embodiments, selection of one AP from multiple candidates can be a random or pseudorandom selection to prevent multiple STAs executing a same association method from attempting to associate with the same AP.

FIG.2Cshows STAx selecting and associating224with AP1202-0. With the association of STAx, AP1202-0can have a revised, smaller, available air time206-0A′ (and larger aggregate dedicated air time202-0D′).

FIG.3is a diagram showing operations in a wireless environment300according to another embodiment. Wireless environment300can include a number of basic service sets (BSSs)326-0to -2that can each be compatible with an IEEE 802.11 wireless standard. Each BSS (326-0to -2) can include an AP associated with a set of STAs. BSS326-0includes AP1302-0associated with STA11to STA15(304-00to -04). BSS326-1includes AP2302-1associated with STA21and STA22(304-10/11). BSS326-2includes AP3302-2associated with STA31to STA33(304-20to -22). BSSs (326-0to -2) can have overlapping operating ranges. Each of APs (302-0to -2) can maintain traffic information328-0to -2that results from associated STAs. In some embodiments, traffic information (328-0to -2) can include a data rate for each associated STA. In some embodiments, some or all of APs (302-0to -2) can operate with air time fairness. However, in alternate embodiments APs (302-0to -2) may not use air time fairness.

Referring still toFIG.3, STAx304-xcan be an unassociated STA in the operating environment, in range of all BSSs (326-0to -2). STAx304-xcan receive beacon transmissions308-0to -2from APs (302-0to -2). Beacon transmissions (308-0to -2) can include information for STAs associated with APs (302-0to -2), which can take the form of any of those described herein, including but not limited to: any or all of data rate information (328-0to -2); available air time; modulation scheme; or symbol rate.

According to embodiments, an unassociated STA can receive a broadcast transmission from APs that include traffic information for the APs. From such traffic information, a newly arrives STA can estimate its own data rate and effect on AP air time were the STA to associate with the AP. Such broadcast transmissions can take any suitable form according to the wireless protocol.FIG.4shows a broadcast transmission according to one embodiment, and should not be construed as limiting.

FIG.4is a diagram of a broadcast transmission408according to an embodiment. A broadcast transmission408can include a beacon frame compatible with one or more IEEE 802.11 wireless standards. A broadcast transmission408can have various fields, including a frame control, duration, destination address, source address, basic service set ID, sequence control, high throughput control, a frame body408-0, and frame check sequence. A frame body408-0can include non-information element (IE) fields and IE fields408-1. IE fields408-1can include a number of IEs, including an AP Traffic IE410. An AP Traffic IE410can include an IE ID field410-0, a length field410-1and an information field410-2. An IE ID field410-0can identify the IE as including AP traffic information (e.g., for use by a newly arrived ST). A length value410-1can indicate a size of the IE. IE information410-2can include traffic (or communication) information according to any of the embodiments described herein and equivalents.

In some embodiments, IE information410-2can include, but is not limited to, the number of STAs associated with the AP410-20and data for each STA associated with the AP410-21. In the embodiment shown, data for each associated STA410-12can include: a downlink power value (RSSI(dwn)) (i.e., the power value at the STA of transmissions from AP) and a modulation and/or coding scheme for the STA (MCS). Optionally, IE information can also include an uplink power value (RSSI(up)) and/or an air time value (A.T.). An air time value (A.T.) can include air time used by a STA (e.g., running average of up/down time) and/or available air time for the AP. From such traffic information, newly arrived STA can estimate its own data rate for the AP.

As noted herein, traffic information can take various forms.FIG.4shows associated STA information410-21′ provided in a beacon for an alternate embodiment. STA information410-21′ can include RSSI(dwn) as well as a data rate for the associated STA (Data Rate). A Data Rate for the associated STA can be a data rate estimated by the AP or by the associated STA based on modulation/coding and power values. Alternatively, a Data Rate for the associated STA can be an actual data rate determined by the associated STA for the AP over a given time period. A Data Rate for the associated STA can be for downlink data (from AP to STA), uplink data (from STA to AP), or combinations thereof. In some embodiments, such Data Rate values can be averages over time.

While the devices and operations disclosed show various methods according to embodiments, additional methods will now be described with reference to a number of flow diagrams.

FIG.5is a flow diagram of a method530according to an embodiment. A method530can be executed by a STA device when deciding to associate with an AP when in the range of multiple APs. A method530can include receiving broadcasts from APs that include traffic data530-0. Such an action can include receiving broadcast transmissions from multiple APs, where such broadcast transmissions can include traffic information for the AP as described herein, or equivalents. From the traffic data for the STAs associated with an AP, a STA can estimate its air time were the STA to associate with the AP530-1. In some embodiments, such an action can include using a received power value for the broadcast for each AP.

A method530can further include determining APs with lowest available estimated available air time530-2. Such an action can include using traffic information from each AP. In some embodiments, each AP can provide an available air time value that it has generated based on traffic over a predetermined time period. However, in other embodiments, an AP can derive an available air time for an AP by aggregating estimated air times for the STAs associated with the AP, and subtracting such a value from a maximum air time. In some embodiments, a set can include multiple APs. However, in other embodiments, a set can include but one AP. A STA can then associate with one of the APs with least estimated available air time530-3. In some embodiments, such an action can include randomly selecting one AP from a set of multiple APs.

FIG.6is a flow diagram of a method630according to another embodiment. A method630can be executed by a STA seeking association with an AP in a dense operating environment. In some embodiments, a method630can be compatible with communications according to one or more IEEE 802.11 wireless standards. A method630can include scanning for new beacon frames630-0. In some embodiments, such an action can include a STA monitoring one or more wireless channels.

A method630can continue to monitor channel(s) until all beacons have been processed630-1. In some embodiments, such an action can include a STA monitoring one or more wireless channels over one or more beacon intervals as indicated by a protocol in use. A beacon interval can be predetermined time period over which a beacon is repeated. In addition or alternatively, such an action can also include monitoring until a STA begins to receive beacons from the same APs.

While all beacons have not been processed630-1(N from630-1), a method630can determine whether a receive power of a beacon is above a predetermined threshold630-2. In some embodiments, this can include determining if a received signal strength indicator (RSSI) is above a predetermined value. If a receive power of a beacon is not above a threshold (N from630-2), a method630can continue scanning for new beacons630-0.

If a receive power of a beacon is above a threshold (Y from630-2), a method630can estimate air time if associated with the AP using beacon data for STAs associated with the AP630-3. In some embodiments, an action can include using power values and modulation/coding schemes for associated STAs, and finding a closest matching STA, or estimating from values of one or more STAs. A method630can determine available air time for the AP from beacon data630-4. Such an action can include, but is not limited to, estimating available air time by aggregating air time for associated STAs or from an air time value provided by an AP.

If a STA estimated air time is not less than an available air time for the AP (N from630-5), a method630can return to scanning for beacons. As will be shown herein, in some embodiments, if all APs do not have sufficient available air time to accommodate a STAs throughput needs, the STA can scale down its estimated air time. If a STA estimated air time is less than an available air time for the AP (Y from630-5), the STA can be saved to a “short list”630-6. A short list can be a list of candidate APs for association. In some embodiments, a short list can be limited to those APs having the least available air time.

When all beacons have been processed (Y from630-1), a method630can randomly select one AP from the candidate list (e.g., short list)630-7. A STA can then associate with the selected AP630-8.

FIG.7Ais a flow diagram of a method730according to another embodiment. A method730can be executed by a STA that is newly arrived at an operating environment having multiple APs. A method730can include scanning for beacons730-0. Such an action can include scanning for AP beacons broadcast according to one or more IEEE 802.11 wireless standards. If AP beacons with traffic data are not detected (N from730-1), a method730can continue to scan for AP beacons.

If an AP beacon with traffic data is detected (Y from730-1), a method730can detect the receive power for the AP beacon (e.g., RSSI(dwn))730-2. Optionally, a method can730can adjust a transmit data power for the STA730-3. Such an action can include adjusting transmit power based on the operating environment, including the detected RSSI(dwn) for the AP.

A method730can include extracting traffic data for other STAs associated with the AP from the beacon730-4. Such an action can include extracting traffic information from a beacon, including but not limited to data for each associated station, including any of: RSSI(dwn), RSSI(up), data rate, or modulation/coding scheme. After extracting data for STAs associated with the AP, an estimated data rate for the STA can be determined730-5. Such an action can include examining traffic data for the associated STAs, and determining a closest matching associated STA based on power levels and/or type of modulation or coding. Such an action can include extrapolating, or using similar estimation algorithms, in the event there is no sufficiently matching associated STA. With an estimated data rate, a method730can estimate a resulting air time, were the STA to associate with the AP730-6. Such an action can include using an estimated data rate with an expected throughput to arrive at an air time. An expected throughput can be the amount of data expected to be transmitted in a predetermined period of time, and can be based on the type of STA device and/or function the STA performs, or can take into account historical data regarding up/down throughput for the STA. If beacon data has not been gathered for all suitable APs in the operating environment (N from730-8), a method continue scanning (return to730-0).

If beacon data for all suitable APs has been acquired (Y from730-8), a method can determine candidate APs for association730-9. In some embodiments, candidate APs can be APs having the least available air time, but still capable of accommodating the STAs estimated air time. An AP can be selected from the candidate APs730-10. Such an action can include a random selection. However, other embodiments can include additional factors, such as how many STAs are already associated with the AP. A STA can then associate with the selected AP730-11.

FIG.7Bis a flow diagram of another method732according to an embodiment. A method732can be executed by a joining STA to determine its estimated data rate were it to join an AP using beacon data from the AP. A method732can include extracting data from an AP beacon732-0. Such an action can include extracting data as described for any of the embodiments herein, including but not limited to RSSI(dwn) data for each associated STA, modulation/coding schemes for each associated STA, and possibly actual or estimated data rates for each associated STA.

A method732can compare receive power levels of STAs associated with the AP to receive power levels of the joining STA732-1. Such an action can include finding a STA with a closest matching power level from all STAs associated with an AP. If a receive power for an associated STA is sufficiently close (Y from732-1), a modulation scheme for the associated can be compared to that of the joining STA732-2. If a modulating scheme of the associated STA is the same or equivalent to that or the joining STA (Y from732-2), the joining STA can use the data rate of the associated STA as its estimated data rate. If a modulating scheme of the associated STA is not the same or equivalent (N from732-2), the joining STA can generate an estimated data rate the data rate of the other STA adjusted according to the modulation/coding difference732-4.

If there is no associated STA with a suitable connection profile (N from732-1or N from732-2), a method732can estimate a data rate from its measured RSSI(dwn) value732-5. In some embodiments, this can include using a table or formula that generates an estimated data rate from an RSSI(dwn) value and modulation/coding scheme (which can be derived from the beacon). A method732can then proceed to determining whether or not to associate with an AP732-6as described for various embodiments herein, or equivalents.

FIG.7Cis a flow diagram of a method734for scaling data rate estimations according to an embodiment. A method734can be executed by a newly arrived STA in a dense deployment environment that determines no AP has sufficient air time for its estimated throughput needs. A method734can include extracting traffic data from AP beacons, determining an available air time for all APs, and determining an estimated air time for the newly arrived STA were it to associate with each AP734-0. Such actions can include those described herein or equivalents.

A method734can determine if there is one or more APs with sufficient available air time to meet the throughput needs of the newly arrived STA734-1. If such an AP exists (Y from734-1), a method732can include selecting the AP for association according to the various approaches described herein, or equivalents.

If there is not an AP with sufficient available air time (N from734-1), a method734can scale its estimated air time down (e.g., by a factor less than one)734-3. Providing such scaling has not reached a limit (N from734-4), a method732can return to determining if the scaled down air time can be met by an AP (return to734-1). If a scaling limit has been reached (Y from734-4), a method734can return to scanning for APs. A scaling limit can be a predetermined limit on data throughput or performance for the newly arrived STA or an application executed by the newly arrived STA.

FIG.7Dis a flow diagram of a method736according to another embodiment. A method736can be executed by an AP to generate a broadcast transmission for STAs seeking association. A method736can be compatible with communications according to one or more IEEE 802.11 wireless standards.

A method736can include communicating with associated STAs736-0. Such an action can include an AP communication with a STA through a collision based protocol (e.g., RTS-CTS) and/or an AP-STA communications occurring in a predetermined time period (e.g., target wake time). An AP can initiate such communications or a STA can initiate such communications. Such communications can be a single communication (transmission of downlink data or reception of uplink data), or can be cumulative (multiple such communications). From such communications with a STA, a method736can determine an RSSI(up) value for the STA736-1, and can receive RSSI(dwn) values from the STA736-2.

Optionally, a method736can determine a physical data rate for the STA736-3. Such an action can include estimating a physical data rate for the STA based on a data for the link with the STA (e.g., modulation/coding scheme, RSSI(up), RSSI(dwn)). In some embodiments, a STA may transmit its own data rate value, which can be an actual downlink data rate, or can be an estimated data rate. As understood from embodiments herein, in other embodiments a newly arrived STA may perform this function based on beacon data provided by an AP.

Optionally, a method736can determine an air time for each STA736-4. Such an action can include recording and/or determining up/dwn transmission time for the STA in a given time period, including a running time period (e.g., running average). As in the case of736-3, in other embodiments a newly arrived STA may perform this function based on beacon data provided by an AP.

While all associated STAs have not been evaluated (N from736-5), a method736can advance to a next associated STA736-6and determine traffic information for the STA (return to736-0). When traffic data has been acquired for all associated STAs (Y from736-5), a method736can generate a beacon containing such data736-7. It is understood that such beacon data can take the form of any of those described herein or equivalents, and includes data sufficient for a newly arrived STA to estimate its own data rate/air time were it to associated with the AP as well as the available air time of the AP. The beacon can then be transmitted736-8.

FIG.8Ais a block diagram of a device850A according to embodiment. A device850A can part of a STA as described herein or equivalents. A device850A can include communication circuits852, controller854, radio circuits856, and input/output (I/O) circuits858. Communication circuits852can include WiFi control circuits852-0and WiFi MAC/PHY circuits852-1. WiFi control circuits852-0can execute communication operations compatible with one or more IEEE 802.11 wireless standards. This can include extracting AP traffic data from received packets860, as well as conventional association functions for associating with an AP862. WiFi MAC/PHY circuits852-1can control data transmission and reception according to one or more IEEE 802.11 wireless standards. Accordingly, WiFi MAC/PHY circuits852-1can detect and receive beacon packets858, including beacon packets having AP traffic information.

A controller854can control transmissions by communication circuits852. In some embodiments, a controller854can include circuits (or instructions executable by circuits) for controlling wireless transmissions according to other processes (e.g., applications). In the embodiment shown, a controller854can include a processor section854-0and a memory section854-1. In the embodiment shown, a memory section854-1can store instructions for executing processes, including an AP selection process864. An AP selection process864can select an AP for association according to any of the embodiments disclosed herein, or an equivalent. In some embodiments, AP selection process864can include a STA air time estimation section864-0and AP available air time estimation section864-1. A STA air time estimation section864-0can estimate the air time for its throughput needs with respect to each detected AP, based on a traffic information from the AP. Such actions can include any of those described herein, or equivalents. In some embodiments, STA air time estimation section864-0can us an RSSI(dwn) value detected by radio circuit846. AP available air time estimation section864-1can estimate or determine the available air time of an AP from received beacon data.

In some embodiments, a memory section854-1can store various values for an AP selection process864. In the embodiment shown, memory section854-1can store a short list of candidate APs866. Such a short list can take the form of any of those described herein, or an equivalent, including a list of APs having the least available air time, yet still able to serve the throughput requirements of the device850A. A memory section854-1can also store one or more RSSI threshold values868. RSSI threshold values868can be used to discard APs from consideration as association candidates (i.e., if an RSSI for an AP is below the RSSI threshold, the AP is not considered for association).

Radio circuits856can include circuits for receiving and transmitting signals according to one or more IEEE 802.11 wireless standards. Radio circuits856can include any suitable circuits according to a selected protocol, and in some embodiments can include baseband circuits. In the embodiment shown, radio circuits856can include RSSI detect circuits856-0which can generate an RSSI value for received packets/data frames, including beacon frames. In some embodiments, radio circuits856can transmit/receive on any internationally recognized industrial, scientific, or medical (ISM) band, as well as portions of such bands. In some embodiments, radio circuits856can operate in any or all of 2.4 GHZ, 5 GHz or 6 GHz bands.

I/O circuits858can enable control of device850A by another system or device. I/O circuits858can include circuits that enable communication with the device according to any suitable method, including any of various serial data communication standards/methods including but not limited to: serial digital interface (SDI), universal serial bus (USB), universal asynchronous receiver transmitter (UART), I2C, or I2S.

When included as part of a system, device850A can include one or more antenna systems870connected to radio circuits856. Antenna system870can include antennas for receiving and transmitting over one or more channels. In some embodiments, antenna system870can be configured for data transmission and reception compatible with one or more IEEE 802.11 wireless standards.

FIG.8Bis a block diagram of a device850B according to embodiment. A device850B can part of an AP as described herein or equivalents. A device850B can include circuits like those ofFIG.8A, and such circuits can operate in the same or an equivalent fashion. As in the case ofFIG.8A, a device850B can execute communication operations compatible with one or more IEEE 802.11 wireless standards. However, such operations can be in the role of an AP, and so can include constructing beacons872-0, including beacons with traffic information as described herein or equivalents, as well as association functions872-1for associating with a STA. WiFi MAC/PHY circuits852-1can transmit beacon packets870, including beacon packets having traffic information.

In the embodiment shown, local devices (1050A-0to -3) can be Internet-of-things (IoT) type devices, such as lighting devices1050A-0, locking devices1050A-1, entertainment devices1050A-2, security devices1050A-3, instrumentation devices20)1050A-4, as but a few of many possible examples. As each local device (1050A-0to -3) is added to the operating environment, it can monitor for broadcasts from gateways devices (1050B-0to -2) that include throughput information, and then select one for association as described herein and equivalents.

While embodiments can include systems and devices with various interconnected components, embodiments can also include unitary devices which can enable devices to execute association processes that can lead to efficient, balanced access to APs in dense operating environments, as describe herein or equivalents. In some embodiments, such unitary devices can be advantageously compact single integrated circuits (i.e., chips).FIG.9show one particular example of a packaged single chip wireless device950. Such a device950can include circuits for providing the STA and/or AP functions described herein and equivalents. In some embodiments, a device950can include circuits like those shown inFIGS.8A and/or8B.

However, it is understood that a device according to embodiments can include any other suitable integrated circuit packaging type, as well as direct bonding of a device chip onto a circuit board or substrate.

FIG.10shows a system1080according to an embodiment. A system1080can include various local devices1050A-0to -4and gateway devices1050B-0to -2. Local devices (1050A-0to -4) can be STAs as described herein or equivalents, and gateway devices (1050B-0to -2) can be APs as described herein or equivalents. Gateway devices1050B-0to -2can have overlapping operating regions. Thus, as local devices (1050-0to -4) are added to an operating environment, such devices (1050-0to -4) can associate with one of the gateway devices (1050B-0to -2).

In the embodiment shown, local devices (1050A-0to -3) can be Internet-of-things (IoT) type devices, such as lighting devices1050-0, locking devices1050-1, entertainment devices1050-2, security devices1050-3, instrumentation devices1050-4, as but a few of many possible examples. As each local device (1050A-0to -3) is added to the operating environment, it can monitor for broadcasts from gateways devices (1050B-0to -2) that include throughput information, and then select one for association as described herein and equivalents.

Embodiments can include a STA associating with one of multiple APs in a dense operating environment based on throughput information broadcast by all such APs, and thus shape or organize traffic in a predetermined way.

Embodiments can include a STA selecting from among APs having a lowest available capacity for association, thus enabling one or more other APs to remain with relatively high throughput for higher traffic devices that may join in the future.

Embodiments can include a STA selecting from among APs operating with air time fairness. In such an arrangement, STAs can tend to be evenly distributed among a set of APs.

Embodiments can limit adverse effects of high-rate STAs joining a dense operating environment, as compared to conventional contention based access methods.

These and other advantages would be evident to those skilled in the art.

While embodiments have included a broadcast transmission from an AP that includes throughput value for that AP, alternate embodiments can include broadcast transmissions that include throughput data for more than one AP.

While throughput data can include air time amounts, throughput data can also include other data, such as transmit power at the AP and/or receive power at the AP for other devices (e.g., STAs).

While embodiments have described wireless environments compatible with IEEE 802.11 wireless standards, alternate embodiments can include operations according to other standards. In such alternate embodiments, an AP can be a device that controls access to a network, as well as transmission with its network. STAs are devices that may be added to the network with permission from the AP (e.g., association).

It should be appreciated that reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Therefore, it is emphasized and should be appreciated that two or more references to “an embodiment” or “one embodiment” or “an alternative embodiment” in various portions of this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined as suitable in one or more embodiments of the invention.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claims require more features than are expressly recited in each claim. Rather, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.