Target wake time parameter renegotiation

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a first peripheral device may receive target wake time (TWT) information and an associated identifier (AID) for a second peripheral device. The first peripheral device may monitor for data for the second peripheral device using the AID of the second peripheral device, based on a determination, from the TWT information, that a second sleep duration of a second TWT of the second peripheral device is greater than a first sleep duration of a first TWT of the first peripheral device. The first peripheral device may renegotiate the first TWT with a central device to obtain a new first TWT. The first peripheral device may monitor, using the new first TWT, for a beacon having data for the second peripheral device based on the AID of the second peripheral device. Numerous other aspects are described.

Description

2500711W0 1TARGET WAKE TIME PARAMETER RENEGOTIATIONCROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Application claims priority to U.S. Patent Application No. 19 / 010,382, filed on January 6, 2025, entitled “TARGET WAKE TIME PARAMETER RENEGOTIATION,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application.FIELD OF THE DISCLOSURE

[0002] Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods associated with renegotiating a target wake time.BACKGROUND

[0003] Wireless communication systems are widely deployed to provide various services, which may involve carrying or supporting voice, text, other messaging, video, data, and / or other traffic. Typical wireless communication systems may employ multiple-access radio access technologies (RATs) capable of supporting communication among multiple wireless communication devices including user devices or other devices by sharing the available system resources (for example, time domain resources, frequency domain resources, spatial domain resources, and / or device transmit power, among other examples). Such multiple-access RATs are supported by technological advancements that have been adopted in various telecommunication standards, which define common protocols that enable different wireless communication devices to communicate on a local, municipal, national, regional, or global level.

[0004] An example telecommunication standard is New Radio (NR). NR, which may also be referred to as 5G, is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP). NR (and other RATs beyond NR) may be designed to better support enhanced mobile broadband (eMBB) access, Internet of things (loT) networks or reduced capability device deployments, and ultra-reliable low latency communication (URLLC) applications. To support these verticals, NR systems may be designed to implement a modularized functional infrastructure, a disaggregated and service-based network architecture, network function virtualization, network slicing, multi-access edge computing, millimeter wave (mmWave) technologies including massive multiple -input multiple-output (MIMO), licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelink and other device-to-device direct communication technologies (for example, cellular vehicle-to-everything (CV2X) communication), multiple-subscriber implementations, high-precision0097-6044PCT2500711W0 2positioning, and / or radio frequency (RF) sensing, among other examples. As the demand for connectivity continues to increase, further improvements in NR may be implemented, and other RATs, such as 6G and beyond, may be introduced to enable new applications and facilitate new use cases.

[0005] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (for example, time, frequency, and power). A wireless network (e.g., a wireless local area network (WLAN), such as a Wi-Fi (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11) network) may include an access point (AP) that may communicate with one or more stations (STAs) or mobile devices. The AP may be coupled to a network, such as the Internet, and may enable a mobile device to communicate via the network (or communicate with other devices coupled to the access point). A wireless device may communicate with a network device bi-directionally. For example, in a WLAN, a STA may communicate with an associated AP via downlink and uplink. “Downlink” may refer to the communication link from the AP to the station, and “uplink” may refer to the communication link from the station to the AP.

[0006] The AP may enable a mobile device to communicate via the network (or communicate with other devices coupled to the access point). A wireless device may communicate with a network device bi-directionally. For example, in a WLAN, a device may communicate with an associated AP via downlink (e.g., the communication link from the AP to the device) and uplink (e.g., the communication link from the device to the AP). A wireless personal area network (WPAN), which may include a Bluetooth® connection, may provide for short range wireless connections between two or more paired wireless devices. For example, wireless devices such as cellular phones may utilize WPAN communications to exchange information such as audio signals with wireless headsets.

[0007] A wireless device may communicate using a short-range wireless protocol, such as a Bluetooth protocol, and may connect and exchange information between devices and paired devices (for example, between mobile phones, computers, digital cameras, wireless headsets, speakers, keyboards, mice or other input peripherals, and similar devices).SUMMARY

[0008] Some aspects described herein relate to a method of wireless communication performed by a first peripheral device. The method may include receiving target wake time (TWT) information and an associated identifier (AID) for a second peripheral device. The method may include monitoring for data for the second peripheral device using the AID of the second peripheral device, based at least in part on a determination, from the TWT information, 0097-6044PCT2500711W0 3that a second sleep duration of a second TWT of the second peripheral device is greater than a first sleep duration of a first TWT of the first peripheral device. The method may include renegotiating the first TWT with a central device to obtain a new first TWT. The method may include monitoring, using the new first TWT, for a beacon having data for the second peripheral device based at least in part on the AID of the second peripheral device.

[0009] Some aspects described herein relate to a method of wireless communication performed by a second peripheral device. The method may include negotiating a TWT with a central device based at least in part on a sleep duration rule. The method may include transmitting, to a first peripheral device, TWT information for the TWT and an AID. The method may include sleeping based at least in part on the TWT. The method may include receiving a wake up signal from the first peripheral device. The method may include renegotiating the TWT to obtain a new TWT.

[0010] Some aspects described herein relate to an apparatus for wireless communication at a first peripheral device. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to receive TWT information and an AID for a second peripheral device. The one or more processors may be individually or collectively configured to monitor for data for the second peripheral device using the AID of the second peripheral device, based at least in part on a determination, from the TWT information, that a second sleep duration of a second TWT of the second peripheral device is greater than a first sleep duration of a first TWT of the first peripheral device. The one or more processors may be individually or collectively configured to renegotiate the first TWT with a central device to obtain a new first TWT. The one or more processors may be individually or collectively configured to monitor, using the new first TWT, for a beacon having data for the second peripheral device based at least in part on the AID of the second peripheral device.

[0011] Some aspects described herein relate to an apparatus for wireless communication at a second peripheral device. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to negotiate a TWT with a central device based at least in part on a sleep duration rule. The one or more processors may be individually or collectively configured to transmit, to a first peripheral device, TWT information for the TWT and an AID. The one or more processors may be individually or collectively configured to sleep based at least in part on the TWT. The one or more processors may be individually or collectively configured to receive a wake up signal from the first peripheral device. The one or more processors may be individually or collectively configured to renegotiate the TWT to obtain a new TWT.0097-6044PCT2500711W0 4

[0012] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a first peripheral device. The set of instructions, when executed by one or more processors of the first peripheral device, may cause the first peripheral device to receive TWT information and an AID for a second peripheral device. The set of instructions, when executed by one or more processors of the first peripheral device, may cause the first peripheral device to monitor for data for the second peripheral device using the AID of the second peripheral device, based at least in part on a determination, from the TWT information, that a second sleep duration of a second TWT of the second peripheral device is greater than a first sleep duration of a first TWT of the first peripheral device. The set of instructions, when executed by one or more processors of the first peripheral device, may cause the first peripheral device to renegotiate the first TWT with a central device to obtain a new first TWT. The set of instructions, when executed by one or more processors of the first peripheral device, may cause the first peripheral device to monitor, using the new first TWT, for a beacon having data for the second peripheral device based at least in part on the AID of the second peripheral device.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a second peripheral device. The set of instructions, when executed by one or more processors of the second peripheral device, may cause the second peripheral device to negotiate a TWT with a central device based at least in part on a sleep duration rule. The set of instructions, when executed by one or more processors of the second peripheral device, may cause the second peripheral device to transmit, to a first peripheral device, TWT information for the TWT and an AID. The set of instructions, when executed by one or more processors of the second peripheral device, may cause the second peripheral device to sleep based at least in part on the TWT. The set of instructions, when executed by one or more processors of the second peripheral device, may cause the second peripheral device to receive a wake up signal from the first peripheral device. The set of instructions, when executed by one or more processors of the second peripheral device, may cause the second peripheral device to renegotiate the TWT to obtain a new TWT.

[0014] Some aspects described herein relate to a first apparatus for wireless communication. The first apparatus may include means for receiving TWT information and an AID for a second apparatus; means for monitoring for data for the second apparatus using the AID of the second apparatus, based at least in part on a determination, from the TWT information, that a second sleep duration of a second TWT of the second apparatus is greater than a first sleep duration of a first TWT of the first apparatus; means for renegotiating the first TWT with a central device to obtain a new first TWT; and means for monitoring, using the new first TWT, for a beacon having data for the second apparatus based at least in part on the AID of the second apparatus.0097-6044PCT2500711W0 5

[0015] Some aspects described herein relate to a second apparatus for wireless communication. The second apparatus may include means for negotiating a TWT with a central device based at least in part on a sleep duration rule; means for transmitting, to a first apparatus, TWT information for the TWT and an AID; means for sleeping based at least in part on the TWT; means for receiving a wake up signal from the first apparatus; and means for renegotiating the TWT to obtain a new TWT.

[0016] Aspects of the present disclosure may generally be implemented by or as a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, network entity, wireless communication device, and / or processing system as substantially described with reference to, and as illustrated by, this specification and accompanying drawings.

[0017] The foregoing paragraphs of this section have broadly summarized some aspects of the present disclosure. These and additional aspects and associated advantages will be described hereinafter. The disclosed aspects may be used as a basis for modifying or designing other aspects for carrying out the same or similar purposes of the present disclosure. Such equivalent aspects do not depart from the scope of the appended claims. Characteristics of the aspects disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying drawings.BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The appended drawings illustrate some aspects of the present disclosure but are not limiting of the scope of the present disclosure because the description may enable other aspects. Each of the drawings is provided for purposes of illustration and description, and not as a definition of the limits of the claims. The same or similar reference numbers in different drawings may identify the same or similar elements.

[0019] Fig. 1 shows a wireless communication network, in accordance with the present disclosure.

[0020] Fig. 2 illustrates an example of a wireless communication network that supports low-latency parameter updates for extended personal audio networks in accordance with the present disclosure.

[0021] Fig. 3 is a diagram illustrating an example of a wireless communication device, in accordance with the present disclosure.

[0022] Fig. 4 is a diagram illustrating examples of target wake time (TWT) information, in accordance with the present disclosure.0097-6044PCT2500711W0 6

[0023] Fig. 5 is a diagram illustrating an example associated with TWT renegotiation, in accordance with the present disclosure.

[0024] Fig. 6 is a diagram illustrating an example process performed, for example, at a first peripheral device or an apparatus of a first peripheral device, in accordance with the present disclosure.

[0025] Fig. 7 is a diagram illustrating an example process performed, for example, at a second peripheral device or an apparatus of a second peripheral device, in accordance with the present disclosure.

[0026] Fig. 8 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.DETAILED DESCRIPTION

[0027] Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Some or all of the described examples may be implemented in any device, system or network that is capable of transmitting and receiving radio frequency (RF) signals according to one or more of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards, the IEEE 802.15 standards, the Bluetooth® standards as defined by the Bluetooth Special Interest Group (SIG), or the Long Term Evolution (LTE), 3G, 4G, 5G (New Radio (NR)) or 6G standards promulgated by the 3rd Generation Partnership Project (3GPP), among others. One skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0028] Devices, such as peripheral devices, may use target wake time (TWT) scheduling to conserve battery power and to avoid uplink access contention. TWT allows a central device, such as an access point (AP), to manage activity in the basic service set (BSS) in order to minimize contention between the devices and to reduce the required amount of time that a device utilizing a power management mode needs to be awake. The AP may schedule TWT0097-6044PCT2500711W0 7time durations during which a device is awake (service interval) and / or has uplink access to the wireless network. The device is otherwise asleep (sleep duration) and / or does not have uplink access to the network.

[0029] Peripheral devices, such as earbuds, may follow a TWT-based power saving mode to dictate a sleep interval or duration that helps to improve power compensation as compared to legacy power saving modes. Based on the service period (periodicity of service intervals) or service interval (service time duration of a sleep cycle) that is negotiated, earbuds can enter sleep cycles. During the service intervals, packets can be communicated to and from the central device (e.g., AP). The service period, service interval, and other TWT parameters may be negotiated based on the current operating requirements or use case. Longer service intervals can provide better power efficiency. However, longer service intervals can cause latency in communicating with an earbud if there is any pending data from the central device.

[0030] According to various aspects described herein, one peripheral device of a pair of peripheral devices may renegotiate a sleep duration of a new TWT with a central device. The sleep duration may be negotiated based at least in part on conditions (e.g., battery, low traffic) of the peripheral device and / or a length of the sleep duration compared to the sleep duration of a peer peripheral device. The sleep duration of the peripheral device may be moved to a longer sleep interval after the TWT renegotiation. The peripheral device may indicate the service interval and association details to a peer peripheral device via a Bluetooth (BT) link. The peer peripheral device may also renegotiate for a new TWT to ensure that at least one beacon will be received during the service interval of the peer peripheral device. The peer peripheral device in a service interval may identify any data (e.g., control information, audio set up information, audio parameters, power parameters, audio stream data) in such a beacon that is pending for the peripheral device, which may be in a longer sleep duration. The data may then be communicated from the peer peripheral device to the peripheral device via the BT link. The peripheral device may exit the TWT sleep and collect the pending data from the AP. After collecting the data, the peripheral device may check the present conditions to return to a longer service interval or to renegotiate a new service interval. The peer peripheral device may also select a different service interval if the peripheral device is not using a long service interval.

[0031] Various aspects relate generally to power management for peripheral devices. Some aspects more specifically relate to one peripheral device of a pair of peripheral devices that may renegotiate a sleep duration of a new TWT. The sleep duration may be negotiated based at least in part on conditions (e.g., battery, low traffic) of the peripheral device. The sleep duration of the peripheral device may be moved to a longer sleep interval after the TWT renegotiation. The peripheral device may indicate the service interval and association details to a peer peripheral device via a BT link. The peer peripheral device may also renegotiate for a new TWT to ensure that at least one beacon will be received during the service interval of the peer peripheral device.0097-6044PCT2500711W0 8If the peer peripheral device in a service interval identifies any data (e.g., control information, audio set up information, audio parameters, power parameters, audio stream data) pending for the peripheral device that is in a longer sleep duration, the peer peripheral device may trigger the peripheral device to wake up and receive the data from the central device. Data may also be communicated from the peer peripheral device to the peripheral device via the BT link. The peripheral device may exit the TWT sleep and collect the pending data from the AP. After collecting the data, the peripheral device may check the present conditions to return to a longer service interval or to renegotiate a new service interval. The peer peripheral device may also select a different service interval if the peripheral device is not using a long service interval.

[0032] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. By renegotiating a TWT sleep duration of a TWT power save method, the AP and the peripheral devices may determine a service interval to save power as compared to legacy power save modes, while reducing latency.

[0033] Several aspects of wireless communication networks will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, and / or algorithms, among other examples (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0034] In some wireless communication networks, a wireless communication device (WCD) may support applications associated with low-latency or lossless audio to one or more other devices, such as one or more personal audio devices. For example, a wireless communication device may support applications and use cases associated with ultra-low-latency (ULL), such as ULL gaming, or streaming lossless audio to one or more personal audio devices (for example, peripheral devices) of a user. In scenarios in which a user uses two peripheral devices, the wireless communication device may support an extended personal audio network (XPAN) via which the wireless communication device may communicate with the two peripheral devices. To meet latency or lossless criteria associated with an application or use case, XPAN devices may employ a TWT technique for communication between the wireless communication device and the peripheral devices. In some systems, the peripheral devices and the wireless communication device may exchange one or more BT messages and implement a complete TWT teardown between the wireless communication device and each of the peripheral devices. Such an exchange of Bluetooth messages and TWT teardown may introduce too much latency for some applications, such as ULL gaming or streaming lossless audio applications.0097-6044PCT2500711W0 9

[0035] In some examples, a WCD, which may be a handset or an AP (for example, a soft AP (SAP)), and a set of peripheral devices (for example, earbuds or audio devices) may use downlink audio data packets to carry updated TWT parameters or any other XPAN-related parameters that the wireless communication device and the peripheral devices may indicate via wireless signaling. Additionally, or alternatively, the wireless communication device may embed a set of updated parameters in a padding section of an audio data packet and may transmit the audio data packet to the peripheral devices. The peripheral devices may each acknowledge the audio data packet transmitted by the wireless communication device, and the wireless communication device may communicate in accordance with the updated parameters based on receiving acknowledgements from each of the peripheral devices.

[0036] Fig. 1 shows a wireless communication network 100, in accordance with the present disclosure. The wireless communication network 100 may be a wireless local area network (WLAN) or a Wi-Fi network. For example, the wireless communication network 100 can be a network implementing at least one of the IEEE 802.11 family of wireless communication protocol standards (such as defined by the IEEE 802.11-2020 specification or amendments thereof including, but not limited to, 802.1 lay, 802.1 lax, 802.1 laz, 802.1 Iba, 802.1 Ibc, 802.11bd, 802.11be, 802.11bf, and 802.11bn). In some other examples, the wireless communication network 100 can be an example of a cellular radio access network (RAN), such as a 5G or 6G RAN that implements one or more cellular protocols such as those specified in one or more 3GPP standards. In some examples, the wireless communication network 100 can include a WLAN that functions in an interoperable or converged manner with one or more personal area networks, such as a network implementing Bluetooth or other wireless technologies, to provide greater or enhanced network coverage or to provide or enable other capabilities, functionality, applications or services.

[0037] The wireless communication network 100 may include a central device 105 (e.g., AP, Bluetooth network entity) and multiple associated devices 115 (such as STAs or SAPs). The devices 115 may include mobile stations, user equipment (UEs), personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, Chromebooks, augmented reality (AR), virtual reality (VR), mixed reality (MR) or extended reality (XR) wireless headsets or other peripheral devices, wireless earbuds, other wearable devices, display devices (for example, TVs, computer monitors, or video gaming consoles), video game controllers, navigation systems, music or other audio or stereo devices, remote control devices, printers, kitchen appliances (including smart refrigerators) or other household appliances, key fobs (for example, for passive keyless entry and start (PKES) systems), Internet of Things (loT) devices, and / or vehicles, among other examples.

[0038] The central device 105 and the associated devices 115 (for example, associated STAs) may represent a BSS or an extended service set (ESS). A BSS includes devices that0097-6044PCT2500711W0 10communicate with each other, and an ESS may include multiple BSSs or one or more BSSs and associated wired networks. The various devices 115 in the network are able to communicate with one another through the central device 105. The central device 105 may support a coverage area 110, which may represent a basic service area (BSA) of the wireless communication network 100. An extended network station (not shown) associated with the wireless communication network 100 may be connected to a wired or wireless distribution system that may allow multiple central devices 105 to be connected in an ESS.

[0039] While only one central device 105 is shown in Fig. 1, the wireless communication network 100 can include multiple central devices 105. The central device 105 can be or represent various different types of network entities including, but not limited to, a home networking AP, an enterprise-level AP, a single-frequency AP, a dual-band simultaneous (DBS) AP, a tri-band simultaneous (TBS) AP, a standalone AP, a non-standalone AP, a software-enabled AP (soft AP), and a multi-link AP (also referred to as an AP multi-link device (MLD)), as well as cellular (such as 3GPP, 4G LTE, 5G or 6G) base stations or other cellular network nodes such as a Node B, an evolved Node B (eNB), a gNB, a transmission reception point (TRP) or another type of device or equipment included in a RAN, including Open-RAN (O-RAN) network entities, such as a central unit (CU), a distributed unit (DU) or a radio unit (RU).

[0040] Although not shown in Fig. 1, a device 115 may be located in the intersection of more than one coverage area 110 and may associated with more than one central device 105. A single AP and an associated set of devices 115 may be referred to as a BSS. A distribution system (not shown) may be used to connect APs in an ESS. In some cases, the coverage area 110 of an AP may be divided into sectors (also not shown). The wireless communication network 100 may include APs of different types (for example, a metropolitan area, or a home network) with varying and / or overlapping coverage areas 110. Two devices 115 may also communicate directly via a direct wireless communication link 125 regardless of whether both devices 115 are in the same coverage area 110. Examples of direct wireless communication links 120 may include Wi-Fi Direct connections, Wi-Fi Tunneled Direct Link Setup (TDLS) links, and other group connections. Devices 115 and APs may communicate according to the WLAN radio and baseband protocol for physical and medium access control (MAC) layers from IEEE 802.11 and versions including 802.1 lb, 802.11g, 802.1 la, 802.1 In, 802.1 lac, 802.1 lad, 802.1 lah, and / or 802.1 lax, among other examples. In other implementations, peer-to-peer connections or ad hoc networks may be implemented within wireless communication network 100.

[0041] In some cases, a device 115 (or an AP) may be detectable by a central AP, but not by other devices 115 in the coverage area 110 of the central AP. For example, one device 115 may be at one end of the coverage area 110 of the central AP while another device 115 may be at the other end. Thus, both devices 115 may communicate with the AP, but may not receive the transmissions of the other. This may result in colliding transmissions for the two devices 115 in0097-6044PCT2500711W0 11a contention-based environment (for example, carrier sense multiple access with collision avoidance (CSMA / CA)) because the devices 115 may not refrain from transmitting on top of each other. A device 115 whose transmissions are not identifiable, but that is within the same coverage area 110 may be known as a hidden node. CSMA / CA may be supplemented by the exchange of a request-to-send (RTS) packet transmitted by a sending device 115 (or AP) and a clear-to-send (CTS) packet transmitted by the receiving device 115 (or AP). This may alert other devices within range of the sender and receiver not to transmit for the duration of the primary transmission. Thus, RTS and / or CTS may help mitigate a hidden node problem.

[0042] The wireless communication network 100 may include a central device 105, devices 115 (for example, which may be referred to as source devices or central devices), and paired devices 115 (for example, which may be referred to as sink devices or peripheral devices) implementing WLAN communications (for example, Wi-Fi communications) and / or Bluetooth communications. For example, devices 115 may include cell phones, UEs, STAs, mobile stations, PDAs, other handheld devices, netbooks, notebook computers, tablet computers, laptops, or some other suitable devices. Paired devices 115 may include Bluetooth-enabled devices capable of pairing with other Bluetooth-enabled devices (for example, such as devices 115), which may include wireless audio devices (for example, headsets, earbuds, speakers, earpieces, headphones), display devices (for example, televisions or computer monitors), microphones, meters, and / or valves, among other examples. As one example, the paired devices 115 may include a wireless audio device 130-a and a wireless audio device 130-b as shown by Fig. 1 (for example, wireless earbuds), and the paired devices 115 may alternatively or additionally communicate with the central device 105. In some aspects, a paired device 115 may communicate with a device 115 using the central device 105.

[0043] “Bluetooth communications” may refer to a short-range communication protocol and may be used to connect and exchange information between devices 115 and paired devices 115 (for example, between mobile phones, computers, digital cameras, wireless headsets, speakers, keyboards, mice or other input peripherals, and similar devices). Bluetooth systems (for example, aspects of wireless communication network 100) may be organized using a centralperipheral relationship employing a time-division duplex protocol having, for example, defined time slots of 625 microseconds, in which transmission alternates between the central device (for example, a device 115) and one or more peripheral devices (for example, paired devices 115). In some examples, “device” 115 may generally refer to a central device, and “paired device” 115 may refer to a peripheral device in the wireless communication network 100. Therefore, in some examples, a device may be referred to as either a device 115 or a paired device 115 based on the Bluetooth role configuration of the device. That is, designation of a device as either a device 115 or a paired device 115 may not necessarily indicate a distinction in device capability, but rather may refer to or indicate roles held by the device in the wireless communication0097-6044PCT2500711W0 12network 100. Generally, “device” 115 may refer to a wireless communication device capable of wirelessly exchanging data signals with another device (for example, a paired device 115), and “paired device” 115 may refer to a device operating in a peripheral role, or to a short-range wireless communication device capable of exchanging data signals with the device 115 (for example, using Bluetooth communication protocols).

[0044] A communication link 125 may be established between two Bluetooth -enabled devices (for example, between a device 115 and a paired device 115) and may provide for communications or services (for example, according to some Bluetooth profdes). The communication link may use, for example, a Bluetooth Low Energy (BLE) audio protocol for transferring audio (point-to-point or by broadcast). The controller stack may be responsible for setting up communication links 125, such as asynchronous connection-oriented links (or asynchronous connection-oriented connections), synchronous connection-orientated (SCO) links (or SCO connections), extended synchronous connection-oriented (eSCO) links (or eSCO connections), and / or other logical transport channel links. For example, a Bluetooth connection may be an eSCO connection for voice calls (for example, which may allow for retransmission), and / or an asynchronous connection-less (ACL) connection for music streaming (for example, advanced audio distribution profde (A2DP)), among other examples. eSCO packets may be transmitted in predetermined time slots (for example, 6 Bluetooth slots each for eSCO). The regular interval between the eSCO packets may be specified when the Bluetooth link is established. The eSCO packets to / from a specific device (for example, paired device 115) are acknowledged and may be retransmitted if not acknowledged during a retransmission window. In addition, audio may be streamed between a device 115 and a paired device 115 using an ACL connection (for example, an A2DP profile). In some cases, the ACL connection may occupy 1, 3, or 5 Bluetooth slots for data or voice. Other Bluetooth profiles supported by Bluetooth-enabled devices may include BLE (for example, providing considerably reduced power consumption and cost while maintaining a similar communication range), human interface device (HID) profile (for example, providing low latency links with low power requirements), etc.

[0045] A device 115 may, in some examples, be capable of both Bluetooth and WLAN communications. For example, WLAN and Bluetooth components may be co-located within a device, such that the device may be capable of communicating according to both Bluetooth and WLAN communication protocols, as each technology may offer different benefits or may improve user experience in different conditions. In some examples, Bluetooth and WLAN communications may share a same medium, such as the same unlicensed frequency medium. In such examples, a device 115 may support WLAN communications via an AP (for example, over communication links 120). The AP and the associated devices 115 may represent a BSS or an ESS. The various devices 115 in the network may be able to communicate with one another0097-6044PCT2500711W0 13through the AP. In some cases the AP may be associated with a coverage area, which may represent a BSA.

[0046] Devices 115 and APs may communicate according to the WLAN radio and baseband protocol for physical and MAC layers from IEEE 802.11 and versions including, but not limited to, 802.1 lb, 802.11g, 802.1 la, 802.1 In, 802.1 lac, 802.1 lad, 802.1 lah, and / or 802.1 lax. In other examples, peer-to-peer connections or ad hoc networks may be implemented within wireless communication network 100, and devices may communicate with each other via communication links 120 (for example, Wi-Fi Direct connections, Wi-Fi TDLS links, peer-to-peer communication links, or other peer or group connections). An AP may be coupled to a network (such as the Internet) and may enable a device 115 to communicate via the network (or communicate with other devices 115 coupled to the AP). A device 115 may communicate with a network device bi-directionally. For example, in a WLAN, a device 115 may communicate with an associated central device 105 via downlink (for example, the communication link from the central device 105 to the device 115) and uplink (for example, the communication link from the device 115 to the central device 105).

[0047] In some examples, content, media, and / or audio, among other examples, exchanged between a device 115 and a paired device 115 may originate from a WLAN. In some examples, device 115 may receive audio from a central device 105 (for example, via WLAN communications), and the device 115 may then relay or pass the audio to the paired device 115 (for example, via Bluetooth communications and / or the central device 105). As one example, the device 115 may relay or pass the audio to the paired device 115 via the direct wireless communication link 125. Alternatively, or additionally, the device 115 may relay and / or pass the audio to the paired device via the central device 105 as shown by reference number 135. In some examples, certain types of Bluetooth communications (for example, such as high quality or high definition (HD) Bluetooth) may require enhanced quality of service. For example, in some examples, delay-sensitive Bluetooth traffic may have a higher priority than WLAN traffic.

[0048] In some examples, a wireless communication device (for example, the central device 105 and / or a device 115) may support applications associated with low -latency or lossless audio to one or more other devices, such as one or more personal audio devices. For example, a wireless communication device may support applications and use cases associated with ULL, such as ULL gaming, or streaming lossless audio to one or more personal audio devices (for example, peripheral devices) of a user or one or more headset devices (for example, AR / VR / MR / XR headset devices). In scenarios in which a user uses two or more peripheral devices (for example, a wireless audio device 130-a and a wireless audio device 130-b), the wireless communication device may support an XPAN enabling communication with the two or more peripheral devices.0097-6044PCT2500711W0 14

[0049] To meet latency or lossless criteria associated with an application or use case, XPAN devices may employ a TWT technique for communication between the wireless communication device and the peripheral devices. Initial or default TWT parameters may be set under an expectation for ideal (for example, interference -free or approximately interference -free) conditions and may be updated in response to changing channel conditions or a changing concurrency situation at the wireless communication device. In some systems, the peripheral devices and the wireless communication device may exchange one or more Bluetooth messages and implement a complete TWT teardown between the wireless communication device and each of the peripheral devices. Such an exchange of Bluetooth messages and TWT teardown may introduce too much latency for some applications, such as ULL gaming or streaming lossless audio applications.

[0050] In some examples, a wireless communication device, which may be a device 115 (for example, a handset) or a central device 105, and a set of peripheral devices may use downlink audio data packets to carry updated TWT parameters or any other XPAN-related parameters that the wireless communication device and the peripheral devices may indicate via wireless signaling. In some examples, the wireless communication device may embed a set of updated parameters (for example, updated TWT parameters or other parameters associated with the XPAN) in one or more fields, such as one or more contributing source (CSRC) fields, of a realtime transport protocol (RTP) audio header of an audio data packet and may transmit the audio data packet to the peripheral devices. Additionally, or alternatively, the wireless communication device may embed a set of updated parameters in a padding section of an audio data packet and may transmit the audio data packet to the peripheral devices. The peripheral devices may each acknowledge the audio data packet transmitted by the wireless communication device and the wireless communication device may communicate in accordance with the updated parameters based on receiving acknowledgements from each of the peripheral devices.

[0051] In accordance with the example implementations described herein, various devices may use over-the-air transmissions to indicate updated parameters (for example, updated XPAN-related parameters, such as updated TWT parameters) via one or both of RTP audio header CSRC fields or padding fields in a payload data section. Consequently, the various devices may use a sequence of over-the-air packet transmissions to change or update a set of parameters (for example, a set of TWT parameters). For example, via audio data packet transmissions, the various devices may configure, trigger, or indicate an increase or a decrease in audio packet periodicity (for example, when TWT service interval (SI) is changed). Further, in accordance with the described techniques, such devices may avoid an explicit TWT teardown, request, and response frame exchange and may instead achieve a TWT sequence0097-6044PCT2500711W0 15change after RTP audio header CSRC fields or a padding section indicates updated TWT parameters.

[0052] Some aspects and techniques as described herein may be implemented, at least in part, using an artificial intelligence (Al) program (for example, referred to herein as an “AI / ML model”), such as a program that includes a machine learning (ML) model and / or an artificial neural network (ANN) model. The AI / ML model may be deployed at one or more devices (for example, one or more devices 115, central devices 105, and / or one or more servers, and / or one or more components of a cloud computing network, among other examples). For example, in an deployment where AI / ML functionality is performed independently at a device, sometimes referred to as “overlay AI / ML”, the AI / ML model (or an instance or portion of the AI / ML model) may be deployed at a device, one or more servers, and / or one or more components of a cloud computing network, among other examples. Additionally or alternatively, in a deployment where AI / ML functionality is coordinated between different devices, sometimes referred to as “coordinated AI / ML”, or performed at all device and network layers, sometimes referred to as “native AI / ML". the AI / ML model (or an instance of the AI / ML model) may be deployed at multiple devices (for example, a first portion of the AI / ML model may be deployed at a central device 105 and a second portion of the AI / ML model may be deployed at a network entity). In other examples of coordinated AI / ML and / or native AI / ML, a first AI / ML model may be deployed at a central device 105 and a second AI / ML model may be deployed at a network entity. The AI / ML model(s) may be configured to enhance various aspects of the wireless communication network (for example, to increase privacy, reliability, and / or efficient use of network bandwidth, and / or to reduce latency, among other examples). For example, the AI / ML model(s) may be trained to identify patterns or relationships in data corresponding to the wireless communication network, a device, and / or an air interface, among other examples. The AI / ML model(s) may support operational decisions relating to one or more aspects associated with wireless communications devices, networks, or services.

[0053] Accordingly, in some examples, the AI / ML model(s) may enable Al-as-a-Service (for example, an end-to-end AI / ML service via a user plane) for use cases such as a self-organizing network (SON), minimization of drive test (MDT), quality of experience (QoE), positioning, sensing, predictive mobility, and / or traffic prediction, among other examples. In some examples, Al-as-a-Service use cases may include measurement collection reporting by a central device or a peripheral device, device selection criteria (for example, according to a geographical area where measurements are to be collected and / or UE capabilities to be used to collected measurements), and / or reporting configurations (for example, reporting parameters such as location, time, and / or sensor information, among other examples). Additionally or alternatively, the AI / ML model(s) may enable AI / ML procedures (for example, RAN-triggered service establishment, configuration, inferencing using UE-side and / or network-side models,0097-6044PCT2500711W0 16performance monitoring and / or management, and / or capability signaling, among other examples). Additionally or alternatively, the AI / ML model(s) may enable RAN-based AI / ML services via one or more application program interfaces (APIs) and / or management interfaces for use cases such as beam management, radio resource monitoring (RRM) relaxation, mobility prediction, load prediction, network energy savings, and / or coverage and capacity improvements, among other examples.

[0054] In some aspects, a first peripheral device (e.g., a device 115) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive TWT information and an associated identifier (AID) for a second peripheral device; monitor for data for the second peripheral device using the AID of the second peripheral device, based at least in part on a determination, from the TWT information, that a second sleep duration of a second TWT of the second peripheral device is greater than a first sleep duration of a first TWT of the first peripheral device; renegotiate the first TWT with a central device to obtain a new first TWT; and monitor, using the new first TWT, for a beacon having data for the second peripheral device based at least in part on the AID of the second peripheral device. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0055] In some aspects, a second peripheral device (e.g., a device 115) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may negotiate a TWT with a central device based at least in part on a sleep duration rule; transmit, to a first peripheral device, TWT information for the TWT and an AID; sleep based at least in part on the TWT; receive a wake up signal from the first peripheral device; and renegotiate the TWT to obtain a new TWT. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0056] Fig. 2 illustrates an example of a wireless communication network 200 that supports low-latency parameter updates for extended personal audio networks in accordance with the present disclosure. The wireless communication network 200 may implement or be implemented to realize aspects of the wireless communication network 100. For example, the wireless communication network 200 illustrates communication between a central device 105, a device 115 (for example, a handset or handheld device), and a wireless audio device 130-a and a wireless audio device 130-b of a user 205 (for example, examples of audio devices and / or peripheral devices), which may be examples of corresponding devices as illustrated by and described with reference to Fig. 1. In some examples, the device 115, the wireless audio device 130-a, and the wireless audio device 130-b may support a signaling-based mechanism according to which the device 115 may transmit an indication of a set of updated parameters to each of the wireless audio device 130-a and the wireless audio device 130-b via one or audio data packets.0097-6044PCT2500711W0 17

[0057] In some examples, the device 115 may communicate with the central device 105 via one or both of a link 210-a and a link 2104), which may be examples of infrastructure links between the central device 105 and the device 115. Alternatively, or additionally, the central device 105 may communicate with the wireless audio device 130-a and / or the wireless audio device 130-b via one or both of a link 210-c and a link 210-d, respectively. In some examples, the wireless audio device 130-a and the wireless audio device 130-b may be connected to a same central device 105 as the device 115. In other aspects, the wireless audio device 130-a and the wireless audio device 130-b may be connected to a different central device 105 than the device 115. Accordingly, and as shown by reference number 215, the device 115, the wireless audio device 130-a, and / or the wireless audio device 130-b may communicate with one another via multiple central devices 105 (e.g., APs). The link 210-a may be an example of a 2.4 GHz link between the central device 105 and the device 115, and the link 210-b may be an example of a 5 GHz link or a 6 GHz link between the central device 105 and the device 115. In some examples, the link 210-c and / or the link 210-d may be a 2.4 GHz link, a 5 GHz, and / or a 6 GHz link.

[0058] The device 115 may communicate wirelessly with each of the wireless audio device 130-a and the wireless audio device 130-b, where each of the wireless audio device 130-a and the wireless audio device 130-b may be associated with an XPAN of the device 115. For example, the device 115 may communicate with the wireless audio device 130-a via a link 220-a and may communicate with the wireless audio device 130-b via a link 220-b, where the link 220-a and the link 220-b may be referred to or understood as XPAN links. The link 220-a may be an example of a 5 GHz link or a 6 GHz link and the link 220-b may be an example of a 5 GHz link or a 6 GHz link. Additionally, in some examples, the device 115 may communicate with the wireless audio device 130-a, which may be an example of a primary earbud, via a communication link 225. The communication link 225 may be an example of a Bluetooth link between the device 115 and the wireless audio device 130-a. The wireless audio device 130-a and the wireless audio device 130-b, which may be an example of a secondary audio device, may communicate with each other via a link 230, which may be an example of a Bluetooth link between the wireless audio device 130-a and the wireless audio device 130-b.

[0059] The device 115 may communicate with the wireless audio device 130-a and / or the wireless audio device 130-b via one or more central devices 105. To illustrate, the device 115 may communicate with a first central device 105 via the link 210-a and / or the link 210-b. The first central device 105 may be connected to a second central device 105, and the second central device 105 may be connected to the wireless audio device 130-a and / or the wireless audio device 130-b via the link 210-c and / or the link 210-d. Accordingly, the device 115 may communicate with the wireless audio device 130-a and / or the wireless audio device 130-b based at least in part on communicating with the first central device 105, the first central device 1050097-6044PCT2500711W0 18communicating with the second central device 105, and the second central device 105 communicating with the wireless audio device 130-a and / or the wireless audio device 1304). However, in other examples, the device 115, the wireless audio device 130-a, and / or the wireless audio device 130-b may be connected to a same central device 105.

[0060] In some examples, the device 115, the wireless audio device 130-a, and the wireless audio device 130-b may support or belong to an XPAN and may use the XPAN to support one or more applications or use cases, such as applications or use cases associated with latency or lossless audio constraints or criteria. For example, the device 115 may support one or more use cases of ULL gaming and streaming lossless audio to the wireless audio device 130-a and the wireless audio device 130-b (for example, personal devices of the device 115). For such applications, the device 115 may be expected to keep end-to-end latency below a relatively stringent latency target (for example, 40 milliseconds (ms) for ULL gaming). Further, the device 115 may also be tasked with handling (for example, gracefully handling without a hard disconnect and / or loss of data) a coexistence of XPAN traffic (for example, traffic to or from one or both of the wireless audio device 130-a and the wireless audio device 130-b) with other concurrency scenarios the user 205 or the system may initiate. Such other concurrency scenarios may include a scan concurrency for channel selection, STA infrastructure link concurrency for online gaming or other traffic to or from the central device 105, or neighbor aware networking (NAN) discovery and NAN data transfer, or any combination thereof.

[0061] The device 115 may have an operating condition and / or an operating specification to meet, such as a data transfer latency operating condition for various applications or use cases (for example, an ultra-low-latency constraint for a ULL gaming use case) and also facilitate coexistence between XPAN and other concurrency scenarios on the device 115. To meet the latency operating condition associated with, for example, ULL gaming, a power constraint of the wireless audio device 130-a and the wireless audio device 130-b, and / or power and concurrency constraints at the device 115, the device 115 may employ a TWT technique for the communication between the device 115 (which may act or function as an SAP) and each of the wireless audio device 130-a and wireless audio device 130-b (which may act or function as STAs). Alternatively, or additionally, the device 115 may employ one or more power saving mode time synchronization techniques as described below.

[0062] Example TWT parameters include a TWT 235, a TWT SI 240, and a TWT service period (SP) 245. A TWT 235 may indicate or be associated with a timing synchronization function (TSF) time indicating a start or beginning of a first TWT session. A TWT SI 240 may indicate a TWT interval, which may refer to a time difference between a start or beginning of two consecutive TWT sessions. A TWT SP 245 may indicate a duration during which one or both of the wireless audio device 130-a and the wireless audio device 130-b are awake during a TWT SI 240. In some aspects, a TWT SP 245 may be referred to or understood as a TWT0097-6044PCT2500711W0 19session. As illustrated by Fig. 2, the TWT SI 240 may indicate a time difference between a TWT SP 245 -a and a TWT 245 -b. A remainder of time within a TWT SI 240 excluding a TWT SP 245 may be referred to or understood as a concurrency time 250 during which the device 115 may perform any operations (for example, transmission or reception) associated with a concurrency scenario at the device 115. In other words, the difference between XPAN TWT SI 240 and XPAN TWT SP 245 may be the time left for the device 115 to support other concurrencies (for example, outside of any channel switching or software overheads).

[0063] For XPAN, each of the wireless audio device 130-a and the wireless audio device 1304) (which may be examples of TWT requesting STAs) may initiate a TWT session with the device 115 (which may be an example of a TWT responding STA). Further, for low -latency use cases (for example, ULL gaming use cases), a target end-to-end latency may be relatively stringent (for example, less than or equal to approximately 40 ms), which may be tied to, associated with, or expect a Wi-Fi latency in a specific range (for example, in the sub- 10 ms range). To achieve such a Wi-Fi latency, a TWT SI 240 and a TWT SP 245 may be selected or set to specific values (for example, a TWT SI 240 may be set to 4 ms with a TWT SP 245 of 2 ms). Further, for a lossless audio use case, for example, a TWT SI 240 may be set to approximately 70 ms with a TWT SP 245 of approximately 23 ms.

[0064] Fig. 3 is a diagram illustrating an example of a wireless communication device 300, in accordance with the present disclosure. In some aspects, the wireless communication device 300 may be an example of the central device 105, the device 115, and / or the wireless audio device 130 described above. In some examples, the central device 105, the device 115, and / or the wireless audio device 130 may include one or more wireless communication devices 300 and / or one or more components of wireless communication device 300.

[0065] In some examples, the wireless communication device 300 is configured to perform process 600 of Fig. 6, process 700 of Fig. 7, or other processes as described herein. The wireless communication device 300 may include one or more chips, system-on-chips (SoCs), chipsets, packages, components or devices that individually or collectively constitute or comprise a processing system. The processing system may interface with other components of the wireless communication device 300, and may generally process information (such as inputs or signals) received from such other components and output information (such as outputs or signals) to such other components. In some examples, an example chip may include a processing system, a first interface to output or transmit information and a second interface to receive or obtain information. For example, the first interface may refer to an interface between the processing system of the chip and a transmission component, such that the wireless communication device 300 may transmit the information output from the chip. In such an example, the second interface may refer to an interface between the processing system of the chip and a reception component, such that the wireless communication device 300 may receive0097-6044PCT2500711W0 20information that is passed to the processing system. In some such examples, the first interface also may obtain information, such as from the transmission component, and the second interface also may output information, such as to the reception component.

[0066] As shown in Fig. 3, the wireless communication device 300 may include processor (or “processing”) circuitry in the form of one or multiple processors, such as processor(s) 302. The processor (or “processing”) circuitry may be in the form of one or multiple processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DUPs)), or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASIC), programmable logic devices (PUDs) (such as field programmable gate arrays (FPGAs)), or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as “processors” or collectively as “the processor” or “the processor circuitry”). One or more of the processors may be individually or collectively configurable or configured to perform various functions or operations described herein. The processor(s) 302 may execute program instructions for the wireless communication device 300. One or more of the processor(s) 302 may be individually or collectively configurable or configured to perform various functions or operations described herein. A group of processor(s) 302 collectively configurable or configured to perform a set of functions may include a first processor configurable or configured to perform a first function of the set and a second processor configurable or configured to perform a second function of the set, or may include the group of processors all being configured or configurable to perform the set of functions.

[0067] The wireless communication device 300 may also include a display 342 that can perform graphics processing and present information to a user. The processor(s) 302 may also be coupled to memory management unit (MMU) 340, which may be configured to receive addresses from the processor(s) 302 and translate the addresses to address locations in memory such as memory 306, read-only memory (ROM) 308, or flash memory 310 and / or to address locations in other circuits or devices, such as the display circuitry 304, radio 330, connector interface 320, and / or display 342. The MMU 340 may also be configured to perform memory protection and page table translation or set up. In some aspects, the MMU 340 may be included as a portion of the processor(s) 302. In some aspects, the wireless communication device 300 may include a communication manager (for example, communication manager 140) that controls the wireless communication device 300 or processor(s) 302 to perform the processes described herein.

[0068] In some examples, the processing system may further include memory circuitry in the form of one or more memory devices, memory blocks, memory elements or other discrete gate or transistor logic or circuitry, each of which may include tangible storage media such as0097-6044PCT2500711W0 21random-access memory (RAM) or ROM, or combinations thereof (all of which may be generally referred to herein individually as “memories” or collectively as “the memory” or “the memory circuitry”), such as the memory 306, ROM 308, and / or flash memory 310. One or more of the memories may be coupled with one or more of the processors and may individually or collectively store processor-executable code that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally or alternatively, in some examples, one or more of the processors may be preconfigured to perform various functions or operations described herein without requiring configuration by software. The processing system may further include or be coupled with one or more modems (such as a Wi-Fi (for example, IEEE compliant) modem or a cellular (for example, 3 GPP 4G LTE, 5G or 6G compliant) modem). In some implementations, one or more processors of the processing system include or implement one or more of the modems. The processing system may further include or be coupled with multiple radios (collectively “the radio”), multiple RF chains or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains or transceivers.

[0069] The processor(s) 302 may be coupled to other circuits of the wireless communication device 300. For example, the wireless communication device 300 may include various memory types, a connector interface 320 through which the wireless communication device 300 can communicate with the computer system, and wireless communication subsystems that can transmit data to, and receive data from, other devices based on one or more wireless communication standards or protocols. For example, in some aspects, the wireless communication subsystems may include (but are not limited to) a WLAN subsystem, a WPAN subsystem, and / or a cellular subsystem (such as a LTE or NR subsystem). The wireless communication device 300 may include multiple antennas 335a, 335b, 335c, and / or 335d for performing wireless communication with, for example, wireless communication devices in a WPAN.

[0070] The wireless communication device 300 may be configured to implement part or all of the techniques described herein by executing program instructions stored on a memory medium (such as a non-transitory computer-readable memory medium) and / or through hardware or firmware operation. In other embodiments, the techniques described herein may be at least partially implemented by a programmable hardware element, such as an FPGA and / or an ASIC.

[0071] In certain aspects, the radio 330 may include separate controllers configured to control communications for various respective radio access technology (RAT) protocols. For example, as shown in Fig. 3, radio 330 may include a WLAN controller 350 that manages0097-6044PCT2500711W0 22WLAN communications, a WPAN controller 352 that manages Bluetooth, BLE, and / or other suitable WPAN communications, and a wireless wide area network (WWAN) controller 356 that manages WWAN communications. In some aspects, the wireless communication device 300 may store and execute a WLAN software driver for controlling WLAN operations performed by the WLAN controller 350, a WPAN software driver for controlling WPAN operations performed by the WPAN controller 352, and / or a WWAN software driver for controlling WWAN operations performed by the WWAN controller 356.

[0072] In some aspects, a first coexistence interface 354 (such as a wired interface) may be used for sending information between the WLAN controller 350 and the WPAN controller 352. Additionally, or alternatively, in some aspects, a second coexistence interface 358 may be used for sending information between the WLAN controller 350 and the WWAN controller 356. Additionally, or alternatively, in some aspects, a third coexistence interface 360 may be used for sending information between the WPAN controller 352 and the WWAN controller 356. In some examples, one or more of the WLAN controller 350, the WPAN controller 352, and / or the WWAN controller 356 may be implemented as hardware, software, firmware or some combination thereof.

[0073] In some aspects, the WLAN controller 350 may be configured to communicate with a second device in a WPAN using a WLAN link using one or more, some, or all of the antennas 335a, 335b, 335c, and 335d. In other configurations, the WPAN controller 352 may be configured to communicate with at least one second device in a WPAN using one or more, some, or all of the antennas 335a, 335b, 335c, and 335d. In other configurations, the WWAN controller 356 may be configured to communicate with a second device in a WPAN using one or more, some, or all of the antennas 335a, 335b, 335c, and 335d. The WLAN controller 350, the WPAN controller 352, and / or the WWAN controller 356 may be configured to adjust a wakeup time interval and a shutdown time for the wireless communication device 300.

[0074] A short-range wireless communications protocol, such as BT, BLE, and / or BR / EDR, may include and / or may use one or more other communications protocols, for example, to establish and maintain communications links. In some examples, the wireless communication device 300 may establish a communications link with one or more peripheral devices, such as a wireless headset or wireless earbuds, according to at least one communications protocol for short-range wireless communications. In some aspects, the communications link may include a communications link that adheres to a protocol included and / or for use with BT, BLE, and / or BR / EDR, among other examples. In one aspect, the communications link may include an asynchronous connection-oriented logical transport, sometimes referred to as an ACL link. When operating as an ACL link, the communications link may allow the wireless communication device 300 to connect or “pair” with a peripheral device. The connection is asynchronous in that the two devices may not need to synchronize, timewise, data0097-6044PCT2500711W0 23communications between each other to permit communication of data packets via the communications link.

[0075] In some examples, a logical link control and adaptation protocol (L2CAP) may be used within a BT protocol stack (not shown in Fig. 3). An L2CAP connection may be established after an ACL link has been established. Reference to L2CAP in the present disclosure may be further applicable to enhanced L2CAP (EL2CAP), which may be an enhanced version of the L2CAP protocol that enables multiplexing of multiple logical data channels via a single radio connection.

[0076] In some examples, the communications link may include an A2DP link. For example, an A2DP link may provide a point-to-point link between a source device, such as the wireless communication device 300, and a sink device, such as the wireless earbuds 130-a and 130-b. With an A2DP link, data packets including audio may be transmitted over an ACL channel, and other information (for example, for controlling the audio stream) may be transmitted over a separate control channel. The data packets may occur non-periodically.

[0077] In some examples, the communications link may support synchronous logical transport mechanisms between a source device and a peripheral device. For example, a communications link may include an SCO link that provides a symmetric point-to-point link between the source device and the peripheral device using time slots reserved for BT communications. In some aspects, an SCO link may not support retransmission of data packets, which may be unsatisfactory in audio streaming and / or voice call use cases in which a dropped audio or voice packet may reduce the quality of the user experience. Accordingly, in some aspects, the communications link may include an eSCO link. An eSCO link may provide a symmetric or asymmetric point-to-point link between a source device and a peripheral device using time slots reserved for BT communications, and may also provide for a retransmission window following the reserved time slots. Because retransmissions may be facilitated using the retransmission window, an eSCO link may be suitable for audio streaming and / or voice call use cases because a dropped audio or voice packet may be retransmitted, and therefore the probability of successfully receiving a data packet may be increased.

[0078] In some aspects, the communications link may include an isochronous (ISO) link. When operating as an ISO link, the communications link may combine some features of both synchronous and asynchronous links. For example, a stream on an ISO link may begin with a start packet, and then data packets may be asynchronously transmitted. On an ISO link, the number of retransmission attempts by a transmitting device may be limited. Thus, if a receiving device is unable to decode a data packet within the limited number of retransmission attempts, then the data packet may be dropped, and the receiving device may continue to receive the stream without data from the dropped data packet.0097-6044PCT2500711W0 24

[0079] In some aspects, a first peripheral device (e.g., a device 115) includes means for receiving TWT information and an AID for a second peripheral device; means for monitoring for data for the second peripheral device using the AID of the second peripheral device, based at least in part on a determination, from the TWT information, that a second sleep duration of a second TWT of the second peripheral device is greater than a first sleep duration of a first TWT of the first peripheral device; means for renegotiating the first TWT with a central device to obtain a new first TWT; and / or means for monitoring, using the new first TWT, for a beacon having data for the second peripheral device based at least in part on the AID of the second peripheral device. In some aspects, the means for the wireless communication device 300 to perform operations described herein may include, for example, one or more of antennas 335a-335d, WPAN controller 352, WLAN controller 350, radio 330, and / or processor 302, among other examples.

[0080] In some aspects, a second peripheral device (e.g., a device 115) includes means for negotiating a TWT with a central device based at least in part on a sleep duration rule; means for transmitting, to a first peripheral device, TWT information for the TWT and an AID; means for sleeping based at least in part on the TWT; means for receiving a wake up signal from the first peripheral device; and / or means for renegotiating the TWT to obtain a new TWT. In some aspects, the means for the wireless communication device 300 to perform operations described herein may include, for example, one or more of antennas 335a-335d, WPAN controller 352, WLAN controller 350, radio 330, and / or processor 302, among other examples.

[0081] The number and arrangement of components shown in Fig. 3 are provided as an example. In practice, device 300 may include additional components, fewer components, different components, or differently arranged components than those shown in Fig. 3.Additionally, or alternatively, a set of components (for example, one or more components) of device 300 may perform one or more functions described as being performed by another set of components of device 300.

[0082] Fig. 4 is a diagram illustrating examples 400 and 402 of TWT information, in accordance with the present disclosure.

[0083] Devices, such as STAs or peripheral devices, may use TWT scheduling to conserve battery power and to avoid uplink access contention. TWT allows a central device, such as an AP, to manage activity in the BSS in order to minimize contention between the devices and to reduce the required amount of time that a device utilizing a power management mode needs to be awake. The AP may schedule TWT time durations during which a device is awake (service interval) and / or has uplink access to the wireless network. The device is otherwise asleep (sleep duration) and / or does not have uplink access to the network.0097-6044PCT2500711W0 25

[0084] The AP may transmit TWT information such that devices may follow a TWT schedule. The AP may negotiate with a device for a TWT by receiving a request for a new TWT or suggested TWT parameters and providing a new TWT. Fig. 4 shows examples 400 and 402 of TWT information. Example 400 shows a TWT element format that includes an element identifier (ID) 404, a length 406, control information 408, and TWT parameter information 410 that is variable. Example 402 shows a TWT information element (IE) control field that includes a null data packet (NDP) paging indicator 412, a responder PM mode 414, a negotiation type 416, an indicator of TWT information frame disabled 418, a wake duration unit 420, and a reserved field 422. The negotiation type is set to 1 for broadcast TWT. The negotiation type is set to 0 for individual TWT. The AP (or SAP) may advertise Broadcast TWT requesting its associated clients to join an existing TWT session.

[0085] Peripheral devices, such as earbuds, may follow a TWT-based power saving mode to dictate a sleep interval or duration that helps to improve power compensation as compared to legacy power saving modes. Based on the service period (periodicity of service intervals) or service interval (service time duration of a sleep cycle) that is negotiated, earbuds can enter sleep cycles. During the service intervals, packets can be communicated to and from the central device (STA or AP). The service period, service interval, and other TWT parameters may be negotiated based on the current operating requirements or use case. Longer service intervals can provide better power efficiency. However, longer service intervals can cause latency in communicating with an earbud if there is any pending data from the central device.

[0086] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4.

[0087] Fig. 5 is a diagram illustrating an example 500 associated with TWT renegotiation, in accordance with the present disclosure. As shown in Fig. 5, a central device 510 (e.g., central device 105, AP) and a first peripheral device 520 (e.g., device 115) may communicate with one another (e.g., via an ACL connection). The first peripheral device 520 (e.g., primary earbud) may be paired with a second peripheral device 525 (e.g., secondary earbud). The peripheral devices may use a BR / EDR link for the pairing.

[0088] According to various aspects described herein, one peripheral device of a pair of peripheral devices may renegotiate a sleep duration of a new TWT. The sleep duration may be renegotiated based at least in part on conditions (e.g., battery, low traffic) of the peripheral device . The sleep duration of the peripheral device may be moved to a longer sleep interval after the TWT renegotiation. The peripheral device may indicate the service interval and association details to a peer peripheral device via a BT link. The peer peripheral device may also renegotiate for a new TWT to ensure that at least one beacon will be received during the service interval of the peer peripheral device. If the peer peripheral device in a service interval identifies (e.g., in a beacon0097-6044PCT2500711W0 26traffic indication map (TIM) field) any data (e.g., control information, audio set up information, audio parameters, power parameters, audio stream data) pending for the peripheral device that is in a longer sleep duration, the peer peripheral deice may wake up the peripheral device to receive the data. The peripheral device may exit the TWT sleep (e.g., with a packet marker (PM) = 0) and collect the pending data from the AP. After collecting the data, the peripheral device may check the present conditions to return to a longer service interval or to renegotiate a new service interval. The peer peripheral device may also select a different service interval if the peripheral device is not using a long service interval.

[0089] By renegotiating a TWT sleep duration of a TWT power save method, the AP and the peripheral devices may determine a service interval, to save power as compared to legacy power save modes, while reducing latency.

[0090] Example 500 shows TWT renegotiation. As shown by reference number 530, the central device 510 may perform association with each peripheral device to connect the peripheral devices to the central device 510. The central device 510 may transmit respective AIDs to the peripheral devices. As shown by reference number 535, the central device 510 may establish a TWT session for each peripheral device, such that the peripheral devices may sleep part of the time to conserve power. The central device 510 may transmit TWT parameters (e.g., sleep cycle period, service interval length, sleep duration length) to each of the peripheral devices.

[0091] As shown by reference number 540, the second peripheral device 525 may determine to use a longer sleep duration to conserve more power based at least in part on a rule. The rule may be, for example, that a battery level of the second peripheral device 525 does not satisfy (e.g., drops below) a battery threshold (e.g., battery level percentage). Other rules may relate to traffic, such as a historical amount of data, a type of data recently received, and / or data to be transmitted.

[0092] As a result of the determination, the second peripheral device may renegotiate a new TWT (new parameters) with the central device 510, as shown by reference number 545. The renegotiation may include the second peripheral device 525 transmitting a request for a new TWT and / or suggested TWT parameters for the new TWT, such as a longer sleep duration as a result of the rule determination. The renegotiation may include the central device 510 transmitting TWT information, with updated TWT parameters (e.g., new service interval) for the new TWT, to the second peripheral device 525. As shown by reference number 550, the second peripheral device 525 may transmit the AID for the second peripheral device 525 and the service interval (SI) obtained in the TWT information to the first peripheral device 520 via a BT link. The second peripheral device 525 may sleep and wake according to the new TWT.0097-6044PCT2500711W0 27

[0093] As shown by reference number 555, the first peripheral device 520 may renegotiate a new TWT with the central device 510 so as to align the service interval with beacons from the central device 510. In some aspects, the first peripheral device 520 may renegotiate for a new TWT based at least in part on a determination that the sleep duration of the first peripheral device 520 is longer than the sleep duration for the second peripheral device 525. The first peripheral device 520 may sleep and wake according to the new TWT.

[0094] The first peripheral device 520 may monitor for a beacon with data directed to the second peripheral device 525 (AID of the second peripheral device 525), while the second peripheral device 525 is able to sleep longer to conserve more power. The first peripheral device 520 may monitor for data for the second peripheral device 525 based at least in part on the sleep duration for the second peripheral device 525 being longer than the sleep duration for the first peripheral device 520. As shown by reference number 560, the first peripheral device 520 may receive a beacon with data for the second peripheral device 525. The first peripheral device 520 may identify the data based at least in part on the AID of the second peripheral device 525.

[0095] As shown by reference number 565, having identified data for the second peripheral device 525, the first peripheral device 520 may transmit a wake up signal to trigger the second peripheral device 525 to wake up. The second peripheral device 525 may receive the data from the central device 510. In some aspects, the first peripheral device 520 may transmit data for the second peripheral device 525 (or other information) to the second peripheral device 525 via the BT link between the peripheral devices.

[0096] In some aspects, as shown by reference number 570, the second peripheral device 525 may renegotiate for a new TWT based at least in part on receiving the wake up trigger. As shown by reference number 575, the first peripheral device 520 may also renegotiate a new TWT to a satisfy a required service interval. The first peripheral device 520 may sleep and wake according to the new TWT.

[0097] By renegotiating sleep durations and monitoring for another peripheral device with a longer sleep duration, the peripheral devices may conserve power without increasing latency.

[0098] As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.

[0099] Fig. 6 is a diagram illustrating an example process 600 performed, for example, at a first peripheral device or an apparatus of a first peripheral device, in accordance with the present disclosure. Example process 600 is an example where the apparatus or the first peripheral device (e.g., first peripheral device 520) performs operations associated with TWT renegotiation.0097-6044PCT2500711W0 28

[0100] As shown in Fig. 6, in some aspects, process 600 may include receiving TWT information and an AID for a second peripheral device (block 610). For example, the first peripheral device (e.g., using reception component 802 and / or communication manager 806, depicted in Fig. 8) may receive TWT information and an AID for a second peripheral device, as described above.

[0101] As further shown in Fig. 6, in some aspects, process 600 may include monitoring for data for the second peripheral device using the AID of the second peripheral device, based at least in part on a determination, from the TWT information, that a second sleep duration of a second TWT of the second peripheral device is greater than a first sleep duration of a first TWT of the first peripheral device (block 620). For example, the first peripheral device (e.g., using communication manager 806, depicted in Fig. 8) may monitor for data for the second peripheral device using the AID of the second peripheral device, based at least in part on a determination, from the TWT information, that a second sleep duration of a second TWT of the second peripheral device is greater than a first sleep duration of a first TWT of the first peripheral device, as described above.

[0102] As further shown in Fig. 6, in some aspects, process 600 may include renegotiating the first TWT with a central device to obtain a new first TWT (block 630). For example, the first peripheral device (e.g., using communication manager 806, depicted in Fig. 8) may renegotiate the first TWT with a central device to obtain a new first TWT, as described above.

[0103] As further shown in Fig. 6, in some aspects, process 600 may include monitoring, using the new first TWT, for a beacon having data for the second peripheral device based at least in part on the AID of the second peripheral device (block 640). For example, the first peripheral device (e.g., using communication manager 806, depicted in Fig. 8) may monitor, using the new first TWT, for a beacon having data for the second peripheral device based at least in part on the AID of the second peripheral device, as described above.

[0104] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0105] In a first aspect, process 600 includes receiving the beacon during a service period of the new first TWT.

[0106] In a second aspect, alone or in combination with the first aspect, the beacon includes data for the second peripheral device, and process 600 comprises waking up the second peripheral device.

[0107] In a third aspect, alone or in combination with one or more of the first and second aspects, process 600 includes receiving an indication from the second peripheral device of a new second TWT that is renegotiated for the second peripheral device, and renegotiating the0097-6044PCT2500711W0 29first TWT based at least in part on a determination, from the indication, that the first sleep duration is greater than a sleep duration of the new second TWT.

[0108] In a fourth aspect, alone or in combination with one or more of the first through third aspects, process 600 includes renegotiating the first TWT, based at least in part on the indication, to obtain a new first TWT, and sleeping according to the new first TWT.

[0109] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, renegotiating the first TWT includes transmitting one or more preferred parameters for the new first TWT or a request for one or more updated parameters for the new first TWT, and receiving the one or more updated parameters for the new first TWT.

[0110] Although Fig. 6 shows example blocks of process 600, in some aspects, process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 6. Additionally, or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0111] Fig. 7 is a diagram illustrating an example process 700 performed, for example, at a second peripheral device or an apparatus of a second peripheral device, in accordance with the present disclosure. Example process 700 is an example where the apparatus or the second peripheral device (e.g., second peripheral device 525) performs operations associated with TWT renegotiation.

[0112] As shown in Fig. 7, in some aspects, process 700 may include negotiating a TWT with a central device based at least in part on a sleep duration rule (block 710). For example, the second peripheral device (e.g., using communication manager 806, depicted in Fig. 8) may negotiate a TWT with a central device based at least in part on a sleep duration rule, as described above.

[0113] As further shown in Fig. 7, in some aspects, process 700 may include transmitting, to a first peripheral device, TWT information for the TWT and an AID (block 720). For example, the second peripheral device (e.g., using transmission component 804 and / or communication manager 806, depicted in Fig. 8) may transmit, to a first peripheral device, TWT information for the TWT and an AID, as described above.

[0114] As further shown in Fig. 7, in some aspects, process 700 may include sleeping based at least in part on the TWT (block 730). For example, the second peripheral device (e.g., using communication manager 806, depicted in Fig. 8) may sleep based at least in part on the TWT, as described above.

[0115] As further shown in Fig. 7, in some aspects, process 700 may include receiving a wake up signal from the first peripheral device (block 740). For example, the second peripheral device (e.g., using reception component 802 and / or communication manager 806, depicted in Fig. 8) may receive a wake up signal from the first peripheral device, as described above.0097-6044PCT2500711W0 30

[0116] As further shown in Fig. 7, in some aspects, process 700 may include renegotiating the TWT to obtain a new TWT (block 750). For example, the second peripheral device (e.g., using communication manager 806, depicted in Fig. 8) may renegotiate the TWT to obtain a new TWT, as described above.

[0117] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0118] In a first aspect, process 700 includes entering an active state based at least in part on the wake up signal, and receiving data from the AP.

[0119] In a second aspect, alone or in combination with the first aspect, renegotiating the TWT includes transmitting, to the central device, one or more preferred parameters for the new TWT or a request for one or more updated parameters for the new TWT, and receiving the one or more updated parameters for the new TWT.

[0120] Although Fig. 7 shows example blocks of process 700, in some aspects, process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 7. Additionally, or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0121] Fig. 8 is a diagram of an example apparatus 800 for wireless communication, in accordance with the present disclosure. The apparatus 800 may be a peripheral device, or a peripheral device (e.g., device 115, wireless communication device 300) may include the apparatus 800. In some aspects, the apparatus 800 includes a reception component 802, a transmission component 804, and / or a communication manager 806, which may be in communication with one another (for example, via one or more buses and / or one or more other components). In some aspects, the communication manager 806 is the communication manager 140 described in connection with Fig. 1. As shown, the apparatus 800 may communicate with another apparatus 806 such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 802 and the transmission component 804. The communication manager 806 may be included in, or implemented via, a processing system of the peripheral device.

[0122] In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with Figs. 1-5. Additionally, or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 600 of Fig. 6, process 700 of Fig. 7, or a combination thereof. In some aspects, the apparatus 800 and / or one or more components shown in Fig. 8 may include one or more components of the peripheral device described in connection with Fig. 1. Additionally, or alternatively, one or more components shown in Fig. 8 may be implemented within one or more0097-6044PCT2500711W0 31components described in connection with Fig. 1. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

[0123] The reception component 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 808. The reception component 802 may provide received communications to one or more other components of the apparatus 800. In some aspects, the reception component 802 may perform signal processing on the received communications, and may provide the processed signals to the one or more other components of the apparatus 800. In some aspects, the reception component 802 may include one or more components of the peripheral device described above in connection with Fig. 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the peripheral device.

[0124] The transmission component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 808. In some aspects, one or more other components of the apparatus 800 may generate communications and may provide the generated communications to the transmission component 804 for transmission to the apparatus 808. In some aspects, the transmission component 804 may perform signal processing on the generated communications, and may transmit the processed signals to the apparatus 808. In some aspects, the transmission component 804 may include one or more components of the peripheral device described above in connection with Fig. 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the peripheral device described in connection with Fig. 1. In some aspects, the transmission component 804 may be co-located with the reception component 802.

[0125] The communication manager 806 may support operations of the reception component 802 and / or the transmission component 804. For example, the communication manager 806 may receive information associated with configuring reception of communications by the reception component 802 and / or transmission of communications by the transmission component 804. Additionally, or alternatively, the communication manager 806 may generate and / or provide control information to the reception component 802 and / or the transmission component 804 to control reception and / or transmission of communications.

[0126] In some aspects associated with a first peripheral device, the reception component 802 may receive TWT information and an AID for a second peripheral device. The communication 0097-6044PCT2500711W0 32manager 806 may monitor for data for the second peripheral device using the AID of the second peripheral device, based at least in part on a determination, from the TWT information, that a second sleep duration of a second TWT of the second peripheral device is greater than a first sleep duration of a first TWT of the first peripheral device. The communication manager 806 may renegotiate the first TWT with a central device to obtain a new first TWT. The communication manager 806 may monitor, using the new first TWT, for a beacon having data for the second peripheral device based at least in part on the AID of the second peripheral device.

[0127] The reception component 802 may receive the beacon during a service period of the new first TWT. The reception component 802 may receive an indication from the second peripheral device of a new second TWT that is renegotiated for the second peripheral device. The communication manager 806 may renegotiate the first TWT based at least in part on a determination, from the indication, that the first sleep duration is greater than a sleep duration of the new second TWT. The communication manager 806 may renegotiate the first TWT, based at least in part on the indication, to obtain a new first TWT. The communication manager 806 may sleep according to the new first TWT.

[0128] In some aspects associated with a second peripheral device, the communication manager 806 may negotiate a TWT with a central device based at least in part on a sleep duration rule. The transmission component 804 may transmit, to a first peripheral device, TWT information for the TWT and an AID. The communication manager 806 may sleep based at least in part on the TWT. The reception component 802 may receive a wake up signal from the first peripheral device. The communication manager 806 may renegotiate the TWT to obtain a new TWT.

[0129] The transmission component 804 may transmit, to the central device, an indication that indicates that the first peripheral device is to receive data for the second peripheral device. The communication manager 806 may enter an active state (e.g., based at least in part on receiving the wake up signal. The reception component 802 may receive data from the AP.

[0130] The number and arrangement of components shown in Fig. 8 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 8. Furthermore, two or more components shown in Fig. 8 may be implemented within a single component, or a single component shown in Fig. 8 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 8 may perform one or more functions described as being performed by another set of components shown in Fig.8.

[0131] The following provides an overview of some Aspects of the present disclosure:0097-6044PCT2500711W0 33

[0132] Aspect 1 : A method of wireless communication performed by a first peripheral device, comprising: receiving target wake time (TWT) information and an associated identifier (AID) for a second peripheral device; monitoring for data for the second peripheral device using the AID of the second peripheral device, based at least in part on a determination, from the TWT information, that a second sleep duration of a second TWT of the second peripheral device is greater than a first sleep duration of a first TWT of the first peripheral device; renegotiating the first TWT with a central device to obtain a new first TWT; and monitoring, using the new first TWT, for a beacon having data for the second peripheral device based at least in part on the AID of the second peripheral device.

[0133] Aspect 2: The method of Aspect 1, further comprising receiving the beacon during a service period of the new first TWT.

[0134] Aspect 3: The method of Aspect 2, wherein the beacon includes data for the second peripheral device; and wherein the method further comprises waking up the second peripheral device.

[0135] Aspect 4: The method of any of Aspects 1-3, further comprising: receiving an indication from the second peripheral device of a new second TWT that is renegotiated for the second peripheral device; and renegotiating the first TWT based at least in part on a determination, from the indication, that the first sleep duration is greater than a sleep duration of the new second TWT.

[0136] Aspect 5: The method of Aspect 4, further comprising: renegotiating the first TWT, based at least in part on the indication, to obtain a new first TWT; and sleeping according to the new first TWT.

[0137] Aspect 6: The method of any of Aspects 1-5, wherein renegotiating the first TWT includes: transmitting one or more preferred parameters for the new first TWT or a request for one or more updated parameters for the new first TWT; and receiving the one or more updated parameters for the new first TWT.

[0138] Aspect 7: A method of wireless communication performed by a second peripheral device, comprising: negotiating a target wake time (TWT) with a central device based at least in part on a sleep duration rule; transmitting, to a first peripheral device, TWT information for the TWT and an associated identifier; sleeping based at least in part on the TWT; receiving a wake up signal from the first peripheral device; and renegotiating the TWT to obtain a new TWT.

[0139] Aspect 8: The method of Aspect 7, further comprising: entering an active state based at least in part on the wake up signal; and receiving data from the central device.

[0140] Aspect 9: The method of any of Aspects 7-8, wherein renegotiating the TWT includes: transmitting, to the central device, one or more preferred parameters for the new TWT0097-6044PCT2500711W0 34or a request for one or more updated parameters for the new TWT; and receiving the one or more updated parameters for the new TWT.

[0141] Aspect 10: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-9.

[0142] Aspect 11 : An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-9.

[0143] Aspect 12: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-9.

[0144] Aspect 13: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-9.

[0145] Aspect 14: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-9.

[0146] Aspect 15: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-9.

[0147] Aspect 16: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-9.

[0148] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects. No element, act, or instruction described herein should be construed as critical or essential unless explicitly described as such.

[0149] It will be apparent that systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. The actual specialized control hardware or software used to implement these systems or methods is not limiting of the aspects. Thus, the operation and behavior of the systems or methods are described herein0097-6044PCT2500711W0 35without reference to specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the systems or methods based, at least in part, on the description herein. A component being configured to perform a function means that the component has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise.

[0150] As used herein, the articles “a” and “an” are intended to refer to one or more items and may be used interchangeably with “one or more” or “at least one.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or “a single one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” “comprise,” “comprising,” “include” and “including,” and derivatives thereof or similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A may also have B). Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (for example, if used in combination with “either” or “only one of’). As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (for example, a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0151] As used herein, the term “determine” or “determining” encompasses a wide variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, estimating, investigating, looking up (such as via looking up in a table, a database, or another data structure), searching, inferring, ascertaining, and / or measuring, among other possibilities. Also, “determining” can include receiving (such as receiving information), accessing (such as accessing data stored in memory) or transmitting (such as transmitting information), among other possibilities. Additionally, “determining” can include resolving, selecting, obtaining, choosing, establishing, and / or other such similar actions.

[0152] As used herein, the phrase “based on” is intended to mean “based at least in part on” or “based on or otherwise in association with” unless explicitly stated otherwise. As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.0097-6044PCT2500711W0 36

[0153] Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the scope of all aspects described herein. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set.0097-6044PCT

Claims

2500711W0 37WHAT IS CLAIMED IS:

1. An apparatus for wireless communication at a first peripheral device, comprising: one or more memories; andone or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the first peripheral device to:receive target wake time (TWT) information and an associated identifier (AID) for a second peripheral device;monitor for data for the second peripheral device using the AID of the second peripheral device, based at least in part on a determination, from the TWT information, that a second sleep duration of a second TWT of the second peripheral device is greater than a first sleep duration of a first TWT of the first peripheral device;renegotiate the first TWT with a central device to obtain a new first TWT; and monitor, using the new first TWT, for a beacon having data for the second peripheral device based at least in part on the AID of the second peripheral device.

2. The apparatus of claim 1, wherein the one or more processors are individually or collectively configured to cause the first peripheral device to receive the beacon during a service period of the new first TWT.

3. The apparatus of claim 2, wherein the beacon includes data for the second peripheral device; and wherein the one or more processors are individually or collectively configured to cause the first peripheral device to wake up the second peripheral device.

4. The apparatus of claim 1, wherein the one or more processors are individually or collectively configured to cause the first peripheral device to:receive an indication from the second peripheral device of a new second TWT that is renegotiated for the second peripheral device; andrenegotiate the first TWT based at least in part on a determination, from the indication, that the first sleep duration is greater than a sleep duration of the new second TWT.

5. The apparatus of claim 4, wherein the one or more processors are individually or collectively configured to cause the first peripheral device to:renegotiate the first TWT, based at least in part on the indication, to obtain a new first TWT; andsleep according to the new first TWT.0097-6044PCT2500711W0 386. The apparatus of claim 1, wherein to renegotiate the first TWT, the one or more processors are individually or collectively configured to cause the first peripheral device to: transmit one or more preferred parameters for the new first TWT or a request for one or more updated parameters for the new first TWT; andreceive the one or more updated parameters for the new first TWT.

7. An apparatus for wireless communication at a second peripheral device, comprising:one or more memories; andone or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the second peripheral device to:negotiate a target wake time (TWT) with a central device based at least in part on a sleep duration rule;transmit, to a first peripheral device, TWT information for the TWT and an associated identifier;sleep based at least in part on the TWT;receive a wake up signal from the first peripheral device; and renegotiate the TWT to obtain a new TWT.

8. The apparatus of claim 7, wherein the one or more processors are individually or collectively configured to cause the second peripheral device to:enter an active state based at least in part on the wake up signal; andreceive data from the central device.

9. The apparatus of claim 7, wherein to renegotiate the TWT, the one or more processors are individually or collectively configured to cause the second peripheral device to:transmit, to the central device, one or more preferred parameters for the new TWT or a request for one or more updated parameters for the new TWT; andreceive the one or more updated parameters for the new TWT.

10. A method of wireless communication performed by a first peripheral device, comprising:receiving target wake time (TWT) information and an associated identifier (AID) for a second peripheral device;monitoring for data for the second peripheral device using the AID of the second peripheral device, based at least in part on a determination, from the TWT information, that a second sleep duration of a second TWT of the second peripheral device is greater than a first sleep duration of a first TWT of the first peripheral device;0097-6044PCT2500711W0 39renegotiating the first TWT with a central device to obtain a new first TWT; and monitoring, using the new first TWT, for a beacon having data for the second peripheral device based at least in part on the AID of the second peripheral device.

11. The method of claim 10, further comprising receiving the beacon during a service period of the new first TWT.

12. The method of claim 11, wherein the beacon includes data for the second peripheral device; and wherein the method further comprises waking up the second peripheral device.

13. The method of claim 10, further comprising:receiving an indication from the second peripheral device of a new second TWT that is renegotiated for the second peripheral device; andrenegotiating the first TWT based at least in part on a determination, from the indication, that the first sleep duration is greater than a sleep duration of the new second TWT.

14. The method of claim 13, further comprising:renegotiating the first TWT, based at least in part on the indication, to obtain a new first TWT; andsleeping according to the new first TWT.

15. The method of claim 10, wherein renegotiating the first TWT includes:transmitting one or more preferred parameters for the new first TWT or a request for one or more updated parameters for the new first TWT; andreceiving the one or more updated parameters for the new first TWT.0097-6044PCT

Images