Bandwidth sentinel

Information

  • Patent Grant
  • 9900251
  • Patent Number
    9,900,251
  • Date Filed
    Monday, July 12, 2010
    14 years ago
  • Date Issued
    Tuesday, February 20, 2018
    6 years ago
Abstract
Minimum guaranteed wireless network bandwidth is provided to client network devices by monitoring the performance of network connections to identify client network devices experiencing network congestion. Congested network connections are then analyzed to determine the source of the network congestion. Depending upon the source of the network congestion, an embodiment of the invention may undertake steps to either improve the quality of the network connection or to mitigate the impact of this network connection on other network connections. High quality network connections may be allocated additional bandwidth, airtime, or other resources to reduce the network congestion. Low quality network connections are not allocated additional bandwidth, airtime, or other resources. Instead, the impact of this network connection on the other network connections is mitigated. Additionally, the low quality network connection may be transferred to another wireless networking device that may be able to provide a better quality network connection.
Description
BACKGROUND

The present invention relates to the field of communication networks, and in particular to the systems and methods for ensuring the provision of minimum wireless network bandwidth to wireless network devices. Communications networks allow computers and other electronic devices to exchange data. Wireless networks, which exchange data without wires, typically using radio waves, are popular with users due to the ability to send and receive data almost anywhere within the physical coverage area of the network. This allows users to access communication networks, including local area networks, organization or company intranets, virtual private networks, and wide area networks, such as the Internet, anywhere within the physical coverage area of the wireless networks.


Networking devices may handle packets generated by and directed to large numbers of clients over the same interface. The bandwidth or data communications capacity of networking devices limits the amount of data or the rate of network packets passing through network devices. The limits on bandwidth are particularly acute in network devices including wireless network interfaces. If the bandwidth limit of a networking device is reached or exceeded by its clients network traffic, packets may be delayed or dropped. Depending on the type of data being communicated over the network, these traffic disruptions caused by reaching or exceeding bandwidth limit of a networking device may adversely affect the performance of applications on a client. For example, clients receiving voice or streaming video data may be adversely affected by even small delays or losses of packets.


Because of the limits on network device bandwidth, many network devices include quality of service (QoS) functionality. Quality of service functionality allows network administrators to provide different priority for packets or other network data based on factors such as the associated client, user, client application, or data flow. Typically, users, clients, or applications are assigned to different quality of service profiles. Each quality of service profile specifies a quality of service parameters to associated packets or other network data. Networking devices use the scheduling weights to prioritize packet traffic and potentially guarantee a minimum level of performance to some or all of the network data flows.


Unfortunately, there are situations in which a wireless network device cannot provide a minimum level of performance to some or all of its associated network traffic flows. This may be occur for a number of reasons, including RF interference or a client device that is malfunctioning, mis-configured, or near the limit of its reception range. In these situations, many types of network traffic prioritization or compensation will have little or no effect of the network connection performance; thus, allocating additional bandwidth, airtime, or other network resources to these network connections is wasteful. However, because prior QoS functions do not attempt to diagnose the cause of network congestion, they waste network resources on attempting to improve the performance of network connections in these situations.





BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be described with reference to the drawings, in which:



FIG. 1 illustrates an example system suitable for implementing embodiments of the invention;



FIG. 2 illustrates a method of operation of a bandwidth sentinel according to an embodiment of the invention; and



FIG. 3 illustrates an example computer system suitable for implementing an embodiment of the invention.





SUMMARY

An embodiment of the invention attempts to provide minimum guaranteed wireless network bandwidth to client network devices, such as user computers, mobile wireless devices, and other devices including wireless network interfaces for exchanging data, by monitoring the performance of network connections to identify client network devices experiencing network congestion while utilizing network bandwidth below a minimum guaranteed bandwidth or airtime usage. Each of these network connections are then analyzed to determine the source of the network congestion. Depending upon the source of the network congestion, an embodiment of the invention may undertake steps to either improve the quality of the network connection or to mitigate the impact of this network connection on other network connections.


For example, in some situations, the network connection has a relatively high quality. In these situations, an embodiment of the invention may allocate additional bandwidth, airtime, or other resources to this network connection to reduce the network congestion.


In another example, in some situations, the network connection has a relative low quality, due to factors such as RF interference, or a client device that is malfunctioning, mis-configured, or near the limit of its reception range. In these situations, allocating additional bandwidth, airtime, or other network resources to these network connections will have little or no effect of the network connection performance. Thus, an embodiment of the invention does not waste additional resources on these types of network connections. Instead, an embodiment of the invention mitigates the impact of this network connection on the other network connections provided by this wireless networking device. Additionally, an embodiment of the invention may transfer the low quality network connection to another wireless networking device that may be able to provide a better quality network connection.


DETAILED DESCRIPTION


FIG. 1 illustrates an example system 100 suitable for implementing embodiments of the invention. The system includes client wireless network devices 105, which are electronic devices including wireless network interfaces for exchanging data. Examples of client network devices 105 include desktop user computers 105a, portable user computer 105b, personal digital assistants 105c, smartphone or other mobile device capable of accessing wireless networks 105d, and tablet computer 105e. The system 100 can interface with any type of electronic device, such as a thin-client computer, Internet-enabled mobile telephone, mobile Internet access device, electronic book, or personal digital assistant, capable of accessing wireless communication networks. Although system 100 is shown with five client wireless network devices 105, any number of user computers can be supported.


The client wireless network devices 105 establish network connections 107 with one or more wireless access points 110. For example, client wireless network devices 105a and 105b establish wireless network connections 107a and 107b, respectively, with wireless access point 110a. Similarly, client wireless network devices 105c and 105d establish wireless network connections 107c and 107d, respectively, with wireless access point 110b and client wireless network device 105e establishes wireless network connection 107e with wireless access point 110c. Network connections 107 include the physical and/or logical communications channels between client wireless network devices 105 and the wireless access points 110. The client wireless network devices 105 and wireless access points 110 may use any standard or proprietary wireless networking technologies and/or protocols known in the art, including one or more of the IEEE 802.11 family of wireless networking standards.


Wireless access points 110 may be connected via wired or wireless networks with other local-area network devices, including one or more network switches 115, one or more server computers, databases, and/or data storage 120, and a router and/or firewall device 125. Additionally, the router and/or firewall device may be connected with a wide-area network 130, such as the internet.


An embodiment of the invention includes a network device including at least one wireless network interface, such as a wireless access point, including a bandwidth sentinel to attempt to provide client network devices, such as user computers, mobile wireless devices, and other electronic devices including wireless network interfaces for exchanging data, with minimum guaranteed bandwidth usage. FIG. 2 illustrates a method 200 of operation of a bandwidth sentinel according to an embodiment of the invention. Step 205 identifies congested network connections. In an embodiment, step 205 identifies network connections that are suffering excessive queuing backlog and that have actual bandwidth/airtime usage below the minimum guaranteed bandwidth/airtime usage. These network connections are referred to as bandwidth sentinel candidate network connections.


In an embodiment, a wireless network interface, such as a wireless access point, includes a quality of service (QoS) module. The QoS module is responsible for allocating the wireless network bandwidth of the wireless network interface among one or more client network devices connected with the wireless network interface via wireless network connections. Embodiments of the QoS module may use any bandwidth allocation or scheduling technique known in the art, including token bucket allocation techniques. In an embodiment, the QoS module maintains one or more queues for each network connection and associated client network device. Each queue buffers or temporarily stores data, for example in the form of network packets, directed to a connected client network device until it can be transmitted via the appropriate wireless network connection.


In an embodiment of step 205, the QoS module identifies bandwidth sentinel candidate network connections as network connections having backlogged queues and using less than their minimum guaranteed wireless network bandwidth and/or airtime. In an embodiment, a network connection's queue or queues are identified as backlogged if the queue depth is above an overall queue depth average threshold. Embodiments of the invention may determine the average queue depth threshold as the product of the minimum desired guaranteed bandwidth and the maximum transmission delay for the wireless network connection. Embodiments of the invention may set different threshold values for each connected client network device, allowing network performance to be tailored to the needs and priorities of different applications and users.


Once one or more bandwidth sentinel candidate network connections have been identified, an embodiment of the invention determines whether the backlog is due to poor network connections or to a lack of network bandwidth. To do this, step 210 evaluates the quality of bandwidth sentinel candidate network connections. A wireless network interface may include a wireless network interface driver module that supervises the operation of the wireless network interface hardware. In an embodiment of method 200, the wireless network interface driver module is adapted to evaluate the quality of a network connection associated with a bandwidth sentinel candidate client network device and identify potential wireless network connection problems.


In an embodiment, the wireless network interface driver module monitors the wireless network connections of one or more connected client network devices using measurements including client network device TX/RX bit rate usage; TX/RX retries (for example on per bit rate basis); radio PHY type, and received signal strength indication (RSSI).


In an embodiment of step 210, the wireless network interface driver module receives a selection of one or more bandwidth sentinel candidate network connections from the QoS module. An embodiment of the wireless network interface driver module evaluates the quality of the network connections associated with the selection of bandwidth sentinel candidate network connections. In a further embodiment, this evaluation may classify network connections into two or more quality categories, for example “good” quality connections or “bad” quality connections. In another example of this embodiment, more than two quality categories may be used to identify network connections experiencing congestion for different specific reasons, such as separate quality categories for network connections with high interference, low signal strength, or a mis-configured client network device.


Embodiments of the wireless network interface driver module may use a formula, heuristic, weighting, and/or scoring scheme to evaluate the quality of network connections. For example, the evaluation of wireless network connection quality may be based on wireless network connection attributes including TX/RX bit rate usage; TX/RX retries (for example on per bit rate basis); RSSI; and its radio PHY type. An embodiment of the wireless network interface driver module can evaluate one or more wireless network connection attributes to determine a quality score for a wireless network connection A further embodiment of the invention may evaluate wireless network connection attributes over a period of time, for example 5 seconds, to determine the quality of the wireless network connection.


One example of a formula used to determine a quality score for a wireless network connection in step 210 is as follows:







Quality_Score
=



n



(


TXRateScore


[
k
]


×

TX

RXRateSuccess


[
k
]



×

TX

RXRateUsage


[
k
]




)



,





where the TXRateScore is defined as the bit-rate divided by 1000 (e.g. 54 Mb/s has a TXRateScore of 54,000), the TXRXRateSuccess is defined as








TX

RXRateSuccess


[
k
]



=


TX

RXSuccess


[
k
]





TX

RXSuccess


[
k
]



+

TX

RXretries


[
k
]






,





and the TXRXRateUsage may be determined directly.


An embodiment of the wireless network interface driver module may compare this quality score with one or more benchmark quality scores to assign each wireless network connection to a quality category. In an embodiment, different PHY types (e.g. different wireless network interface types) may have different benchmark quality scores. In a further embodiment, the quality scores of one or more network connections may be monitored over time to determine a statistical distribution of the range of quality scores. One or more benchmark quality scores may be determined based on a desired quantile within this distribution of quality scores. For example, a benchmark quality score for a typical wireless network connection may be selected as the median or 50th percentile quality score value in the distribution of quality scores. In another example, a benchmark quality score for a performance critical wireless network connection (such as for a mission-critical application or a high priority user) may be selected as a quality score greater than the median quality score (e.g. the 75th percentile). In another example, a benchmark quality score for a non-critical wireless network connection (such as for a guest user in a network) may be selected as a quality score less than the median quality score (e.g. the 25th percentile).


The wireless network interface driver module then returns the results of this evaluation, such as the classifications of the wireless network connections associated with the selection of bandwidth sentinel candidate network connections. Based on the results of this evaluation, an embodiment of the QoS module may modify its bandwidth and/or airtime allocation to one or more client network devices.


Decision block 215 evaluates the quality scores of the bandwidth sentinel candidate network connections. For bandwidth sentinel candidate network connections having good quality network connections, as determined by an assigned category, quality score, or other indicator, an embodiment of method 200 performs step 220 to improve the performance of the network connection. Embodiments of step 220 may attempt to improve the wireless network connection performance by taking actions including: attempting to allocate more wireless network interface airtime and/or more wireless network interface bandwidth to these bandwidth sentinel candidate network connections (taking some bandwidth and/or airtime away from other normally operating network connections); using cooperative load balancing to allow other network devices, such as other wireless access points, to provide wireless network connections to one or more client network devices, thereby relieving the network device of the burden of providing wireless network connections to some of its client network devices; sending a message or notification to a log, management application, or system administrator; and/or de-associating one or more client network devices from the network device, thereby relieving the network device of the burden of providing wireless network connections to some of its client network devices.


In an example of step 220, the QoS module may increase the bandwidth and/or airtime allocated to a bandwidth sentinel candidate network connection. Allocating additional wireless network bandwidth to a wireless network connection increases the maximum potential data rate. Allocating additional wireless network airtime to a wireless network connection enables the network device to retransmit lost network packets, which increases the actual data rate but not necessarily the maximum potential data rate.


In one embodiment, the QoS module may increase the number and/or rate of tokens assigned to this network connection in a token bucket allocation scheme. For example, the QoS module may increase the size of one or more token buckets associated with the wireless network connection of the client network device. The size of the token bucket may be increased by a predetermined amount or percentage (e.g. a 10% increase of the current token bucket size). In a further embodiment, the size of the token bucket may be limited to a maximum token bucket size value. If the token bucket size reaches its maximum size value, in an embodiment of step 220, the QoS module sends an indicator that the size limit has been reached, such as an event notification or trap, to a management module. The indicator may include information identifying the affected client network device and/or diagnostic information, including, for example, a client network device MAC address, the desired guaranteed wireless network connection bandwidth, and the actual wireless network connection bandwidth.


Conversely, if decision block 215 determines that one or more of the bandwidth sentinel candidate network connections has a low quality network connection, as determined by an assigned category, quality score, or other indicator, an embodiment of method 200 performs step 225 to mitigate the impact of this low quality network connection on the performance of other network connections provided by this network device. Embodiments of step 225 may attempt to mitigate the impact of network connections with connectivity problems on the other network connections provided by this network device by taking actions including: using cooperative load balancing to allow other network devices, such as other wireless access points, to provide wireless network connections to one or more client network devices, thereby relieving the network device of the burden of providing wireless network connections to some of its client network devices; sending a message or notification to a log, management application, or system administrator; and/or de-associating one or more client network devices from the network device, thereby relieving the network device of the burden of providing wireless network connections to some of its client network devices.


In an example of step 225, the QoS module or any other module may attempt to compensate for the bad network connection, for example using cooperative load balancing to transfer the bad quality wireless network connection from the current wireless access point to a different network device, such as a different wireless access point, that may be able to provide the client network device with a better quality connection. In a further embodiment, the QoS module sends an indicator of the bad quality wireless network connection, such as an event notification or trap, to a management module. The indicator may include information identifying the affected client network device and/or diagnostic information, including, for example, a client network device MAC address, the desired guaranteed wireless network connection bandwidth, and the actual wireless network connection bandwidth.


As described above, embodiments of method 200 may utilize more than two quality categories in evaluating network connections. For these embodiments, decision block 215 of method 200 may be extended to evaluate one or more quality scores for each network connection to assign the network connection to the appropriate quality category. Method 200 may be extended with any number of steps similar to steps 220 and/or 225, each of which corresponding with a different quality category. Each of these additional steps may be tailored to perform one or more actions appropriate for the quality category. Although each quality category may have its own set of one or more actions, some or all of these actions may not be unique to the quality category. For example, different quality categories may have some actions in common.


For client network devices with either good or bad network connections, embodiments of the invention may choose to do nothing and ignore the problems of one or more bandwidth sentinel candidate network connections.


In an embodiment, if the wireless network connection of a bandwidth sentinel candidate network connection is congested at the start of the evaluation of the quality of its wireless network connection, but is uncongested by the time this evaluation has been completed, an embodiment of the bandwidth sentinel may choose to leave the wireless network connection of this bandwidth sentinel candidate network connection unchanged.


A further embodiment of the invention measures the effectiveness of the bandwidth sentinel using attributes such as client network device TX/RX bit rate usage; client network device TX/RX retries; client network device TX/RX airtime; queue depths; and client network device TX/RX bandwidth usage. An embodiment of the invention uses these attributes to establish measurements of client network device bandwidth and airtime allocations with or without bandwidth sentinel. Statistical measurements such as distributions and standard deviations may be used to compare the effectiveness of the bandwidth sentinel under a variety of operating conditions. The bandwidth sentinel feature may be activated or deactivated for some or all of the client network devices depending upon operating conditions and network administrator preferences.


As described above, an embodiment of a network device implements a bandwidth sentinel using both QoS and wireless network interface driver modules. Alternate embodiments of a network device may implement a bandwidth sentinel using one or more other types of modules.


In a further embodiment, the bandwidth sentinel may modify the allocation of bandwidth and/or airtime to one or more of the client network devices that are not receiving sufficient bandwidth. For example, the bandwidth sentinel may reduce the rate at which an enlarged token bucket used to increase bandwidth to a client network device is returned to its nominal size. In yet a further embodiment, the bandwidth sentinel may restore the token bucket size if the network connection congestion is relieved and the guaranteed minimum bandwidth for the network connection is met.


In an embodiment, the actions undertaken in step 220 in response to either improve wireless network connection performance for client network devices with good network connections or in step 225 to mitigate the impact of client network devices with bad network connections are different and may be selected based on the intended usage and environment of the network device, the types of client network devices, and/or the types of users of client network devices. The actions performed by the network device in either case may be configured or specified by network administrators or other users.


In an embodiment, a management module associated with one or more network devices including wireless network interfaces may be adapted to configure the bandwidth sentinel. Embodiments of the management module may configure bandwidth sentinels independently or collectively for multiple network devices. The configuration of each bandwidth sentinel may include enabling or disabling the bandwidth sentinel, minimum guaranteed bandwidth for one or more client network devices, congestion thresholds for identifying bandwidth sentinel candidate network connections, and benchmark quality scores for one or more types of wireless network interfaces. A further embodiment of the management module may configure any or all of these bandwidth sentinel attributes independently for different users or client network devices.



FIG. 3 illustrates a computer system suitable for implementing an embodiment of the invention. FIG. 3 is a block diagram of a computer system 2000, such as a personal computer or other digital device, suitable for practicing an embodiment of the invention. Embodiments of computer system 2000 include dedicated networking devices, such as wireless access points, network switches, hubs, routers, hardware firewalls, network traffic optimizers and accelerators, network attached storage devices, and combinations thereof.


Computer system 2000 includes a central processing unit (CPU) 2005 for running software applications and optionally an operating system. CPU 2005 may be comprised of one or more processing cores. Memory 2010 stores applications and data for use by the CPU 2005. Examples of memory 2010 include dynamic and static random access memory. Storage 2015 provides non-volatile storage for applications and data and may include fixed or removable hard disk drives, flash memory devices, ROM memory, and CD-ROM, DVD-ROM, Blu-ray, HD-DVD, or other magnetic, optical, or solid state storage devices. Memory 2010 may store a firmware image comprising applications and data adapted to be executed by computer system 2000.


Optional user input devices 2020 communicate user inputs from one or more users to the computer system 2000, examples of which may include keyboards, mice, joysticks, digitizer tablets, touch pads, touch screens, still or video cameras, and/or microphones. In an embodiment, user input devices may be omitted and computer system 2000 may present a user interface to a user over a network, for example using a web page or network management protocol and network management software applications.


Computer system 2000 includes one or more network interfaces 2025 that allow computer system 2000 to communicate with other computer systems via an electronic communications network, and may include wired or wireless communication over local area networks and wide area networks such as the Internet. Computer system 2000 may support a variety of networking protocols at one or more levels of abstraction. For example, computer system may support networking protocols at one or more layers of the seven layer OSI network model. An embodiment of network interface 2025 includes one or more wireless network interfaces adapted to communicate with wireless clients and with other wireless networking devices using radio waves, for example using the 802.11 family of protocols, such as 802.11a, 802.11b, 802.11g, and 802.11n.


An embodiment of the computer system 2000 may also include a wired networking interface, such as one or more Ethernet connections to communicate with other networking devices via local or wide-area networks. In a further embodiment, computer system 2000 may be capable of receiving some or all of its required electrical power via the network interface 2025, for example using a wired networking interface power over Ethernet system.


The components of computer system 2000, including CPU 2005, memory 2010, data storage 2015, user input devices 2020, and network interface 2025 are connected via one or more data buses 2060. Additionally, some or all of the components of computer system 2000, including CPU 2005, memory 2010, data storage 2015, user input devices 2020, and network interface 2025 may be integrated together into one or more integrated circuits or integrated circuit packages. Furthermore, some or all of the components of computer system 2000 may be implemented as application specific integrated circuits (ASICS) and/or programmable logic.


A power supply 2030 provides electrical power to the computer system 2000. Power supply 2030 may be adapted to draw electrical power from a connection with an electrical power distribution grid. In an embodiment, power supply 2030 is connected with network interface 2025 to draw electrical power for computer system 2000 from one or more wired network connections using a network power standard, such as IEEE 802.3af.


Although embodiments of the invention are discussed with reference to the IEEE 802.11 standard, embodiments of the invention are equally applicable to other standard and proprietary wireless network protocols. Additionally, embodiments of the invention are not limited to 802.11 wireless network connections and may be utilized for any type of communication network where a network connection between a client wireless network device and a wireless network device is required.


Further embodiments can be envisioned to one of ordinary skill in the art from the specification and figures. In other embodiments, combinations or sub-combinations of the above disclosed invention can be advantageously made. The block diagrams of the architecture and flow charts are grouped for ease of understanding. However it should be understood that combinations of blocks, additions of new blocks, re-arrangement of blocks, and the like are contemplated in alternative embodiments of the present invention. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that various modifications and changes may be made thereunto without departing from the broader spirit and scope of the invention as set forth in the claims.

Claims
  • 1. A method for configuring a network connection, the method comprising: identifying a wireless network connection of a network between a wireless network device and a client network device, the wireless network connection having network congestion;determining a quality score for the wireless network connection, the quality score based on at least two of receiving bit rate usage, transmission bit rate usage, transmission retries, receiving retries, received signal strength indication, and wireless network interface type of the wireless network connection;analyzing the wireless network connection, based on the quality score, to determine the wireless network connection is a source of the network congestion;determining another quality score for an additional wireless network connection between the wireless network device and another client network device based on at least two of receiving bit rate usage, transmission bit rate usage, transmission retries, receiving retries, received signal strength it and wireless network interface type of the additional wireless network connection;determining the additional wireless network connection is a high quality network connection based on the another quality score for the additional wireless network connection;allocating additional bandwidth and airtime to the additional wireless network connection based on the determination that the additional wireless network connection is the high quality network connection in order to mitigate impact of the network congestion at the wireless network connection on other network connections of the network;using cooperative load balancing to allow other network devices to provide the client network device wireless access to the network in order to mitigate impact of the network congestion at the wireless network connection on the client network device accessing the network.
  • 2. The method of claim 1, further comprising: comparing the quality score for the wireless network connection with a benchmark quality score.
  • 3. The method of claim 2, wherein the benchmark quality score is associated with a wireless network interface type.
  • 4. The method of claim 2, wherein the benchmark quality score is associated with a wireless network user type.
  • 5. The method of claim 2, wherein the benchmark quality score is associated with a wireless network client application type.
  • 6. The method of claim 2, wherein the benchmark quality score is based on a quantile of a statistical distribution of previously determined quality scores.
  • 7. The method of claim 1, further comprising: allocating additional wireless network interface bandwidth to the wireless network connection.
  • 8. The method of claim 1, further comprising: allocating additional wireless network interface airtime to the wireless network connection.
  • 9. The method of claim 1, further comprising: transferring the at least one additional wireless network connection to a second wireless network device.
  • 10. The method of claim 1, further comprising: transferring the wireless network connection to a second wireless network device.
  • 11. The method of claim 1, further comprising: transferring the at least one additional wireless network connection to a second wireless network device.
  • 12. The method of claim 1, further comprising: transferring the wireless network connection to a second wireless network device.
  • 13. The method of claim 1, further comprising: sending a notification identifying the wireless network connection and the quality score for the wireless network connection.
  • 14. The method of claim 1, further comprising selecting the wireless network connection front a set of wireless network connections provided by the wireless network device based on a management configuration.
  • 15. The method of claim 14, further comprising assigning each of the set of wireless network connections to a congestion threshold.
  • 16. The method of claim 14, further comprising assigning each of the set of wireless network connections to a benchmark quality score.
  • 17. The method of claim 14, further comprising assigning each of the set of wireless network connections to a minimum guaranteed bandwidth.
  • 18. The method of claim 1, wherein the wireless network device includes a wireless access point.
  • 19. The method of claim 1, wherein the wireless network connection enables communication between the wireless network device and the client network device.
  • 20. The method of claim 1, further comprising selecting a first and second quality from a group comprising at least three qualities.
  • 21. A system comprising: a means for identifying a wireless network connection of a network between a wireless network device and a client network device, the wireless network connection having network congestion;a means for determining a quality score for the wireless network connection, the quality score based on at least two of receiving bit rate usage, transmission bit rate usage, transmission retries, receiving retries, received signal strength indication, and wireless network interface type of the wireless network connection,a means for analyzing the wireless network connection, based on the quality score, to determine the wireless network connection is a source of the network congestion;a means for determining another quality score for an additional wireless network connection between the wireless network device and another client network device based on at least two of receiving bit rate usage, transmission hit rate usage, transmission retries, receiving retries, received signal strength indication, and wireless network interface type of the additional wireless network connection;a means for determining the additional wireless network connection is a high quality network connection based on the another quality score for the additional wireless network connection;a means for allocating additional bandwidth and airtime to the additional wireless network connection based on the determination that the additional wireless network connection is the high quality network connection in order to mitigate impact of the network congestion at the wireless network connection on other network connections of the network;a means for using cooperative load balancing to allow other network devices to provide the client network device wireless access to the network in order to mitigate impact of the network congestion at the wireless network connection on the client network device accessing the network.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application No. 61/224,716, filed Jul. 10, 2009, and entitled “Bandwidth Sentinel,” which is incorporated by reference herein for all purposes.

US Referenced Citations (237)
Number Name Date Kind
5471671 Wang et al. Nov 1995 A
5697059 Carney Dec 1997 A
5726984 Kubler et al. Mar 1998 A
5956643 Benveniste Sep 1999 A
6061799 Eldridge et al. May 2000 A
6112092 Benveniste Aug 2000 A
6154655 Borst et al. Nov 2000 A
6201792 Lahat Mar 2001 B1
6314294 Benveniste Nov 2001 B1
6473413 Chiou et al. Oct 2002 B1
6496699 Benveniste Dec 2002 B2
6519461 Andersson et al. Feb 2003 B1
6628623 Noy Sep 2003 B1
6628938 Rachabathuni et al. Sep 2003 B1
6636498 Leung Oct 2003 B1
6775549 Benveniste Aug 2004 B2
6865393 Baum et al. Mar 2005 B1
6957067 Iyer et al. Oct 2005 B1
7002943 Bhagwat et al. Feb 2006 B2
7057566 Theobold Jun 2006 B2
7085224 Oran Aug 2006 B1
7085241 O'Neill et al. Aug 2006 B1
7130629 Leung et al. Oct 2006 B1
7154874 Bhagwat et al. Dec 2006 B2
7164667 Rayment et al. Jan 2007 B2
7174170 Steer et al. Feb 2007 B2
7177646 O'Neill et al. Feb 2007 B2
7181530 Halasz et al. Feb 2007 B1
7224697 Banerjea et al. Mar 2007 B2
7216365 Bhagwat et al. May 2007 B2
7251238 Joshi et al. Jul 2007 B2
7336670 Calhoun Feb 2008 B1
7339914 Bhagwat et al. Mar 2008 B2
7346338 Calhoun et al. Mar 2008 B1
7366894 Kalimuthu et al. Apr 2008 B1
7370362 Olson et al. May 2008 B2
7440434 Chaskar et al. Oct 2008 B2
7512379 Nguyen Mar 2009 B2
7536723 Bhagwat et al. May 2009 B1
7562384 Huang Jul 2009 B1
7593356 Friday et al. Sep 2009 B1
7656822 AbdelAziz et al. Feb 2010 B1
7706789 Qi et al. Apr 2010 B2
7716370 Devarapalli May 2010 B1
7751393 Chaskar et al. Jul 2010 B2
7768952 Lee Aug 2010 B2
7793104 Zheng et al. Sep 2010 B2
7804808 Bhagwat et al. Sep 2010 B2
7843907 Abou-Emara et al. Nov 2010 B1
7844057 Meier et al. Nov 2010 B2
7856209 Rawat Dec 2010 B1
7921185 Chawla et al. Apr 2011 B2
7949342 Cuffaro et al. May 2011 B2
7961725 Nagarajan et al. Jun 2011 B2
7970894 Patwardhan Jun 2011 B1
8000308 Dietrich et al. Aug 2011 B2
8069483 Matlock Nov 2011 B1
8219688 Wang Jul 2012 B2
8249606 Neophytou et al. Aug 2012 B1
8493918 Karaoguz et al. Jul 2013 B2
8789191 Bhagwat et al. Jul 2014 B2
8824448 Narayana et al. Sep 2014 B1
8948046 Kang et al. Feb 2015 B2
9003527 Bhagwat et al. Apr 2015 B2
20010006508 Pankaj et al. Jul 2001 A1
20020012320 Ogier et al. Jan 2002 A1
20020021689 Robbins et al. Feb 2002 A1
20020071422 Amicangioli Jun 2002 A1
20020091813 Lamberton et al. Jul 2002 A1
20020116463 Hart Aug 2002 A1
20020128984 Mehta et al. Sep 2002 A1
20030005100 Barnard et al. Jan 2003 A1
20030039212 Lloyd et al. Feb 2003 A1
20030087629 Juitt May 2003 A1
20030104814 Gwon et al. Jun 2003 A1
20030129988 Lee et al. Jul 2003 A1
20030145091 Peng et al. Jul 2003 A1
20030179742 Ogier et al. Sep 2003 A1
20040003285 Whelan et al. Jan 2004 A1
20040013118 Borella Jan 2004 A1
20040022222 Clisham Feb 2004 A1
20040054774 Barber et al. Mar 2004 A1
20040064467 Kola et al. Apr 2004 A1
20040077341 Chandranmenon et al. Apr 2004 A1
20040103282 Meier et al. May 2004 A1
20040109466 Van Ackere et al. Jun 2004 A1
20040162037 Shpak Aug 2004 A1
20040185876 Groenendaal et al. Sep 2004 A1
20040192312 Li et al. Sep 2004 A1
20040196977 Johnson et al. Oct 2004 A1
20040236939 Watanabe et al. Nov 2004 A1
20040255028 Chu et al. Dec 2004 A1
20050053003 Cain et al. Mar 2005 A1
20050074015 Chari et al. Apr 2005 A1
20050099983 Nakamura et al. May 2005 A1
20050122946 Won Jun 2005 A1
20050154774 Giaffreda et al. Jul 2005 A1
20050207417 Ogawa et al. Sep 2005 A1
20050259682 Yosef et al. Nov 2005 A1
20050262266 Wiberg et al. Nov 2005 A1
20050265288 Liu et al. Dec 2005 A1
20050266848 Kim Dec 2005 A1
20060010250 Eisl et al. Jan 2006 A1
20060013179 Yamane Jan 2006 A1
20060026289 Lyndersay et al. Feb 2006 A1
20060062250 Payne, III Mar 2006 A1
20060107050 Shih May 2006 A1
20060117018 Christiansen et al. Jun 2006 A1
20060140123 Conner et al. Jun 2006 A1
20060146748 Ng et al. Jul 2006 A1
20060146846 Yarvis et al. Jul 2006 A1
20060165015 Melick et al. Jul 2006 A1
20060187949 Seshan et al. Aug 2006 A1
20060221920 Gopalakrishnan et al. Oct 2006 A1
20060233128 Sood et al. Oct 2006 A1
20060234701 Wang et al. Oct 2006 A1
20060245442 Srikrishna et al. Nov 2006 A1
20060251256 Asokan et al. Nov 2006 A1
20060268802 Faccin Nov 2006 A1
20060294246 Stieglitz et al. Dec 2006 A1
20070004394 Chu et al. Jan 2007 A1
20070010231 Du Jan 2007 A1
20070025274 Rahman et al. Feb 2007 A1
20070025298 Jung Feb 2007 A1
20070049323 Wang et al. Mar 2007 A1
20070077937 Ramakrishnan et al. Apr 2007 A1
20070078663 Grace Apr 2007 A1
20070082656 Stieglitz et al. Apr 2007 A1
20070087756 Hoffberg Apr 2007 A1
20070091859 Sethi et al. Apr 2007 A1
20070115847 Strutt et al. May 2007 A1
20070116011 Lim et al. May 2007 A1
20070121947 Sood et al. May 2007 A1
20070133407 Choi et al. Jun 2007 A1
20070140191 Kojima Jun 2007 A1
20070150720 Oh et al. Jun 2007 A1
20070153741 Blanchette et al. Jul 2007 A1
20070156804 Mo Jul 2007 A1
20070160017 Meier et al. Jul 2007 A1
20070171885 Bhagwat et al. Jul 2007 A1
20070192862 Vermeulen et al. Aug 2007 A1
20070195761 Tatar et al. Aug 2007 A1
20070247303 Payton Oct 2007 A1
20070249324 Jou et al. Oct 2007 A1
20070263532 Mirtorabi et al. Nov 2007 A1
20070280481 Eastlake et al. Dec 2007 A1
20070288997 Meier et al. Dec 2007 A1
20080002642 Borkar et al. Jan 2008 A1
20080022392 Karpati et al. Jan 2008 A1
20080037552 Dos Remedios et al. Feb 2008 A1
20080080369 Sumioka Apr 2008 A1
20080080377 Sasaki et al. Apr 2008 A1
20080090575 Barak et al. Apr 2008 A1
20080095094 Innami Apr 2008 A1
20080095163 Chen et al. Apr 2008 A1
20080107027 Allan et al. May 2008 A1
20080109879 Bhagwat et al. May 2008 A1
20080130495 Dos Remedios et al. Jun 2008 A1
20080146240 Trudeau Jun 2008 A1
20080151751 Ponnuswamy et al. Jun 2008 A1
20080159128 Shaffer Jul 2008 A1
20080170527 Lundsgaard et al. Jul 2008 A1
20080186932 Do et al. Aug 2008 A1
20080194271 Bedekar et al. Aug 2008 A1
20080207215 Chu et al. Aug 2008 A1
20080212562 Bedekar et al. Sep 2008 A1
20080219286 Ji et al. Sep 2008 A1
20080225857 Lange Sep 2008 A1
20080229095 Kalimuthu et al. Sep 2008 A1
20080240128 Elrod Oct 2008 A1
20080253370 Cremin et al. Oct 2008 A1
20080273520 Kim et al. Nov 2008 A1
20080279161 Stirbu et al. Nov 2008 A1
20090019521 Vasudevan Jan 2009 A1
20090028052 Strater et al. Jan 2009 A1
20090040989 da Costa et al. Feb 2009 A1
20090043901 Mizikovsky et al. Feb 2009 A1
20090082025 Song Mar 2009 A1
20090088152 Orlassino Apr 2009 A1
20090097436 Vasudevan et al. Apr 2009 A1
20090111468 Burgess et al. Apr 2009 A1
20090113018 Thomson et al. Apr 2009 A1
20090141692 Kasslin et al. Jun 2009 A1
20090144740 Gao Jun 2009 A1
20090168645 Tester et al. Jul 2009 A1
20090172151 Davis Jul 2009 A1
20090197597 Kotecha Aug 2009 A1
20090207806 Makela et al. Aug 2009 A1
20090239531 Andreasen et al. Sep 2009 A1
20090240789 Dandabany Sep 2009 A1
20090247170 Balasubramanian et al. Oct 2009 A1
20090303883 Kucharczyk et al. Dec 2009 A1
20090310557 Shinozaki Dec 2009 A1
20100046368 Kaempfer et al. Feb 2010 A1
20100057930 DeHaan Mar 2010 A1
20100067379 Zhao et al. Mar 2010 A1
20100112540 Gross et al. May 2010 A1
20100115278 Shen et al. May 2010 A1
20100115576 Hale et al. May 2010 A1
20100132040 Bhagwat et al. May 2010 A1
20100208614 Harmatos Aug 2010 A1
20100228843 Ok et al. Sep 2010 A1
20100240313 Kawai Sep 2010 A1
20100254316 Sendrowicz Oct 2010 A1
20100260091 Seok Oct 2010 A1
20100290397 Narayana et al. Nov 2010 A1
20100304738 Lim Dec 2010 A1
20100311420 Reza et al. Dec 2010 A1
20100322217 Jin et al. Dec 2010 A1
20100325720 Etchegoyen Dec 2010 A1
20110004913 Nagarajan et al. Jan 2011 A1
20110040867 Kalbag Feb 2011 A1
20110051677 Jetcheva et al. Mar 2011 A1
20110055326 Michaelis et al. Mar 2011 A1
20110055928 Brindza Mar 2011 A1
20110058524 Hart et al. Mar 2011 A1
20110064065 Nakajima et al. Mar 2011 A1
20110085464 Nordmark et al. Apr 2011 A1
20110182225 Song et al. Jul 2011 A1
20110185231 Balestrieri et al. Jul 2011 A1
20110258641 Armstrong et al. Oct 2011 A1
20110292897 Wu et al. Dec 2011 A1
20120014386 Xiong et al. Jan 2012 A1
20120290650 Montuno et al. Nov 2012 A1
20130003729 Raman et al. Jan 2013 A1
20130003739 Raman et al. Jan 2013 A1
20130003747 Raman et al. Jan 2013 A1
20130028158 Lee et al. Jan 2013 A1
20130059570 Nara et al. Mar 2013 A1
20130086403 Jenne et al. Apr 2013 A1
20130103833 Ringland et al. Apr 2013 A1
20130227306 Santos et al. Aug 2013 A1
20130230020 Backes Sep 2013 A1
20130250811 Vasseur et al. Sep 2013 A1
20140269327 Fulknier et al. Sep 2014 A1
20140298467 Bhagwat et al. Oct 2014 A1
20150120864 Unnimadhavan et al. Apr 2015 A1
Foreign Referenced Citations (8)
Number Date Country
0940999 Sep 1999 EP
1732276 Dec 2006 EP
1771026 Apr 2007 EP
1490773 Jan 2013 EP
0059251 Oct 2000 WO
2004042971 May 2004 WO
2006129287 Dec 2006 WO
2009141016 Nov 2009 WO
Non-Patent Literature Citations (13)
Entry
Clausen, T., et al., Optimized Link State Routing Protocol (OLSR), Network Working Group, Oct. 2003, pp. 1-71.
Perkins, C., et al., Ad hoc On-Demand Distance Vector (AODV) Routing, Network Working Group, Oct. 2003, pp. 1-35.
International Application No. PCT/US2011/047591, International Search Report and Written Opinion dated Dec. 19, 2011.
International Application No. PCT/US2008/061674, International Search Report and Written Opinion dated Oct. 14, 2008.
He, Changhua et al., “Analysis of the 802.11i 4-Way Handshake,” Proceedings of the 3rd ACM Workshop on Wireless Security, pp. 43-50, Oct. 2004.
Lee, Jae Woo et al, “z2z: Discovering Zeroconf Services Beyond Local Link,” 2007 IEEE Globecom Workshops, pp. 1-7, Nov. 26, 2007.
International Application No. PCT/US2012/059093, International Search Report and Written Opinion dated Jan. 4, 2013.
Wu, Haitao et al., “Layer 2.5 SoftMAC: End-System Based Media Streaming Support on Home Networks,” IEEE Global Telecommunications Conference (GLOBECOM '05), vol. 1, pp. 235-239, Nov. 2005.
European Patent Application No. 12879114.2, Search Report dated Jan. 21, 2016.
European Patent Application No. 11823931.8, Search Report dated Aug. 29, 2016.
Chirumamilla, Mohan K. et al., “Agent Based Intrustion Detection and Response System for Wireless LANs,” CSE Conference and Workshop Papers, Paper 64, Jan. 1, 2003.
Craiger, J. Philip, “802.11, 802.1x, and Wireless Security,” SANS Institute InfoSec Reading Room, Jun. 23, 2002.
Finlayson, Ross et al., “A Reverse Address Resolution Protocol,” Nework Working Group, Request for Comments: 903 (RFC 903), Jun. 1984.
Provisional Applications (1)
Number Date Country
61224716 Jul 2009 US