Method and apparatus for energy efficient access point in wireless communication system

Abstract

A system and method are disclosed for implementing a power saving protocol for devices in a wireless communication system. There is provided a method performed by an AP, comprising: transmitting a first message indicating a power saving schedule of the AP to an STA; and transitioning from a wake-up state to a reduced power state during a time window of the schedule based on the power saving schedule. Reducing the power state is associated with a power state transition capability.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of priority to U.S. Provisional Application Nos. 63 / 537,730, 63 / 591,244, 63 / 621,205, and 63 / 564,286, filed on September 11, 2023, October 18, 2023, January 16, 2024, and March 12, 2024, respectively, and U.S. Non-Provisional Application No. 18 / 819,413, filed on August 29, 2024, the disclosures of which are incorporated herein by reference in their entireties as if fully set forth herein. Technical Field

[0003] The present disclosure generally relates to power saving protocols for devices in wireless communication systems. More specifically, the subject matter disclosed herein relates to balancing power saving and performance requirements by using access point (AP) scheduling and / or capability adjustment to improve the energy efficiency of the AP. Background Art

[0004] In recent years, the number of wireless local area network (WLAN) devices has been growing steadily due to the increasing demand for wireless data and applications as well as the high performance and easy deployment of WLAN protocols.

[0005] Requirements and recommendations are currently being developed from standards development organizations, such as the Institute of Electrical and Electronics Engineers (IEEE), to improve the energy efficiency of APs for sustainability purposes, such as meeting net-zero and carbon neutrality goals.

[0006] Existing power saving protocols are mainly designed for non-AP stations (STAs) without paying attention to APs.

[0007] The Wi-Fi Alliance (WFA) has defined a notification of absence (NoA) for power saving of peer group owners (P2PGO) in Wi-Fi Direct. In addition, a power management mode has been provided for PBSS control points in a personal basic service set (PBSS). However, even if these types of power saving methods can be applied to IEEE802.11 APs, they will introduce functional and performance degradation for both APs and non-APSTAs. For example, neither of these methods is applicable to legacy devices, data on demand, or any device that is unaware of the doze state of the AP. Summary of the invention

[0008]

[0013] Accordingly, one aspect of the present disclosure is to provide protocols and options for improving the energy efficiency of an AP while limiting negative impacts.

[0009]

[0013] Therefore, another aspect of the present disclosure is to provide protocols and options for APs to balance power conservation and performance requirements by adjusting the scheduling and capabilities of the APs.

[0010] According to another aspect of the present disclosure, the AP may be absent for certain periods of time using absence notifications. For example, this allows the AP to reduce power / energy consumption in certain scenarios, such as when there are a small number of associated clients or a small amount of data traffic.

[0011] According to another aspect of the present disclosure, to satisfy the requirements of legacy devices and on-demand data while staying in power save mode, the AP may periodically switch to a listening state and choose to respond to legacy devices or on-demand data in a deferred or immediate manner.

[0012] According to another aspect of the present disclosure, the AP may remain in a reduced capability mode, such as operating with a single antenna, reduced bandwidth, low modulation and coding scheme (MCS), etc., during a scheduled time window.

[0013] According to another aspect of the present disclosure, a non-AP STA can send a presence request or activity frame to influence the power saving schedule of the AP.

[0014] In one embodiment, a method is provided for an AP. The method includes: sending a first message indicating a power saving schedule of the AP to a STA; and based on the power saving schedule, transitioning from an awake state to a reduced power state during a scheduled time window. The reduced power state is associated with a power state transition capability.

[0015] In one embodiment, an AP is provided, comprising: a transceiver; and a processor configured to send a first message indicating a power saving schedule of the AP to a STA via the transceiver, and based on the power saving schedule, transition the AP from an awake state to a reduced power state during a scheduled time window. The reduced power state is associated with a power state transition capability. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In the following sections, various aspects of the subject matter disclosed herein will be described with reference to exemplary embodiments shown in the accompanying drawings, in which:

[0017] Figure 1 An example of scheduled AP power management according to an embodiment is shown;

[0018] Figure 2 shows a table comparing characteristics of an AP in different power states and power management modes according to an embodiment;

[0019] Figure 3 An example of an AP specifying a power saving schedule using absence notification according to an embodiment is shown;

[0020] Figure 4 An example of an AP stopping and resuming power saving scheduling according to an embodiment is shown;

[0021] Figure 5 An example of an AP operating in a listening state according to an embodiment is shown;

[0022] Fig. 6A is a flow chart illustrating a method performed by an AP according to an embodiment;

[0023] Figure 6B is a flow chart illustrating a method performed by an AP according to an embodiment;

[0024] Figure 7 is a block diagram of an electronic device in a network environment according to an embodiment; and

[0025] Figure 8 A system including an AP and STAs communicating with each other is shown. DETAILED DESCRIPTION

[0026] In the following detailed description, many specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be appreciated by those skilled in the art that the disclosed aspects can be practiced without these specific details. In other instances, well-known methods, processes, components, and circuits are not described in detail to avoid obscuring the subject matter disclosed herein.

[0027] References throughout this specification to "one embodiment" or "embodiment" mean that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment disclosed herein. Therefore, the phrases "in one embodiment" or "in an embodiment" or "according to an embodiment" (or other phrases with similar meanings) that appear in various places throughout this specification may not necessarily all indicate the same embodiment. In addition, specific features, structures or characteristics may be combined in any suitable manner in one or more embodiments. In this regard, as used herein, the word "exemplary" means "used as an example, instance or illustration". Any embodiment described herein as "exemplary" should not be interpreted as necessarily being preferred or advantageous over other embodiments. In addition, specific features, structures or characteristics may be combined in any suitable manner in one or more embodiments. In addition, depending on the context discussed herein, a singular term may include a corresponding plural form, and a plural term may include a corresponding singular form. Similarly, hyphenated terms (e.g., "two-dimensional," "predetermined," "pixel-specific," etc.) may occasionally be used interchangeably with corresponding non-hyphenated versions (e.g., "two-dimensional," "predetermined," "pixel-specific," etc.), and capitalized terms (e.g., "counter clock," "row select," "pixel output," etc.) may be used interchangeably with corresponding non-capitalized versions (e.g., "counter clock," "row select," "pixel output," etc.). Such occasional interchangeable usage should not be considered inconsistent with one another.

[0028] In addition, depending on the context discussed herein, singular terms may include corresponding plural forms, and plural terms may include corresponding singular forms. It should also be noted that the various drawings (including component drawings) shown and discussed herein are for illustrative purposes only and are not drawn to scale. For example, for clarity, the size of some elements may be exaggerated relative to other elements. In addition, if deemed appropriate, reference numerals are repeated in the drawings to indicate corresponding and / or similar elements.

[0029] The terms used herein are only used for the purpose of describing some example embodiments and are not intended to limit the claimed subject matter. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that when used in this specification, the terms "include" and / or "comprise" specify the presence of features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0030] It will be understood that when an element or layer is referred to as being on, "connected to" or "coupled to" another element or layer, it can be directly on, connected to or coupled to another element or layer, or there may be intermediate elements or layers. Conversely, when an element is referred to as being "directly on," "directly connected to" or "directly coupled to" another element or layer, intermediate elements or layers are absent. The same reference numerals always indicate the same element. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0031] As used herein, the terms "first," "second," and the like are used as labels for the nouns that follow them and do not imply any type of ordering (e.g., spatial, temporal, logical, etc.) unless explicitly so defined. In addition, the same reference numerals may be used across two or more figures to indicate parts, components, blocks, circuits, units, or modules having the same or similar functions. However, such use is only for simplicity of illustration and ease of discussion; it does not mean that the construction or architectural details of such components or units are the same across all embodiments, or that such commonly referenced components / modules are the only way to implement some example embodiments disclosed herein.

[0032] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the subject matter belongs. It will be further understood that terms (such as those defined in commonly used dictionaries) should be interpreted as having a meaning consistent with their meaning in the context of the relevant art, and will not be interpreted in an idealized or overly formal sense unless explicitly so defined herein.

[0033] As used herein, the term "module" indicates any combination of software, firmware, and / or hardware configured to provide the functionality described herein in conjunction with the module. For example, software may be embodied as a software package, code, and / or instruction set or instructions, and the term "hardware" as used in any embodiment described herein may include, for example, individually or in any combination, components, hardwired circuits, programmable circuits, state machine circuits, and / or firmware storing instructions executed by programmable circuits. Modules may be collectively or individually embodied as circuits forming part of a larger system, such as, but not limited to, an integrated circuit (IC), a system on a chip (SoC), a component, and the like.

[0034] According to embodiments of the present disclosure, protocols and operations for absence notification and power state transition capabilities and scheduling management are provided that allow an AP to save power while being able to adapt to different network conditions / requirements, power saving requirements, and tolerance for functionality and performance degradation.

[0035] More specifically, the present disclosure provides:

[0036] • Power savings for APs while limiting negative impacts - such as issues regarding connectivity, performance, quality of service, fairness, etc.

[0037] • Options to trade off and balance between power savings and performance requirements.

[0038] • Absence notification that allows the AP to be absent for certain time periods, which provides power savings for the AP.

[0039] • Capability options that allow the AP to respond to legacy devices with different emergency requirements and on-demand data (such as probe requests and latency-sensitive data).

[0040] Provide scheduling options that allow the AP and / or STA to interrupt, update, request, report, adjust, feedback, etc., scheduling in different scenarios, such as different network conditions / requirements, power saving requirements, and tolerance for functional and performance degradation.

[0041] • AP and STA have the option to negotiate / agree on power saving modes / levels / scheduling.

[0042] Figure 1An example of scheduled AP power management according to an embodiment is shown. More specifically, Figure 1 An example of a schedule is shown during which an AP may be in different power states with different capabilities.

[0043] refer to Figure 1 , the AP stays in active mode (ie, awake state) outside the scheduled time window. In the awake state, the AP can send and receive frames at any time.

[0044] In the scheduled time window, the AP can be in different power states, such as a doze state, a listening state, or an awake state with reduced capabilities (or a reduced capability awake state). For example, in the scheduled time window 1, the AP can be in the doze state, in the scheduled time window 2, the AP can be in the listening state, and in the scheduled time window 3, the AP can be in the awake state with reduced capabilities.

[0045] In the doze state, the AP turns off the radio and does not transmit, receive, or update buffers.

[0046] In the listening state, the AP does not transmit, but may perform clear channel assessment (CCA) or detect the presence of wireless signals. An AP in the listening state may have less power savings than the doze state, but introduce less functionality and performance degradation. For example, an AP in the listening state may respond to on-demand data and change the schedule later, for example, after the scheduled time window, or exit the power save mode early and respond to on-demand data immediately.

[0047] In the awake state with reduced capabilities, the AP remains in the awake state but with reduced capabilities, for example, using a single antenna, reduced bandwidth, low MCS, etc.

[0048] The AP may also have different power state transition capabilities during a scheduled time window. The power state transition capabilities may be set for one or more specific scheduled time windows, or may apply to the entire schedule.

[0049] In the scheduled time window for the doze state, the AP may or may not have the ability to wake up. When the AP cannot wake up during the scheduled time window for the doze state, the AP remains in the doze state throughout the scheduled time window and can only wake up and enter the awake state after the scheduled time window expires.

[0050] When the AP is able to wake up during the scheduled time window for the doze state, the AP may wake up and enter the awake state based on certain signals, such as wake-up radio (WUR) and / or multi-link operation (MLO).

[0051] During the scheduled time window for the listening state, the AP may or may not have the ability to transmit, i.e., the ability to interrupt the listening state before the scheduled time window ends. When the AP cannot transmit during the scheduled time window for the listening state, the AP remains in the listening state for the entire scheduled time window and cannot switch to the transmitting state until the scheduled time window expires. However, the AP can switch to the receiving state to update the buffer before the scheduled time window expires.

[0052] When the AP is able to transmit during the scheduled time window for the listening state, the AP may switch to the receiving state for on-demand data, such as a probe request or delay-sensitive data. That is, in response to a probe request or delay-sensitive data during the scheduled time window for the listening state, the AP may exit the listening state and switch to the sending state to respond.

[0053] In the scheduled time window for the wake-up state with reduced capabilities, the AP may or may not have the ability to switch to a transmit, receive, or listen state with full capabilities. When the AP cannot switch to a transmit, receive, or listen state with full capabilities in the scheduled time window for the wake-up state with reduced capabilities, the AP may switch to a transmit, receive, or listen state with partial capabilities, such as single-input single-output (SISO) or non-high throughput (HT) mode, before the scheduled time window expires.

[0054] When the AP is able to switch to a transmit, receive, or listen state with full capabilities within a scheduled time window for an awake state with reduced capabilities, the AP may switch to a transmit, receive, or listen state with full capabilities, i.e., awake state, before the scheduled time window expires.

[0055] Outside the scheduled time window, ie, in the awake state, the AP can switch freely between the transmit, receive and listen states, and can receive and transmit frames at any time.

[0056] The AP may use different scheduling parameters, such as start time, stop time, duration, interval, count, power state, power state transition capability, etc., to indicate the schedule and balance power saving and performance requirements. For example, the AP may reuse existing information elements (IEs) such as scheduling elements and / or existing functions such as target wake-up time (TWT). In addition, the scheduling information may be sent in separate IEs or a single IE.

[0057] The AP can change the schedule based on network conditions, traffic volume, power saving requirements, functionality and performance, etc.

[0058] Non-AP STAs may indicate their presence information, for example, by sending presence requests using probe requests or activity frames, to influence AP scheduling in terms of a single scheduled time window, all scheduled time windows (or multiple) of a scheduled instance, or multiple scheduled instances. Non-AP STAs may also send scheduling requests to obtain the latest scheduling and capability information from the AP.

[0059] According to an embodiment, the AP may use absence notification to notify the STA of the scheduled time window. For example, the AP may determine to be absent (e.g., in doze state) for certain time periods in certain scenarios (e.g., when there are a small number of associated clients or low data volume). That is, the AP may use absence notification and enter a power saving mode that switches between awake state and doze state. Absence notification can be issued by the AP in beacon and / or activity frame.

[0060] Figure 2 A table comparing characteristics of APs in different power states and power management modes is shown according to an embodiment.

[0061] refer to Figure 2 , among other characteristics, the table shows the tradeoff between power level savings and performance degradation in different power states with different power state transition capabilities.

[0062] More specifically, when operating outside of the scheduled time window, the AP is in an awake state, e.g. Figure 1 shown.

[0063] When operating within the scheduled time window, the AP may be in a doze (or absent) state, a listening state, or an awake state with reduced capabilities. In addition, within the scheduled time window, the AP may have different power state transition capabilities in the listening state and the awake state with reduced capabilities. That is, in the listening state, the AP may interrupt the listening state or may have the ability to interrupt the listening state, for example, switching to the transmitting state before the scheduled time window expires. In addition, in the awake state with reduced capabilities, the AP may or may not have the ability to switch to the transmitting, receiving, or listening state with full capabilities.

[0064] As shown in the table, an AP in a doze state has high power savings, but at the tradeoff of high performance degradation.

[0065] An AP in the listening state without the capability to interrupt the listening state has medium to high power savings and medium performance degradation. An AP in the listening state with the capability to interrupt the listening state has low to medium power savings and low to medium performance degradation.

[0066] An AP in a wake state with reduced capabilities that does not have the ability to switch to a transmit, receive, or listen state with full capabilities has low to moderate power savings and low to moderate performance degradation. An AP in a wake state with reduced capabilities that has the ability to switch to a transmit, receive, or listen state with full capabilities has no power savings and no performance degradation because it is basically operating in the wake mode.

[0067] Additionally, the table shows the level of support for traditional STAs and data on demand and by traditional APs for different power states.

[0068] Figure 3 An example is shown in which the AP specifies a power saving schedule using absence notification according to an embodiment.

[0069] refer to Figure 3 , the AP is communicating with STA1 operating in active mode and STA2 operating in power saving mode, and STA2 switches between doze state and active state. Figure 3 An example is shown in which the AP is communicating with two STAs, but the present disclosure is not limited to this example, and the AP may communicate with more than two STAs.

[0070] At 301 , STA2 sends data to AP.

[0071] At 302, the AP sends a beacon to STA1 and STA2. The AP can specify a power saving schedule in the beacon and send an absence notification. Alternatively, the AP can specify a power saving schedule in a probe response or an activity frame and send an absence notification.

[0072] exist Figure 3 In the example of , the power saving schedule and absence notification provide schedule parameters including a start time, a duration, an interval, and a count.

[0073] After receiving and decoding the beacon, STA1 operating in active mode can transition to doze state corresponding to the time of AP absence based on the power saving schedule. Since STA2 is already operating in power saving mode, it can enter doze state according to its power saving mode setting.

[0074] At 303 and 304, during the wake-up state between the absence intervals at counts 4 and 3 and counts 2 and 1, respectively, the AP sends a beacon to STA1 and STA2, which may resend the previous power saving schedule and absence notification, or may specify changes to the power saving schedule and absence notification. The AP may also send data to STA1 and / or STA2 when in active mode.

[0075] At 305, STA2, now operating in active mode, may also transition to a doze state corresponding to the time of the AP's absence based on a power saving schedule after receiving and decoding the beacon.

[0076] Figure 4 An example in which an AP stops and resumes power saving scheduling according to an embodiment is shown.

[0077] refer to Figure 4 , the AP is communicating with STA1 operating in active mode and STA2 operating in power saving mode, and STA2 switches between doze state and active state. Figure 4 An example is shown in which the AP is communicating with two STAs, but the present disclosure is not limited to this example, and the AP may communicate with more than two STAs.

[0078] Similar to the above Figure 3 , the AP sends a beacon to STA1 and STA2. The AP can specify a power saving schedule in the beacon and send an absence notification. Alternatively, the AP can specify a power saving schedule in a probe response or an activity frame and send an absence notification.

[0079] After receiving and decoding the beacon, STA1 operating in active mode can transition to doze state corresponding to the time of AP absence based on the power saving schedule. Since STA2 is already operating in power saving mode, it can enter doze state according to its power saving mode setting.

[0080] At 401 , STA1 sends a presence request to the AP in the awake state.

[0081] At 402, in response to the presence request, the AP sends a response frame to STA1 and STA2 indicating that the power saving schedule is being stopped and the AP will remain in the awake state.

[0082] At 403, STA1 can send data to the AP because it has not switched to the absent (doze) state.

[0083] At 404, the AP sends another beacon to STA1 and STA2. The beacon can indicate the resumption of a previous power saving schedule or a new power saving schedule.

[0084] At 405, during the awake state, the AP sends another beacon to STA1 and STA2. The beacon indicates that the power saving schedule is being stopped and the AP will remain in the awake state.

[0085] After that, the AP and STA1 and STA2 can send and receive data.

[0086] Figure 5An example in which the AP operates in a listening state according to the embodiment is shown.

[0087] refer to Figure 5 , the AP is communicating with STA1 operating in active mode and STA2 operating in power saving mode, and STA2 switches between doze state and active state. Figure 5 An example is shown in which the AP is communicating with two STAs, but the present disclosure is not limited to this example, and the AP may communicate with more than two STAs.

[0088] Similar to the above Figure 3 and Figure 4 , the AP sends a beacon to STA1 and STA2. The AP can specify a power saving schedule in the beacon and send an absence notification. Alternatively, the AP can specify a power saving schedule in a probe response or an activity frame and send an absence notification.

[0089] and Figure 3 and Figure 4 Differently, instead of scheduling a doze state, the power saving schedule and absence notification indicate a listening state that cannot be interrupted, during which the AP does not transmit, but can perform CCA or detect the presence of wireless signals from STA1 and STA2. Compared with the doze state, the AP in the listening state can have less power savings, but introduces less functional and performance degradation.

[0090] After receiving and decoding the beacon, STA1 operating in active mode can transition to doze state corresponding to the time the AP is in listening state based on the power saving schedule. Since STA2 is already operating in power saving mode, it can enter doze state according to its power saving mode setting.

[0091] As described above, during the scheduled time window for the listening state, the AP may or may not have the ability to transmit. When the AP cannot transmit during the scheduled time window for the listening state, the AP remains in the listening state throughout the scheduled time window and cannot switch to the transmitting state until the scheduled time window expires. However, the AP can switch to the receiving state to update the buffer before the scheduled time window expires.

[0092] More specifically, STA1 sends a presence request to the AP in the listening state at 501. Here, since the AP does not have the ability to interrupt and transmit, it remains in the listening state throughout the scheduled time window and switches to the transmitting state after the scheduled time window expires.

[0093] In addition, since the AP does not have the ability to interrupt and send, STA1 can also switch to the doze state during the remaining listening state interval.

[0094] At 502, the AP sends a notification frame to STA1 indicating that the power saving schedule (ie, the next scheduled listening state) is being stopped and the AP will remain in the awake state. Figure 5 The announcement frame is shown being sent to STA1, but the present disclosure is not limited thereto. For example, the AP may send the indication using an activity frame or some other type of frame, such as a control, management, and / or data frame.

[0095] Afterwards, STA1 can send data to the AP.

[0096] At 503, the AP sends another beacon to STA1 and STA2. The AP specifies another power saving schedule in the beacon and sends an absence notification. Alternatively, the AP can specify the power saving schedule and send an absence notification in a probe response or activity frame. Unlike previous beacons, the power saving schedule and absence notification indicate a listening state that can be interrupted.

[0097] At 504, upon determining delay-sensitive (or on-demand) data, STA1 sends an indication of the data to the AP in the listening state. For example, STA1 may send an indication with delay-sensitive data so that the AP wakes up to receive the data, or STA1 may simply send the data so that the AP wakes up. Because the AP is in a listening state that can be interrupted, the AP may switch to a receiving state for on-demand data. That is, in response to delay-sensitive data during a scheduled time window for the listening state, the AP may exit the listening state and switch to a sending state to respond.

[0098] In addition, because the AP has the ability to interrupt and transmit, STA1 does not switch to the doze state during the remaining listening state interval because STA1 expects the AP to transmit.

[0099] At 505 , in response to the indication of received data, the AP sends a response frame (or announcement frame) to STA1 indicating that the power saving schedule (ie, the current listening state) is being stopped early and the AP will switch to the awake state.

[0100] After that, the AP and STA1 can send and receive data.

[0101] Fig. 6A is a flow chart illustrating a method performed by an AP according to an embodiment. More specifically, Fig. 6AThe following diagram illustrates the operation of an AP when a reduced power state is associated with a power state transition capability that does not allow the AP to transition before the scheduled time window of the reduced power state expires. For example, when the reduced power state is a listening state and the associated power state transition capability is that the listening state cannot be interrupted, or when the reduced power state is a reduced capability awake state and the associated power state transition capability is that the reduced capability awake state cannot be switched to a fully capable awake state, the AP may perform Fig. 6A Operations in .

[0102] refer to Fig. 6A In step 601, the AP operates in an awake state, wherein the AP is able to establish a connection with one or more STAs, provide the STAs with a power saving schedule of the AP, and transmit and receive data with the STAs.

[0103] In step 602, based on the AP's power saving schedule, the AP transitions to a reduced power state. Figure 1 During the scheduled time windows shown in , the AP may transition to a reduced power state, such as a listening state or an awake state with reduced capabilities.

[0104] In step 603, while in the reduced power state, the AP receives a message from one of the STAs, such as an indication of the presence of a request or latency-sensitive data. Fig. 6A The operation in is performed with a power state transition capability that does not allow the AP to transition before the scheduled time window of the reduced power state expires, so the AP does not respond to receiving messages while in the reduced power state. However, the AP can switch the receiving state and buffer the received messages.

[0105] In step 604, the AP determines whether the scheduled time window has expired. If the scheduled time window has not expired, the AP continues to operate in the reduced power state in step 602. However, if the scheduled time window has expired, the AP transitions from the reduced power state back to the awake state in step 601.

[0106] Once in the awake state, the AP may respond to messages received from STAs while in the reduced power state. Figure 5 As shown at 502 in FIG. 1 , the AP may send an announcement frame to STA1 indicating that the power saving scheduling (ie, the next scheduled listening state) is being stopped and the AP will remain in the awake state.

[0107] Figure 6B is a flow chart illustrating a method performed by an AP according to an embodiment. More specifically, Fig. 6AThe AP operation is shown when a reduced power state is associated with a power state transition capability that allows the AP to transition before the scheduled time window of the reduced power state expires. For example, when the reduced power state is a listening state and the associated power state transition capability is that the listening state can be interrupted, or when the reduced power state is a reduced capability awake state and the associated power state transition capability is that the reduced capability awake state can be switched to a fully capable awake state, the AP may perform Figure 6B Operations in .

[0108] refer to Figure 6B In step 610, the AP operates in an awake state, wherein the AP is able to establish a connection with one or more STAs, provide the AP's power saving schedule to the STAs, and transmit and receive data with the STAs.

[0109] In step 611, the AP transitions to a reduced power state based on the AP's power saving schedule. Figure 1 During the scheduled time windows shown in , the AP may transition to a reduced power state, such as a listening state or an awake state with reduced capabilities.

[0110] In step 612, while in the reduced power state, the AP receives a message from one of the STAs, such as an indication of the presence of a request or latency-sensitive data. Figure 6B The operations in are performed with a power state transition capability that allows the AP to transition before a scheduled time window for a reduced power state expires, so the AP can respond to received messages while in a reduced power state.

[0111] Therefore, in response to the received message, the AP terminates the reduced power state during the scheduled time window in step 613 and transitions from the reduced power state back to the awake state in step 610 .

[0112] Once in the awake state, the AP can respond to messages received from STAs. Figure 5 As shown at 505 in , in response to the indication of receiving the data, the AP sends a response frame (or announcement frame) to STA1, indicating that the power saving scheduling (ie, the current listening state) is being stopped early and the AP will switch to the awake state.

[0113] According to the embodiments described above, scheduled AP power management can be used to adjust the scheduling of APs and the power saving capabilities of APs, absence notifications can be used when an AP is absent during certain time periods, which provides power saving for the AP, and provides listening states with different power conversion capabilities and wake-up states with reduced capability settings, allowing the AP to respond to legacy devices and on-demand data with different power saving requirements and urgency / performance requirements, such as probe requests and delay-sensitive data.

[0114] Figure 7 is a block diagram of electronic devices in a network environment 700 according to an embodiment.

[0115] refer to Figure 7 , an electronic device 701 (e.g., an AP or a non-AP STA) in a network environment 700 may communicate with an electronic device 702 via a first network 798 (e.g., a short-range wireless communication network), or communicate with an electronic device 704 or a server 708 via a second network 799 (e.g., a long-range wireless communication network). The electronic device 701 may communicate with the electronic device 704 via the server 708. The electronic device 701 may include a processor 720, a memory 730, an input device 750, a sound output device 755, a display device 760, an audio module 770, a sensor module 776, an interface 777, a haptic module 779, a camera module 780, a power management module 788, a battery 789, a communication module 790, a user identification module (SIM) card 796, or an antenna module 797. In one embodiment, at least one of the components (e.g., the display device 760 or the camera module 780) may be omitted from the electronic device 701, or one or more other components may be added to the electronic device 701. Some of the components may be implemented as a single integrated circuit (IC). For example, the sensor module 776 (eg, a fingerprint sensor, an iris sensor, or an illumination sensor) may be embedded in the display device 760 (eg, a display).

[0116] The processor 720 may execute software (e.g., program 740) to control at least one other component (e.g., hardware or software component) of the electronic device 701 coupled to the processor 720, and may perform various data processing or calculations. For example, the processor 720 may execute software to control the electronic device 701 to perform Fig. 6A and Figure 6B The method shown in .

[0117] As at least part of data processing or calculation, the processor 720 may load commands or data received from another component (e.g., the sensor module 776 or the communication module 790) into the volatile memory 732, process the commands or data stored in the volatile memory 732, and store the resultant data in the non-volatile memory 734. The processor 720 may include a main processor 721 (e.g., a central processing unit (CPU) or an application processor (AP)) and an auxiliary processor 723 (e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that may operate independently of the main processor 721 or in conjunction with the main processor 721. Additionally or alternatively, the auxiliary processor 723 may be adapted to consume less power than the main processor 721, or to perform a specific function. The auxiliary processor 723 may be implemented to be separate from the main processor 721 or to be a part of the main processor 721.

[0118] The auxiliary processor 723 may control at least some of the functions or states related to at least one component (e.g., display device 760, sensor module 776, or communication module 790) among the components of the electronic device 701 instead of the main processor 721 while the main processor 721 is in an inactive (e.g., sleep) state, or control at least some of the functions or states related to at least one component (e.g., display device 760, sensor module 776, or communication module 790) among the components of the electronic device 701 together with the main processor 721 while the main processor 721 is in an active state (e.g., executing an application). The auxiliary processor 723 (e.g., an image signal processor or a communication processor) may be implemented as a part of another component (e.g., a camera module 780 or a communication module 790) that is functionally related to the auxiliary processor 723.

[0119] The memory 730 may store various data used by at least one component of the electronic device 701 (e.g., the processor 720 or the sensor module 776). The various data may include, for example, software (e.g., program 740) and input data or output data for commands related thereto. The memory 730 may include a volatile memory 732 or a non-volatile memory 734. The non-volatile memory 734 may include an internal memory 736 and / or an external memory 738.

[0120] The program 740 may be stored as software in the memory 730 , and may include, for example, an operating system (OS) 742 , middleware 744 , or applications 746 .

[0121] The input device 750 may receive a command or data to be used by another component (eg, the processor 720) of the electronic device 701 from outside (eg, a user) of the electronic device 701. The input device 750 may include, for example, a microphone, a mouse, or a keyboard.

[0122] The sound output device 755 can output a sound signal to the outside of the electronic device 701. The sound output device 755 may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as playing multimedia or recording, and the receiver may be used to receive an incoming call. The receiver may be implemented as a separate speaker or as a part of the speaker.

[0123] The display device 760 can visually provide information to the outside (e.g., user) of the electronic device 701. The display device 760 may include, for example, a display, a hologram device, or a projector, and a control circuit for controlling a corresponding one of the display, the hologram device, and the projector. The display device 760 may include a touch circuit suitable for detecting a touch or a sensor circuit (e.g., a pressure sensor) suitable for measuring the strength of a force caused by a touch.

[0124] The audio module 770 can convert sound into an electrical signal, and vice versa. The audio module 770 can obtain sound via the input device 750, or output sound via the sound output device 755 or the earphone of the external electronic device 702 directly (eg, wired) or wirelessly coupled to the electronic device 701.

[0125] The sensor module 776 can detect the operating state (e.g., power or temperature) of the electronic device 701 or the environmental state (e.g., the state of the user) outside the electronic device 701, and then generate an electrical signal or data value corresponding to the detected state. The sensor module 776 may include, for example, a gesture sensor, a gyroscope sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illumination sensor.

[0126] The interface 777 may support one or more designated protocols for coupling the electronic device 701 directly (e.g., wired) or wirelessly with the external electronic device 702. The interface 777 may include, for example, a high-definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0127] The connection terminal 778 may include a connector via which the electronic device 701 may be physically connected to the external electronic device 702. The connection terminal 778 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

[0128] The haptic module 779 may convert the electrical signal into a mechanical stimulus (eg, vibration or movement) or an electrical stimulus that can be recognized by the user via a sense of touch or a sense of movement. The haptic module 779 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0129] The camera module 780 may capture still images or moving images. The camera module 780 may include one or more lenses, an image sensor, an image signal processor, or a flash. The power management module 788 may manage the power provided to the electronic device 701. The power management module 788 may be implemented as at least a portion of a power management integrated circuit (PMIC), for example.

[0130] The battery 789 may supply power to at least one component of the electronic device 701. The battery 789 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0131] The communication module 790 can support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 701 and an external electronic device (e.g., electronic device 702, electronic device 704, or server 708), and perform communication via the established communication channel. The communication module 790 may include one or more communication processors that can operate independently of the processor 720 (e.g., AP) and support direct (e.g., wired) communication or wireless communication. The communication module 790 may include a wireless communication module 792 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 794 (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules can communicate via a first network 798 (e.g., a short-range communication network such as BLUETOOTH). TM , Wireless Fidelity (Wi-Fi) Direct, or Infrared Data Association (IrDA) standards) or a second network 799 (e.g., a long-distance communication network such as a cellular network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN)) to communicate with an external electronic device. These various types of communication modules can be implemented as a single component (e.g., a single IC), or can be implemented as multiple components separated from each other (e.g., multiple ICs). The wireless communication module 792 can use user information (e.g., International Mobile Subscriber Identity (IMSI)) stored in the user identification module 796 to identify and authenticate the electronic device 701 in a communication network (such as the first network 798 or the second network 799).

[0132] The antenna module 797 may transmit a signal or power to the outside of the electronic device 701 (e.g., an external electronic device) or receive a signal or power from the outside of the electronic device 701. The antenna module 797 may include one or more antennas, and at least one antenna suitable for a communication scheme used in a communication network (such as the first network 798 or the second network 799) may be selected from them by the communication module 790 (e.g., the wireless communication module 792), for example. Then, a signal or power may be transmitted or received between the communication module 790 and the external electronic device via the selected at least one antenna.

[0133] A command or data may be sent or received between the electronic device 701 and the external electronic device 704 via a server 708 coupled to the second network 799. Each of the electronic devices 702 and 704 may be a device of the same type or a different type as the electronic device 701. All or some of the operations to be performed at the electronic device 701 may be performed at one or more of the external electronic devices 702, 704, or 708. For example, if the electronic device 701 should automatically perform a function or service, or in response to a request from a user or another device, the electronic device 701 may request one or more external electronic devices to perform at least a portion of the function or service instead of or in addition to performing the function or service. The one or more external electronic devices receiving the request may perform at least a portion of the requested function or service, or additional functions or additional services related to the request, and send the result of the execution to the electronic device 701. The electronic device 701 may provide the result as at least a portion of the reply to the request with or without further processing the result. To this end, for example, cloud computing, distributed computing, or client-server computing technology may be used.

[0134] Figure 8 A system including a STA 805 and an AP 810 communicating with each other is shown. The AP 810 may include a radio 815 and a processing circuit (or component for processing) 820, which may perform various methods disclosed herein, for example, Fig. 6A and Figure 6B For example, the processing circuit 820 may receive a transmission from the STA 805 via the radio 815, and the processing circuit 820 may send a signal to the STA 805 via the radio 815 (eg, using one or more links).

[0135] The subject matter and the embodiments of the operation described in this specification can be implemented in digital electronic circuits, or in computer software, firmware or hardware (including the structures disclosed in this specification and their structural equivalents), or in a combination of one or more of them. The embodiments of the subject matter described in this specification can be implemented as one or more computer programs, that is, one or more modules of computer program instructions, which are encoded on a computer storage medium for execution by a data processing device or control of the operation of the data processing device. Alternatively or additionally, the program instructions can be encoded on an artificially generated propagation signal, for example, a machine-generated electrical, optical or electromagnetic signal, which is generated to encode information for transmission to a suitable receiver device for execution by a data processing device. The computer storage medium can be or be included in a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination thereof. In addition, although the computer storage medium is not a propagation signal, the computer storage medium can be the source or destination of the computer program instructions encoded in the artificially generated propagation signal. The computer storage medium can also be, or be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices). In addition, the operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.

[0136] Although this specification may include many specific implementation details, the implementation details should not be interpreted as a limitation on the scope of any claimed subject matter, but rather as a description of features specific to a particular embodiment. Certain features described in the context of a separate embodiment in this specification may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination. In addition, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from the claimed combination may be removed from the combination in some cases, and the claimed combination may be directed to a sub-combination or a variation of the sub-combination.

[0137] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring that such operations be performed in the particular order shown or in sequence, or that all of the operations shown be performed, to achieve the desired results. In some cases, multitasking and parallel processing can be advantageous. In addition, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, 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.

[0138] Thus, specific embodiments of the subject matter have been described herein. Other embodiments are within the scope of the following claims. In some cases, the actions set forth in the claims can be performed in a different order and still achieve the desired results. Additionally, the processes depicted in the accompanying drawings do not necessarily require the particular order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing can be advantageous.

[0139] As those skilled in the art will recognize, the innovative concepts described herein may be modified and varied over a wide range of applications.Accordingly, the scope of the claimed subject matter should not be limited to any of the specific exemplary teachings discussed above, but rather is defined by the appended claims.

Claims

1. A method performed by an access point (AP), the method comprising: sending a first message indicating a power saving schedule of the AP to a station (STA); as well as Based on a power saving schedule, transitioning from an awake state to a reduced power state during a scheduled time window, The reduced power state is associated with a power state transition capability.

2. The method according to claim 1, further comprising: After the scheduled time window expires, a transition is made from the reduced power state to the awake state.

3. The method according to claim 2, further comprising: A second message is sent to the STA indicating that the power saving schedule is stopped.

4. The method according to claim 2, further comprising: After transitioning from the reduced power state to the awake state, receiving a second message from the STA; modifying a power saving schedule based on the second message; as well as A third message is sent to the STA indicating a modification to the power saving schedule.

5. The method according to claim 4, wherein: The second message includes an indication of the presence of a request or latency sensitive data.

6. The method according to claim 4, further comprising: A fourth message is sent to the STA indicating that the power saving scheduling is resumed.

7. The method according to claim 6, wherein: The fourth message includes a beacon.

8. The method according to claim 4, wherein: Modifying the power saving schedule includes canceling a subsequent transition to a reduced power state that was scheduled to occur in a next scheduled time window.

9. The method according to claim 1, wherein: The reduced power state is a listening state in which the AP receives signals from the STA but cannot transmit, and an associated power state transition capability is that the listening state cannot be interrupted.

10. The method according to claim 9, further comprising: While in the listening state, receiving a second message from the STA; After the scheduled time window expires, the state switches from the listening state to the awake state; as well as In response to the second message, a third message is sent to the STA.

11. The method according to claim 10, wherein: The second message includes an indication of the presence of a request or latency sensitive data, and The third message includes an activity frame indicating that the power saving scheduling is stopped.

12. The method according to claim 1, wherein: The reduced power state is a listening state in which the AP can receive signals from a STA but cannot transmit, and an associated power state transition capability is that the listening state can be interrupted.

13. The method according to claim 12, further comprising: While in the listening state, receiving a second message from the STA; Before the scheduled time window expires, the state changes from the listening state to the awake state; as well as In response to the second message, a third message is sent to the STA.

14. The method according to claim 13, wherein: The second message includes an indication of the presence of a request or latency sensitive data, and The third message includes an activity frame indicating that the power saving scheduling is stopped.

15. The method according to claim 1, wherein: The first message includes a beacon, a probe response, or an activity frame.

16. The method according to claim 1, wherein: The power saving schedule indicates a plurality of scheduled time windows, and The method further includes repeatedly switching between the awake state and the reduced power state according to a plurality of scheduled time windows.

17. The method according to claim 1, wherein: The reduced power state is a reduced capability wake-up state, and the associated power state transition capability is that the reduced capability wake-up state can be switched to a wake-up state having full capabilities.

18. The method according to claim 17, further comprising: While in the reduced capability wake-up state, receiving a second message from the STA; Before the scheduled time window expires, transition from the reduced-capacity wake-up state to the full-capacity wake-up state; and In response to the second message, a third message is sent to the STA.

19. The method according to claim 18, wherein: The second message includes an indication of the presence of a request or latency sensitive data, and The third message includes an activity frame indicating that the power saving scheduling is stopped.

20. An access point (AP), comprising: Transceiver; as well as The processor is configured as: sending, via the transceiver, to a station (STA) a first message indicating a power saving schedule of the AP, and Based on the power saving schedule, the AP is transitioned from the awake state to a reduced power state during the scheduled time window, The reduced power state is associated with a power state transition capability.

Images