WO2021248304A1

WO2021248304A1 - Enhanced airtime fairness

Info

Publication number: WO2021248304A1
Application number: PCT/CN2020/095078
Authority: WO
Inventors: Lidan CHEN
Original assignee: Arris Enterprises Llc
Priority date: 2020-06-09
Filing date: 2020-06-09
Publication date: 2021-12-16

Abstract

An electronic gateway device includes a network interface configured to electronically wirelessly communicate with client devices, a memory having software stored thereon, and a processor configured to run the software to cause the electronic gateway device to execute at least the following: establish service set identifiers (SSIDs) for communication with the client devices via the network interface; and for each SSID: (i) automatically allocate a first airtime percentage to a first group of the client devices connected to the SSID, and a second airtime percentage to a second group of the client devices connected to the SSID; and (ii) automatically assign a new client device to the first group when the new client device connects to the SSID.

Description

ENHANCED AIRTIME FAIRNESS

TECHNICAL FIELD

The subject matter of the present disclosure relates generally to providing enhanced airtime fairness (ATF) for client devices using a gateway/access point device.

BACKGROUND

Wireless networks for providing services to client devices or end devices via a gateway or access point device are prevalent in many homes and businesses. A single home may have multiple client devices which are associated or paired through a network such as a wired local area network (LAN) , a wireless LAN (WLAN) (e.g., Wi-Fi) , Bluetooth connectivity, etc. Client devices that are legacy devices or that have poor link quality ( “edge” or “bad apple” devices) can consume a disproportionate amount of airtime or bandwidth and adversely impact aggregate throughput of a gateway device.

Existing solutions for reducing such adverse impact on airtime include ATF techniques whereby a user can allocate airtime for each service set identifier (SSID) established by the gateway device. In this way, the amount of airtime consumed by edge or bad apple devices can be limited so as to reduce the overall burden on the gateway device and more airtime can be distributed to client devices with higher link quality so as to increase aggregate throughput. ATF techniques generally include global ATF and weighted ATF.

With global ATF, airtime is shared equally among all active client devices. However, global ATF is a one size fits all approach and cannot be tailored for bespoke applications. Accordingly, edge or bad apple devices can still be allocated an inefficient amount of airtime.

With weighted ATF, airtime is shared among active client devices as per preconfigured weights and an ATF distribution is applied per SSID. However, a user must individually add each client device (e.g., the Media Access Control (MAC) address of the client device) as a station (STA) index to an ATF group and must individually configure a specific airtime percentage for each client device. Furthermore, weighted ATF cannot be applied to specific groups of client devices but must be applied to client devices one by one. In addition, if a client device is inactive or offline for an extended period of time, the client device cannot be automatically cleared from the ATF distribution and must be manually removed by a user. Therefore, existing solutions require copious amounts of user configuration.

Thus, it would be advantageous and an improvement over the relevant technology to provide an electronic device, method, and program for providing enhanced ATF whereby new client devices can be automatically added into the ATF distribution and the ATF distribution can be applied to specific groups of client devices thereby simplifying the implementation of ATF for users and reducing configuration time and burden.

SUMMARY

An embodiment of the present disclosure provides an electronic device (e.g., gateway/access point device) for providing enhanced ATF for client devices. The electronic gateway device comprises a network interface configured to electronically wirelessly communicate with client devices; a memory having software stored thereon; and a processor configured to run the software to cause the electronic gateway device to execute at least the following: establish service set identifiers (SSIDs) for communication with the client devices via the network interface; and for each SSID: (i) automatically allocate a first airtime percentage to a first group of the client devices connected to the SSID, and a second airtime percentage to a second group of the client devices connected to the SSID; and (ii) automatically assign a new client device to the first group when the new client device connects to the SSID.

An embodiment of the present disclosure provides a method for providing enhanced ATF for client devices. The method comprises establishing service set identifiers (SSIDs) for communication with client devices via a network interface of an electronic gateway device; and for each SSID: (i) automatically allocating a first airtime percentage to a first group of the client devices connected to the SSID, and a second airtime percentage to a second group of the client devices connected to the SSID; and (ii) automatically assigning a new client device to the first group when the new client device connects to the SSID.

An embodiment described in the present disclosure provides a non-transitory computer-readable recording medium in an electronic device (e.g., gateway/access point device) for providing enhanced ATF for client devices. The non-transitory computer-readable recording medium stores one or more programs which when executed by a hardware processor performs the steps of the methods described above.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements.

FIG. 1 is a schematic diagram of a system for providing enhanced ATF for client devices using a gateway/access point device according to an embodiment of the present disclosure;

FIG. 2 is a more detailed schematic diagram of a gateway/access point device, and a client device in the system for providing enhanced ATF for client devices using a gateway/access point device according to an embodiment of the present disclosure;

FIG. 3 illustrates a method and algorithm for providing enhanced ATF for client devices using a gateway/access point device according to an embodiment of the present disclosure;

FIG. 4 is a bar graph of an example ATF distribution for multiple SSIDs;

FIG. 5 is a pie chart of an example ATF distribution for a single SSID;

FIG. 6 is a bar graph illustrating effects of ATF; and

FIG. 7 shows graphs illustrating effects of ATF.

DETAILED DESCRIPTION

The following detailed description is made with reference to the accompanying drawings and is provided to assist in a comprehensive understanding of various example embodiments of the present disclosure. The following description includes various details to assist in that understanding, but these are to be regarded as merely examples. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the spirit and scope of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are merely used to enable a clear and consistent understanding of the present disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of the present disclosure is provided for illustration purposes only, and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

FIG. 1 is a schematic diagram of a system for providing enhanced ATF for client devices using a gateway/access point device according to an embodiment of the present disclosure. As shown in FIG. 1, the system includes a gateway/access point device 100 connected to an operator 300 via a WAN connection 130 and also connected to client devices 200 ₁-200 ₈ via respective connections 120 ₁-120 ₈ (e.g., Wi-Fi connections) . The WAN connection 130 constructively provides access to the Internet 400.

Although FIG. 1 shows one gateway/access point device 100 and eight client devices 200 ₁-200 ₈, any number of gateway/access point devices and any number of client devices may be included.

In FIG. 1, the operator 300 may include network equipment, (e.g., cable modem termination system, headend hardware, etc. ) , of a cable television provider, a satellite television provider, an Internet service provider (ISP) , telco or multiple systems operator (MSO) . The connection 340, the Internet 400, and the connection 130, between the operator 300 and the gateway/access point device 100 can be considered as encompassing and including any of a WAN, a virtual private network (VPN) , metropolitan area networks (MANs) , system area networks (SANs) , a Data Over Cable Service Interface Specification (DOCSIS) network, a media over coax (MoCA) network, a fiber optics network (such as FTTH (fiber to the home) or FTTX (fiber to the x) ) , a hybrid fiber coaxial (HFC) network, a public switched data network (PSDN) , a global Telex network, a digital subscriber line (DSL) , or a wireless broadband system such as a 2G, 3G, 4G or 5G network, for example.

The gateway/access point device 100 is a hardware electronic device that acts as a router for providing content received from the operator 300 to network devices (e.g., client devices 200 ₁-200 ₈) in one of more wireless networks. It is also contemplated by the present disclosure that the gateway/access point device 100 can be, but is not limited to, an Internet Protocol/Quadrature Amplitude Modulator (IP/QAM) set-top box (STB) or smart media device (SMD) that is capable of decoding audio/video content, and playing over-the-top (OTT) or MSO provided content.

Each client device 200 ₁-200 ₈ is, for example, any computer, smartphone, electronic tablet, e-reader, personal digital assistant (PDA) , portable music player with smart capabilities, appliance, smart speaker, Internet of Things (IoT) device, iControl device, or other wireless consumer electronic device capable of executing and displaying the content received through, for example, the gateway/access point device 100. Each client device 200 ₁-200 ₈ is capable of interconnecting with other devices via Wi-Fi protocols. The connection 120 ₁-120 ₈ between the gateway/access point device 100 and each client device 200 ₁-200 ₈ is implemented through a wireless connection that operates in accordance with, but is not limited to, any IEEE 802.11 protocol, RF4CE protocol, ZigBee protocol, Z-Wave protocol, or IEEE 802.15.4 protocol. In some embodiments, each client device 200 ₁-200 ₈ may also be capable of connecting to the Internet 400 over cellular networks and interconnecting with other devices via Bluetooth protocols.

In FIG. 1, as an exemplary implementation, the gateway/access point device 100 establishes a WLAN for communication using, e.g., Wi-Fi, and allows the client devices 200 ₁-200 ₈ to access the Internet 400 via the WLAN established by the gateway/access point device 100.

A detailed description of the exemplary internal components of the gateway/access point device 100 and the client devices 200 ₁-200 ₈ shown in FIG. 1 will be provided in the discussion of FIG. 2. However, in general, it is contemplated by the present disclosure that the gateway/access point device 100 and the client devices 200 ₁-200 ₈ include electronic components or electronic computing devices operable to receive, transmit, process, store, and/or manage data and information associated with the system, which encompasses any suitable processing device adapted to perform computing tasks consistent with the execution of computer-readable instructions stored in a memory or a computer-readable recording medium.

Further, any, all, or some of the computing devices in the gateway/access point device 100 and the client devices 200 ₁-200 ₈ may be adapted to execute any operating system, including Linux, UNIX, Windows, MacOS, DOS, and Chrome OS as well as virtual machines adapted to virtualize execution of a particular operating system, including customized and proprietary operating systems. The gateway/access point device 100 and the client devices 200 ₁-200 ₈ are further equipped with components to facilitate communication with other computing devices over the one or more network connections to local and wide area networks, wireless and wired networks, public and private networks, and any other communication network enabling communication in the system.

It is contemplated by the present disclosure that the term “user” may include any home user, end user, customer, personnel of an operator such as an MSO, etc.

FIG. 2 illustrates a more detailed schematic diagram of the gateway/access point device 100 and the client devices 200 ₁-200 ₈ in the system for providing enhanced ATF according to an embodiment of the present disclosure. For simplicity, only one client device 200 _n is shown in FIG. 2. However, it is contemplated by the present disclosure that the client device 200 _n may represent any of the client devices 200 ₁-200 ₈ and that any number of client devices may be provided.

Now referring to FIG. 2 (e.g., from left to right) , the client device 200 _n is any computer, smartphone, electronic tablet, e-reader, PDA, portable music player with smart capabilities, appliance, smart speaker, IoT device, iControl device, or other wireless consumer electronic device capable of executing and displaying the content received through, for example, the gateway/access point device 100. The client device 200 _n is capable of interconnecting with other devices via Wi-Fi protocols. As shown in FIG. 2, an exemplary client device 200 _n can include a user interface 201 _n, a power supply 202 _n, a network interface 203 _n, a WAN interface 204 _n, a controller 205 _n, and a memory 206 _n. The user interface 201 _n may include, but is not limited to, push buttons, a keyboard, a keypad, a liquid crystal display (LCD) , a cathode ray tube (CRT) , a thin film transistor (TFT) , a light-emitting diode (LED) , and/or a high definition (HD) or other similar display device including a display device having touch screen capabilities so as to allow interaction between a user and the client device 200 _n. The power supply 202 _n supplies power to the internal components of the client device 200 _n through an internal bus 208 _n. The power supply 202 _n includes a self-contained power source such as a battery pack with an interface to be powered through an electrical charger connected to an outlet (e.g., either directly or by way of another device) . The power supply 202 _n can also include a rechargeable battery that can be detached allowing for replacement such as a nickel-cadmium (NiCd) , a nickel metal hydride (NiMH) , a lithium-ion (Li-ion) , or a lithium Polymer (Li-pol) battery.

The network interface 203 _n can include various network cards, interfaces, and circuitry implemented in software and/or hardware to enable communications with the gateway/access point device 100 using connection 120 _n using a wireless protocol. The various network cards, interfaces, and circuitry enable communications via connection 120 _n using a wireless connection that operates in accordance with, but is not limited to, any IEEE 802.11 protocol, RF4CE protocol, ZigBee protocol, Z-Wave protocol, or IEEE 802.15.4 protocol.

In some embodiments, the client device 200 _n may be configured with a WAN interface 204 _n including Internet connection circuitry (via, e.g., a cellular network interface such as 2G, 3G, 4G, or 5G) , allowing the client device 200 _n to access the Internet 400 via a WLAN established by the network interface 203 of client device 200 _n and via the WAN interface 204 _n of the client device 200 _n. However, it is contemplated by the present disclosure that the WAN interface 204 _n could be omitted.

The memory 206 _n includes a single memory or one or more memories or memory locations that include, but are not limited to, random access memory (RAM) , dynamic random access memory (DRAM) , a memory buffer, a hard drive, a database, an erasable programmable read only memory (EPROM) , an electrically erasable programmable read only memory (EEPROM) , read only memory (ROM) , flash memory, logic blocks of a field programmable gate array (FPGA) , a hard disk or any other various layers of memory hierarchy.

The memory 206 _n can be used to store any type of instructions including software 207 _n associated with algorithms, processes, or operations for controlling the general functions and operations of the client device 200 _n.

The controller 205 _n controls the general operations of the client device 200 _n and includes, but is not limited to, a central processing unit (CPU) , a hardware processor such as, a microprocessor, a multi-core processor, a single core processor, a field programmable gate array (FPGA) , a microcontroller, an application specific integrated circuit (ASIC) , a digital signal processor (DSP) , or other similar processing device capable of executing any type of instructions, algorithms, or software for controlling the operation and performing the functions of the client device 200 _n. General communication between the components (e.g., 201 _n-206 _n) of the client device 200 _n may be performed using an internal bus 208 _n.

The gateway/access point device 100 is a hardware electronic device that acts as a router for providing content received from a WAN interface 103 to the devices (e.g., client device 200 _n) in a wireless network using connection 120 _n. As shown in FIG. 2, the gateway/access point device 100 includes a user interface 101, a network interface 102, the WAN interface 103, a power supply 104, a memory 105, and a controller 107.

The network interface 102 may include various network cards, and circuitry implemented in software and/or hardware to enable communications with the client device 200 _n using connection 120 _n. The various network cards, interfaces, and circuitry of the network interface 102 enable communications via connection 120 to the client device 200 _n using a wireless protocol that operates in accordance with, but is not limited to, any IEEE 802.11 protocol, RF4CE protocol, ZigBee protocol, Z-Wave protocol, or IEEE 802.15.4 protocol.

The WAN interface 103 may include various network cards, and circuitry implemented in software and/or hardware to enable communications with operator network 130 (not shown) . The various network cards, interfaces, and circuitry of the network interface 102 enable communications to be routed from network interface 203 _n to the Internet 400 via the WAN interface 103.

The memory 105 includes a single memory or one or more memories or memory locations that include, but are not limited to, RAM, DRAM, a memory buffer, a hard drive, a database, an EPROM, an EEPROM, ROM, flash memory, logic blocks of a FPGA, a hard disk or any other various layers of memory hierarchy. The memory 105 can be used to store any type of instructions including software 106 associated with algorithms, processes, or operations for controlling the general functions and operations of the gateway/access point device 100 for providing enhanced ATF for the client devices 200 ₁-200 ₈.

The controller 107 controls the general operations of the gateway/access point device 100 and includes, but is not limited to, a CPU, a hardware processor such as a microprocessor, a multi-core processor, a single core processor, a FPGA, a microcontroller, an ASIC, a DSP, or other similar processing device capable of executing any type of instructions, algorithms, or software for controlling the operation and performing the functions of the gateway/access point device 100. Communication between the components (e.g., 101-105 and 107) of the gateway/access point device 100 may be established using an internal bus 108.

FIG. 3 illustrates an exemplary method and algorithm for providing enhanced ATF for client devices using a gateway/access point device according to an embodiment of the present disclosure. It is assumed that the gateway/access point device 100 and the client devices 200 ₁-200 ₈ include their respective software 106, 207 ₁-207 ₈ in their respective memories 105, 206 ₁-207 ₈. In FIG. 3, the method and algorithm illustrate operations performed by processors running the software 106 of the gateway/access point device 100 and the software 207 ₁-207 ₈ of the client devices 200 ₁-200 ₈ providing enhanced ATF. The software 106, 207 ₁-207 ₈ in the respective memories 105, 206 ₁-206 ₈ can be for implementing, for example, a procedure between the gateway/access point device 100 and the client device 200 ₁-200 ₈ for providing enhanced ATF. Although FIG. 3 refers to only one new client device, it is contemplated by the present disclosure that the method and algorithm can be applied to any number of gateway/access point devices and client devices for providing enhanced ATF described with reference to FIG. 1.

In Step S1, the gateway/access point device 100 establishes an SSID for communication with the client devices 200 ₁-200 ₈.

In Step S2, it is determined whether a user has defined a custom ATF distribution for client devices. For example, airtime percentages may be modified by a user via a graphical user interface (GUI) for the gateway/access point device 100. If the airtime percentages have not been modified from default airtime percentages, the process proceeds to Step S3. If the airtime percentages have been modified from default airtime percentages, the process proceeds to Step S4.

In Step S3, airtime is allocated according to a default ATF distribution predefined in advance. Initially, a default airtime percentage for each ATF group is recommended so as to reduce the user’s involvement. For example, the default ATF distribution may be 40%for Group 1, 40%for

Group

2 and 20%unallocated (see, e.g., Private SSID shown in FIG. 4) . The process then proceeds to Step S5.

In Step S4, airtime is allocated according to a custom ATF distribution defined by a user. For example, the custom ATF distribution may be 80%for Group 1, 10%for

Group

2 and 10%for Group 3 (see, e.g., FIG. 5) . The process then proceeds to Step S5.

In Step S5, it is determined if a request from any new client device to connect to the SSID has been received by the gateway/access point device 100. A new client device is any client device that has not previously connected to the SSID. If no connection request has been received, the process proceeds to Step S6 at which the process ends. If a connection request has been received, the process proceeds to Step S7.

In Step S7, the gateway/access point device 100 automatically adds the new client device to Group 1. In some implementations, this can include adding a unique identifier of the new client device to Group 1. As one example, this can include adding a MAC address of the new client device to Group 1. However, it is contemplated by the present disclosure that any type of unique identifier of the new client device can be used to add the new client device to Group 1.

In Step S8, the gateway/access point device 100 notifies a user that the new client device has been added to Group 1. This step can be performed, for example, when a new client device connects to a lower priority SSID (e.g., a Hotspot SSID with a higher probability of edge or bad apple devices being connected thereto) . The user can then identify the priority of the client device and decide whether to reassign the client device to another ATF group.

In Step S9, it is determined if the user has reassigned the new client device from Group 1 to another ATF group. For example, a user can move any client device from one ATF group to another by changing the STA index of the client device from Group 1 to Group 2 via the GUI or a protocol such as Simple Network Management Protocol (SNMP) or Technical Report 069 (TR-069) Protocol. If the new client device has not been reassigned and the default ATF distribution is applicable, the process returns to Step S3 and the new client device is allocated airtime according to Group 1 in the default ATF distribution. Alternatively, if the new client device has not been reassigned and a custom ATF distribution is applicable, the process returns to Step S4 and the new client device is allocated airtime according to Group 1 in the custom ATF distribution. Accordingly, a user can distinguish client devices into different ATF groups as desired. If the new client device has been reassigned, the process proceeds to Step S10.

In Step S10, it is determined if a new ATF group (e.g., an ATF group other than existing Groups 1 and 2) has been created for the new client device to be reassigned to. For example, if the user changes the STA index of a new client device to a new ATF group number that does not already exist, the gateway/access point device 100 can automatically create a new ATF group corresponding to the new ATF group number. If a new ATF group has not been created, the process proceeds to Step S11. If a new ATF group (e.g., Group 3) has been created, the process proceeds to Step S12.

In Step S11, the new client device is automatically reassigned to Group 2. If the default ATF distribution is applicable, the process returns to Step S3 and the new client device is allocated airtime according to Group 2 in the default ATF distribution. If a custom ATF distribution is applicable, the process returns to Step S4 and the new client device is allocated airtime according to Group 2 in the custom ATF distribution.

In Step S12, new Group 3 is created and the new client device is reassigned to Group 3. Accordingly, new ATF groups can be created as desired. The process then proceeds to Step S13.

In Step S13, the applicable ATF distribution (default or custom) is modified to accommodate new Group 3. If the aggregate airtime of the existing ATF groups has already reached 100%, the airtime of one or more of the existing ATF groups may be reduced so as to provide airtime for new Group 3. A message can be sent to the user to confirm that the airtime should be redistributed. In some variations, the user may decide that no airtime should be given to the new ATF group. For example, it may be determined that the client device in Group 3 is an illegal or trespassing client device. Accordingly, Group 3 would be allocated 0%of airtime and client devices in Group 3 cannot establish a WAN/LAN connection through the SSID.

If the user has not specified an airtime percentage for the new ATF group, a default airtime percentage may be allocated to the new ATF group. When a new ATF group is created, it can be suggested to allocate at least 10%of the airtime of the SSID to the new ATF group. For example, the unallocated 20% (see FIG. 4) may be distributed to Group 3. Alternatively, the user may define the airtime percentage for the new ATF group. Accordingly, the user’s redefinition of the ATF distribution is followed and Group 3 is allocated 10%, for example (see FIG. 5) . The process then returns to Step S5.

In some variations, any of the client devices may be removed from the ATF group to which it is assigned if the client device is inactive for a period of time. For example, if the gateway/access point device does not receive any data packets from the client device for a period of time (for example, twelve hours, twenty four hours, forty eight hours, etc. ) or the client device is disconnected from the SSID for the period of time, the gateway/access point device can automatically remove the client device from the ATF group to which it is assigned. However, if the client device becomes active after removal from an ATF group (i.e., the client device reconnects to the SSID) , the gateway/access point device can automatically add the client device back into the group to which the client device was previously assigned before removal.

Although FIG. 3 shows only one SSID, it is contemplated by the present disclosure that any number of SSIDs and respective ATF distributions may be established.

FIG. 4 is a bar graph of an example ATF distribution for multiple SSIDs. In the example of FIG. 4, two different SSIDs (i.e., Private SSID (e.g. Wi-Fi) and Hotspot SSID) are created and have respective ATF distributions.

In general, all client devices in an ATF group share the allocated airtime equally. In addition, unallocated airtime of an SSID is equally distributed across all client devices connected to the SSID (regardless of which ATF group each client device is in) .

In the example of FIG. 4, 80%of the overall airtime provided by the gateway/access point device 100 is allocated to the Private SSID to which client devices 200 ₁-200 ₅ are connected. 20%of the airtime of the Private SSID remains unallocated to any ATF group and is equally distributed across client devices 200 ₁-200 ₅.

Client devices 200 ₁-200 ₄ are assigned to Group 1 of the Private SSID which is allocated 40%of the airtime of the Private SSID. Therefore, each of client devices 200 ₁-200 ₄ is allocated 11.2%of the overall airtime (i.e., 80%of overall airtime *40%of the airtime of the Private SSID *1 client device/4 total client devices in Group 1 of the Private SSID + 80%of overall airtime *20%of the airtime of the Private SSID *1 client device/5 total client devices connected to the Private SSID) .

Client device 200 ₅ is assigned to Group 2 of the Private SSID which is allocated 40%of the airtime of the Private SSID. Therefore, client device 200 ₅ is allocated 35.2%of the overall airtime (i.e., 80%of overall airtime *40%of the airtime of the Private SSID *1 client device/1 total client device in Group 2 of the Private SSID + 80%of overall airtime *20%of the airtime of the Private SSID *1 client device/5 total client devices connected to the Private SSID) . In this example, client device 200 ₅ is given higher priority (i.e., treated as a VIP user) and is provided a better service experience.

If only one client device is assigned to one ATF group, the one client device will occupy all of the airtime of the one ATF group. This example is analogous to existing Weighted ATF techniques, and therefore in this example, the present disclosure contemplates backward compatibility to existing Weighted ATF techniques.

In the example of FIG. 4, 20%of the overall airtime provided by the gateway/access point device 100 is allocated to the Hotspot SSID to which client devices 200 ₆-200 ₈ are connected.

Client device 200 ₆ is assigned to Group 1 of the Hotspot SSID which is allocated 40%of the airtime of the Hotspot SSID. Therefore, client device 200 ₆ is allocated 8%of the overall airtime (i.e., 20%of overall airtime *40%of the airtime of the Hotspot SSID *1 client device/1 total client device in Group 1 of the Hotspot SSID) .

Client devices 200 ₇-200 ₈ are assigned to Group 2 of the Hotspot SSID which is allocated 60%of the airtime of the Hotspot SSID. Therefore, each of client devices 200 ₇-200 ₈ is allocated 6%of the overall airtime (i.e., 20%of overall airtime *60%of the airtime of the Hotspot SSID *1 client device/2 total client devices in Group 2 of the Hotspot SSID) .

FIG. 5 is a pie chart of an example ATF distribution for a single SSID. In this example, client devices in Group 1 equally share 80%of the overall airtime, client devices in Group 2 equally share 10%of the overall airtime, and client devices in Group 3 equally share 10%of the overall airtime. In this example, Group 1 is given higher priority and is provided a better service experience.

FIG. 6 is a bar graph illustrating effects of ATF. In this example, a Hotspot SSID is given lower priority (e.g., due to a higher probability of edge or bad apple devices being connected to the Hotspot SSID) . The left bar represents a network in which airtime is unmanaged (i.e., no ATF is applied) and the Hotspot SSID unfairly consumes a disproportionate amount of airtime (over 20%) . The right bar represents a network in which airtime is managed (i.e., ATF is applied) and the Hotspot SSID is constrained to 20%of airtime so as to mitigate the bandwidth consumption by the Hotspot SSID which has lower priority. Accordingly, the Private SSID (e.g., Wi-Fi) is provided 80%of airtime and overall throughput of the system is increased.

FIG. 7 shows graphs illustrating effects of ATF. The top two graphs represent a network in which airtime is unmanaged (i.e., no ATF is applied) and the bottom two graphs represent a network in which airtime is managed (i.e., ATF is applied) . The lighter bars represent a slow client device (e.g., a client device that is a legacy device or has a weak signal) and the darker horizontal bars represent a fast client device (e.g., a client device that is a contemporary device or has a strong signal) . In the unmanaged network, the speed of the network is determined by the slowest client device and overall throughput is limited. In the managed network, the fast client device is prioritized and given more airtime thereby allowing the fast client device to transmit more data packets, finish transmission more quickly, and free up bandwidth for the slow client device. In this way, overall throughput of the system is improved substantially.

The present disclosure may be implemented as any combination of an apparatus, a system, an integrated circuit, and a computer program on a non-transitory computer readable recording medium. The one or more processors may be implemented as an integrated circuit (IC) , an application specific integrated circuit (ASIC) , or large scale integrated circuit (LSI) , system LSI, super LSI, or ultra LSI components that perform a part or all of the functions described in the present disclosure.

The present disclosure includes the use of software, applications, computer programs, or algorithms. The software, applications, computer programs, or algorithms can be stored on a non-transitory computer-readable medium for causing a computer, such as the one or more processors, to execute the steps described in FIG. 3. For example, the one or more memories store software or algorithms with executable instructions and the one or more processors can execute a set of instructions of the software or algorithms in association with providing enhanced ATF for client devices using a gateway/access point device.

The software and computer programs, which can also be referred to as programs, software applications, applications, components, or code, include machine instructions for a programmable processor, and can be implemented in a high-level procedural language, an object-oriented programming language, a functional programming language, a logical programming language, or an assembly language or machine language. The term computer-readable recording medium refers to any computer program product, apparatus or device, such as a magnetic disk, optical disk, solid-state storage device, memory, and programmable logic devices (PLDs) , used to provide machine instructions or data to a programmable data processor, including a computer-readable recording medium that receives machine instructions as a computer-readable signal.

By way of example, a computer-readable medium can comprise DRAM, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired computer-readable program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Disk or disc, as used herein, include compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Use of the phrases “capable of, ” “capable to, ” “operable to, ” or “configured to” in one or more embodiments, refers to some apparatus, logic, hardware, and/or element designed in such a way to enable use of the apparatus, logic, hardware, and/or element in a specified manner. The subject matter of the present disclosure is provided as examples of apparatus, systems, methods, and programs for performing the features described in the present disclosure. However, further features or variations are contemplated in addition to the features described above. It is contemplated that the implementation of the components and functions of the present disclosure can be done with any newly arising technology that may replace any of the above implemented technologies.

Additionally, the above description provides examples, and is not limiting of the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure. Various embodiments may omit, substitute, or add various procedures or components as appropriate. For instance, features described with respect to certain embodiments may be combined in other embodiments.

Claims

An electronic gateway device comprising:

a network interface configured to electronically wirelessly communicate with client devices;

a memory having software stored thereon; and

a processor configured to run the software to cause the electronic gateway device to execute at least the following:

establish service set identifiers (SSIDs) for communication with the client devices via the network interface; and

for each SSID: (i) automatically allocate a first airtime percentage to a first group of the client devices connected to the SSID, and a second airtime percentage to a second group of the client devices connected to the SSID; and (ii) automatically assign a new client device to the first group when the new client device connects to the SSID.
The electronic gateway device of claim 1, wherein the processor is configured to run the software to cause the electronic gateway device to define the first airtime percentage and the second airtime percentage based on input from a user.
The electronic gateway device of claim 1, wherein the processor is configured to run the software to cause the electronic gateway device to assign any of the client devices in the first group to the second group or vice versa based on input from a user.
The electronic gateway device of claim 1, wherein the processor is configured to run the software to cause the electronic gateway device to, for any SSID:

define a third group of the client devices connected to the SSID based on input from a user; and

automatically allocate a third airtime percentage to the third group.
The electronic gateway device of claim 4, wherein the processor is configured to run the software to cause the electronic gateway device to adjust the first airtime percentage or the second airtime percentage to accommodate the third airtime percentage.
The electronic gateway device of claim 4, wherein the processor is configured to run the software to cause the electronic gateway device to define the third airtime percentage based on input from the user.
The electronic gateway device of claim 1, wherein the processor is configured to run the software to cause the electronic gateway device to remove one of the client devices from the group to which the one of the client devices is assigned if the one of the client devices is inactive for a period of time.
The electronic gateway device of claim 7, wherein the processor is configured to run the software to cause the electronic gateway device to reassign the one of the client devices to the group to which the one of the client devices was previously assigned if the one of the client devices becomes active after removal.
The electronic gateway device of claim 1, wherein the first airtime percentage and the second airtime percentage for a first of the SSIDs are different from the first airtime percentage and the second airtime percentage for a second of the SSIDs.
A method implemented on an electronic gateway device, the method comprising:

establishing service set identifiers (SSIDs) for communication with client devices via a network interface of the electronic gateway device; and

for each SSID: (i) automatically allocating a first airtime percentage to a first group of the client devices connected to the SSID, and a second airtime percentage to a second group of the client devices connected to the SSID; and (ii) automatically assigning a new client device to the first group when the new client device connects to the SSID.
The method of claim 10, further comprising defining the first airtime percentage and the second airtime percentage based on input from a user.
The method of claim 10, further comprising assigning any of the client devices in the first group to the second group or vice versa based on input from a user.
The method of claim 10, further comprising, for any SSID:

defining a third group of the client devices connected to the SSID based on input from a user; and

automatically allocating a third airtime percentage to the third group.
The method of claim 13, further comprising adjusting the first airtime percentage or the second airtime percentage to accommodate the third airtime percentage.
The method of claim 13, further comprising defining the third airtime percentage based on input from the user.
The method of claim 10, further comprising removing one of the client devices from the group to which the one of the client devices is assigned if the one of the client devices is inactive for a period of time.
The method of claim 16, further comprising reassigning the one of the client devices to the group to which the one of the client devices was previously assigned if the one of the client devices becomes active after removal.
The method of claim 10, wherein the first airtime percentage and the second airtime percentage for a first of the SSIDs are different from the first airtime percentage and the second airtime percentage for a second of the SSIDs.
A non-transitory computer readable recording medium having stored thereon a program implemented on an electronic gateway device, the program causing the electronic gateway device to perform steps comprising:

establishing service set identifiers (SSIDs) for communication with client devices via a network interface of the electronic gateway device; and

for each SSID: (i) automatically allocating a first airtime percentage to a first group of the client devices connected to the SSID, and a second airtime percentage to a second group of the client devices connected to the SSID; and (ii) automatically assigning a new client device to the first group when the new client device connects to the SSID.
The non-transitory computer readable recording medium of claim 19, wherein the program causes the electronic gateway device to perform a further step of defining the first airtime percentage and the second airtime percentage based on input from a user.