Operation of UHR soft AP with signaling of unavailability periods

Abstract

The invention relates to operation of a UHR soft AP with signaling of an unavailability period. Embodiments herein provide systems, apparatuses, and methods for a soft access point (AP) to signal an unavailability period to a station. The soft AP may generate an unavailability notification (UA) frame including an unavailability configuration file. The unavailability profile includes information indicating an unavailability period of a soft AP interface of the soft AP. The soft AP may transmit the UA frame to one or more stations associated with the soft AP interface.

Description

Technical Field

[0001] The present application generally relates to wireless communication systems, including a framework for a soft access point to indicate periods of unavailability to stations. Background Art

[0002] Wireless communication technologies use various standards and protocols to transmit data between access points and wireless communication devices. For example, wireless communication system standards and protocols may include, for example, the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for wireless local area networks (WLANs) (commonly referred to within industry organizations as IEEE). ).

[0003] In the 802.11 standard for WLAN, an access point (AP) is a device that creates a wireless local area network (WLAN) or An AP is a device that connects to a wired network (such as an Ethernet network) and provides wireless access to that network for other devices. A station is a device that can wirelessly connect to an AP to join a WLAN network. A station can be a laptop, smartphone, tablet, or any other device with a WLAN adapter.

[0004] AP and station use Various protocols have been established to improve the security of wireless communication networks. For example, simultaneous authentication of peers is the core authentication protocol of WPA3-Personal. Alliance-certified devices, including both access points (APs) and non-AP stations (STAs), must support the protocol. Summary of the Invention

[0005] Provided herein is a method performed by a soft access point (AP), the method comprising: generating an unavailability notification (UA) frame including an unavailability profile, wherein the unavailability profile includes information indicating an unavailability period of a soft AP interface of the soft AP; transmitting the UA frame to one or more stations (STAs) associated with the soft AP interface; and changing the operation of a radio component of the soft AP such that the soft AP interface becomes unavailable during the unavailability period indicated in the unavailability profile.

[0006] The present invention also provides a method performed by a station (STA), the method comprising: receiving an unavailability notification (UA) frame including an unavailability profile from a soft access point (AP), wherein the unavailability profile includes information indicating an unavailability period of a soft AP interface of the soft AP; determining the unavailability period of the soft AP interface based on the unavailability profile; and scheduling uplink frame exchanges so that any of the uplink frame exchanges is not initiated during the unavailability period.

[0007] Also provided herein is an apparatus comprising means for performing the method herein.

[0008] Also provided herein is a computer-readable medium comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method herein.

[0009] Also provided herein is an apparatus comprising logical components, modules or circuits for executing the methods herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0011] Figure 1A An example timeline of operation of a Soft AP according to some embodiments is illustrated.

[0012] Figure 1B An example timeline of operation of a UHR soft AP according to some embodiments is illustrated.

[0013] Figure 2 An example UE operating as a soft AP in accordance with some embodiments is illustrated.

[0014] Figure 3 Illustrated is an example signaling diagram of a STA attempting to transmit an uplink frame exchange to a Soft AP in accordance with some embodiments.

[0015] Figure 4 An example transmission timeline including notification of unavailability is illustrated according to some embodiments.

[0016] Figure 5 An example timeline is illustrated in accordance with some embodiments, where the TXOP duration requested by the UHR STA does not overlap with the Soft AP unavailability period.

[0017] Figure 6An example timeline is illustrated according to some embodiments, where the TXOP duration requested by the UHR STA does overlap with the Soft AP unavailability period, and the UHR STA device is unable to dynamically adjust the PPDU / TXOP.

[0018] Figure 7 An example timeline is illustrated in accordance with some embodiments, where the TXOP duration requested by a UHR STA does overlap with the Soft AP unavailability period, and the UHR STA device is able to dynamically adjust the PPDU / TXOP.

[0019] Figure 8 An example frame format of a UA frame according to some embodiments is illustrated.

[0020] Figure 9 An example transmission timeline is illustrated in accordance with some embodiments, where a UHR soft AP transmits a management frame that includes a field indicating that a period of unavailability may exist.

[0021] Figure 10 Example methods performed by a soft AP according to some embodiments are illustrated.

[0022] Figure 11 Example methods performed by a STA according to some embodiments are illustrated.

[0023] Figure 12 An example system for performing signaling between a wireless device and a network device according to embodiments disclosed herein is illustrated. DETAILED DESCRIPTION

[0024] Wireless communication technology uses various standards and protocols to send data between access points and wireless communication devices. One standard for wireless communication is the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for wireless local area networks (WLANs), commonly referred to within the industry as ). Provides a convenient way to establish a network between devices. Devices (e.g., stations) can connect to Access point to join a network and connect to the Internet wirelessly. Security is important to protect data and devices from unauthorized access.

[0025] Various embodiments are described with respect to stations (STAs) (e.g., user equipment (UE)) and access points (APs). However, references to STAs and APs are provided for illustrative purposes only. Example embodiments may be used with any electronic component that can establish a connection to a network and is configured with hardware, software, and / or firmware to exchange information and data with the network. Therefore, as described herein, STAs and APs are intended to represent any suitable electronic component.

[0026] A soft access point (soft AP) is a software-based access point that enables devices to connect to a wireless network. Unlike traditional APs that use dedicated hardware, soft APs are implemented in software, allowing devices to emulate the functionality of a physical AP. Soft APs are often used in scenarios where physical access points are unavailable or impractical, such as in mobile devices, laptops, or other systems that require self-organizing networking capabilities. These software-based APs can facilitate the creation of wireless networks and support connectivity for multiple devices, providing a flexible and adaptable solution for wireless communication.

[0027] For example, a cell phone may include hotspot functionality. When the hotspot functionality is enabled, the cell phone can act as a Wi-Fi access point (AP) to which other devices can connect and access the Internet. The hotspot functionality can be enabled by software.

[0028] Soft APs consume significant amounts of power, which can be detrimental to battery-powered devices. This increased power consumption is primarily due to the intensive processing and radio transmission operations required to emulate the functionality of a physical access point. Because a Soft AP continuously processes and transmits data to facilitate wireless connectivity for multiple devices, it places a constant demand on the device battery. Furthermore, the continuous operation of the Soft AP can prevent the device's radio components from entering low-power mode, further impacting battery life. This leads to accelerated depletion of the device's battery. For battery-powered devices, the increased power consumption associated with Soft AP functionality presents challenges in maintaining optimal battery life and user experience.

[0029] Therefore, mitigating the power consumption of soft APs is crucial to ensuring efficient operation and extending battery life in such devices.Embodiments herein describe methods, systems, and apparatus for optimizing the operation of soft APs.

[0030] Figure 1AAn example timeline 102 of the operation of a soft AP according to some embodiments is illustrated. As shown, the soft AP is always active and operates in full capability mode 104. Operating in full capability mode 104 means that the soft AP is supporting the maximum supported channel bandwidth, and all RF chains and all antennas are active. In the illustrated configuration, it is expected that the soft AP is always on or always available for use by associated devices. This means that the soft AP device will always consume a large amount of power.

[0031] This ensures that the soft AP is ready and able to receive uplink frames 106 from the associated STAs. However, in this illustrated embodiment, the soft AP remains active even when no useful frames are being exchanged with the associated STAs, thereby wasting power. Therefore, it may be desirable to allow the soft AP to enter a lower power mode when not participating in communications with the associated STAs.

[0032] For example, Figure 1B An example timeline 108 of the operation of an ultra-high reliability (UHR) soft AP according to some embodiments is illustrated. The UHR soft AP is capable of operating in both a full capability mode 110 and a low-power listening mode 112. When not actively participating in the transmission / reception of Wi-Fi frames, the UHR soft AP switches to operation in the low-power listening mode 112. The UHR soft AP can switch to the full capability mode 110 to exchange frames with associated stations. In the low-power listening mode 112, the soft AP can use less power than when in the full capability mode 110. Some embodiments herein describe how to further optimize the use of the low-power listening mode 112 and the transition between the full capability mode 110 and the low-power listening mode 112.

[0033] Soft APs can be implemented in different ways. For example, in some embodiments, a soft AP may include a single primary radio that switches between low-power listening mode and full-capability mode. In some embodiments, a soft AP may include a secondary radio or scanning radio for low-power listening mode and a primary radio for full-capability mode. For a soft AP, the radio is likely shared with the STA interface and other interfaces within the same device. For example, in addition to the soft AP interface and STA interface, the radio may be shared with in-device coexistence technologies such as Bluetooth, ultra-wideband, etc.

[0034] For example, Figure 2An example UE 202 is illustrated operating as a soft AP. UE 202 acts as two different classes of device. As shown in the illustrated embodiment, UE 202 maintains both a soft AP interface 206 and other in-device interfaces 204 (e.g., InfraSTA, in-device coexistence technologies (e.g., Bluetooth, ultra-wideband, etc.)). UE 202 includes one or more radio components (e.g., a scanning radio component and a master radio component) shared between the soft AP interface 206 and the other in-device interfaces 204.

[0035] Because multiple in-device interfaces share the same radio resources, there may be reasons why a SoftAP may be unavailable to its associated devices. For example, when the scanning radio or the primary radio is busy at one or more in-device interfaces 204, the SoftAP may be unable to simultaneously serve its associated STAs via the SoftAP interface 206. This type of SoftAP unavailability can be short-term and can be periodic or aperiodic. Furthermore, in some cases, a SoftAP may be unavailable for energy conservation reasons, which may result in long-term, periodic unavailability.

[0036] The scanning radio component can be used for high-priority operations in other in-device interfaces 204, such as STA interfaces, in-device coexistence technologies (such as Bluetooth, ultra-wideband, etc.). For example, the scanning radio component can be used by the STA interface 204 for passive channel scanning. In addition, the scanning radio component can be used by other in-device interfaces 204 for technologies such as UWB, Thread, etc. The main radio component may be busy with channel scanning or in-device coexistence activities or peer-to-peer activities in other in-device interfaces 204.

[0037] During these times when other in-device interfaces 204 are using radio resources, STAs associated with the soft AP may not be able to use the soft AP interface 206. Therefore, it may be desirable to have a framework for the UHR soft AP to advertise a short-term unavailability schedule (if known) to associated UHR STAs. One benefit of such a framework is that it prevents UHR STAs from initiating frame exchanges with the UHR soft AP when the UHR soft AP is unavailable.

[0038] Figure 3 An example signaling diagram 306 illustrates an STA 304 attempting to transmit an uplink frame exchange to the soft AP 302. Signaling of unavailability periods from the soft AP 302 can benefit both the soft AP 302 as well as the STA 304.

[0039] For example, if STA 304 is not informed of the unavailability of soft AP 302, STA 304 may continuously initiate uplink frame exchanges with soft AP 302 while the soft AP is unavailable. This may result in consecutive frame failures in the uplink due to the unavailability of soft AP 302. Due to the frame failures, STA 304 may take undesirable steps. For example, STA 304 may drop to a lower data rate and / or drop packets. In addition, the lower data rate for uplink transmissions may result in a longer duration for sending pending data payloads. This may cause soft AP 302 to spend more time in an active receive state, resulting in higher energy consumption at soft AP 302. These effects may be exacerbated when soft AP 302 is unavailable for a significant period of time (e.g., a longer coexistence / P2P / roaming scan, tens of milliseconds long).

[0040] Signaling unavailability can also benefit STA 304. If STA 304 is unaware of the unavailability schedule of soft AP 302, several consecutive uplink frames from STA 304 to soft AP 302 may fail. Due to uplink frame failures, STA 304 may invoke rate adaptation and drop to a lower rate, resulting in poor uplink latency performance and longer active transmission time to clear uplink payloads. This may lead to higher energy consumption for STA 304. STA 304 may choose to drop packets due to exceeding retry limits. Due to the continuous transmission of ICFs, energy consumption at the STA may increase. The STA may double its contention window after each frame failure, resulting in longer channel access delays. The medium may be flooded with unnecessary ICFs, especially if multiple STAs are associated with the soft AP. Long-duration unavailability at the soft AP can exacerbate these problems. These effects can be exacerbated when soft AP unavailability extends for a significant period of time.

[0041] Some embodiments herein provide a framework for preventing or reducing such undesirable effects. For example, some embodiments include signaling of unavailability periods from the soft AP 302. Signaling of unavailability periods from the soft AP 302 can benefit devices acting as soft APs as well as STAs.

[0042] Figure 4 An example transmission timeline 402 including an announcement of unavailability according to some embodiments is illustrated. A soft AP may broadcast an announcement to indicate aperiodic, short-term unavailability to associated STAs. In some embodiments, soft AP unavailability may not be deterministic or periodic and may be known only a short time in advance.

[0043] As shown, a UHR soft AP may transmit a frame to associated STAs indicating a soft AP unavailability period 406. Signaling of the unavailability schedule may be transmitted in a new control frame called an unavailability notification (UA), such as a UA frame 404. The UA frame 404 may be broadcast by the soft AP to all associated STAs. For example, the receiver address field of the UA frame 404 may be set to a broadcast address (i.e., RA = Broadcast Address). The UHR soft AP transmits a UA frame (RA = Broadcast Address) with information about the upcoming unavailability period (start time and duration).

[0044] As shown, the UA frame 404 may include an RA field set to broadcast. The UA frame 404 may also include a transmitter address (TA) field set to the soft AP address of the UA frame 404. The TA field may help STAs identify the transmitter of the UA frame 404 within the wireless network. The UA frame 404 may also include an unavailability profile. The unavailability profile may include the start time of the unavailability period 406 and the duration of the unavailability period 406.

[0045] All associated UHR STAs that are awake (e.g., not in power save mode) receive the UA frame 404. The UHR STAs use the received UA frame 404 to determine the start and duration of the upcoming unavailability period 406. Thus, by using the UA frame 404, the UHR STAs are aware of the impending unavailability of the soft AP. During the unavailability period 406 signaled by the soft AP in the UA frame 404, the UHR STAs refrain from initiating any uplink frame exchanges. The UHR STAs may exchange frames with the UHR soft AP before or after the unavailability period 406.

[0046] In some embodiments, to improve signaling robustness, the soft AP may choose to transmit UA frame 404 multiple times. For example, in the illustrated embodiment, the soft AP optionally transmits UA frame 404, a second UA frame 408, and a third UA frame 410. In some embodiments, the multiple UA frames may be periodic. Multiple transmissions increase the chances that the UHR STA will receive the information.

[0047] In some embodiments, request-response signaling may be used to indicate soft AP availability. For example, a UHR STA may send a request to a soft AP, and the soft AP may respond to the UHR with information about the upcoming unavailability period (e.g., a UA frame). In some embodiments, the UHR STA should initiate each transmit opportunity (TXOP) using an Initial Control Frame (ICF) unicast to the soft AP. In response to the ICF received from the UHR STA, the UHR soft AP may indicate the upcoming unavailability profile in a UA frame. The unavailability profile may include the start time and duration of the soft AP's unavailability period. In some embodiments, the UA frame may be broadcast addressed so that all associated awake UHR STAs become aware of the upcoming unavailability. During the unavailability period signaled by the soft AP in the UA frame, the UHR STA may refrain from initiating any uplink frame exchanges.

[0048] Additionally, for this request-response signaling framework, the Soft AP can adjust its response based on the UHR STA's capabilities. Some UHR STAs may not be able to adjust the PPDU / TXOP duration based on the unavailability profile received in the UA frame. Some UHR STAs are able to dynamically adjust the PPDU / TXOP duration based on the unavailability profile signaled in the UA frame. The UA frame response may vary based on the STA's capabilities.

[0049] For example, Figure 5 and Figure 6 Two example transmission timelines for a UHR soft AP communicating with a UHR STA that cannot dynamically adjust PPDU / TXOP are illustrated. Specifically, Figure 5 An example timeline 502 is illustrated in which a TXOP duration 504 requested by a UHR STA does not overlap with a soft AP unavailability period 506 . Figure 6 An example timeline 602 is illustrated where a TXOP duration 604 requested by a UHR STA does overlap with a soft AP unavailability period 606 .

[0050] refer to Figure 5, if the UHR STA is unable to dynamically adjust the PPDU / TXOP and the uplink TXOP duration 504 does not overlap with the soft AP unavailability period 506, the soft AP may allow the UHR STA to send an uplink PPDU frame 508. Whenever the STA wants to initiate an uplink frame exchange, it may transmit an ICF 510. The ICF 510 may request the uplink TXOP duration 504. In the illustrated embodiment, the UHR soft AP receives the ICF 510 and determines that the UHR STA is unable to dynamically adjust the PPDU / TXOP. The UHR soft AP may determine whether the uplink TXOP duration 504 does not overlap with the soft AP unavailability period 506.

[0051] exist Figure 5 506. In response to the ICF 510, the UHR soft AP determines that the uplink TXOP duration 504 does not overlap with the soft AP unavailability period 506. In response to the ICF 510, the UHR soft AP sends a UA 512. Because the uplink TXOP duration 504 does not overlap with the soft AP unavailability period 506, the soft AP may set the duration field of the UA 512 to the time period requested by the UHR STA. The UA 512 may also include an unavailability profile with a start time and duration for the soft AP unavailability period 506. Because the duration field is set to the requested time, the UHR STA may continue to transmit uplink PPDU frames 508 to the UHR soft AP. In response, the UHR soft AP may transmit a block acknowledgment (BA) frame 514. The UHR STA may determine the soft AP unavailability period 506 based on the unavailability profile in the UA 512. During the soft AP unavailability period 506, the UHR STA refrains from initiating uplink frame exchanges.

[0052] refer to Figure 6 In the event that the UHR STA is unable to dynamically adjust the PPDU / TXOP and the uplink TXOP duration 604 does overlap with the soft AP unavailability period 606, the soft AP may request the STA to terminate the uplink TXOP. Whenever the STA wishes to initiate an uplink frame exchange, it may transmit an ICF 608. The ICF 608 may request the uplink TXOP duration 604. In the illustrated embodiment, the UHR soft AP receives the ICF 608 and determines that the UHR STA is unable to dynamically adjust the PPDU / TXOP. The UHR soft AP may determine whether the uplink TXOP duration 604 requested in the ICF overlaps with the soft AP unavailability period 606.

[0053] exist Figure 6In FIG6 , the UHR soft AP determines that the uplink TXOP duration 604 overlaps with the soft AP unavailability period 606. In response to the ICF 608, the UHR soft AP sends a UA 610. Because the uplink TXOP duration 604 overlaps with the soft AP unavailability period 606, the soft AP may set the duration field in the MAC header of the UA 610 to zero. Setting the duration field to zero may indicate to the STA to terminate the UL TXOP. The UA 610 may also include an unavailability profile with a start time and duration of the soft AP unavailability period 606. Since the duration field is set to zero, the UHR STA may terminate the uplink UL TXOP. The UHR STA may determine the soft AP unavailability period 606 based on the unavailability profile in the UA 610. During the soft AP unavailability period 606, the UHR STA avoids initiating uplink frame exchanges.

[0054] Some UHR STA devices may be able to dynamically adjust PPDU / TXOP. Figure 7 An example timeline 702 is illustrated, in which the TXOP duration 704 requested by the UHR STA does overlap with the soft AP unavailability period 706, and the UHR STA device is able to dynamically adjust the PPDU / TXOP. Whenever the STA wants to initiate an uplink frame exchange, it can transmit an ICF 708. The ICF 708 can request the uplink TXOP duration 704.

[0055] In the illustrated embodiment, the UHR soft AP receives the ICF 708 and determines that the UHR STA is capable of dynamically adjusting the PPDU / TXOP. The UHR soft AP may determine whether the uplink TXOP duration 704, as requested in the ICF, overlaps with the soft AP unavailability period 706. In the illustrated example, the UHR soft AP determines that the uplink TXOP duration 704 overlaps with the soft AP unavailability period 706. Based on the UHR STA capabilities, the UHR soft AP may generate a UA 710 including a duration field set to a time until the start of the soft AP unavailability period 706. Setting the duration field of the UA 710 based on the time until the start of the soft AP unavailability period 706 truncates the TXOP so that it ends before the start of the soft AP unavailability period 706. The UA 710 may also include an unavailability profile with the start time and duration of the soft AP unavailability period 706.

[0056] In response to the ICF 708, the UHR soft AP sends a UA 710. The UHR receives the UA 710 and determines, based on the duration field, that the uplink TXOP duration has been shortened. Prior to the start of the soft AP unavailability, the STA limits the uplink TXOP. During the shortened duration, the UHR STA transmits an uplink PPDU frame 712 to the UHR soft AP. In response, the UHR soft AP may transmit a BA frame 714. The UHR STA may determine a soft AP unavailability period 706 based on the unavailability profile in the UA 710. During the soft AP unavailability period 706, the UHR STA refrains from initiating uplink frame exchanges.

[0057] In some embodiments (e.g., Figures 6 to 8 In the embodiment shown in FIG. 1 , the UHR STA may indicate to the UHR soft AP that it is capable of dynamically adjusting the PPDU / TXOP duration based on the unavailability profile received from the soft AP after the TXOP has been initiated. In some embodiments, such signaling may be accomplished by setting the capability field at association time or at some other time. If the UHR STA has explicitly indicated the capability to dynamically adjust the uplink PPDU / TXOP duration, the UHR soft AP may perform Figure 7 Otherwise, the soft AP can follow Figure 5 and Figure 6 The sequence described.

[0058] Figure 8 An example frame format of a UA frame 802 according to some embodiments is illustrated. A soft AP may generate and transmit the UA frame 802 to a UHR STA to notify the UHR STA of an upcoming unavailability period. As shown, the UA frame 802 may include a frame control field 804. The frame control field 804 may include control information for managing the transmission and reception of the UA frame 802. The UA frame 802 may also include a duration field 806. The duration field 806 may indicate the duration of time available for uplink from the UHR STA.

[0059] As shown, the UA frame 802 may also include an address field. For example, the UA frame 802 may include a receiver address field (RA field 808) to direct the frame to the appropriate STA within the wireless network. The UA frame 802 may also include a TA field 810, which is set to the soft AP address of the transmitting UA frame 802.

[0060] The UA frame 802 may also include an unavailability profile include field 812. The unavailability profile include field 812 may indicate whether the UA frame 802 includes an unavailability profile 816. For example, in some embodiments, the soft AP may set the unavailability profile include field 812 to 0xff if the unavailability profile 816 is available, and may set the unavailability profile include field 812 to 0x00 if the unavailability profile 816 is not available.

[0061] The unavailability profile 816 may include an unavailability start time field 814 and an unavailability duration field 818. The unavailability start time field 814 may indicate the start time of the upcoming period during which the soft AP will be unavailable. The unavailability duration field 818 may indicate the duration of the upcoming period during which the soft AP will be unavailable. Additionally, the UA frame 802 may include a frame check sequence (e.g., FCS field 820).

[0062] In some embodiments, the UHR Soft AP may also provide an indication that unavailability periods may exist on frames other than UA frames. For example, Figure 9 An example transmission timeline 902 is illustrated in accordance with some embodiments, wherein a UHR soft AP transmits a management frame 904 (e.g., a beacon, probe response, association response, or any other frame) that includes a field indicating a possible period of unavailability. If the associated UHR STA is active (not in a power-saving state), the previously described embodiments take effect. Such embodiments can be enhanced to better support STAs that are in a power-saving state when the UE frame is transmitted.

[0063] When the soft AP announces its impending unavailability (in UA frame 906), some associated UHR STAs may be in a power state. When the soft AP is unavailable and therefore fails, such STAs may initiate uplink transmissions to the soft AP. As previously described, UHR STAs may be required to initiate each uplink TXOP using an ICF.

[0064] To prevent undesirable effects (e.g., dropping to a lower data rate and / or dropping packets), the following can be implemented. The SoftAP can indicate to the UHR STA the possibility of a period of unavailability during a session. This indication can be provided before association (via a beacon / probe response frame), at association (via an association response frame), or after association (via a beacon frame). If an unavailability indication has been received from the SoftAP, the UHR STA should not consider the lack of a response to the ICF as a trigger for rate reduction / packet dropping.

[0065] For example, Figure 9As illustrated, the UHR soft AP may transmit a management frame 904 to a UHR STA. The management frame 904 may include a field indicating a possible period of unavailability. When the UHR STA receives the management frame 904 from the UHR soft AP, it may determine the likelihood of an unavailability period for the UHR soft AP based on the included field. If the field indicates that the soft AP is unlikely to have an unavailability period, the UHR STA may perform a rate reduction / packet drop in the absence of a response to an ICF. If the field indicates that the soft AP is likely to have an unavailability period, the UHR STA does not consider the lack of response to the ICF as a trigger for a rate reduction / packet drop in the absence of a response to the ICF.

[0066] For example, in Figure 9 904, a field in a management frame 904 sent by the UHR soft AP indicates that a period of unavailability may exist. In the illustrated example, the UHR STA enters power save mode 908, and while the UHR STA is in power save mode 908, the UHR soft AP transmits a UA frame 906. Due to the power save state of the UHR STA, the UHR STA fails to receive the UA frame 906. The UHR STA enters the active state 910 and sends one or more ICFs 912. The UHR soft AP fails to transmit a response to the ICF because the UHR soft AP is in an unavailability period 914. Due to the previous indication of unavailability by the soft AP via the management frame 904, the failure of the ICF should not result in a rate drop or packet drops at the UHR STA.

[0067] As described herein, it is desirable to design a scheme that enables a UHR soft AP to notify a UHR STA of an unavailability schedule (both short-term and long-term). This unavailability may be due to critical operations in other interfaces (channel scanning in the STA interface, in-device coexistence activities, peer events, etc.). One benefit of such notification is that when a soft AP is unavailable, the UHR STA is prevented from initiating a frame exchange with the soft AP. The embodiments herein propose a mechanism for signaling short-term (or near-term) non-periodic unavailability. In some embodiments, a broadcast control frame (e.g., unavailability notification) is used for short-term unavailability notification. In some embodiments, short-term unavailability signaling can be performed through a request-response frame exchange.

[0068] Figure 10An example method 1000 performed by a soft AP according to some embodiments is illustrated. The illustrated method includes generating 1002 a UA frame including an unavailability profile, wherein the unavailability profile includes information indicating an unavailability period for a soft AP interface of the soft AP. The method 1000 also includes transmitting 1004 the UA frame to one or more STAs associated with the soft AP interface. The method 1000 also includes changing 1006 the operation of a radio component of the soft AP such that the soft AP interface becomes unavailable during the unavailability period indicated in the unavailability profile.

[0069] In some embodiments, method 1000 further includes transmitting the UA frame multiple times before the unavailability period.

[0070] In some embodiments, the unavailability profile includes a start time and a duration of the unavailability period.

[0071] In some embodiments, method 1000 further includes receiving an ICF specifying a requested TXOP duration from one of the STAs, wherein the UA frame is transmitted in response to the ICF.

[0072] In some embodiments, the UA frame is an unsolicited broadcast.

[0073] In some embodiments, the method 1000 further includes receiving an indication from the first STA that the first STA is capable of dynamically adjusting the TXOP duration and the PPDU duration after the TXOP has been initiated.

[0074] In some embodiments, the indication includes a capabilities field transmitted during association.

[0075] In some embodiments, method 1000 further includes: when the first STA cannot dynamically adjust, determining whether the requested TXOP duration specified by the first STA in the ICF overlaps with the unavailability period; if the requested TXOP duration overlaps with the unavailability period, setting the duration field of the UA frame to zero to terminate the uplink TXOP; and if the requested TXOP duration does not overlap with the unavailability period, setting the duration field of the UA frame to the requested TXOP duration.

[0076] In some embodiments, method 1000 further includes, when the first STA is capable of dynamic adjustment, setting the duration field in the UA frame to a time until the start of the unavailability period if the requested TXOP duration specified by the STA in the ICF overlaps with the unavailability period.

[0077] In some embodiments, the UA frame includes a field indicating whether the unavailability profile is included.

[0078] In some embodiments, method 1000 further includes sending an indication in the beacon regarding the likelihood of future unavailability periods.

[0079] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of method 1000. The apparatus may be, for example, an AP (such as AP 1218, as described herein).

[0080] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 1000. The non-transitory computer-readable medium may be, for example, a memory of an AP (such as memory 1222 of AP 1218, as described herein).

[0081] Embodiments contemplated herein include an apparatus comprising logical components, modules, or circuits operable to perform one or more elements of method 1000. The apparatus may be, for example, an AP, such as AP 1218, as described herein.

[0082] Embodiments contemplated herein include an apparatus comprising one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 1000. The apparatus may be, for example, an AP, such as AP 1218, as described herein.

[0083] Embodiments contemplated herein include a signal as described in or associated with one or more elements of method 1000 .

[0084] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element causes the processing element to perform one or more elements of method 1000. The processor may be a processor of an AP (such as processor 1220 of AP 1218, as described herein). The instructions may be located, for example, in the processor and / or in a memory of the AP (such as memory 1222 of AP 1218, as described herein).

[0085] Figure 11An example method 1100 performed by a STA according to some embodiments is illustrated. The method 1100 includes receiving 1102 a UA frame from a soft AP that includes an unavailability profile, wherein the unavailability profile includes information indicating an unavailability period for a soft AP interface of the soft AP. The method 1100 also includes determining 1104 the unavailability period for the soft AP interface based on the unavailability profile. The method 1100 also includes scheduling 1106 uplink frame exchanges such that none of the uplink frame exchanges are initiated during the unavailability period.

[0086] In some embodiments, the method 1100 further includes receiving UA frames a plurality of times prior to the unavailability period.

[0087] In some embodiments, the unavailability profile includes a start time and a duration of the unavailability period.

[0088] In some embodiments, method 1100 further includes transmitting an ICF specifying the requested TXOP duration to the soft AP, wherein the UA frame is transmitted in response to the ICF.

[0089] In some embodiments, the UA frame is an unsolicited broadcast.

[0090] In some embodiments, the method 1100 further includes transmitting an indication to the soft AP that the STA can dynamically adjust the TXOP duration and the PPDU duration after the TXOP has been initiated.

[0091] In some embodiments, the indication includes a capabilities field transmitted during association.

[0092] In some embodiments, when the STA cannot dynamically adjust and whether the requested TXOP duration specified by the STA in the ICF overlaps with the unavailability period, if the requested TXOP duration overlaps with the unavailability period, the Duration field of the UA frame is set to zero to terminate the uplink TXOP, and if the requested TXOP duration does not overlap with the unavailability period, the Duration field of the UA frame is set to the requested TXOP duration.

[0093] In some embodiments, when the STA is capable of dynamic adjustment, in the event that the requested TXOP duration specified by the STA in the ICF overlaps with the unavailability period, the duration field in the UA frame is set to the time until the start of the unavailability period.

[0094] In some embodiments, the UA frame includes a field indicating whether the unavailability profile is included.

[0095] In some embodiments, method 1100 further includes receiving an indication in a beacon from the soft AP regarding the likelihood of a future unavailability period.

[0096] Embodiments contemplated herein include an apparatus comprising means for performing one or more elements of method 1100. The apparatus may be, for example, an apparatus of a STA, such as STA 1202, as described herein.

[0097] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 1100. The non-transitory computer-readable medium may be, for example, a memory of a STA (such as memory 1206 of STA 1202, as described herein).

[0098] Embodiments contemplated herein include an apparatus comprising logical components, modules, or circuits operable to perform one or more elements of the method 1100. The apparatus may be, for example, an apparatus of a STA, such as STA 1202, as described herein.

[0099] Embodiments contemplated herein include an apparatus comprising one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 1100. The apparatus may be, for example, an STA, such as STA 1202, as described herein.

[0100] Embodiments contemplated herein include a signal as described in or associated with one or more elements of method 1100 .

[0101] The embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor causes the processor to perform one or more elements of the method 1100. The processor may be a processor of a STA (such as the processor 1204 of the STA 1202, as described herein). The instructions may be located, for example, in the processor and / or in a memory of the STA (such as the memory 1206 of the STA 1202, as described herein).

[0102] Figure 12A system 1200 is illustrated for performing signaling 1234 between a STA 1202 and an AP 1218 according to embodiments disclosed herein. The system 1200 can be part of a wireless communication system as described herein. The STA 1202 can be, for example, a UE of the wireless communication system. The AP 1218 can be, for example, an access point or soft AP of the wireless communication system.

[0103] The STA 1202 may include one or more processors 1204. The processor 1204 may execute instructions to cause the various operations of the STA 1202 to be performed, as described herein. The processor 1204 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof, configured to perform the operations described herein.

[0104] STA 1202 may include memory 1206. Memory 1206 may be a non-transitory computer-readable storage medium that stores instructions 1208 (which may include, for example, instructions executed by processor 1204). Instructions 1208 may also be referred to as program code or a computer program. Memory 1206 may also store data used by processor 1204 and results computed by the processor.

[0105] STA 1202 may include one or more transceivers 1210, which may include radio frequency (RF) transmitter circuitry and / or receiver circuitry that uses an antenna 1212 of STA 1202 to facilitate signaling (e.g., signaling 1234) to and / or from STA 1202 with other devices (e.g., AP 1218).

[0106] STA 1202 may include one or more antennas 1212 (e.g., one, two, four, or more antennas). For implementations with multiple antennas 1212, STA 1202 may take full advantage of the spatial diversity of such multiple antennas 1212 to transmit and / or receive multiple different data streams on the same time-frequency resources. This behavior may be referred to as, for example, multiple-input multiple-output (MIMO) behavior (referring to the multiple antennas used at each of the transmitting device and the receiving device to implement this aspect). MIMO transmission by STA 1202 may be implemented based on precoding (or digital beamforming) applied at STA 1202, which multiplexes the data streams across the antennas 1212 based on known or assumed channel characteristics, so that each data stream is received with appropriate signal strength relative to the other streams and at a desired location in the spatial domain (e.g., the location of the receiver associated with the data stream). Certain embodiments may use single-user MIMO (SU-MIMO) methods (where data streams are all directed to a single receiver) and / or multi-user MIMO (MU-MIMO) methods (where separate data streams may be directed to separate (different) receivers in different locations in the spatial domain).

[0107] In certain embodiments with multiple antennas, STA 1202 may implement analog beamforming techniques whereby the phases of signals transmitted by antennas 1212 are relatively adjusted such that the (joint) transmissions of antennas 1212 are directed (this is sometimes referred to as beam steering).

[0108] The STA 1202 may include one or more interfaces 1214. The interfaces 1214 may be used to provide input to or output from the STA 1202. For example, the STA 1202, which is a UE, may include interfaces 1214, such as a microphone, a speaker, a touch screen, and buttons, to allow a user of the UE to provide input to and / or output to the UE. Other interfaces of such a UE may be composed of transmitters, receivers, and other circuits (e.g., in addition to the transceiver 1210 / antenna 1212 already described) that allow the UE to communicate with other devices, and may be configured according to known protocols (e.g., and etc.) to perform the operation.

[0109] STA 1202 may include an unavailability period module 1216. The unavailability period module 1216 may be implemented via hardware, software, or a combination thereof. For example, the unavailability period module 1216 may be implemented as a processor, circuitry, and / or instructions 1208 stored in memory 1206 and executed by processor 1204. In some examples, the unavailability period module 1216 may be integrated within the processor 1204 and / or transceiver 1210. For example, the unavailability period module 1216 may be implemented via a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuits) within the processor 1204 or transceiver 1210.

[0110] The unavailability period module 1216 may be used in various aspects of the present disclosure, for example, FIG. Figure 12 The unavailability period module 1216 is configured to determine an unavailability period of a soft AP (eg, AP 1218) based on the UA frame.

[0111] The AP 1218 may include one or more processors 1220. The processor 1220 may execute instructions to cause the various operations of the AP 1218 to be performed, as described herein. The processor 1220 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0112] AP 1218 may include memory 1222. Memory 1222 may be a non-transitory computer-readable storage medium that stores instructions 1224 (which may include, for example, instructions executed by processor 1220). Instructions 1224 may also be referred to as program code or a computer program. Memory 1222 may also store data used by processor 1220 and results computed by the processor.

[0113] AP 1218 may include one or more transceivers 1226, which may include RF transmitter circuitry and / or receiver circuitry that uses antenna 1228 of AP 1218 to facilitate signaling (e.g., signaling 1234) to and / or from AP 1218 with other devices (e.g., STA 1202).

[0114] AP 1218 may include one or more antennas 1228 (e.g., one, two, four, or more antennas). In embodiments with multiple antennas 1228, AP 1218 performs MIMO, digital beamforming, analog beamforming, beamsteering, etc., as already described.

[0115] The AP 1218 may include one or more interfaces 1230. The interfaces 1230 may be used to provide input to or output from the AP 1218. For example, the AP 1218 as a base station may include an interface 1230 composed of a transmitter, a receiver, and other circuits (e.g., in addition to the transceiver 1226 / antenna 1228 already described), which enables the base station to communicate with other equipment in the core network and / or enables the base station to communicate with external networks, computers, databases, etc., to achieve the purpose of operating, managing, and maintaining the base station or other equipment operably connected to the base station.

[0116] AP 1218 may include an unavailability period module 1232. Unavailability period module 1232 may be implemented via hardware, software, or a combination thereof. For example, unavailability period module 1232 may be implemented as a processor, circuitry, and / or instructions 1224 stored in memory 1222 and executed by processor 1220. In some examples, unavailability period module 1232 may be integrated within processor 1220 and / or transceiver 1226. For example, unavailability period module 1232 may be implemented via a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuits) within processor 1220 or transceiver 1226.

[0117] The unavailability period module 1232 may be used in various aspects of the present disclosure, for example, FIG. Figure 12 The unavailability period module 1232 is configured to generate a UA frame to indicate an unavailability period.

[0118] For one or more embodiments, at least one of the components described in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a processor described herein in conjunction with one or more of the preceding figures may be configured to operate according to one or more of the examples described herein. For another example, circuitry associated with a STA or AP described above in conjunction with one or more of the preceding figures may be configured to operate according to one or more of the examples described herein.

[0119] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of the various embodiments.

[0120] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing the operations; or may include a combination of hardware, software, and / or firmware.

[0121] It should be understood that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into a single system, partially combined into other systems, separated into multiple systems, or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be understood that unless expressly stated otherwise herein, these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment.

[0122] It is widely acknowledged that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0123] Although the foregoing has been described in considerable detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways of implementing both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method performed by a soft access point (AP), the method comprising: generating an unavailability notification (UA) frame including an unavailability profile, wherein the unavailability profile includes information indicating an unavailability period of a soft AP interface of the soft AP; transmitting the UA frame to one or more stations (STAs) associated with the soft AP interface; as well as Operation of a radio component of the soft AP is altered such that the soft AP interface becomes unavailable during the unavailability period indicated in the unavailability profile.

2. The method according to claim 1, further comprising: The UA frame is transmitted a plurality of times before the unavailability period. The method of claim 1 , wherein the unavailability profile comprises a start time and a duration of the unavailability period.

4. The method according to claim 1, further comprising: An initial control frame (ICF) specifying a requested transmit opportunity (TXOP) duration is received from one of the STAs, wherein the UA frame is transmitted in response to the ICF. The method of claim 1 , wherein the UA frame is an unsolicited broadcast.

6. The method according to claim 1, further comprising: An indication is received from a first STA that the first STA can dynamically adjust a transmit opportunity (TXOP) duration and a physical protocol data unit (PPDU) duration after a TXOP has been initiated. The method of claim 6 , wherein the indication comprises a capability field transmitted during association.

8. The method according to claim 6, further comprising: determining whether a requested TXOP duration specified by the first STA in an initial control frame (ICF) overlaps with the unavailability period when the first STA is unable to dynamically adjust; If the requested TXOP duration overlaps with the unavailability period, setting the duration field of the UA frame to zero to terminate the uplink TXOP; as well as If the requested TXOP duration does not overlap with the unavailability period, setting the Duration field of the UA frame to the requested TXOP duration.

9. The method according to claim 6, further comprising: When the first STA is capable of dynamic adjustment, in a case where a requested TXOP duration specified by the first STA in an initial control frame (ICF) overlaps with the unavailability period, setting the duration field in the UA frame to a time until the start of the unavailability period.

10. The method according to claim 1, wherein the UA frame includes a field indicating whether the unavailability profile is included.

11. The method according to claim 1 , further comprising: An indication in a beacon is sent regarding the likelihood of future unavailability periods.

12. A method performed by a station (STA), the method comprising: receiving an unavailability notification (UA) frame including an unavailability profile from a soft access point (AP), wherein the unavailability profile includes information indicating an unavailability period of a soft AP interface of the soft AP; determining the unavailability period of the soft AP interface based on the unavailability profile; as well as Uplink frame exchanges are scheduled such that none of the uplink frame exchanges are initiated during the unavailability period.

13. The method according to claim 12, further comprising: The UA frame is received a plurality of times before the unavailability period. The method of claim 12 , wherein the unavailability profile comprises a start time and a duration of the unavailability period.

15. The method according to claim 12, further comprising: An initial control frame (ICF) specifying a requested transmit opportunity (TXOP) duration is transmitted to the soft AP, wherein the UA frame is transmitted in response to the ICF.

16. The method of claim 12, wherein the UA frame is an unsolicited broadcast.

17. The method according to claim 12, further comprising: An indication is transmitted to the soft AP that the STA can dynamically adjust a transmit opportunity (TXOP) duration and a physical protocol data unit (PPDU) duration after a TXOP has been initiated.

18. The method of claim 17, wherein the indication comprises a capability field transmitted during association.

19. The method of claim 17 , wherein when the STA cannot dynamically adjust, whether a requested TXOP duration specified by the STA in an Initial Control Frame (ICF) overlaps with the unavailability period, and if the requested TXOP duration overlaps with the unavailability period, setting the Duration field of the UA frame to zero to terminate the uplink TXOP, and if the requested TXOP duration does not overlap with the unavailability period, setting the Duration field of the UA frame to the requested TXOP duration.

20. The method according to claim 17, wherein When the STA is capable of dynamic adjustment, in a case where the requested TXOP duration specified by the STA in an initial control frame (ICF) overlaps with the unavailability period, setting the duration field in the UA frame to a time until the start of the unavailability period.

21. The method of claim 12, wherein the UA frame includes a field indicating whether the unavailability profile is included.

22. The method according to claim 12, further comprising: An indication of the likelihood of a future unavailability period is received in a beacon from the soft AP.

23. An apparatus comprising means for performing the method according to any one of claims 1 to 22.

24. A computer-readable medium comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method according to any one of claims 1 to 22.

25. An apparatus comprising logic components, modules or circuits for performing the method according to any one of claims 1 to 22.

Images