Patent Description:
In computer networking, a wireless Access Point (AP) is a networking hardware device that allows a Wi-Fi compatible client device to connect to a wired network and to other client devices. The AP usually connects to a router (directly or indirectly via a wired network) as a standalone device, but it can also be an integral component of the router itself. Several APs may also work in coordination, either through direct wired or wireless connections, or through a central system, commonly called a Wireless Local Area Network (WLAN) controller. An AP is differentiated from a hotspot, which is the physical location where Wi-Fi access to a WLAN is available.

Prior to wireless networks, setting up a computer network in a business, home, or school often required running many cables through walls and ceilings in order to deliver network access to all of the network-enabled devices in the building. With the creation of the wireless AP, network users are able to add devices that access the network with few or no cables. An AP connects to a wired network, then provides radio frequency links for other radio devices to reach that wired network. Most APs support the connection of multiple wireless devices. APs are built to support a standard for sending and receiving data using these radio frequencies. <CIT> forms part of the related prior art.

Multi-link selection based on Transmit Power Control (TPC) may be provided. A computing device may receive Multi-Link Device (MLD) association information associated with a client device. The MLD association information may describe MLD links the client device may require. A set of MLD links available on a network may be determined based on the MLD association information. The determined set of MLD links may then be sent to the client device.

Both the foregoing overview and the following example embodiments are examples and explanatory only, and should not be considered to restrict the disclosure's scope, as described and claimed. Furthermore, features and/or variations may be provided in addition to those described. For example, embodiments of the disclosure may be directed to various feature combinations and sub-combinations described in the example embodiments.

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar elements. While embodiments of the disclosure may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the disclosure. Instead, the proper scope of the disclosure is defined by the appended claims.

Wi-Fi <NUM> and Wi-Fi <NUM> in <NUM> may have various Transmit Power Control (TPC) options. These TPC options may include, but are not limited to, Standard Power (SP), which may be governed by the Automated Frequency Control (AFC) system and Low Power Indoor (LPI), which may be governed by fixed geographic-specific rules. While the Institute of Electrical and Electronics Engineers (IEEE) <NUM>. 11be standard may provide Information Elements (IEs) for Access Points (APs) to advertise the TPC regime in effect on each Basic Service Set Identifier (BSSID) and Stations (STAs) (e.g., client devices) to indicate support for these regimes on each radio, there may be no guidance or rules established for a Multi-Link Device (MLD) that may be able to associate with one or both of these types of links. Furthermore, there may be no policy for how the AP should configure each radio link given this flexibility. Embodiments of the disclosure may determine a set of MLD links available on a multi power-class network based on the MLD needs of a client device and provide the client device with these links.

<FIG> shows an operating environment <NUM> for providing multi-link selection based on Transmit Power Control (TPC). As shown in <FIG>, operating environment <NUM> may comprise a controller <NUM> and a plurality of Access Points (APs). The plurality of APs may comprise a first AP <NUM>, a second AP <NUM>, and a third AP <NUM>. Each of the plurality of APs may be compatible with specification standards such as, but not limited to, the IEEE <NUM> specification standard for example.

The plurality of APs may provide a coverage environment (e.g., a multi power-class network). For example, first AP <NUM> may provide a first AP first coverage environment <NUM> (e.g., through high bandwidth LPI links) and a first AP second coverage environment <NUM> (e.g., through SP links (i.e., coverage links)). Similarly, second AP <NUM> may provide a second AP first coverage environment <NUM> (e.g., through high bandwidth LPI links) and a second AP second coverage environment <NUM> (e.g., through SP links (i.e., coverage links)). Likewise, third AP <NUM> may provide a third AP first coverage environment <NUM> (e.g., through high bandwidth LPI links) and a third AP second coverage environment <NUM> (e.g., through SP links (i.e., coverage links)).

Taken together, first AP first coverage environment <NUM>, first AP second coverage environment <NUM>, second AP first coverage environment <NUM>, second AP second coverage environment <NUM>, third AP first coverage environment <NUM>, and third AP second coverage environment <NUM> may provide a Wireless Local Area Network (WLAN) through the plurality of APs. This WLAN may provide wireless network access (e.g., access to the WLAN) for a plurality of client devices as the plurality of client devices move within operating environment <NUM> for example. Ones of the plurality of client devices may comprise, but are not limited to, a smart phone, a personal computer, a tablet device, a mobile device, a telephone, a remote control device, a set-top box, a digital video recorder, an Internet-of-Things (IoT) device, a network computer, a router, an Automated Transfer Vehicle (ATV), a drone, an Unmanned Aerial Vehicle (UAV), or other similar microcomputer-based device. In the example shown in <FIG>, the plurality of client devices may comprise a first client device <NUM> (e.g., a laptop computer), a second client device <NUM> (e.g., a smart phone), a third client device <NUM> (e.g., an ATV), and a fourth client device <NUM> (e.g., a drone).

Controller <NUM> may comprise a Wireless Local Area Network controller (WLC) and may provision and control operating environment <NUM> (e.g., the WLAN). Controller <NUM> may allow the plurality of client devices to join operating environment <NUM>. In some embodiments of the disclosure, controller <NUM> may be implemented by a Digital Network Architecture Center (DNAC) controller (i.e., a Software-Defined Network (SDN) controller) that may configure information for operating environment <NUM> in order to provide multi-link selection based on TPC.

The elements described above of operating environment <NUM> (e.g., controller <NUM>, first AP <NUM>, second AP <NUM>, third AP <NUM>, first client device <NUM>, second client device <NUM>, third client device <NUM>, and fourth client device <NUM>) may be practiced in hardware and/or in software (including firmware, resident software, micro-code, etc.) or in any other circuits or systems. The elements of operating environment <NUM> may be practiced in electrical circuits comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. Furthermore, the elements of operating environment <NUM> may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to, mechanical, optical, fluidic, and quantum technologies. As described in greater detail below with respect to <FIG>, the elements of operating environment <NUM> may be practiced in a computing device <NUM>.

<FIG> is a flow chart setting forth the general stages involved in a method <NUM> consistent with the claimed invention for providing multi-link selection based on Transmit Power Control (TPC). Method <NUM> may be implemented using controller <NUM> as described in more detail above with respect to <FIG>. Ways to implement the stages of method <NUM> will be described in greater detail below.

Consistent with the claimed invention, controller <NUM> may formulate recommended MLD links (e.g., combination of a first link (e.g., <NUM>), a second link (e.g., <NUM>), and a third link (e.g., <NUM>)) based, for example, on an AP supporting both LPI and SP, and specific client device capabilities (e.g., supporting SP or just LPI) and characteristics (e.g., client device being mobile or high bandwidth needs).

One objective of this formulation may be for an AP to provide coverage extension with high-power SP in a macro-cell of a dual <NUM> AP for better handoff and LPI in a micro-cell of the dual-<NUM> AP. Another formulation objective may be to provide SP and LPI in the same omni-cell of the dual <NUM> AP, but one with low bandwidth (e.g., SP) and one with high bandwidth (e.g., LPI) for capacity. Furthermore, yet another formulation objective for a dual-band <NUM>/<NUM> client device may be seamless handover with maximum capacity in which case the desired client device attachment sequence may be to start with a primary link using the high bandwidth LPI <NUM> radio with a backup on the <NUM> radio link and then as it transitions out of the micro-cell, swap to the high-power <NUM> SP macro-cell as primary for wider coverage and keep the backup <NUM> radio. An LPI radio may have a higher bias towards larger channel bandwidth (i.e., constant Power Spectral Density (PSD)), which may be suitable for bandwidth hungry client devices, but may result in more roaming events if the client devices are mobile. On the contrary, an AFC enabled SP radio may not care much regarding the channel bandwidth (i.e., no constant PSD) or have limited bandwidth available, and be useful to provide much larger coverage with limited bandwidth (e.g., <NUM>) suitable for mobile clients. Connecting to the SP radio may mean less roaming events, and thus fewer chances of losing connectivity to the network.

An additional link selection consideration may be to avoid large coverage mismatch (e.g., an AP may use SP, but a client device may only use LPI or the AP uses LPI, but the client device may use SP, both AP and STA under SP or LPI but STA operating 6dB below AP as per spec). The former may be trivial, because it can be steered to a better BSSID with LPI-only, but the second and third may require excluding advertisement of the <NUM> transmit power envelope (TPE) IE (i.e., LPI-only) to the client device.

Steering the client device towards a desired link set, as described above, may be challenging (the client device may ultimately decide), but when a client device initiates association with an MLD AP for (e.g., default) all radios the AP contains, controller <NUM> may formulate the desired MLD combination (e.g., based on the above process). In addition, controller <NUM> may exclude inappropriate BSSIDs and add better BSSIDs into the MLD association response.

Method <NUM> begins starting block <NUM> and proceeds in the claimed invention to stage <NUM> where controller <NUM> receives Multi-Link Device (MLD) association information associated with a client device. The MLD association information may describe MLD links the client device requires. For example, a client device may provide the MLD association information to seek the available links to establish MLD association by providing its requirements. Such an exchange from the client devices to controller <NUM> may be possible during an <NUM> initial association or through Access Network Query Protocol (ANQP).

First client device <NUM> (e.g., a laptop computer), for example, may be less mobile and may be running a high bandwidth application. In this case, first client device <NUM> may provide the MLD association information to seek a first high bandwidth link and a second high bandwidth link. Second client device <NUM> (e.g., a smart phone) may be more mobile than a laptop and may be running a high bandwidth application. In this case, second client device <NUM> may provide the MLD association information to seek a first high bandwidth link and a first coverage link. Third client device <NUM> (e.g., an ATV) and fourth client device <NUM> (e.g., a drone or an UAV) may be more mobile than a laptop or a smart phone and may frequently pass between the coverages of the plurality of APs. In this case, third client device <NUM> and fourth client device <NUM> may provide the MLD association information to seek a first coverage link and a second coverage link.

From stage <NUM>, where controller <NUM> receives the MLD association information associated with the client device, method <NUM> advances in the claimed invention of to stage <NUM> where controller <NUM> determines a set of MLD links available on a multi power-class network (e.g., operating environment <NUM>) based on the MLD association information. For example, in response to receiving the MLD association information, controller <NUM> may formulate the available links to be provided to the client device.

In the above example where first client device <NUM> (e.g., a laptop computer) may provide the MLD association information to seek a first high bandwidth link and a second high bandwidth link, the formulated available links may comprise a first high bandwidth LPI link and a second high bandwidth LPI link, both on the same AP or from different APs. In the above example where second client device <NUM> (e.g., a smart phone) may provide the MLD association information to seek a first high bandwidth link and a first coverage link, the formulated available links may comprise a first high bandwidth LPI link and a first SP link (e.g., high coverage AFC), both on the same AP or from different APs. In the above example where third client device <NUM> (e.g., an ATV) and fourth client device <NUM> (e.g., a drone or a UAV) may provide the MLD association information to seek a first coverage link and a second coverage link, the formulated available links may comprise a first SP link (e.g., high coverage AFC) and a second SP link (e.g., high coverage AFC), both on the same AP or from different APs.

Once controller <NUM> determines the set of MLD links available on the multi power-class network based on the MLD association information in stage <NUM>, method <NUM> continues in the claimed invention to stage <NUM> where controller <NUM> sends the determined set of MLD links to the client device. For example, the formulated links described above for the different example client devices may be sent to the different example client devices. Each of the links exchanged with a client device may include AP radio type information associated with the set of MLD links, for example: i) AFC enable SP with channel bandwidth; ii) LPI radio with channel bandwidth; and iii) regular <NUM>/<NUM> link.

After controller <NUM> sends the determined set of MLD links to the client device in stage <NUM>, method <NUM> may proceed to stage <NUM> where the client device may determine to use the determined set of MLD links. For example, the client device may determine the MLD links to choose using the recommendation that was formulated and provided by controller <NUM> using a mix of LPI and SP powered radios or LPI/SP on both radios depending on its characteristics (e.g., mobile or high bandwidth needs). Once the client device determines to use the determined set of MLD links in stage <NUM>, method <NUM> may then end at stage <NUM>.

<FIG> shows a computing device <NUM>. As shown in <FIG>, computing device <NUM> may include a processing unit <NUM> and a memory unit <NUM>. Memory unit <NUM> may include a software module <NUM> and a database <NUM>. While executing on processing unit <NUM>, software module <NUM> may perform, for example, processes for providing multi-link selection based on Transmit Power Control (TPC) as described above with respect to <FIG>. Computing device <NUM>, for example, may provide an operating environment for controller <NUM>, first AP <NUM>, second AP <NUM>, third AP <NUM>, first client device <NUM>, second client device <NUM>, third client device <NUM>, and fourth client device <NUM>. Controller <NUM>, first AP <NUM>, second AP <NUM>, third AP <NUM>, first client device <NUM>, second client device <NUM>, third client device <NUM>, and fourth client device <NUM> may operate in other environments and are not limited to computing device <NUM>.

Computing device <NUM> may be implemented using a Wi-Fi access point, a tablet device, a mobile device, a smart phone, a telephone, a remote control device, a set-top box, a digital video recorder, a cable modem, a personal computer, a network computer, a mainframe, a router, a switch, a server cluster, a smart TV-like device, a network storage device, a network relay devices, or other similar microcomputer-based device. Computing device <NUM> may comprise any computer operating environment, such as hand-held devices, multiprocessor systems, microprocessor-based or programmable sender electronic devices, minicomputers, mainframe computers, and the like. Computing device <NUM> may also be practiced in distributed computing environments where tasks are performed by remote processing devices. The aforementioned systems and devices are examples and computing device <NUM> may comprise other systems or devices.

Embodiments of the disclosure, for example, may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process. Accordingly, the present disclosure may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). In other words, embodiments of the present disclosure may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. A computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

Embodiments of the disclosure may be practiced via a system-on-a-chip (SOC) where each or many of the element illustrated in <FIG> may be integrated onto a single integrated circuit. Such an SOC device may include one or more processing units, graphics units, communications units, system virtualization units and various application functionality all of which may be integrated (or "burned") onto the chip substrate as a single integrated circuit. When operating via an SOC, the functionality described herein with respect to embodiments of the disclosure, may be performed via application-specific logic integrated with other components of computing device <NUM> on the single integrated circuit (chip).

Claim 1:
A method comprising:
receiving (<NUM>), by a computing device (<NUM>), Multi-Link Device MLD, association information associated with a client device wherein the MLD association information describes MLD links the client device requires;
determining (<NUM>) a set of MLD links available on a network based on the MLD association information, wherein determining the set of MLD links available on the network based on the MLD association information comprises determining a first MLD link and a second MLD link from a plurality of multi-power class links; and
sending (<NUM>) the determined set of MLD links to the client device (<NUM>).