Managing wake-up schedules for client devices based on data traffic

Abstract

Embodiments of the invention relate to managing wake-up schedules for client devices based on data traffic. An example method for managing a wake-up schedule for a client device is presented. A wireless networking device determines a value of a data traffic characteristic of a client device based on monitoring of data traffic associated with the client device. If it is determined that the client device is capable of implementing the TWT mechanism, the wireless networked device may set a wake-up schedule for the client device based on the value of the data traffic characteristic. Once the wake-up schedule is set, the wireless networked device communicates with the client device in accordance with the wake-up schedule. In some examples, when client devices have different behaviors for the same data traffic characteristic, a wireless networking device may set a customized wake-up schedule for different client devices. Further, in some examples, the wireless networking device may set a customized wake-up schedule for the same client device even for different activity periods.

Description

Background Art

[0001] Nowadays, wireless devices are everywhere. From printers, smart TVs to Internet of Things (IoT) devices, many devices are vying for connections to wireless networks. Some of these devices operate using batteries with limited stored energy. The new generation of Wi-Fi standards introduces a series of technologies that can reduce power consumption to address the challenges associated with operating devices with limited stored energy. Target wake time (TWT) and restricted TWT (R-TWT) (hereinafter collectively referred to as TWT mechanisms) are some example mechanisms defined in the new Wi-Fi standards that aim to reduce power consumption. The TWT mechanism allows wireless networking devices such as access points to use enhanced medium access protection and resource reservation to provide predictable delays with higher reliability for delay-sensitive services on wireless links. In particular, the TWT mechanism enables access points and devices to negotiate and define specific times for devices to wake up from their power saving modes and access the communication medium. Therefore, TWT can significantly increase device sleep time, thereby reducing power consumption. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] One or more examples of the present disclosure are described in detail with reference to the following drawings. The drawings provided are for illustration purposes only and depict examples only.

[0003] Figure 1 depicts a block diagram of a networked system in which various examples presented herein may be implemented;

[0004] Figure 2 A flow chart depicting an example method for setting customized wake-up schedules for different client devices based on corresponding data traffic analysis;

[0005] Figure 3A-3B depicts a flow chart of another example method for setting customized wake-up schedules for different client devices based on corresponding data traffic analysis;

[0006] Figure 4 A flow chart depicting another example method for setting a customized wake schedule for a client device for different time periods;

[0007] Figure 5A-Figure 5B A flow chart depicting yet another example method for setting a customized wake schedule for a client device for different time periods;

[0008] Figure 6 depicts an example frame sequence for setting a wake-up schedule for a client device; and

[0009] Figure 7 A block diagram of an example computing system is depicted.

[0010] The drawings are not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. DETAILED DESCRIPTION

[0011] The Institute of Electrical and Electronics Engineers (IEEE) 802.11ax defines a TWT mechanism, and IEEE 802.1be defines an R-TWT mechanism, which is intended to save power consumption of battery-powered wireless devices (also referred to as stations (STAs) or client devices). These TWT mechanisms enable client devices to determine when and how long the client device wakes up to send and / or receive data. Using the TWT mechanism, an access point (AP) and a client device can negotiate a specific service period (e.g., also referred to as a TWT service period or wake-up duration), during which the client device can wake up from a power saving mode and communicate with the AP. When outside the service period, the client device can be placed in a power saving mode to reduce power consumption or perform non-channel operations. In addition to reduced power consumption, the negotiated service period can also allow the AP to manage the activities of client devices by scheduling client devices to operate at different times, and thereby minimize contention between client devices.

[0012] The TWT mechanism provides two major categories of agreements - individual TWT and broadcast TWT. Under individual TWT, service periods can be negotiated on a per-station basis, and each client device can set its service period. Under broadcast TWT, the AP can collectively set service periods for a group of client devices by broadcasting TWT parameters to the group of client devices. Each client device can choose whether to subscribe to the schedule specified in the TWT parameters.

[0013] Obviously, the data traffic for a given client device depends on the applications running on the client device. For example, the traffic for an application that requires video multicast is primarily downlink, periodic, and real-time. If the client device does not know when to wake up or is configured with outdated TWT parameters, the performance of the client device may be negatively impacted. For example, a client device waking up too frequently may waste power, while a client device waking up infrequently may introduce jitter. Therefore, setting the correct set of TWT parameters is an ongoing challenge.

[0014] To address this issue, in an example consistent with the teachings of the present disclosure, a wireless networking device (e.g., an AP) is configured with the ability to analyze the traffic patterns of its associated client devices. With a broader understanding of the traffic patterns of the client devices, the wireless networking device can intelligently guide the client devices to wake up and sleep for data communications, resulting in minimal jitter or even no jitter while efficiently reducing power consumption. According to one example, the proposed wireless networking device determines the value of a data traffic characteristic of the client device based on the data traffic associated with the client device. The wireless networking device can implement deep packet inspection (DPI) and determine data traffic characteristics such as burst intervals, burst durations, average bandwidth, application types, and quality of service (QoS) requirements of the client device.

[0015] Based on the measurement of one or more data service characteristics, the wireless networking device can first determine whether the client device is capable of implementing the TWT mechanism. If it is determined that the client device is capable of implementing the TWT mechanism, the wireless networking device can set the wake-up schedule of the client device based on the value of the data service characteristic. The wake-up schedule can be defined using parameters such as wake-up duration and wake-up interval. The wake-up duration may refer to the period during which the client device remains active for wireless communication. In addition, the wake-up interval may refer to the duration during which the client device wakes up again to communicate with the wireless networking device after the wake-up duration is completed. In particular, the wireless networking device can determine the wake-up duration and wake-up interval of the client device based on the burst interval and burst duration of the data service. In one example, the wake-up duration can be set to a value higher than the burst duration so that the client device has enough time to complete the data transmission. In addition, the wake-up interval of the client device is set to the same as the burst interval, so that the client device wakes up synchronously with the burst interval of the data service of the client device. Once the wake-up schedule is set, the wireless networking device communicates with the client device according to the wake-up schedule.

[0016] In one example implementation, when different client devices (e.g., a first client device and a second client device) have different behaviors for the same data service characteristic, the wireless networking device can set different (i.e., customized) wake-up schedules for these clients. To do this, the wireless networking device can calculate a first value of the data service characteristic corresponding to the first client device, and set a first wake-up schedule for the first client device based on the first value. When observing that the second client device has a different second value for the same data service characteristic, the wireless networking device sets a second wake-up schedule for the second client device based on the second value. The wireless networking device can then communicate with the first client device according to the first wake-up schedule, and communicate with the second client device according to the second wake-up schedule.

[0017] In some cases, a given client device may run different applications at different time periods, resulting in changes in the data service pattern of the client device. According to one implementation, the wireless networking device may set different (i.e., customized) wake-up schedules for the same client device for different activity periods (e.g., a first period and a second period). To this end, the wireless networking device may determine a value of a data service characteristic corresponding to the client device for a first period (hereinafter referred to as a first period service characteristic value), and set a first wake-up schedule for the first period based on the first period service characteristic value. In addition, during operation, the wireless networking device may determine another value of a data service characteristic corresponding to the client device for a second period (hereinafter referred to as a second period service characteristic value). When it is determined that the second period service characteristic value is different from the first period service characteristic value, the wireless networking device may set a second wake-up schedule for the second period based on the second period service characteristic value.

[0018] As will be appreciated, such a setting of the wake-up schedule can allow the client device to wake up synchronously with the data traffic characteristics of the client device and have sufficient time to complete the data transmission. Such an efficient data transmission and wake-up schedule can reduce the power consumption of the client device with minimal or no jitter.

[0019] The following detailed description refers to the accompanying drawings. It should be clearly understood that the drawings are for illustration and description purposes only. Although several examples are described in this document, modifications, adaptations and other implementations are also possible. Therefore, the following detailed description does not limit the disclosed examples. On the contrary, the proper scope of the disclosed examples can be defined by the appended claims.

[0020] Before describing in detail examples of the disclosed systems and methods, it is useful to describe an example network installation with which the systems and methods may be implemented in various applications. Figure 1 A system 100 is shown in which various examples presented herein may be implemented. The system 100 may be implemented in any setting, such as in a home setting or in an organization, such as a business, an educational institution, a government entity, a medical institution, or other organization. The system 100 depicts a network of devices (hereinafter referred to as network devices) (e.g., wireless networking device 102) and a plurality of client devices (e.g., client devices 104 and 106). The system 100 may include, for example, Figure 1 A greater or lesser number of wireless networking devices as shown.

[0021] The client devices 104, 106 may be electronic devices capable of wirelessly communicating with the wireless networking device 102 or other electronic devices. Examples of the client devices 104, 106 may include desktop computers, laptop computers, servers, network servers, authentication servers, authentication authorization accounting (AAA) servers, domain name system (DNS) servers, dynamic host configuration protocol (DHCP) servers, Internet protocol (IP) servers, virtual private network (VPN) servers, network policy servers, mainframes, tablet computers, e-readers, netbook computers, televisions and similar displays (e.g., smart TVs), content receivers, set-top boxes, personal digital assistants (PDAs), mobile phones, smart phones, smart terminals, dumb terminals, virtual terminals, video game consoles, virtual assistants, Internet of Things (IoT) devices, etc.

[0022] Client devices 104 and 106 can communicate with wireless networking device 102 via respective communication links 110 and 112. In an example implementation, communication links 110 and 112 can be wireless connections established between wireless networking device 102 and client devices 104 and 106 according to a wireless communication protocol, such as the 802.11 standard, Wi-Fi Alliance specifications, or any other wireless communication standard. In some examples, communication via communication links 110 and 112 can be performed according to IEEE 802.11ax and / or IEEE 802.11be specifications. In certain other examples, communication links 110 and 112 can include telecommunication lines, such as telephone lines, broadcast coaxial cables, fiber optic cables, satellite communications, cellular communications, and the like. In some examples, communication links 110 and 112 can include any number of intermediate network devices, such as switches, routers, gateways, servers, and / or controllers.

[0023] The wireless networking device 102 may be a combination of hardware, software, and / or firmware configured to provide wireless network connectivity to the client devices 104, 106. In some examples, the wireless networking device 102 may include, be implemented as, or be referred to as a radio router, a radio transceiver, a switch, a Wi-Fi hotspot device, a basic service set (BSS) device, an extended service set (ESS) device, a radio base station (RBS), or some other terminology, and may act as a network access point for the client devices 104, 106. In one example implementation, the wireless networking device 102 may be a wireless access point (also referred to as an access point (AP)). Although not shown, in some examples, the system 100 may include additional network devices, such as, but not limited to, additional APs, wireless local area network (WLAN) controllers, network switches, gateway devices, routers, and the like. Via the wireless networking device 102, the client devices 104, 106 may communicate with each other and / or any other network devices (e.g., network switches, WLAN controllers, and / or gateway devices) to which the wireless networking device 102 is communicatively connected.

[0024] According to an example consistent with the teachings of the present disclosure, the wireless networking device 102 can be configured to manage the wake-up schedule of one or more of the client devices 104 and 106 based on the data traffic conditions associated with the client devices 104, 106. In particular, the wireless networking device 102 can intelligently guide the client devices 104, 106 to wake up and sleep for data communication, thereby causing minimal jitter or even no jitter, while efficiently reducing power consumption. In some examples, to achieve these goals, the wireless networking device 102 can include a machine-readable storage medium 114 and a processing resource 116 coupled to the machine-readable storage medium 114.

[0025] The machine-readable storage medium 114 may be non-transitory, and is alternatively referred to as a non-transitory machine-readable storage medium, not covering transient propagation signals. The machine-readable storage medium 114 may be any electronic, magnetic, optical, or other type of storage device that can store data and / or executable instructions. Examples of the machine-readable storage medium 114 may include random access memory (RAM), non-volatile RAM (NVRAM), electrically erasable programmable read-only memory (EEPROM), a storage drive (e.g., a solid-state drive (SSD) or a hard disk drive (HDD)), flash memory, etc. The machine-readable storage medium 114 may be encoded with instructions 118 to manage a wake-up schedule for one or more of the client devices 104, 106. Although not shown, in some examples, the machine-readable storage medium 120 may be encoded with certain additional executable instructions to perform any other operations performed by the wireless networking device 102 without limiting the scope of the present disclosure.

[0026] The processing resource 116 may be a physical device, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), other hardware device capable of retrieving and executing instructions stored in the machine-readable storage medium 114, or a combination thereof. The processing resource 116 may retrieve, decode, and execute instructions 118 stored in the machine-readable storage medium 114 to manage the wake-up schedule of the client devices 104, 106. Instead of or in addition to executing the instructions 118, the processing resource 116 may include at least one integrated circuit (IC), control logic, electronic circuitry, or a combination thereof, which includes several electronic components for performing the functions intended to be performed by the wireless networking device 102.

[0027] According to some examples, the wireless networking device 102 can implement a method for managing the wake-up schedule of the client devices 104, 106 by executing the instructions 118 through the processing resource 116. The processing resource 116 can execute one or more instructions in the instructions 118 to perform the combination described later. Figure 2 , Figure 3A , Figure 3B , Figure 4 , Figure 5A and Figure 5B Describe the method steps.

[0028] In some examples, the processing resource 116 may execute one or more instructions in the instructions 118 to determine whether a given client device is capable of implementing a TWT mechanism based on the value of a data service characteristic associated with a given client device (e.g., client devices 104, 106). For example, the data service characteristic of a given client device may be a parameter indicating the periodicity of the data service of the given client device. Examples of data service characteristics may be burst intervals, burst durations, average bandwidth, application types, or quality of service (QoS) requirements. In response to determining that a given client device is capable of implementing a TWT mechanism, the wireless networking device 102 may set a wake-up schedule for the given client device based on the value of the data service characteristic. In particular, the wireless networking device 102 may determine the wake-up duration and wake-up interval of a given client device based on data service characteristics such as burst intervals and burst durations of the data service. Once the wake-up schedule is set, the wireless networking device 102 communicates with the given client device according to the set wake-up schedule.

[0029] In some examples, if the client devices 104, 106 have different behaviors for the same data traffic characteristics, the wireless networking device 102 can set a customized (i.e., custom) wake-up schedule for each of the client devices 104 and 106. The wireless networking device can then communicate with the client devices 104 and 106 according to the corresponding customized wake-up schedule. Figure 2 , Figure 3A and Figure 3B The method described in describes additional details for setting a customized wake-up schedule for client devices 104 and 106.

[0030] Because client devices 104 and / or 106 can run different applications at different time periods, resulting in changes in the corresponding data service patterns. According to some examples, for a given client device in client devices 104 and 106, if the given client device exhibits different behaviors for the same data service characteristics during each such active period, the wireless networking device 102 can set a customized wake-up schedule for different active periods (e.g., a first period and a second period). As will be appreciated, such setting of the wake-up schedule can allow the client device to wake up synchronously with the data service characteristics of the client device and have sufficient time to complete the data transmission. Such efficient data transmission and wake-up schedules can reduce the power consumption of the client device with minimal or no jitter.

[0031] In the following description, with the help of Figure 2 , Figure 3A , Figure 3B , Figure 4 , Figure 5A and Figure 5B The flowcharts shown describe several operations performed by a wireless networking device (e.g., wireless networking device 102). In some examples, the operations described in these flowcharts can be performed by a processing resource (e.g., processing resource 116) by executing instructions (e.g., instructions 118) stored in a machine-readable storage medium (e.g., machine-readable storage medium 114). As an alternative or in addition to retrieving and executing instructions, the operations described in these flowcharts can be performed by implementing one or more electronic circuits including electronic components, such as FPGAs, ASICs, or other electronic circuits.

[0032] Reference now Figure 2 , depicts a flow chart of an example method 200 for managing a wake-up schedule for a client device. In particular, method 200 represents an example technique for setting customized wake-up schedules for different client devices based on corresponding data traffic analysis. In situations where client devices have different behaviors for the same data traffic characteristics, this helps the client devices operate with minimal or no jitter while saving power.

[0033] At step 202, the wireless networking device may determine a first value of a data service characteristic corresponding to a first client device (e.g., client device 104). In particular, for the first client device, the wireless networking device may examine its data service for a certain duration (also referred to as a first monitoring phase). During the first monitoring phase, the wireless networking device may analyze the data service, for example by applying a deep packet inspection technique, to calculate the value of one or more data service characteristics. Examples of data service characteristics that the wireless networking device may determine include burst interval, burst duration, average bandwidth, application type, or QoS requirements. The term "burst duration" as used herein may refer to the duration for which a data block (e.g., a group of data packets) is transmitted. In addition, the term "burst interval" may refer to the duration between two consecutive data blocks. The term "average bandwidth" as used herein may refer to the number of bytes of service data transmitted per second. The term "application type" as used herein may refer to different service priorities, such as "voice", "video", etc. The "QoS requirement" as used herein may refer to service delay or packet loss requirements for different types of service types.

[0034] One or more of these data service characteristics may indicate the periodicity of the data service. For example, a data service having a consistent burst interval and burst duration may be periodic. In addition, some applications require periodic data transmission. Therefore, knowing the application type may also be used to determine whether the data service is periodic.

[0035] If the data service of the first client device is identified as periodic based on the first data service characteristic, the wireless networking device can be configured to communicate with the first client device according to a target wake-up time (TWT) suitable for the data service of the first client device. To do this, in step 204, the wireless networking device determines a first wake-up schedule for the first client device based on the first value. In particular, determining the wake-up schedule may include determining TWT parameters, such as a wake-up duration and a wake-up interval. In some examples, the wireless networking device may determine the first wake-up duration and the first wake-up interval based on a burst duration and a burst interval of the data service of the first client device.

[0036] Once the first wake-up duration and the first wake-up interval are determined, the wireless networking device can negotiate a TWT session with the first client device according to the TWT technology specified in one or more specifications of the IEEE802.11 specification (e.g., the IEEE 802.11ax or IEEE 802.11be specification). In an implementation where the first client device supports the R-TWT technology specified in the IEEE 802.11be specification, the wireless networking device can negotiate an R-TWT session with the first client device.

[0037] Typically, in a network, other client devices, such as a second client device (e.g., 106), may be connected to the wireless networking device for wireless connection. Therefore, the wireless networking device may also monitor the data service of the second client device (in a similar manner as described in conjunction with step 202) to see whether the second client device is capable of operating using TWT technology. Therefore, in step 206, the wireless networking device may determine a second value of a data service characteristic corresponding to the second client device, wherein the second value is different from the first value. In particular, the wireless networking device may analyze the data service of the second client device during the second monitoring phase by applying deep packet inspection technology to determine the second value of the data service characteristic. The second monitoring phase may overlap with the first monitoring phase in whole or in part; end before the first monitoring phase begins, or begin after the first monitoring phase ends.

[0038] Since the second value is different from the first value, in step 208, the wireless networking device sets a second wake-up schedule for the second client device that is different from the first wake-up schedule based on the second value. For example, the values ​​of the burst duration and the burst interval of the first client device may be different from the values ​​of the burst duration and the burst interval of the second client device. Therefore, in order to ensure that the second client device also operates in a reduced jitter and power-efficient manner, the wireless networking device sets a second wake-up schedule, which is a customized wake-up schedule for the second client device. In particular, the wireless networking device may determine the second wake-up duration and the second wake-up interval for the second client device based on the burst duration and the burst interval of the data service of the second client device. Once the second wake-up duration and the second wake-up interval are determined, the wireless networking device may negotiate a TWT session with the second client device in accordance with the TWT technology specified in one or more specifications in the IEEE 802.11 specification.

[0039] Once the wireless networking device establishes a TWT session with the first client device and / or the second client device, in step 210, the wireless networking device communicates with the first client device according to a first wake-up schedule and communicates with the second client device according to a second wake-up schedule.

[0040] Reference now Figure 3A and Figure 3B , presents a flow chart of an example method 300 for setting customized wake-up schedules for different client devices (eg, client devices 104, 106) based on respective data traffic analysis. For the sake of brevity, certain details of the operations described in any previous figures are not repeated herein.

[0041] At step 302, the wireless networking device monitors data traffic associated with a first client device (e.g., first client device 104) for a duration (also referred to as a first monitoring phase). During the first monitoring phase, the wireless networking device may analyze the data traffic, for example, by applying deep packet inspection techniques. Additionally, at step 304, the wireless networking device determines a first value of a data traffic characteristic (e.g., burst interval, burst duration, average bandwidth, application type, and / or QoS requirement) based on monitoring the data traffic during the first monitoring phase.

[0042] Some of these data service characteristics indicate the periodicity of the data service, and client devices with periodic data service are suitable for implementing TWT technology. Therefore, in step 306, the wireless networking device performs a check to determine whether the data service of the first client device (DT1) is periodic during the first monitoring phase. The periodicity of the data service can be determined based on first values ​​of data service characteristics such as burst interval and burst duration (hereinafter referred to as first burst interval and first burst duration, respectively). In order to check the periodicity of the data service, the wireless networking device can determine whether the first burst duration and the first burst interval are consistent during the first monitoring interval. If the first burst duration and the first burst interval of the data packets in the data service are consistent, the wireless networking device can determine that the data service of the first client device is periodic (i.e., "yes" in step 306), and therefore determine that the first client device has TWT capability (see result 310).

[0043] If the first burst duration and / or the first burst interval of the first client device are inconsistent (i.e., no at step 306), then in some examples, the wireless networking device may allow a certain tolerance for periodicity to achieve TWT with the first client device. In such an implementation, at step 308, the wireless networking device may perform another check to determine if the burst interval fluctuation (BIF) in the data traffic of the first client device is consistent. DT1 ) is within a first predefined range, and a burst duration variation (BDV) in the data service of the first client device DT1 ) is within a second predefined range (R2). In one example, the term "burst interval fluctuation" as used herein may refer to an average difference between two consecutive burst intervals within a given duration (e.g., a first monitoring phase). In addition, in one example, the term "burst duration variation" as used herein may refer to an average difference between burst sizes of data packets within a given duration (e.g., a first monitoring phase). If the burst interval fluctuation (BIF DT1 ) is within a first predefined range and the burst duration variation (BDV DT1) is within the second predefined range (“yes” at step 308), the wireless networking device may determine that the first client device has TWT capability (see result 310). However, at step 308, if the wireless networking device determines that the burst interval fluctuation (BIF) DT1 ) is outside the first predefined range and the burst duration variation (BDV DT1 ) is outside the second predefined range, the wireless networking device determines that the first client device is not suitable for implementing TWT technology and continues to monitor the data services of the associated client devices.

[0044] In response to determining that the first client device has TWT capability (see result 310), in step 312, the wireless networking device can determine a first wake-up schedule by calculating first TWT configuration parameters (such as a first wake-up duration and a first wake-up interval) of the first client device based on the first burst duration and the first burst interval, respectively. In some examples, the wireless networking device calculates the first wake-up interval to be the same as the first burst interval, so that when the TWT feature is implemented for the first client device, the first client device can wake up at the same time that the first client device transmits / receives a data burst. In an example implementation, if the first client device is a Voice over Internet Protocol (VoIP) device and the burst interval of its data service is determined to be 20 milliseconds (ms), the wireless networking device determines the first wake-up interval to be the same as the burst interval (e.g., 20 ms). Therefore, the first client device can wake up at intervals of every 20 ms to communicate with the wireless networking device.

[0045] In addition, in some examples, the wireless networking device calculates the first wake-up duration by adding the margin duration to the first burst duration. Therefore, the first wake-up duration can be slightly longer than the first burst duration, thereby allowing the first client device enough time to complete the data transmission. In an example implementation, if the burst duration of the data service of the first client device is determined to be 3ms, the wireless networking device determines the first wake-up duration as the burst duration (e.g., 3ms) plus the margin duration (e.g., 1ms). Therefore, the first wake-up duration can be determined to be 4ms, thereby allowing the first client device to completely transmit / receive the service burst of 3ms duration.

[0046] In some examples, the margin duration can be determined based on a burst duration value (e.g., a first burst duration). For example, the margin duration can be a predefined percentage of the burst duration value. The predefined percentage can be customizable, and in one example, the predefined percentage can be in a range from about 10% to 30%. In certain other examples, the margin duration can be a fixed value or a customizable value independent of the burst duration value. For example, the margin duration can be set to 1 ms, regardless of the burst duration value used in the examples described above.

[0047] After the TWT parameters are determined, the wireless networking device may negotiate a TWT session with the first client device. The TWT session may be negotiated according to the TWT technology specified in one or more specifications in the IEEE 802.11 specifications. In particular, such a TWT negotiation may require the wireless networking device to transmit a TWT negotiation frame indicating a first wake-up interval and a first wake-up duration to the first client device in step 314. Subsequently, in step 316, the wireless networking device may receive a TWT session confirmation from the first client device. In the event that the TWT session confirmation is received, the first client device is considered to be configured with a first wake-up schedule. Therefore, during subsequent operations, the first client device is configured to remain active during the wake-up duration at the end of the wake-up interval for wireless communication with the wireless networking device. In some examples, the wireless networking device may also announce the wake-up interval and wake-up duration in one or more beacon frames transmitted to the client device.

[0048] Typically, in a network, other client devices (such as a second client device (e.g., 106)) can be connected to the wireless networking device for wireless connection. Therefore, in step 318, the wireless networking device can also monitor the data service associated with the second client device for the second monitoring phase service (in a manner similar to that described in conjunction with step 202) to see if it is capable of implementing TWT technology. In addition, in step 320, the wireless networking device determines a second value of a data service characteristic (e.g., one or more of a burst interval, burst duration, average bandwidth, application type, or QoS requirement) based on monitoring of the data service during the second monitoring phase.

[0049] Additionally, at step 322, the wireless networking device performs a check to determine whether the second value is different from the first value. At step 322, if it is determined that the second value is the same as the first value, then at step 324, the wireless networking device may set a first wake-up schedule with the second client device. In some examples, the wireless networking device may perform a process similar to the process described in steps 314 and 316 for the second client device.

[0050] However, at step 322, if it is determined that the second value is different from the first value, the wireless networking device performs a check at step 326 to determine whether the data traffic of the second client device is periodic during the second monitoring phase, in a manner similar to that described in conjunction with determining the periodicity of the first client device. At step 326, if it is determined that the data traffic of the first client device is periodic (i.e., "yes" at step 326), and the second client device is deemed to have TWT capability (see result 328).

[0051] If the data service of the second client device is not strictly periodic (i.e., the second burst duration and / or the second burst interval of the data packets in the data service are inconsistent, no at step 326), then in some examples, the wireless networking device may allow a certain tolerance for periodicity to implement the TWT technique on the second client. In such an implementation, at step 330, the wireless networking device may perform a check to determine whether the burst interval fluctuation (BIF) in the data service of the second client device is consistent with the second burst duration and / or the second burst interval of the data packets in the data service. DT2 ) is within the first predefined range (R1), and a burst duration variation (BDV) in the data service of the second client device DT1 ) is within the second predefined range (R2). If the burst interval fluctuation (BIF DT2 ) is determined to be within the first predefined range and the burst duration variation (BDV DT2 ) is determined to be within the second predefined range (“yes” at step 330), the wireless networking device may determine that the second client device has TWT capability (see result 328). However, at step 330, if the burst interval fluctuation (BIF) DT2 ) is determined to be outside the first predefined range and the burst duration variation (BDV DT2 ) is determined to be outside the second predefined range ("No" in step 330), the wireless networking device determines that the first client device is not suitable for implementing TWT technology and continues to monitor the data traffic of the relevant client devices.

[0052] In response to determining that the second client device also has TWT capability (see result 328), in step 332, the wireless networking device can determine a second wake-up schedule, similar to that described in conjunction with the first wake-up schedule (e.g., in step 312). The second wake-up schedule may include values ​​of second TWT configuration parameters (such as a second wake-up duration and a first wake-up interval determined based on a second burst duration and a second burst interval, respectively). In an example implementation, if the second client device is an IoT device and the burst interval of its data service is determined to be 5ms, the wireless networking device determines the second wake-up interval to be the same as the burst interval (e.g., 5ms). Therefore, the second client device can wake up at intervals of every 5ms to communicate with the wireless networking device. In addition, if the burst duration of the second client device is 4ms, the wireless networking device determines the second wake-up duration to be the burst duration (e.g., 4ms) plus a margin duration (e.g., 1ms). Therefore, the second wake-up duration can be determined to be 5ms, allowing the second client device to fully transmit / receive a service burst of 4ms duration.

[0053] After the second wake-up schedule is determined, the wireless networking device may negotiate a TWT session with the second client device in a manner similar to that described in conjunction with negotiating the first wake-up schedule. For example, in step 334, the wireless networking device sends a TWT negotiation frame to the second client device that specifies a second wake-up interval and a second wake-up duration. Subsequently, in step 336, the wireless networking device may receive a TWT session confirmation from the second client device. Upon receipt of the TWT session confirmation, the second client device is considered to be configured with the second wake-up schedule. Therefore, during subsequent operations, the second client device is configured to remain active at the end of the second wake-up interval and during the second wake-up duration for wireless communication with the wireless networking device. In some examples, the wireless networking device may also announce the second wake-up interval and the second wake-up duration in one or more beacon frames transmitted to the client device.

[0054] Once the wireless networking device establishes a TWT session with the first client device and / or the second client device, in step 338, the wireless networking device communicates with the first client device according to the first wake-up schedule and communicates with the second client device according to the second wake-up schedule.

[0055] Client devices may run different applications at different times. Depending on the type of application running at a given duration, the data traffic pattern of the client device may change, resulting in different values ​​for the same data traffic characteristic for the same client device. In this case, it would be useful to dynamically update the wake-up schedule of the client device in response to detecting a change in the data traffic pattern. Figure 4A flow chart of one such example method 400 for setting a customized wake schedule for a client device during different time periods is depicted. For the sake of brevity, certain details of the operations described in any previous figures are not repeated herein.

[0056] In step 402, the wireless networking device determines a value of a data service characteristic corresponding to a client device (e.g., client device 104) by examining the data service of the client device. The data service characteristic may be any one or more of a burst interval, a burst duration, an average bandwidth, an application type, and a QoS requirement. The value of the data service characteristic determined in step 402 is hereinafter referred to as a first period service characteristic value (FPTCV). The wireless networking device may determine the first period service characteristic value by monitoring the data service of the client device.

[0057] Based on the first time period service characteristic value, if it is found that the client device has TWT capability, then in step 404, the wireless networking device sets a wake-up schedule for the first time period based on the first time period service characteristic value. Such a wake-up schedule set for the first time period is referred to as the first time period wake-up schedule hereinafter. In particular, in order to set the first time period wake-up schedule, the wireless networking device may determine the first time period TWT parameters, such as the first time period wake-up interval and the first time period wake-up duration, based on the first time period service characteristic value (for example, one or more of the values ​​of the burst interval and the burst duration measured during the monitoring phase). Once the first time period TWT parameters are determined, the wireless networking device may negotiate the first time period wake-up schedule with the client device according to the TWT technology specified in the IEEE802.11 specification. The details of negotiating the wake-up schedule have been described above.

[0058] After the first period wake-up schedule is set, the wireless networking device may communicate with the client device during the first period according to the first period wake-up schedule in step 406. In particular, based on the set first period wake-up schedule, the client device may wake up at each first period wake-up interval within the first period wake-up duration for data communication with the wireless networking device.

[0059] In addition, during operation, the wireless networking device may continuously monitor the data traffic of the client device. Based on the monitoring, at step 408, the wireless networking device may again determine a value of the data traffic characteristic corresponding to the client device that is different from the first period traffic characteristic value (e.g., the value of the data traffic characteristic determined at step 402). The value of the data traffic characteristic determined at step 408 is hereinafter referred to as the second period traffic characteristic value (SPTCV).

[0060] Based on the second time period service characteristic value, if it is found that the client device has TWT capability even for the changed data service mode, then in step 410, the wireless networking device sets a wake-up schedule for the second time period based on the second time period service characteristic value. The wake-up schedule set for the second time period is hereinafter referred to as a second time period wake-up schedule that is different from the first time period wake-up schedule. In particular, in order to set the second time period wake-up schedule, the wireless networking device can determine the second time period TWT parameters, such as the second time period wake-up interval and the second time period wake-up duration, based on the second time period service characteristic value (for example, one or more of the values ​​of the burst interval and the burst duration measured in step 408). Once the second time period TWT parameters are determined, the wireless networking device can negotiate the second time period wake-up schedule with the client device according to the TWT technology specified in the IEEE 802.11 specification. The details of negotiating the wake-up schedule have been described above.

[0061] After the second period wake-up schedule is set, the wireless networking device may communicate with the client device during the second period according to the second period wake-up schedule in step 412. In particular, based on the set second period wake-up schedule, the client device may wake up at each second period wake-up interval within the wake-up duration of the second period for data communication with the wireless networking device.

[0062] Reference now Figure 5A and Figure 5B , presents a flowchart of an example method 500 for setting a customized wake-up schedule for a client device during different time periods. In particular, the method 500 may be a flowchart representing Figure 4 An example of method 400 and may include certain additional steps and provide information about Figure 4 For the sake of brevity, certain details of the operations described in any previous figures are not repeated herein.

[0063] At step 502, the wireless networking device monitors data traffic (DT1) associated with a client device (e.g., client device 104) for a certain duration to analyze the data traffic, for example, by applying deep packet inspection techniques. In addition, at step 504, the wireless networking device determines a value of a data traffic characteristic (also referred to as a first period traffic characteristic value (FPTCV)) based on monitoring of the data traffic during the first monitoring phase. The first period traffic characteristic value may be a value of one or more of a burst interval, a burst duration, an average bandwidth, an application type, and / or a QoS requirement.

[0064] In addition, in step 506, the wireless networking device performs a check to determine whether the data service of the client device is periodic based on the first time period service characteristic value. In order to check the periodicity of the data service, the wireless networking device can determine whether the values ​​of the burst duration and the first burst interval are consistent in the data service of the client device. If the values ​​of the burst duration and the burst interval of the data packets in the data service are consistent, the wireless networking device can determine that the data service of the client device is periodic (i.e., "yes" in step 506), and therefore determine that the client device has TWT capability (see result 510).

[0065] If the burst duration and / or burst interval of the data packets in the data traffic are inconsistent (i.e., no at step 506), then in some examples, the wireless networking device may allow a certain tolerance for periodicity to implement TWT with the client device. In such an implementation, at step 508, the wireless networking device may perform another check to determine if the burst interval fluctuation (BIF) in the data traffic based on the first monitoring (e.g., the monitoring at step 502) is consistent. FM ) is within a first predefined range (R1), and based on a burst duration variation (BDV) in the first monitored data service. FM ) is within the second predefined range (R2). If the burst interval fluctuation (BIF FM ) is within a first predefined range and the burst duration variation (BDV FM ) is within the second predefined range (“yes” at step 508), the wireless networking device may determine that the client device has TWT capability (see result 510). However, at step 508, if the wireless networking device determines that the burst interval fluctuation (BIF) FM ) is outside the first predefined range and the burst duration variation (BDV FM ) is outside the second predefined range, the wireless networking device determines that the client device is not suitable for implementing TWT technology and continues to monitor the data traffic of the associated client device.

[0066] In response to determining that the client device has TWT capability (see result 510), at step 512, the wireless networking device can determine a first period wake-up schedule by calculating the first period TWT configuration parameters (such as the first period wake-up duration and the first period wake-up interval) of the client device based on the values ​​of the burst duration and the burst interval determined in step 504, respectively. The first period wake-up duration and the first period wake-up interval can be determined in a manner similar to that described in conjunction with method 300.

[0067] After the first time period TWT parameters are determined, the wireless networking device can negotiate a first time period TWT session with the client device. The TWT session can be negotiated according to the TWT technology specified in one or more specifications in the IEEE 802.11 specification. In particular, such TWT negotiation may require the wireless networking device to transmit a TWT negotiation frame indicating the first time period wake-up interval and the first time period wake-up duration to the client device in step 514. Subsequently, in step 516, the wireless networking device can receive a TWT session confirmation from the client device. In the event that a TWT session confirmation is received, the client device is considered to be configured with a first time period wake-up schedule. In some examples, the wireless networking device may also announce the first time period wake-up interval and the first time period wake-up duration in one or more beacon frames transmitted to the client device.

[0068] After the first period wake-up schedule is negotiated, the wireless networking device may communicate with the client device during the first period according to the first period wake-up schedule in step 517. In particular, based on the set first period wake-up schedule, the client device may wake up at each first period wake-up interval within the first period wake-up duration for data communication with the wireless networking device.

[0069] In addition, during operation, the wireless network device may continuously monitor the data traffic of the client device, see step 518, to determine whether there are any changes in the digital traffic pattern of the client device and whether the wake-up schedule needs to be changed. In addition, in step 520, the wireless networking device determines a value of the data traffic characteristic based on the monitoring of the data traffic. The value of the data traffic characteristic determined in step 520 is referred to as the second time period traffic characteristic value (SPTCV) hereinafter. Examples of the second time period traffic characteristic value may be the second time period burst duration and the second time period burst interval, or any value of the QoS requirement, application type and / or average bandwidth determined in step 520.

[0070] In addition, at step 522, the wireless networking device performs a check to determine whether the second time period service characteristic value is different from the first time period service characteristic value. At step 522, if it is determined that the second time period service characteristic value is the same as the first time period service characteristic value, then at step 524, the wireless networking device may negotiate the first time period wake-up schedule with the client device. In some examples, the wireless networking device may perform a process similar to the process described in steps 514 and 516.

[0071] However, in step 522, if it is determined that the second time period service characteristic value is different from the first time period service characteristic value, then in step 526, the wireless networking device performs a check based on the second time period service characteristic value (e.g., the second time period burst duration and the second time period burst interval) in a manner similar to that described above to determine whether the data service of the client device is periodic. In step 526, if it is determined that the data service of the client device is periodic (i.e., "yes" in step 526), ​​it is determined that the client device has TWT capability (see result 530). If the data service of the client device is not strictly periodic (i.e., the second time period burst duration and the second time period burst interval in the data service are inconsistent, no in step 526), ​​then in some examples, the wireless networking device may allow a certain tolerance for periodicity to achieve TWT with the client device. In such an implementation, in step 528, the wireless networking device may perform a check to determine the burst interval fluctuation (BIF) in the data service of the client device based on the second monitoring (e.g., the monitoring in step 518). SM ) is within a first predefined range (R1), and based on a burst duration variation (BDV) in a second monitored data service SM ) is within the second predefined range (R2). If the burst interval fluctuation (BIF SM ) is determined to be within the first predefined range and the burst duration variation (BDV SM ) is determined to be within the second predefined range (“yes” at step 528), the wireless networking device may determine that the client device has TWT capability (see result 530). However, at step 528, if the burst interval fluctuation (BIF) SM ) is outside the first predefined range and the burst duration variation (BDV SM ) is outside the second predefined range, the wireless networking device determines that the client device is not suitable for implementing TWT technology and continues to monitor the data traffic of the associated client device.

[0072] In response to determining that the client device also has TWT capability based on the second period traffic characteristic value (see result 530), in step 532, the wireless networking device can determine a second period wake-up schedule similar to that described in conjunction with the first period wake-up schedule (e.g., in step 512). The second period wake-up schedule may include values ​​of second period TWT configuration parameters, such as a second period wake-up duration and a second period wake-up interval determined based on the second period burst duration and the second period burst interval, respectively.

[0073] After the second time period wake-up schedule is determined, the wireless networking device can negotiate a TWT session with the client device in a manner similar to that described in conjunction with negotiating the first time period wake-up schedule. For example, in step 534, the wireless networking device sends a TWT negotiation frame to the client device that specifies the second time period wake-up interval and the second time period wake-up duration. Subsequently, in step 536, the wireless networking device can receive a TWT session confirmation from the client device. Upon receiving the TWT session confirmation, the client device is considered to be configured with the second time period wake-up schedule. Therefore, during subsequent operations, the client device is configured to remain active for wireless communication with the wireless networking device during the second time period wake-up duration at the end of the second time period wake-up interval.

[0074] After the second period wake-up schedule is set, the wireless networking device may communicate with the client device during the second period according to the second period wake-up schedule in step 538. In particular, based on the set second period wake-up schedule, the client device may wake up at each second period wake-up interval within the second period wake-up duration for data communication with the wireless networking device.

[0075] Figure 6 Depicted is a method for transmitting data to and from a wireless networked device (e.g., Figure 1 The wireless networking device 102 is shown as a client device (e.g., Figure 1 104) establishes an example frame sequence 600 of a wake-up schedule. In particular, Figure 6 The example frame sequence 600 of can represent data traffic of a client device (e.g., a VoIP phone). The frame sequence 600 depicts two types of traffic, e.g., downlink (DL) traffic 602 (indicating data traffic from a wireless network device to a client device) and uplink (UL) traffic 604 (indicating data traffic from a client device to a wireless network device), shown on timelines 601 and 603, respectively. The DL traffic 602 can include beacons (e.g., beacons 605 and 608) and traffic units (e.g., data traffic units 607 and 609) and other management traffic (e.g., not shown). In addition, the UL traffic 604 can include data traffic units 611 and 613 and other management traffic (not shown). It can be appreciated that although some of the beacons and data traffic units are labeled with the same reference numerals, the contents of such beacons and data traffic units can be different.

[0076] After the client device is associated with the wireless networking device, the wireless networking device begins analyzing the DL traffic 602 and the UL traffic 604 of the client device during a monitoring phase 606. Based on the data traffic analysis during the monitoring phase 606, the wireless network device can determine that the burst duration and the burst interval of the client device are 3ms and 20ms, respectively. In addition, the wireless network device can determine that the DL traffic 602 and the UL traffic 604 are periodic, with a stable traffic burst duration of 3ms and a traffic burst interval of 20ms. Based on the traffic burst duration of 3ms and the traffic burst interval of 20ms, the wireless network device can determine the TWT wake-up duration and the TWT wake-up interval of the client device to be 4ms and 20ms, respectively, in a manner similar to that described above.

[0077] In the frame sequence 600, time T0 marks the end of the monitoring phase 606. Therefore, at time T0, the wireless networking device can send a beacon 608. The beacon 608 may include a TWT element (e.g., an R-TWT element) that specifies the TWT wake-up duration and TWT wake-up interval of the client device. In addition, at time T1, the wireless networking device sends a TWT negotiation action frame 610. In an example implementation, the TWT negotiation action frame 610 may include a broadcast TWT parameter set field, specify a negotiation type = 3 in the control field of the TWT element, and specify an acceptance condition for the TWT setting command field (e.g., accept TWT). In addition, the TWT negotiation action frame 610 may specify the TWT wake-up duration field and the TWT wake-up interval field as 4ms and 20ms, respectively. In addition, at T3, the target wake-up time may be set to the client device STA wake-up time point.

[0078] In addition, at time T2, after the client device completes sending the TWT session confirmation frame 612 to the wireless networking device and enters the power saving mode. In addition, at time T3, the client device wakes up to receive and send packets. At time T4, the client device completes the DL and UL service burst communications, enters the power saving mode, and waits for the next wake-up time point again. The interval between each wake-up duration is marked as a power saving duration, during which the client device can enter the power saving mode. The duration that the client device can remain in the power saving mode is called the power saving duration. Figure 6 Several such power saving durations are also marked in . In some examples, when operating in the power saving mode, the client device can disable its data communication circuitry to cease data communication with the wireless networking device.

[0079] Figure 7A block diagram of an example computing system 700 is depicted in which various examples described herein may be implemented. In some examples, the computing system 700 may be configured to function as a wireless networking device such as Figure 1 The computing system 700 may be configured to operate as a wireless networking device (such as a wireless networking device 102) and may perform various operations described in conjunction with one or more of the previous figures. Figure 1 The computing system 700 may be operated by a wireless networking device 102 and may perform various operations described in one or more of the previous figures. Examples of devices and / or systems that may be implemented as the computing system 700 may include desktop computers, laptop computers, servers, network servers, authentication servers, AAA servers, DNS servers, DHCP servers, IP servers, VPN servers, network policy servers, mainframes, tablet computers, e-readers, netbook computers, televisions and similar monitors (e.g., smart TVs), content receivers, set-top boxes, PDAs, mobile phones, smart phones, intelligent terminals, dumb terminals, virtual terminals, video game consoles, virtual assistants, IoT devices, etc.

[0080] The computing system 700 may include a bus 702 or other communication mechanism for communicating information, a hardware processor (also referred to as a processing resource 704), and a machine-readable storage medium 705 coupled to the bus 702 for processing information. In some examples, the processing resource 704 may include one or more CPUs, semiconductor-based microprocessors, and / or other hardware devices suitable for retrieving and executing instructions stored in the machine-readable storage medium 705. The processing resource 704 may retrieve, decode, and execute instructions to manage the transmission power of the wireless networking device. As an alternative or in addition to retrieving and executing instructions, the processing resource 704 may include one or more electronic circuits including electronic components such as an FPGA, an ASIC, or other electronic circuits for performing the functions of one or more instructions.

[0081] In some examples, the machine-readable storage medium 705 may include a main memory 706, such as a RAM, cache, and / or other dynamic storage device, coupled to the bus 702 for storing information and instructions to be executed by the processing resource 704. The main memory 706 may also be used to store temporary variables or other intermediate information during the execution of instructions to be executed by the processing resource 704. When stored in a storage medium accessible to the processing resource 704, such instructions render the computing system 700 as a special-purpose machine customized to perform the operations specified in the instructions. The machine-readable storage medium 705 may also include a read-only memory (ROM) 708 or other static storage device, which is coupled to the bus 702 for storing static information and instructions for the processing resource 704. In addition, in the machine-readable storage medium 705, a storage device 710 (such as a magnetic disk, an optical disk, or a universal serial bus (USB) thumb drive (flash drive) or the like) may be provided and coupled to the bus 702 for storing information and instructions.

[0082] In some examples, computing system 700 can be coupled to a display 712, such as a liquid crystal display (LCD) (or touch-sensitive screen), via bus 702 for displaying information to a computer user. In some examples, input device 714, including alphanumeric and other keys (physical or software generated and displayed on a touch-sensitive screen), can be coupled to bus 702 for communicating information and command selections to processing resources 704. Additionally, in some examples, another type of user input device, such as cursor control 716, can be connected to bus 702. Cursor control 716 can be a mouse, trackball, or cursor direction keys. Cursor control 716 can communicate direction information and command selections to processing resources 704 for controlling cursor movement on display 712. In some other examples, the same direction information and command selections as a cursor control can be implemented by receiving touches on a touch screen without a cursor.

[0083] In some examples, computing system 700 may include a user interface module for implementing a graphical user interface (GUI), which may be stored in a mass storage device as executable software code executed by (multiple) computing devices. For example, this module and other modules may include components, such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, program code segments, drivers, firmware, microcode, circuit systems, data, databases, data structures, tables, arrays, and variables.

[0084] The computing system 700 also includes a network interface 718 coupled to the bus 702. The network interface 718 provides bidirectional data communication coupled to one or more network links connected to one or more local networks. For example, the network interface 718 can be an integrated services digital network (ISDN) card, a cable modem, a satellite modem, or a modem for providing a data communication connection to a corresponding type of telephone line. As another example, the network interface 718 can be a local area network (LAN) card or a wireless communication unit (e.g., a Wi-Fi chip / module).

[0085] In some examples, machine-readable storage medium 705 (e.g., one or more of main memory 706, ROM 708, or storage device 710) stores instructions 707, which when executed by processing resource 704 may cause processing resource 704 to perform one or more of the methods / operations described above. Instructions 707 may be stored on any of main memory 706, ROM 708, or storage device 710. In some examples, instructions 707 may be distributed across one or more of main memory 706, ROM 708, or storage device 710. In some examples, instructions 707 may include instructions that when executed by processing resource 704 may cause processing resource 704 to perform Figure 2 , Figure 3A , Figure 3B , Figure 4 , Figure 5A and Figure 5B Instructions of one or more of the methods described in.

[0086] Unless otherwise expressly stated, the terms and phrases used in this document and their variations should be interpreted as open-ended, rather than restrictive. As an example of the foregoing, the term "including" should be understood as "including but not limited to" and other meanings. The term "example" is used to provide an exemplary example of the project under discussion, rather than its exhaustive or restrictive list. The term "a" or "an" should be understood as "at least one", "one or more" and other meanings. In some cases, the appearance of broadening words and phrases such as "one or more", "at least", "but not limited to" or other similar phrases should not be understood as intending or needing to use narrower situations in the absence of such broadening phrases. In addition, the term "and / or" used in this article refers to and covers any and all possible combinations of related listed items. It should also be understood that although the terms first, second, third, etc. can be used to describe various elements in this article, these elements should not be limited by these terms, because unless otherwise specified or the context indicates otherwise, these terms are only used to distinguish one element from another element.

Claims

1. A method comprising: determining, by the wireless networking device, a first value of a data traffic characteristic corresponding to the first client device, wherein the data traffic characteristic indicates a periodicity of the data traffic; setting, by the wireless networking device, a first wake-up schedule for the first client device based on the first value; determining, by the wireless networking device, a second value of the data traffic characteristic corresponding to a second client device, wherein the second value is different than the first value; setting, by the wireless networking device, a second wake-up schedule for the second client device based on the second value, wherein the second wake-up schedule is different from the first wake-up schedule; as well as The wireless networking device communicates with the first client device according to the first wake-up schedule and communicates with the second client device according to the second wake-up schedule.

2. The method according to claim 1, wherein the data service characteristics include one or more of the following: burst interval, burst duration, average bandwidth, application type, or quality of service (QoS) requirement.

3. A method according to claim 1, wherein setting the first wake-up schedule includes negotiating a first target wake-up time TWT session with the first client device, and wherein setting the second wake-up schedule includes negotiating a second TWT session with the second client device, and wherein the first TWT session and the second TWT session are negotiated according to TWT technology specified in one or more specifications of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specifications.

4. The method according to claim 3 also includes determining, by the wireless networking device, whether a given client device has TWT capability based on the first value or the second value, wherein the given client device is the first client device or the second client device, and wherein the first wake-up schedule is set in response to determining that the first client device has TWT capability, and wherein the second wake-up schedule is set in response to determining that the second client device has TWT capability.

5. The method of claim 4, wherein determining that the given client device has TWT capabilities comprises performing one or more of the following: determining that the data service is periodic; or It is determined that the burst interval fluctuation in the data service is within a first predefined range and the burst duration variation is within a second predefined range.

6. The method of claim 4, further comprising determining, by the wireless networking device, a wake-up interval and a wake-up duration for the given client device based on a corresponding burst interval and burst duration. 7 . The method according to claim 6 , wherein the wake-up interval is set to be the same as the burst interval, and the wake-up duration is set to be higher than the burst duration.

8. The method of claim 6, wherein negotiating the first TWT session comprises: Transmitting, by the wireless networking device to the first client device, a TWT negotiation frame indicating the wake-up interval and the wake-up duration; as well as A TWT session confirmation is received by the wireless networking device from the first client device, wherein in response to sending the TWT session confirmation, the first client device is configured to remain active for wireless communication with the wireless networking device during the wake-up duration at the end of the wake-up interval.

9. The method of claim 6, further comprising advertising, by the wireless networking device, the wake-up interval and the wake-up duration in a beacon frame.

10. A method according to claim 3, wherein in response to determining that the first client device supports the restricted TWT R-TWT technology specified in the IEEE802.11be specification, the first TWT session is negotiated according to the R-TWT technology, and in response to determining that the second client device supports the R-TWT technology, the second TWT session is negotiated according to the R-TWT technology.

11. A method comprising: determining, by the wireless networking device, a first value of a data traffic characteristic corresponding to the client device; Setting, by the wireless networking device, a first wake-up schedule for a first time period for the client device based on the first value; communicating, by the wireless networking device, with the client device according to the first wake-up schedule during the first period; determining, by the wireless networking device, a second value of the data traffic characteristic corresponding to the client device, wherein the second value is different than the first value; setting, by the wireless networking device, a second wake-up schedule for a second time period for the client device based on the second value, wherein the second wake-up schedule is different from the first wake-up schedule; as well as The wireless networking device communicates with the client device according to the second wake-up schedule during the second time period. The method of claim 11 , wherein the first time period and the second time period are non-overlapping.

13. The method according to claim 11, further comprising: For a given period of time, The wireless networking device determines whether the client device has TWT capability based on the first value or the second value, wherein the given time period is the first time period or the second time period.

14. The method of claim 13, wherein determining that the client device has TWT capability comprises one or more of: determining that the data service is periodic; or It is determined that the burst interval fluctuation in the data service is within a first predefined range and the burst duration variation is within a second predefined range.

15. The method of claim 14, further comprising determining, by the wireless networking device, a wake-up interval and a wake-up duration for the client device based on a corresponding burst interval and burst duration for the given time period.

16. The method of claim 15, further comprising negotiating a TWT session for a given period of time comprising: Transmitting, by the wireless networking device to the client device, a TWT negotiation frame indicating the wake-up interval and the wake-up duration; as well as A TWT session confirmation is received by the wireless networking device from the client device, wherein in response to sending the TWT session confirmation, the client device is configured to remain active for wireless communication with the wireless networking device during the wake-up duration at the end of the wake-up interval.

17. A wireless networking device, comprising: a machine-readable storage medium storing instructions; as well as a processing resource coupled to the machine-readable storage medium and configured to execute one or more of the instructions to: determining a first value of a data traffic characteristic corresponding to a first client device, wherein the data traffic characteristic indicates a periodicity of data traffic; setting a first wake-up schedule for the first client device based on the first value; determining a second value of the data service characteristic corresponding to a second client device, wherein the second value is different from the first value; setting a second wake schedule for the second client device based on the second value, wherein the second wake schedule is different from the first wake schedule; and Communicating with the first client device according to the first wake schedule and communicating with the second client device according to the second wake schedule.

18. The wireless networking device of claim 17, wherein the data traffic characteristics include one or more of: burst interval, burst duration, average bandwidth, application type, or QoS requirement.

19. A wireless networking device according to claim 17, wherein the processing resource is further configured to execute one or more of the instructions to: determine whether a given client device has TWT capability based on the first value or the second value, wherein the given client device is the first client device or the second client device.

20. The wireless networking device of claim 19, wherein in response to determining that the given client device has TWT capabilities, the processing resources are configured to execute one or more of the instructions to: transmitting a TWT negotiation frame indicating a wake-up interval and a wake-up duration to the given client device; and A TWT session confirmation is received from the given client device, wherein in response to sending the TWT session confirmation, the given client device is configured to remain active for wireless communication with the wireless networking device during the wake-up duration at the end of the wake-up interval.

Images