Patent Application
20250113297
This disclosure relates generally to wireless communication, and more specifically, to techniques for power savings mechanisms in wireless networks.
A wireless local area network (WLAN) may be formed by one or more wireless access points (APs) that provide a shared wireless communication medium for use by multiple client devices also referred to as wireless stations (STAs). The basic building block of a WLAN conforming to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards is a Basic Service Set (BSS), which is managed by an AP. Each BSS is identified by a Basic Service Set Identifier (BSSID) that is advertised by the AP. An AP periodically broadcasts beacon frames to enable any STAs within wireless range of the AP to establish or maintain a communication link with the WLAN.
The systems, methods and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.
One innovative aspect of the subject matter described in this disclosure may be implemented as a method for wireless communications at a first wireless node. The method includes obtaining information regarding a topology of a mesh network; and performing, based on the information, one or more actions to adjust power consumption at one or more wireless nodes of the mesh network.
Another innovative aspect of the subject matter described in this disclosure may be implemented at an apparatus for wireless communications. The apparatus includes at least one processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: obtain information regarding a topology of a mesh network; and perform, based on the information, one or more actions to adjust power consumption at one or more wireless nodes of the mesh network.
In some examples, the one or more actions comprise steering one or more clients away from a first wireless node of the mesh network to a second wireless node of the mesh network.
Other aspects provide: an apparatus operable, configured, or otherwise adapted to perform any one or more of the aforementioned methods and/or those described elsewhere herein; a non-transitory, computer-readable media comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform the aforementioned methods as well as those described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the aforementioned methods as well as those described elsewhere herein; and/or an apparatus comprising means for performing the aforementioned methods as well as those described elsewhere herein. By way of example, an apparatus may comprise a processing system, a device with a processing system, or processing systems cooperating over one or more networks.
Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.
Like reference numbers and designations in the various drawings indicate like elements.
The following description is directed to some particular examples for the purposes of describing innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. Some or all of the described examples may be implemented in any device, system or network that is capable of transmitting and receiving radio frequency (RF) signals according to one or more of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards, the IEEE 802.15 standards, the Bluetooth® standards as defined by the Bluetooth Special Interest Group (SIG), or the Long Term Evolution (LTE), 3G, 4G or 5G (New Radio (NR)) standards promulgated by the 3rd Generation Partnership Project (3GPP), among others. The described examples can be implemented in any device, system or network that is capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), spatial division multiple access (SDMA), rate-splitting multiple access (RSMA), multi-user shared access (MUSA), single-user (SU) multiple-input multiple-output (MIMO) and multi-user (MU)-MIMO. The described examples also can be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless personal area network (WPAN), a wireless local area network (WLAN), a wireless wide area network (WWAN), a wireless metropolitan area network (WMAN), or an internet of things (IoT) network.
Various aspects relate generally to wireless communication. Some aspects more specifically relate to power savings mechanisms in wireless networks. In some cases, the power savings mechanisms proposed herein may be used to activate/de-activate links between wireless nodes in wireless networks. As used herein, “wireless node” generally refers to any type of device capable of communicating wirelessly, such as an access point (AP), a wireless station (STA) serving as an AP (an AP-STA), a STA that is not serving as an AP (a non-AP STA), or a user equipment (UE).
Advances in wireless technology often come with some form of cost. For example, features added in each new Wi-Fi generation tend to add a greater energy toll on the access point (AP). For example, WiFi-6e (an enhanced version of 802.11ax) added an additional link (6 GHz), WiFi-7 (802.11 be) added multiple concurrent links to support multilink operation (MLO), and WiFi-8 plans to add even higher bandwidth (e.g., 640 MHz or more).
This additional power, in terms of operating watts, increases cost both to build the product and operate the product. For example, potentially expensive heat sinks and power-adapters used to accommodate the increased power may end up dominating the bill of material (BOM) cost, resulting in increased product cost and/or reduced profit margins.
The higher energy cost may be felt by the end user, which may impact purchasing decisions. As illustrated in the example 500 of
One approach to energy management is de-centralized, with individual nodes (e.g., APs serving as repeaters) performing actions to reduce power consumption. For example, each individual AP may calculate metrics per-link and perform actions to reduce power consumption based on the metrics. As an example, based on metrics indicative of link loading, an AP could activate/de-activate certain links or ports and/or adjust parameters such as operating bandwidth (BW) and modulation and coding schemes (MCS).
In some cases, applying energy management in individual nodes may be less than optimal for a mesh network. For example, mesh networks in a home environment may involve coordination between nodes. As such, mesh networks may benefit from topology awareness to make effective energy management/saving decisions that consider the mesh network as a whole (e.g., to achieve optimal whole home coverage).
Aspects of the present disclosure, however, provide a centralized energy management that may consider a topology of a mesh network when making power savings decisions. Such a centralized energy management approach may utilize power savings mechanisms that may help mitigate the increase in power consumption associated with advanced network features.
According to certain aspects, a first wireless node (e.g., an AP serving as a root node or a controller entity) may obtain information regarding a topology of a mesh network that includes a number of repeaters (APs). The information may include, for example, capability/status of repeaters, information regarding clients connected to the repeaters, position/location of the repeaters, and/or position/location of the clients. Based on the information, the first wireless node may perform one or more actions to adjust power consumption at one or more wireless nodes of the mesh network.
As a result, aspects of the present disclosure may help reduce overall power consumption in a network. The power savings mechanisms proposed herein may help reduce energy costs associated with operating the network. The power savings mechanisms proposed herein may also allow help avoid costly parts (e.g., expensive heat sinks and power-adapters), which may help reduce the build cost.
Each of the STAs 104 also may be referred to as a mobile station (MS), a mobile device, a mobile handset, a wireless handset, an access terminal (AT), a user equipment (UE), a subscriber station (SS), or a subscriber unit, among other examples. The STAs 104 may represent various devices such as mobile phones, personal digital assistant (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, chromebooks, extended reality (XR) headsets, wearable devices, display devices (for example, TVs (including smart TVs), computer monitors, navigation systems, among others), music or other audio or stereo devices, remote control devices (“remotes”), printers, kitchen appliances (including smart refrigerators) or other household appliances, key fobs (for example, for passive keyless entry and start (PKES) systems), Internet of Things (IoT) devices, and vehicles, among other examples. The various STAs 104 in the network are able to communicate with one another via the AP 102.
A single AP 102 and an associated set of STAs 104 may be referred to as a basic service set (BSS), which is managed by the respective AP 102.
To establish a communication link 106 with an AP 102, each of the STAs 104 is configured to perform passive or active scanning operations (“scans”) on frequency channels in one or more frequency bands (for example, the 2.4 GHz, 5 GHz, 6 GHz or 60 GHz bands). To perform passive scanning, a STA 104 listens for beacons, which are transmitted by respective APs 102 at a periodic time interval referred to as the target beacon transmission time (TBTT) (measured in time units (TUs) where one TU may be equal to 1024 microseconds (μs)). To perform active scanning, a STA 104 generates and sequentially transmits probe requests on each channel to be scanned and listens for probe responses from APs 102. Each STA 104 may identify, determine, ascertain, or select an AP 102 with which to associate in accordance with the scanning information obtained through the passive or active scans, and to perform authentication and association operations to establish a communication link 106 with the selected AP 102. The AP 102 assigns an association identifier (AID) to the STA 104 at the culmination of the association operations, which the AP 102 uses to track the STA 104.
As a result of the increasing ubiquity of wireless networks, a STA 104 may have the opportunity to select one of many BSSs within range of the STA or to select among multiple APs 102 that together form an extended service set (ESS) including multiple connected BSSs. An extended network station associated with the WLAN 100 may be connected to a wired or wireless distribution system that may allow multiple APs 102 to be connected in such an ESS. As such, a STA 104 can be covered by more than one AP 102 and can associate with different APs 102 at different times for different transmissions. Additionally, after association with an AP 102, a STA 104 also may periodically scan its surroundings to find a more suitable AP 102 with which to associate. For example, a STA 104 that is moving relative to its associated AP 102 may perform a “roaming” scan to find another AP 102 having more desirable network characteristics such as a greater received signal strength indicator (RSSI) or a reduced traffic load.
In some cases, STAs 104 may form networks without APs 102 or other equipment other than the STAs 104 themselves. One example of such a network is an ad hoc network (or wireless ad hoc network). Ad hoc networks may alternatively be referred to as mesh networks or peer-to-peer (P2P) networks. In some cases, ad hoc networks may be implemented within a larger wireless network such as the WLAN 100. In such examples, while the STAs 104 may be capable of communicating with each other through the AP 102 using communication links 106, STAs 104 also can communicate directly with each other via direct wireless communication links 110. Additionally, two STAs 104 may communicate via a direct communication link 110 regardless of whether both STAs 104 are associated with and served by the same AP 102. In such an ad hoc system, one or more of the STAs 104 may assume the role filled by the AP 102 in a BSS. Such a STA 104 may be referred to as a group owner (GO) and may coordinate transmissions within the ad hoc network. Examples of direct wireless communication links 110 include Wi-Fi Direct connections, connections established by using a Wi-Fi Tunneled Direct Link Setup (TDLS) link, and other P2P group connections.
The APs 102 and STAs 104 may function and communicate (via the respective communication links 106) according to one or more of the IEEE 802.11 family of wireless communication protocol standards. These standards define the WLAN radio and baseband protocols for the PHY and MAC layers. The APs 102 and STAs 104 transmit and receive wireless communications (hereinafter also referred to as “Wi-Fi communications” or “wireless packets”) to and from one another in the form of PHY protocol data units (PPDUs). The APs 102 and STAs 104 in the WLAN 100 may transmit PPDUs over an unlicensed spectrum, which may be a portion of spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the 2.4 GHz band, the 5 GHz band, the 60 GHz band, the 3.6 GHz band, and the 900 MHz band. Some examples of the APs 102 and STAs 104 described herein also may communicate in other frequency bands, such as the 5.9 GHz and the 6 GHz bands, which may support both licensed and unlicensed communications. The APs 102 and STAs 104 also can communicate over other frequency bands such as shared licensed frequency bands, where multiple operators may have a license to operate in the same or overlapping frequency band or bands.
Each of the frequency bands may include multiple sub-bands or frequency channels. For example, PPDUs conforming to the IEEE 802.11n, 802.11ac, 802.11ax and 802.11be standard amendments may be transmitted over the 2.4 GHz, 5 GHz or 6 GHz bands, each of which is divided into multiple 20 MHz channels. As such, these PPDUs are transmitted over a physical channel having a minimum bandwidth of 20 MHz, but larger channels can be formed through channel bonding. For example, PPDUs may be transmitted over physical channels having bandwidths of 40 MHz, 80 MHz, 160 or 320 MHz by bonding together multiple 20 MHz channels.
Each PPDU is a composite structure that includes a PHY preamble and a payload in the form of a PHY service data unit (PSDU). The information provided in the preamble may be used by a receiving device to decode the subsequent data in the PSDU. In instances in which PPDUs are transmitted over a bonded channel, the preamble fields may be duplicated and transmitted in each of the multiple component channels. The PHY preamble may include both a legacy portion (or “legacy preamble”) and a non-legacy portion (or “non-legacy preamble”). The legacy preamble may be used for packet detection, automatic gain control and channel estimation, among other uses. The legacy preamble also may generally be used to maintain compatibility with legacy devices. The format of, coding of, and information provided in the non-legacy portion of the preamble is associated with the particular IEEE 802.11 protocol to be used to transmit the payload
The L-STF 206 generally enables a receiving device to perform coarse timing and frequency tracking and automatic gain control (AGC). The L-LTF 208 generally enables a receiving device to perform fine timing and frequency tracking and also to perform an initial estimate of the wireless channel. The L-SIG 210 generally enables a receiving device to determine (for example, obtain, select, identify, detect, ascertain, calculate, or compute) a duration of the PDU and to use the determined duration to avoid transmitting on top of the PDU. The legacy portion of the preamble, including the L-STF 206, the L-LTF 208 and the L-SIG 210, may be modulated according to a binary phase shift keying (BPSK) modulation scheme. The payload 204 may be modulated according to a BPSK modulation scheme, a quadrature BPSK (Q-BPSK) modulation scheme, a quadrature amplitude modulation (QAM) modulation scheme, or another appropriate modulation scheme. The payload 204 may include a PSDU including a data field (DATA) 214 that, in turn, may carry higher layer data, for example, in the form of MAC protocol data units (MPDUs) or an aggregated MPDU (A-MPDU).
Referring back to the MPDU frame 310, the MAC delimiter 312 may serve as a marker of the start of the associated MPDU 316 and indicate the length of the associated MPDU 316. The MAC header 314 may include multiple fields containing information that defines or indicates characteristics or attributes of data encapsulated within the frame body 316. The MAC header 314 includes a duration field indicating a duration extending from the end of the PPDU until at least the end of an acknowledgment (ACK) or Block ACK (BA) of the PPDU that is to be transmitted by the receiving wireless communication device. The use of the duration field serves to reserve the wireless medium for the indicated duration, and enables the receiving device to establish its network allocation vector (NAV). The MAC header 314 also includes one or more fields indicating addresses for the data encapsulated within the frame body 316. For example, the MAC header 314 may include a combination of a source address, a transmitter address, a receiver address or a destination address. The MAC header 314 may further include a frame control field containing control information. The frame control field may specify a frame type, for example, a data frame, a control frame, or a management frame.
Some APs and STAs may implement techniques for spatial reuse that involve participation in a coordinated communication scheme. According to such techniques, an AP may contend for access to a wireless medium to obtain control of the medium for a TXOP. The AP that wins the contention (hereinafter also referred to as a “sharing AP”) may select one or more other APs (hereinafter also referred to as “shared APs”) to share resources of the TXOP. The sharing and shared APs may be located in proximity to one another such that at least some of their wireless coverage areas at least partially overlap. Some examples may specifically involve coordinated AP TDMA or OFDMA techniques for sharing the time or frequency resources of a TXOP. To share its time or frequency resources, the sharing AP may partition the TXOP into multiple time segments or frequency segments each including respective time or frequency resources representing a portion of the TXOP, The sharing AP may allocate the time or frequency segments to itself or to one or more of the shared APs. For example, each shared AP may utilize a partial TXOP assigned by the sharing AP for its uplink or downlink communications with its associated STAs.
In some examples of such TDMA techniques, each portion of a plurality of portions of the TXOP includes a set of time resources that do not overlap with any time resources of any other portion of the plurality of portions. In such examples, the scheduling information may include an indication of time resources, of multiple time resources of the TXOP, associated with each portion of the TXOP. For example, the scheduling information may include an indication of a time segment of the TXOP such as an indication of one or more slots or sets of symbol periods associated with each portion of the TXOP such as for multi-user TDMA.
In some other examples of OFDMA techniques, each portion of the plurality of portions of the TXOP includes a set of frequency resources that do not overlap with any frequency resources of any other portion of the plurality of portions. In such implementations, the scheduling information may include an indication of frequency resources, of multiple frequency resources of the TXOP, associated with each portion of the TXOP. For example, the scheduling information may include an indication of a bandwidth portion of the wireless channel such as an indication of one or more subchannels or resource units (RUs) associated with each portion of the TXOP such as for multi-user OFDMA.
In this manner, the sharing AP's acquisition of the TXOP enables communication between one or more additional shared APs and their respective BSSs, subject to appropriate power control and link adaptation. For example, the sharing AP may limit the transmit powers of the selected shared APs such that interference from the selected APs does not prevent STAs associated with the TXOP owner from successfully decoding packets transmitted by the sharing AP. Such techniques may be used to reduce latency because the other APs may not need to wait to win contention for a TXOP to be able to transmit and receive data according to conventional CSMA/CA or EDCA techniques. Additionally, by enabling a group of APs associated with different BSSs to participate in a coordinated AP transmission session, during which the group of APs may share at least a portion of a single TXOP obtained by any one of the participating APs, such techniques may increase throughput across the BSSs associated with the participating APs and may also achieve improvements in throughput fairness. Furthermore, with appropriate selection of the shared APs and the scheduling of their respective time or frequency resources, medium utilization may be maximized or otherwise increased while packet loss resulting from OBSS interference is minimized or otherwise reduced. Various implementations may achieve these and other advantages without requiring that the sharing AP or the shared APs be aware of the STAs associated with other BSSs, without requiring a preassigned or dedicated master AP or preassigned groups of APs, and without requiring backhaul coordination between the APs participating in the TXOP.
In some examples in which the signal strengths or levels of interference associated with the selected APs are relatively low (such as less than a given value), or when the decoding error rates of the selected APs are relatively low (such as less than a threshold), the start times of the communications among the different BSSs may be synchronous. Conversely, when the signal strengths or levels of interference associated with the selected APs are relatively high (such as greater than the given value), or when the decoding error rates of the selected APs are relatively high (such as greater than the threshold), the start times may be offset from one another by a time period associated with decoding the preamble of a wireless packet and determining, from the decoded preamble, whether the wireless packet is an intra-BSS packet or is an OBSS packet. For example, the time period between the transmission of an intra-BSS packet and the transmission of an OBSS packet may allow a respective AP (or its associated STAs) to decode the preamble of the wireless packet and obtain the BSS color value carried in the wireless packet to determine whether the wireless packet is an intra-BSS packet or an OBSS packet. In this manner, each of the participating APs and their associated STAs may be able to receive and decode intra-BSS packets in the presence of OBSS interference.
In some examples, the sharing AP may perform polling of a set of un-managed or non-co-managed APs that support coordinated reuse to identify candidates for future spatial reuse opportunities. For example, the sharing AP may transmit one or more spatial reuse poll frames as part of determining one or more spatial reuse criteria and selecting one or more other APs to be shared APs. According to the polling, the sharing AP may receive responses from one or more of the polled APs. In some specific examples, the sharing AP may transmit a coordinated AP TXOP indication (CTI) frame to other APs that indicates time and frequency of resources of the TXOP that can be shared. The sharing AP may select one or more candidate APs upon receiving a coordinated AP TXOP request (CTR) frame from a respective candidate AP that indicates a desire by the respective AP to participate in the TXOP. The poll responses or CTR frames may include a power indication, for example, an RX power or RSSI measured by the respective AP. In some other examples, the sharing AP may directly measure potential interference of a service supported (such as UL transmission) at one or more APs, and select the shared APs based on the measured potential interference. The sharing AP generally selects the APs to participate in coordinated spatial reuse such that it still protects its own transmissions (which may be referred to as primary transmissions) to and from the STAs in its BSS. The selected APs may then be allocated resources during the TXOP as described above.
Retransmission protocols, such as hybrid automatic repeat request (HARQ), also may offer performance gains. A HARQ protocol may support various HARQ signaling between transmitting and receiving wireless communication devices as well as signaling between the PHY and MAC layers to improve the retransmission operations in a WLAN. HARQ uses a combination of error detection and error correction. For example, a HARQ transmission may include error checking bits that are added to data to be transmitted using an error-detecting (ED) code, such as a cyclic redundancy check (CRC). The error checking bits may be used by the receiving device to determine if it has properly decoded the received HARQ transmission. In some examples, the original data (information bits) to be transmitted may be encoded with a forward error correction (FEC) code, such as using a low-density parity check (LDPC) coding scheme that systematically encodes the information bits to produce parity bits. The transmitting device may transmit both the original information bits as well as the parity bits in the HARQ transmission to the receiving device. The receiving device may be able to use the parity bits to correct errors in the information bits, thus avoiding a retransmission.
Implementing a HARQ protocol in a WLAN may improve reliability of data communicated from a transmitting device to a receiving device. The HARQ protocol may support the establishment of a HARQ session between the two devices. Once a HARQ session is established, If a receiving device cannot properly decode (and cannot correct the errors) a first HARQ transmission received from the transmitting device, the receiving device may transmit a HARQ feedback message to the transmitting device (for example, a negative acknowledgement (NACK)) that indicates at least part of the first HARQ transmission was not properly decoded. Such a HARQ feedback message may be different than the traditional Block ACK feedback message type associated with conventional ARQ. In response to receiving the HARQ feedback message, the transmitting device may transmit a second HARQ transmission to the receiving device to communicate at least part of further assist the receiving device in decoding the first HARQ transmission. For example, the transmitting device may include some or all of the original information bits, some or all of the original parity bits, as well as other, different parity bits in the second HARQ transmission. The combined HARQ transmissions may be processed for decoding and error correction such that the complete signal associated with the HARQ transmissions can be obtained.
In some examples, the receiving device may be enabled to control whether to continue the HARQ process or revert to a non-HARQ retransmission scheme (such as an ARQ protocol). Such switching may reduce feedback overhead and increase the flexibility for retransmissions by allowing devices to dynamically switch between ARQ and HARQ protocols during frame exchanges. Some implementations also may allow multiplexing of communications that employ ARQ with those that employ HARQ.
Some wireless communication devices (including both APs and STAs) are capable of multi-link operation (MLO). In some examples, MLO supports establishing multiple different communication links (such as a first link on the 2.4 GHz band, a second link on the 5 GHz band, and the third link on the 6 GHz band) between the STA and the AP. Each communication link may support one or more sets of channels or logical entities. In some cases, each communication link associated with a given wireless communication device may be associated with a respective radio of the wireless communication device, which may include one or more transmit/receive (Tx/Rx) chains, include or be coupled with one or more physical antennas, or include signal processing components, among other components. An MLO-capable device may be referred to as a multi-link device (MLD). For example, an AP MLD may include multiple APs each configured to communicate on a respective communication link with a respective one of multiple STAs of a non-AP MLD (also referred to as a “STA MLD”). The STA MLD may communicate with the AP MLD over one or more of the multiple communication links at a given time.
One type of MLO is multi-link aggregation (MLA), where traffic associated with a single STA is simultaneously transmitted across multiple communication links in parallel to maximize the utilization of available resources to achieve higher throughput. That is, during at least some duration of time, transmissions or portions of transmissions may occur over two or more links in parallel at the same time. In some examples, the parallel wireless communication links may support synchronized transmissions. In some other examples, or during some other durations of time, transmissions over the links may be parallel, but not be synchronized or concurrent. In some examples or durations of time, two or more of the links may be used for communications between the wireless communication devices in the same direction (such as all uplink or all downlink). In some other examples or durations of time, two or more of the links may be used for communications in different directions. For example, one or more links may support uplink communications and one or more links may support downlink communications. In such examples, at least one of the wireless communication devices operates in a full duplex mode. Generally, full duplex operation enables bi-directional communications where at least one of the wireless communication devices may transmit and receive at the same time.
MLA may be implemented in a number of ways. In some examples, MLA may be packet-based. For packet-based aggregation, frames of a single traffic flow (such as all traffic associated with a given traffic identifier (TID)) may be sent concurrently across multiple communication links. In some other examples, MLA may be flow-based. For flow-based aggregation, each traffic flow (such as all traffic associated with a given TID) may be sent using a single one of multiple available communication links. As an example, a single STA MLD may access a web browser while streaming a video in parallel. The traffic associated with the web browser access may be communicated over a first communication link while the traffic associated with the video stream may be communicated over a second communication link in parallel (such that at least some of the data may be transmitted on the first channel concurrently with data transmitted on the second channel).
In some other examples, MLA may be implemented as a hybrid of flow-based and packet-based aggregation. For example, an MLD may employ flow-based aggregation in situations in which multiple traffic flows are created and may employ packet-based aggregation in other situations. The determination to switch among the MLA techniques or modes may additionally or alternatively be associated with other metrics (such as a time of day, traffic load within the network, or battery power for a wireless communication device, among other factors or considerations).
To support MLO techniques, an AP MLD and a STA MLD may exchange supported MLO capability information (such as supported aggregation type or supported frequency bands, among other information). In some examples, the exchange of information may occur via a beacon signal, a probe request or probe response, an association request or an association response frame, a dedicated action frame, or an operating mode indicator (OMI), among other examples. In some examples, an AP MLD may designate a given channel in a given band as an anchor channel (such as the channel on which it transmits beacons and other management frames). In such examples, the AP MLD also may transmit beacons (such as ones which may contain less information) on other channels for discovery purposes.
MLO techniques may provide multiple benefits to a WLAN. For example, MLO may improve user perceived throughput (UPT) (such as by quickly flushing per-user transmit queues). Similarly, MLO may improve throughput by improving utilization of available channels and may increase spectral utilization (such as increasing the bandwidth-time product). Further, MLO may enable smooth transitions between multi-band radios (such as where each radio may be associated with a given RF band) or enable a framework to set up separation of control channels and data channels. Other benefits of MLO include reducing the ON time of a modem, which may benefit a wireless communication device in terms of power consumption. Another benefit of MLO is the increased multiplexing opportunities in the case of a single BSS. For example, multi-link aggregation may increase the number of users per multiplexed transmission served by the multi-link AP MLD.
In some examples, the wireless communication devices 414 sense, measure, collect or otherwise obtain and process data and then transmit such raw or processed data to an intermediate device 412 for subsequent processing or distribution. Additionally or alternatively, the intermediate device 412 may transmit control information, digital content (for example, audio or video data), configuration information or other instructions to the wireless communication devices 414. The intermediate device 412 and the wireless communication devices 414 can communicate with one another via wireless communication links 416. In some examples, the wireless communication links 416 include Bluetooth links or other PAN or short-range communication links.
In some examples, the intermediate device 412 also may be configured for wireless communication with other networks such as with a Wi-Fi WLAN or a wireless (for example, cellular) wide area network (WWAN), which may, in turn, provide access to external networks including the Internet. For example, the intermediate device 412 may associate and communicate, over a Wi-Fi link 418, with an AP 402 of a WLAN network, which also may serve various STAs 404. In some examples, the intermediate device 412 is an example of a network gateway, for example, an IoT gateway. In such a manner, the intermediate device 412 may serve as an edge network bridge providing a Wi-Fi core backhaul for the IoT network including the wireless communication devices 414. In some examples, the intermediate device 412 can analyze, preprocess and aggregate data received from the wireless communication devices 414 locally at the edge before transmitting it to other devices or external networks via the Wi-Fi link 418. The intermediate device 412 also can provide additional security for the IoT network and the data it transports.
Some wireless communication devices (including both APs and STAs) are capable of multi-link operation (MLO). In some examples, MLO supports establishing multiple different communication links (such as a first link on the 2.4 GHz band, a second link on the 5 GHz band, and the third link on the 6 GHz band) between the STA and the AP. Each communication link may support one or more sets of channels or logical entities. In some cases, each communication link associated with a given wireless communication device may be associated with a respective radio of the wireless communication device, which may include one or more transmit/receive (Tx/Rx) chains, include or be coupled with one or more physical antennas, or include signal processing components, among other components. An MLO-capable device may be referred to as a multi-link device (MLD). For example, an AP MLD may include multiple APs each configured to communicate on a respective communication link with a respective one of multiple STAs of a non-AP MLD (also referred to as a “STA MLD”). The STA MLD may communicate with the AP MLD over one or more of the multiple communication links at a given time.
One type of MLO is multi-link aggregation (MLA), where traffic associated with a single STA is simultaneously transmitted across multiple communication links in parallel to maximize the utilization of available resources to achieve higher throughput. That is, during at least some duration of time, transmissions or portions of transmissions may occur over two or more links in parallel at the same time. In some examples, the parallel wireless communication links may support synchronized transmissions. In some other examples, or during some other durations of time, transmissions over the links may be parallel, but not be synchronized or concurrent. In some examples or durations of time, two or more of the links may be used for communications between the wireless communication devices in the same direction (such as all uplink or all downlink). In some other examples or durations of time, two or more of the links may be used for communications in different directions. For example, one or more links may support uplink communications and one or more links may support downlink communications. In such examples, at least one of the wireless communication devices operates in a full duplex mode. Generally, full duplex operation enables bi-directional communications where at least one of the wireless communication devices may transmit and receive at the same time.
MLA may be implemented in a number of ways. In some examples, MLA may be packet-based. For packet-based aggregation, frames of a single traffic flow (such as all traffic associated with a given traffic identifier (TID)) may be sent concurrently across multiple communication links. In some other examples, MLA may be flow-based. For flow-based aggregation, each traffic flow (such as all traffic associated with a given TID) may be sent using a single one of multiple available communication links. As an example, a single STA MLD may access a web browser while streaming a video in parallel. The traffic associated with the web browser access may be communicated over a first communication link while the traffic associated with the video stream may be communicated over a second communication link in parallel (such that at least some of the data may be transmitted on the first channel concurrently with data transmitted on the second channel).
In some other examples, MLA may be implemented as a hybrid of flow-based and packet-based aggregation. For example, an MLD may employ flow-based aggregation in situations in which multiple traffic flows are created and may employ packet-based aggregation in other situations. The determination to switch among the MLA techniques or modes may additionally or alternatively be associated with other metrics (such as a time of day, traffic load within the network, or battery power for a wireless communication device, among other factors or considerations).
To support MLO techniques, an AP MLD and a STA MLD may exchange supported MLO capability information (such as supported aggregation type or supported frequency bands, among other information). In some examples, the exchange of information may occur via a beacon signal, a probe request or probe response, an association request or an association response frame, a dedicated action frame, or an operating mode indicator (OMI), among other examples. In some examples, an AP MLD may designate a given channel in a given band as an anchor channel (such as the channel on which it transmits beacons and other management frames). In such examples, the AP MLD also may transmit beacons (such as ones which may contain less information) on other channels for discovery purposes.
MLO techniques may provide multiple benefits to a WLAN. For example, MLO may improve user perceived throughput (UPT) (such as by quickly flushing per-user transmit queues). Similarly, MLO may improve throughput by improving utilization of available channels and may increase spectral utilization (such as increasing the bandwidth-time product). Further, MLO may enable smooth transitions between multi-band radios (such as where each radio may be associated with a given RF band) or enable a framework to set up separation of control channels and data channels. Other benefits of MLO include reducing the ON time of a modem, which may benefit a wireless communication device in terms of power consumption. Another benefit of MLO is the increased multiplexing opportunities in the case of a single BSS. For example, multi-link aggregation may increase the number of users per multiplexed transmission served by the multi-link AP MLD.
Advances in wireless technology often come with some form of cost. Aspects of the present disclosure, however, provide power savings mechanisms that may help mitigate the increase in power consumption associated with advanced network features.
Various networks may have certain energy consumption guidelines for APs. For example, referring to mesh network 600 of
As noted above, applying energy management in individual nodes may be less than optimal for a mesh network. For example, mesh networks in a home environment may involve coordination between nodes. As such, mesh networks may benefit from topology awareness to make effective energy management decisions that consider holistic knowledge about the mesh network topology and capabilities.
Aspects of the present disclosure, however, provide a centralized energy management that may consider a topology of a mesh network when making power savings decisions. Such a centralized energy management approach may utilize power savings mechanisms that may help mitigate the increase in power consumption associated with advanced network features.
In some cases, the power savings mechanisms proposed herein may be implemented as part of an overall AP architecture, such as the architecture 700 shown in
The energy service generally strives to achieve the access point's power-save goals aligning with the SA-framework's SLA-goals. Such an energy service may be achieved via various algorithms described herein. In some cases, at a driver level 720, the power saving may involve various power saving mechanisms in a WLAN driver, Ethernet driver, or other driver platform. The WLAN driver power saving mechanisms may include band coalescing 722, which generally refers to inactivating one link, effectively merging that link with one or more other links. Such coalescing may be achieved using mechanisms such as TID to link mapping (T2LM), BSS transmission management (BTM), and/or link utilization (LU) mechanisms. Additional power savings mechanisms 724 may include RF chain reduction and bandwidth reduction. In some cases, a driver (e.g., 802.3az) may be used for certain signaling and control. At the firmware level 730, power saving may be achieved via various PS mechanisms 732, such as chain reduction, rate control, and dynamic bandwidth reduction.
As illustrated in the example mesh network 800 of
As shown at 802, AP-level energy management may be performed at an individual repeater 514, and may include link/port management, adjusting processing (e.g., CPU core/clock gating), and/or adjusting parameters, such as operating BW, MCS, and the like. In some cases, AP-level energy management may be performed in addition to, or as an alternative to, centralized energy management if one or more conditions are met.
As shown at 804, centralized energy management may be performed at a root AP 512 (or controller entity) in a manner that considers a topology of the mesh network 800. For example, AP 512 may perform topology-aware energy management by steering clients 518 to certain APs, transitioning certain APs to low power states, and/or reducing the amount of control messages exchanged between APs via a backhaul 516. The exchange of such control messages may be referred to as chatter, and reducing the amount of chatter may be referred to as chatter control.
As noted above, energy aware repeater transition may be achieved by steering one or more clients away from a specific mesh node to provide an opportunity for that node to enter a power savings or standby mode (such modes may be defined, for example, by placing one or more components in a low power state, deactivating links, or performing some other action, as will be described in greater detail below). In some cases, clients may be steered from nodes that are farther away (e.g., end nodes) to nodes that are closer to the Root (in terms of hops), which gives an opportunity for the end nodes to exercise energy saving policies.
Examples of energy aware repeater transition and AP/client steering may be understood with reference to example scenarios 900 and 1000 depicted in
Referring first to
In some cases, the root node (or controller entity) may select the particular clients and APs for steering based on one or more suitability criteria (based on topology information).
For example, in the example shown in
In some cases, distance from the root node may be considered when performing AP/client steering.
For example, in the example shown in
Another example of topology aware decision making for energy management may involve topology aware backhaul management. As an example, if a mesh is a daisy chain topology of multiple hops, as in the Example of
For example, in the scenario 1100 illustrated in
On the other hand, in the scenario 1200 illustrated in
According to certain aspects, a controller (e.g., root node or other centralized controller entity) may be configured to select various operating parameters to optimize energy savings opportunities. For example, the controller may attempt to select a best channel, bandwidth, and/or number of spatial streams (NSS) for specific nodes in an effort to facilitate energy saving opportunities in the mesh network. For example, the controller may increase BW or NSS on a specific repeater, so that a repeater can serve additional nearby clients, to allow another repeater to transition to standby.
Another example of topology aware decision making for energy management may involve adaptive power control. As an example, if multiple mesh nodes are in close proximity, a controller may reduce a maximum transmission (TX) power on certain nodes to conserve energy, without impacting a desired coverage area (e.g., a whole home coverage).
In the scenario 1300A illustrated in
As noted above, another example of topology aware decision making involves (smart) chatter control, based on topology information. For example, in the scenario 1400 illustrated in
In some cases, a controller may determine a frequency of Request-Response of periodic control messages (chatter) for mesh node communication in order to reduce chatter based on a topology aware power save policy. The controller may control a Request timer in which repeaters respond to controller requests. Example of control messages that may be considered chatter include, but are not limited to: topology request/response messages, link statistics request/response messages, client statistics request/response messages, and other types of request/response messages. In some cases, mesh topology aware energy management may be implemented using various types of communication and messaging. For example, mesh topology aware energy management may be implemented using multi-AP protocol messages (e.g., according to IEEE 1905.1) including Type-length-values (TLVs).
In some cases, topology aware decision making may consider location information associated with one or more of the clients. For example, a controller may consider location information of one or more clients relative to one or more nodes (repeaters), when making steering decisions. In some cases, the controller may also consider a capabilities match between a client (that is a candidate for steering) and an AP (that is a potential to steer the client to).
Topology aware energy management proposed herein may be understood with reference to the flow diagram 1500 of
As shown at 1502, a root node of a mesh network may be powered on and, at 1504, the root node may associate with other nodes in the mesh network. At 1506, the root node builds a detailed mesh layout, gathering topology information for use in making topology-aware energy management decisions.
For example, the root node may obtain topology information via topology discover requests and responses. The topology information obtained may include, for example, a number of nodes in the mesh network and various information per node. The per-node information may include a number of interfaces and types, link statistics, channel supervision/selection/channel availability check (CAC). The information may also include AP statistics and telemetry information, such as a number of clients, STA link metrics, operating BW, classified flows and SLAs. The information may also include per-client information, such as client capabilities, organizationally unique identifier (OUI) IDs (used for classification of devices), and/or a neighborhood map.
As illustrated at 1508, the root node/controller may calculate a weight or metric per node (periodically or based on certain triggers). If periodically, the calculation may be based on a timer. Triggers may include certain topology notification events.
The weights may be used to determine if one or more prerequisites for AP steering have been met. If the prerequisites are met, as determined at 1510, the controller may initiate AP steering, at 1512. In some cases, AP steering prerequisites may be based on a STAs airtime utilization and SLAs. For example, lower throughput, higher latency clients may be steered to repeaters that can potentially operate on fewer links to reduce energy consumption.
In some cases, it may be beneficial for a root to be able to trigger a repeater to exit a standby mode and transition to an active state. Considerations for transitioning a repeater from a standby mode to an active state may be understood with reference to the flow diagram 1600 of
As shown at 1602, a root node of a root network may periodically monitor SLAs across the mesh network. The example assumes, at 1604, that an SLA breach warning is triggered based on the monitoring.
The root node determines, at 1606, if transitioning a repeater (or repeaters) to an active state would help address the SLA breach. If so, at 1608, the root node may send an activation to the repeater(s) in standby. After bringing repeaters to active, the root node may re-assess the topology and re-assign STAs to repeaters to optimize energy savings. For example, at 1610, the root node may steer one or more candidate stations to an activated repeater.
In some cases, repeaters in standby mode may transition to an active state upon receiving certain defined packets, such as wake-on-LAN or wake-on-WLAN packets. In such cases, the repeaters may communicate this change in state, for example, via a topology notification message to the root (and/or other repeaters).
At 1710, the process 1700 includes obtaining information regarding a topology of a mesh network.
At 1720, the process 1700 includes performing, based on the information, one or more actions to adjust power consumption at one or more wireless nodes of the mesh network.
In some aspects, the at least one action comprises steering one or more clients away from a first wireless node of the mesh network to a second wireless node of the mesh network.
In some aspects, the method 1700 further includes selecting the second wireless node based on one or more suitability criteria.
In some examples, the wireless communication device 1800 can be a device for use in an AP, such as AP 102 described with reference to
The wireless communication device 1800 includes obtaining component 1802, outputting component 1804, performing component 1806, steering component 1808, selecting component 1810, and adjusting component 1812.
Portions of one or more of the components 1802, 1804, 1806, 1808, 1810, and/or 1812 may be implemented at least in part in hardware or firmware. In some examples, at least some of the components 1802, 1804, 1806, 1808, 1810, and/or 1812 are implemented at least in part by a processor and as software stored in a memory. For example, portions of one or more of the components 1802, 1804, 1806, 1808, 1810, and/or 1812 can be implemented as non-transitory instructions (or “code”) executable by the processor to perform the functions or operations of the respective module.
In some implementations, the processor may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the wireless communication device 1800). For example, a processing system of the wireless communication device 1800 may refer to a system including the various other components or subcomponents of the wireless communication device 1800, such as the processor, or a transceiver, or a communications manager, or other components or combinations of components of the wireless communication device 1800. The processing system of the wireless communication device 1800 may interface with other components of the wireless communication device 1800, and may process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of the wireless communication device 1800 may include a processing system, a first interface to output information and a second interface to obtain information. In some implementations, the first interface may refer to an interface between the processing system of the chip or modem and a transmitter, such that the wireless communication device 1800 may transmit information output from the chip or modem. In some implementations, the second interface may refer to an interface between the processing system of the chip or modem and a receiver, such that the wireless communication device 1800 may obtain information or signal inputs, and the information may be passed to the processing system. A person having ordinary skill in the art will readily recognize that the first interface also may obtain information or signal inputs, and the second interface also may output information or signal outputs.
The obtaining component 1802 may be capable of, configured to, or operable to at least obtain a first request that requests the first wireless node to modify the wireless operating parameters.
The outputting component 1804 may be capable of, configured to, or operable to at least output, for transmission, information that indicates at least one of (i) one or more criteria that, when met by a second wireless node, indicate the second wireless node is allowed to request that the first wireless node modify one or more wireless operating parameters, or (ii) one or more options for modifying the wireless operating parameters of the first wireless node.
Various components of the wireless communication device 1800 may provide means for performing the process 1700 described with reference to
Means for obtaining, means for performing, means for outputting, means for selecting, means for adjusting, means for reducing, and/or means for steering may include one or more processors (such as a receive processor, a controller, and/or a transmit processor) of the AP 102 described with reference to
In some cases, rather than actually transmitting, for example, signals and/or data, the wireless communication device 1800 may have an interface to output signals and/or data for transmission (means for outputting). For example, a processor may output signals and/or data, via a bus interface, to a radio frequency (RF) front end of the wireless communication device 1800 for transmission. In various aspects, the RF front end may include various components, including transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, and the like.
In some cases, rather than actually receiving signals and/or data, the wireless communication device 1800 may have an interface to obtain the signals and/or data received from another device (means for obtaining). For example, a processor may obtain (or receive) the signals and/or data, via a bus interface, from an RF front end of the wireless communication device 1800 for reception. In various aspects, the RF front end may include various components, including transmit and receive processors, transmit and receive MIMO processors, modulators, demodulators, and the like.
Implementation examples are described in the following numbered clauses:
As used herein, the term “determine” or “determining” encompasses a wide variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), inferring, ascertaining, measuring, and the like. Also, “determining” can include receiving (such as receiving information), accessing (such as accessing data stored in memory), transmitting (such as transmitting information) and the like. Also, “determining” can include resolving, selecting, obtaining, choosing, establishing and other such similar actions.
As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c. As used herein, “or” is intended to be interpreted in the inclusive sense, unless otherwise explicitly indicated. For example, “a or b” may include a only, b only, or a combination of a and b.
As used herein, “based on” is intended to be interpreted in the inclusive sense, unless otherwise explicitly indicated. For example, “based on” may be used interchangeably with “based at least in part on,” “associated with”, or “in accordance with” unless otherwise explicitly indicated. Specifically, unless a phrase refers to “based on only ‘a,’” or the equivalent in context, whatever it is that is “based on ‘a,’” or “based at least in part on ‘a,’” may be based on “a” alone or based on a combination of “a” and one or more other factors, conditions or information.
As used herein, “a processor,” “at least one processor” or “one or more processors” generally refers to a single processor configured to perform one or multiple operations or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, performance the one or more operations could be divided amongst different processors, though one processor may perform multiple operations, and multiple processors could collectively perform a single operation. Similarly, “a memory,” “at least one memory” or “one or more memories” generally refers to a single memory configured to store data and/or instructions, multiple memories configured to collectively store data and/or instructions.
The various illustrative components, logic, logical blocks, modules, circuits, operations and algorithm processes described in connection with the examples disclosed herein may be implemented as electronic hardware, firmware, software, or combinations of hardware, firmware or software, including the structures disclosed in this specification and the structural equivalents thereof. The interchangeability of hardware, firmware and software has been described generally, in terms of functionality, and illustrated in the various illustrative components, blocks, modules, circuits and processes described above. Whether such functionality is implemented in hardware, firmware or software depends upon the particular application and design constraints imposed on the overall system.
Various modifications to the examples described in this disclosure may be readily apparent to persons having ordinary skill in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of this disclosure. Thus, the claims are not intended to be limited to the examples shown herein, but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.
Additionally, various features that are described in this specification in the context of separate examples also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple examples separately or in any suitable subcombination. As such, although features may be described above as acting in particular combinations, and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Further, the drawings may schematically depict one or more example processes in the form of a flowchart or flow diagram. However, other operations that are not depicted can be incorporated in the example processes that are schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the illustrated operations. In some circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the examples described above should not be understood as requiring such separation in all examples, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
