TARGET WAKE TIME ALIGNMENT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a first wireless device may transmit, to a second wireless device, a request to configure a target wake time (TWT) schedule for a first link associated with the second wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time. The first wireless device may receive, from the second wireless device, a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link. Numerous other aspects are described.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for target wake time alignment.

BACKGROUND

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 (e.g., time, frequency, and power). A wireless network, for example a wireless local area network (WLAN), such as a Wi-Fi (i.e., 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, an 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.

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 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.

SUMMARY

Some aspects described herein relate to a method of wireless communication performed by a first wireless device. The method may include transmitting, to a second wireless device, a request to configure a target wake time (TWT) schedule for a first link associated with the second wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time. The method may include receiving, from the second wireless device, a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link.

Some aspects described herein relate to a method of wireless communication performed by a second wireless device. The method may include receiving a request to configure a TWT schedule for a first link associated with a first wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with the first wireless device and a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time. The method may include transmitting a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link.

Some aspects described herein relate to a first wireless device for wireless communication. The first wireless device may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit, to a second wireless device, a request to configure a TWT schedule for a first link associated with the second wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time. The one or more processors may be configured to receive, from the second wireless device, a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link.

Some aspects described herein relate to a second wireless device for wireless communication. The second wireless device may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a request to configure a TWT schedule for a first link associated with a first wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with the first wireless device and a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time. The one or more processors may be configured to transmit a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a first wireless device. The set of instructions, when executed by one or more processors of the first wireless device, may cause the first wireless device to transmit, to a second wireless device, a request to configure a TWT schedule for a first link associated with the second wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time. The set of instructions, when executed by one or more processors of the first wireless device, may cause the first wireless device to receive, from the second wireless device, a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a second wireless device. The set of instructions, when executed by one or more processors of the second wireless device, may cause the second wireless device to receive a request to configure a TWT schedule for a first link associated with a first wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with the first wireless device and a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time. The set of instructions, when executed by one or more processors of the second wireless device, may cause the second wireless device to transmit a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a second wireless device, a request to configure a TWT schedule for a first link associated with the second wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time. The apparatus may include means for receiving, from the second wireless device, a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a request to configure a TWT schedule for a first link associated with a first wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with the first wireless device and a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time. The apparatus may include means for transmitting a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link.

DETAILED DESCRIPTION

In some 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 (e.g., 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 target wake time (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 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.

In some implementations, a wireless communication device (WCD), which may be a handset or an access point (AP) (e.g., a soft AP (SAP)), and a set of peripheral devices (e.g., 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.

FIG.1illustrates a wireless communication system100(also known as a wireless local area network (WLAN) or a Wi-Fi network) configured in accordance with the present disclosure. The wireless communication system100may include an AP105and multiple associated devices115(such as stations (STAs) or SAPs), which may represent devices such as mobile stations, personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, display devices (e.g., TVs, computer monitors, etc.), printers, etc. The AP105and the associated devices115(e.g., associated STAs) may represent a basic service set (BSS) or an extended service set (ESS). The various devices115in the network are able to communicate with one another through the AP105. Also shown is a coverage area110of the AP105, which may represent a basic service area (BSA) of the wireless communication system100. An extended network station (not shown) associated with the wireless communication system100may be connected to a wired or wireless distribution system that may allow multiple APs105to be connected in an ESS.

Although not shown inFIG.1, a device115may be located in an intersection of more than one coverage area110and may associate with more than one AP105. A single AP105and an associated set of devices115may be referred to as a BSS. An ESS is a set of connected BSSs. A distribution system (not shown) may be used to connect APs105in an ESS. In some cases, the coverage area110of an AP105may be divided into sectors (also not shown). The wireless communication system100may include APs105of different types (e.g., metropolitan area, home network, etc.), with varying and overlapping coverage areas110. Two devices115may also communicate directly via a direct wireless communication link125regardless of whether both devices115are in the same coverage area110. Examples of direct wireless communication links120may include Wi-Fi Direct connections, Wi-Fi Tunneled Direct Link Setup (TDLS) links, and other group connections. Devices115and APs105may 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.11b, 802.11g, 802.11a, 802.11n, 802.11ac, 802.11ad, 802.11ah, 802.11ax, etc. In other implementations, peer-to-peer connections or ad hoc networks may be implemented within wireless communication system100.

In some cases, a device115(or an AP105) may be detectable by a central AP105, but not by other devices115in the coverage area110of the central AP105. For example, one device115may be at one end of the coverage area110of the central AP105while another device115may be at the other end. Thus, both devices115may communicate with the AP105, but may not receive the transmissions of the other. This may result in colliding transmissions for the two devices115in a contention-based environment (e.g., carrier sense multiple access with collision avoidance (CSMA/CA)) because the devices115may not refrain from transmitting on top of each other. A device115whose transmissions are not identifiable, but that is within the same coverage area110may 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 device115(or AP105) and a clear-to-send (CTS) packet transmitted by the receiving device115(or AP105). 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.

The wireless communication system100may include an AP105, devices115(e.g., which may be referred to as source devices or central devices), and paired devices115(e.g., which may be referred to as sink devices or peripheral devices) implementing WLAN communications (e.g., Wi-Fi communications) and/or Bluetooth communications. For example, devices115may include cell phones, user equipment (UEs), STAs, mobile stations, PDAs, other handheld devices, netbooks, notebook computers, tablet computers, laptops, or some other suitable terminology. Paired devices115may include Bluetooth-enabled devices capable of pairing with other Bluetooth-enabled devices (e.g., such as devices115), which may include wireless audio devices (e.g., headsets, earbuds, speakers, earpieces, headphones), display devices (e.g., TVs, computer monitors), microphones, meters, valves, etc.

“Bluetooth communications” may refer to a short-range communication protocol and may be used to connect and exchange information between devices115and paired devices115(e.g., between mobile phones, computers, digital cameras, wireless headsets, speakers, keyboards, mice or other input peripherals, and similar devices). Bluetooth systems (e.g., aspects of wireless communication system100) may be organized using a central-peripheral relationship employing a time-division duplex protocol having, for example, defined time slots of 625 microseconds, in which transmission alternates between the central device (e.g., a device115) and one or more peripheral devices (e.g., paired devices115). In some examples, “device115” may generally refer to a central device, and “paired device115” may refer to a peripheral device in the wireless communication system100. Therefore, in some examples, a device may be referred to as either a device115or a paired device115based on the Bluetooth role configuration of the device. That is, designation of a device as either a device115or a paired device115may not necessarily indicate a distinction in device capability, but rather may refer to or indicate roles held by the device in the wireless communication system100. Generally, “device115” may refer to a wireless communication device capable of wirelessly exchanging data signals with another device (e.g., a paired device115), and “paired device115” 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 device115(e.g., using Bluetooth communication protocols).

A communication link125may be established between two Bluetooth-enabled devices (e.g., between a device115and a paired device115) and may provide for communications or services (e.g., according to some Bluetooth profiles). The controller stack may be responsible for setting up communication links125, such as asynchronous connection-oriented links (or asynchronous connection-oriented connections), synchronous connection-oriented (SCO) links (or SCO connections), extended synchronous connection-oriented (eSCO) links (or eSCO connections), other logical transport channel links, etc. For example, a Bluetooth connection may be an eSCO connection for voice calls (e.g., which may allow for retransmission), an asynchronous connection-less (ACL) connection for music streaming (e.g., advanced audio distribution profile (A2DP)), etc. eSCO packets may be transmitted in predetermined time slots (e.g., 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 (e.g., paired device115) are acknowledged and may be retransmitted if not acknowledged during a retransmission window. In addition, audio may be streamed between a device115and a paired device115using an ACL connection (e.g., 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 Bluetooth Low Energy (BLE) (e.g., providing considerably reduced power consumption and cost while maintaining a similar communication range), human interface device (HID) profile (e.g., providing low latency links with low power requirements), etc.

A device 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 device115may support WLAN communications via AP105(e.g., over communication links120). The AP105and the associated devices115may represent a BSS or an ESS. The various devices115in the network may be able to communicate with one another through the AP105. In some cases, the AP105may be associated with a coverage area, which may represent a BSA.

Devices115and APs105may 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.11b, 802.11g, 802.11a, 802.11n, 802.11ac, 802.11ad, 802.11ah, 802.11ax, etc. In other implementations, peer-to-peer connections or ad hoc networks may be implemented within system100, and devices may communicate with each other via communication links120(e.g., Wi-Fi Direct connections, Wi-Fi TDLS links, peer-to-peer communication links, or other peer or group connections). AP105may be coupled to a network (such as the Internet) and may enable a device115to communicate via the network (or communicate with other devices115coupled to the AP105). A device115may communicate with a network device bi-directionally. For example, in a WLAN, a device115may communicate with an associated AP105via downlink (e.g., the communication link from the AP105to the device115) and uplink (e.g., the communication link from the device115to the AP105).

In some examples, content, media, audio, etc. exchanged between a device115and a paired device115may originate from a WLAN. For example, in some examples, device115may receive audio from an AP105(e.g., via WLAN communications), and the device115may then relay or pass the audio to the paired device115(e.g., via Bluetooth communications). In some examples, certain types of Bluetooth communications (e.g., 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.

In some deployments, a wireless communication device may support applications associated with low-latency or lossless audio with 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 (e.g., peripheral devices) of a user. In scenarios in which a user uses two peripheral devices (e.g., a wireless earbud130-aand a wireless earbud130-b), the wireless communication device may support an 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. Initial or default TWT parameters may be set under an expectation for ideal (e.g., 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.

In some implementations, a wireless communication device, which may be a device115(e.g., a handset) or an AP105, 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.

FIG.2illustrates an example of a wireless communication system200that supports low-latency parameter updates for extended personal audio networks in accordance with the present disclosure. The wireless communication system200may implement or be implemented to realize aspects of the wireless communication system100. For example, the wireless communication system200illustrates communication between an AP105, a device115(e.g., a handset or handheld device), and a wireless earbud130-aand a wireless earbud130-bof a user205(e.g., examples of audio devices and/or peripheral devices), which may be examples of corresponding devices as illustrated by and described with reference toFIG.1. In some implementations, the device115, the wireless earbud130-a, and the wireless earbud130-bmay support a signaling-based mechanism according to which the device115may transmit an indication of a set of updated parameters to each of the wireless earbud130-aand the wireless earbud130-bvia one or more audio data packets.

In some deployments, the device115may communicate with the AP105via one or both of a link210-aand a link210-b, which may be examples of infrastructure links between the AP105and the device115. The link210-amay be an example of a 2.4 GHz link between the AP105and the device115, and the link210-bmay be an example of a 5 GHz link or a 6 GHz link between the AP105and the device115. Further, the device115may communicate wirelessly with each of the wireless earbud130-aand the wireless earbud130-b, where each of the wireless earbud130-aand the wireless earbud130-bmay be associated with an XPAN of the device115. For example, the device115may communicate with the wireless earbud130-avia a link215-aand may communicate with the wireless earbud130-bvia a link215-b, where the link215-aand the link215-bmay be referred to or understood as XPAN links. The link215-amay be an example of a 5 GHz link or a 6 GHz link and the link215-bmay be an example of a 5 GHz link or a 6 GHz link. Additionally, in some examples, the device115may communicate with the wireless earbud130-a, which may be an example of a primary earbud, via a communication link220. The communication link220may be an example of a Bluetooth link between the device115and the wireless earbud130-a. The wireless earbud130-aand the wireless earbud130-b, which may be an example of a secondary earbud, may communicate with each other via a link225, which may be an example of a Bluetooth link between the wireless earbud130-aand the wireless earbud130-b.

In some cases, the device115, the wireless earbud130-a, and the wireless earbud130-bmay 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 device115may support one or more use cases of ULL gaming and streaming lossless audio to the wireless earbud130-aand the wireless earbud130-b(e.g., personal devices of the device115). For such applications, the device115may be expected to keep end-to-end latency below a relatively stringent latency target (e.g., 40 ms for ULL gaming). Further, the device115may also be tasked with handling (e.g., gracefully handling) a coexistence of XPAN traffic (e.g., traffic to or from one or both of the wireless earbud130-aand the wireless earbud130-b) with other concurrency scenarios that the user205or 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 AP105, or neighbor aware networking (NAN) discovery and NAN data transfer, or any combination thereof.

The device115may be expected to meet a latency constraint for various applications or use cases (e.g., an ultra-low-latency constraint for a ULL gaming use case) and also facilitate coexistence between XPAN and other concurrency scenarios on the device115. To meet the latency constraints associated with, for example, ULL gaming, a power constraint of the wireless earbud130-aand the wireless earbud130-b, and/or power and concurrency constraints at the device115, the device115may employ a TWT technique for the communication between the device115(which may act or function as an SAP) and each of the wireless earbud130-aand wireless earbud130-b(which may act or function as STAs).

Example TWT parameters include a TWT230, a TWT service interval (SI)235, and a TWT service period (SP)240. A TWT230may indicate or be associated with a timing synchronization function (TSF) time indicating a start or beginning of a first TWT service period. A TWT SI235may indicate a TWT interval, which may refer to a time difference between a start or beginning of two consecutive TWT service periods. A TWT SP240may indicate a duration during which one or both of the wireless earbud130-aand the wireless earbud130-bare awake during a TWT SI235. In some aspects, a TWT SP240may be referred to or understood as a TWT session. As illustrated byFIG.2, the TWT SI235may indicate a time difference between a TWT SP240-aand a TWT240-b. A remainder of time within a TWT SI235excluding a TWT SP240may be referred to or understood as a concurrency time245during which the device115may perform any operations (e.g., transmission or reception) associated with a concurrency scenario at the device115. In other words, the difference between XPAN TWT SI235and XPAN TWT SP240may be the time left for the device115to support other concurrencies (e.g., outside of any channel switching or software overheads).

For XPAN, each of the wireless earbud130-aand the wireless earbud130-b(which may be examples of TWT requesting STAs) may initiate a TWT session with the device115(which may be an example of a TWT responding STA). Further, for low-latency use cases (e.g., ULL gaming use cases), a target end-to-end latency may be relatively stringent (e.g., 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 (e.g., in the sub-10 ms range). To achieve such a Wi-Fi latency, a TWT SI235and a TWT SP240may be selected or set to specific values (e.g., a TWT SI235may be set to 4 ms with a TWT SP240of 2 ms). Further, for a lossless audio use case, for example, a TWT SI235may be set to approximately 70 ms with a TWT SP240of approximately 23 ms.

In some cases, a default or initial set of TWT parameters for XPAN may be configured or set expecting ideal (e.g., interference-free or approximately interference-free) conditions (e.g., link conditions, channel conditions, or environmental conditions). In some deployments, Wi-Fi channel conditions, a concurrency situation of the device115, or XPAN constraints may change over time. Such changes may trigger, be associated with, or mandate a TWT parameter update. Further, in applications or use cases associated with low latency (e.g., ULL gaming and streaming lossless audio), the TWT parameter update may be expected to be performed with low latency, to continue to meet XPAN constraints without compromising a user experience. As an example, for XPAN gaming use cases, a TWT SP240may be approximately 2 ms. A communication overhead of the updated TWT parameters, or other information communicated from the device115to the wireless earbud130-aand the wireless earbud130-b, may also be expected to be relatively small.

In some systems, however, a TWT parameter update procedure may be associated with a relatively high latency. Further, because TWT sessions may be initiated by the wireless earbud130-aand the wireless earbud130-b(with default or initial parameters), any update for TWT parameters triggered by a condition change on the device115may involve the device115transmitting the updated parameters to the wireless earbud130-aand the wireless earbud130-bfollowed by a TWT parameter change at the wireless earbud130-aand the wireless earbud130-b.

An example TWT parameter update procedure may include a sequence of signaling steps that involve one or more transmissions using a Bluetooth link, which may introduce relatively large delays. For example, a Wi-Fi sub-system (SS) of the device115may send, to a Bluetooth host (BT host) of the device115, a request (e.g., a TWT parameter update request) to update one or more TWT parameters after one or more conditions are detected that trigger one or more TWT parameter changes. The BT host of the device115may communicate an updated set of TWT parameters to a BT host of a primary earbud (e.g., the wireless earbud130-a) using a Bluetooth link. Such an updated TWT configuration sent via a Bluetooth link may add approximately 80 ms of delay. The BT host of the primary earbud may signal the new TWT parameters internally to a Wi-Fi SS of the primary earbud, and the BT host of the primary earbud may communicate the new TWT parameters to a BT host of a secondary earbud (e.g., the wireless earbud130-b) using a Bluetooth link. Such an indication of a TWT configuration via a Bluetooth link between the primary earbud and the secondary earbud may add approximately 120 ms of delay. The BT host of the secondary earbud may signal the new TWT parameters internally to a Wi-Fi SS of the secondary earbud.

The Wi-Fi SS of the primary earbud may start a TWT session teardown and parameter update process. The TWT session teardown and parameter update process may involve a transmission, from the Wi-Fi SS of the primary earbud to the Wi-Fi SS of the device115via an XPAN Wi-Fi link, of a TWT Teardown message and a TWT Request message that carries the new TWT parameters, and a transmission, from the Wi-Fi SS of the device115to the Wi-Fi SS of the primary earbud via the XPAN Wi-Fi link, of an acknowledgement (ACK) of the new TWT parameters with a TWT Response message. The Wi-Fi SS of the device115may update the BT host of the device115that a new TWT session with the primary earbud has been established (e.g., the Wi-Fi SS may indicate a TWT session update to the BT host). Such a TWT session teardown and parameter update process may additionally be performed between the device115and the secondary earbud.

FIG.3is an example300of a link set up procedure for multi-link devices. As shown inFIG.3, an access point (AP) multi-link device (MLD)302may establish multiple links with a non-AP MLD. The multiple links may be associated with different frequency bands.

As shown inFIG.3, an AP multi-link device302may include, or may be associated with, a first AP304, a second AP306, and a third AP308. A non-AP multi-link device310may include, or may be associated with, a station312, a station314, and a station316. The station312may transmit a TWT request318that requests for the AP MLD302to set up TWT sessions between the first AP304, the second AP306, and the third AP308with the station312, station the314, and the station316. For example, the TWT request318may include a bitmap that indicates a request to set up TWT sessions on the links of each of the station312, the station314, and the station316. The bitmap may be associated with different frequency bands that are associated with the different links on which the stations operate.

The first AP304may transmit a TWT response320that indicates an initiation of setup procedures for each of the station312, the station314and the station316. Based at least in part on the first AP304transmitting the TWT response320, the AP MLD302and the non-AP MLD310may have previously performed link setup procedures and subsequently perform TWT setups with each of the station312, the station314and the station316. For example, the first AP304and the station312may perform a first TWT setup322, the second AP306and the station314may perform a second TWT setup324, and the third AP308and the station316may perform a third TWT setup326.

FIG.4is an example400of a configuration of multi-link communications by MLDs. As shown inFIG.4, an AP MLD may communication via multiple links with a non-AP MLD. The multiple links may be associated with different frequency bands.

As shown inFIG.4, the AP MLD may communicate with the non-AP MLD via a first link402, a second link404, and a third link406. The first link402may be associated with a link between a first STA of the non-AP MLD and a first wireless device of the AP MLD. Similarly, the second link404may be associated with a link between a second STA of the non-AP MLD and a second wireless device of the AP MLD, and the third link406may be associated with a link between a third STA of the non-AP MLD and a third wireless device of the AP MLD.

The non-AP STA and the AP may perform TWT setup408. The TWT setup408may include a cross-link TWT signaling mechanism to support negotiation of multiple TWT agreements associated with the links402,404, and406. However, the TWT setup408may include independent setup of the multiple TWT agreements, where timing of the first link402(e.g., a TWT start time, a TWT wake interval, and/or a TWT service period duration) is configured without consideration of timing of the second link404or the third link406.

As shown inFIG.4, the first link402may be configured with a TWT service period (SP)410and a TWT wake interval412. The TWT SP410may be configured to begin at a start time of the TWT wake interval412. Similarly, the second link404may be configured with a TWT SP414and a TWT wake interval416and the third link406may be configured with a TWT SP418and a TWT wake interval420.

As shown inFIG.4, based at least in part on TWT timing of the first link402, the second link404, and the third link406being unaligned, the non-AP MLD and the AP MLD may have an active TWT SP for at least one of the links during an extended amount of time relative to an SP of any one of the links. In this way, the first wireless device may consume power resources that may have otherwise been conserved if the TWT SPs were aligned (e.g., start times of the TWTs were aligned). This is based at least in part on the non-AP MLD and the AP MLD maintaining an active transmission and/or reception chain during the TWT SPs for all of the links.

In some aspects described herein, a first wireless device (e.g., an STA and/or a non-AP MLD) may transmit a request to configure a TWT schedule for a first link associated with a second wireless device. In some aspects, the request to configure the TWT schedule for the first link may include an indication (e.g., a request) for TWT alignment with a TWT schedule of a second link associated with a third wireless device. In some aspects, the indication for TWT alignment with the TWT schedule of the second link may indicated within a field that is configured to indicate a TWT start time.

The second wireless device may receive the request and may configure the TWT schedule of the first link for time alignment with the TWT schedule of the second link. In some aspects, the second wireless device and the third wireless device may be APs associated with an AP MLD. In some aspects, the third wireless device may be a same device as the second wireless device.

In some aspects, the first wireless device may transmit the indication within a TWT request with an explicit request for MLD alignment. For example, a TWT request frame sent by the first wireless device (e.g., a non-AP STA of an MLD) includes two or more TWT IEs where a setup command field (e.g., TWT Setup Command field) of all of the TWT elements indicates to request a TWT (e.g., Request TWT). In some aspects, no mixing of commands may be allowed (e.g., from a perspective of a communication protocol) in the same request frame.

Each bitmap field of a link identification (e.g., Link ID Bitmap field) contained in the TWT element has only one bit set to 1, and a nonzero bit cannot appear more than once unless a range of TWT parameters is being provided for that particular link. These are links for which the TWT alignment is requested by the first wireless device (e.g., a first STA) affiliated with a non-AP MLD.

Each TWT field of TWT IEs may be in reference to a timing synchronization function (TSF) time of an associated link indicated by the Link ID Bitmap field of the TWT IE. In this way, the first wireless device may indicate a specific first TWT. Alternatively, the first wireless device may indicate an MLD alignment request using any nonzero TWT value. In some aspects, when a TWT value is set to zero, the TWT value indicates that the first wireless device does not request timing alignment.

In some aspects, APs of the AP MLD may transmit beacons (e.g., periodically) or other information that provides connection and/or synchronization information associated with the APs. For example, a beacon may include a time stamp that indicates an absolute time, in a domain of an associated AP, associated with transmission of the beacon. In this way, the first wireless device may identify an absolute time of the AP and may identify a desired TWT schedule in the domain of the associated AP. For example, different STAs of the first wireless device may obtain information from associated beacons and share the information with the first wireless device (e.g., an STA associated with the first link). In some aspects, the APs may be aware of absolute times of others of the APs based at least in part on being affiliated (e.g., affiliated with an AP MLD).

In some aspects, the STAs affiliated with the non-AP MLD may coordinate to request that all TWTs have a same global start time (e.g., independent from domains of the APs); however, the TWTs are requested with reference to the timestamps of each of the APs operating in those links. In some aspects the TWT wake intervals, which are specified by the TWT Wake Interval Mantissa & TWT Wake Interval Exponent fields of the TWT elements, may be equal (e.g., within a threshold difference) across TWT IEs.

In some aspects, TWT wake intervals may be multiples of a common denominator instead of aligning at the start of each TWT wake interval for both of the links. For example, a first link may have a TWT wake interval that is 2 times (×) a TWT wake interval of a second link. Additionally, or alternatively, a third link may have a TWT wake interval that is 3×the TWT wake interval of the second link. In this way, each of the links will have a common TWT start time every six TWT wake intervals of the second link.

In some aspects, a communication protocol may allow a nonzero TWT field in a TWT request frame with a TWT Setup Command that indicates a Request TWT. In some aspects, the nonzero TWT field may indicate a TSF time at which the first wireless device requests for a first TWT start time (e.g., to cause global start time alignment with one or more additional TWT start times of other links).

In some aspects, the communication protocol may require TWT wake intervals across the links to be a multiple of a common denominator. In some aspects, the multiple may be limited in size to increase a frequency of time alignment. For example, the multiple may be limited to 4, 6, 8, or 12, among other examples. In some aspects, other values for TWT parameters (e.g., TWT SP duration) may be dependent on a link configuration.

In some aspects, the second device (e.g., an AP associated with an AP MLD) may respond to the TWT request that indicates time alignment with the second link. In some aspects, a TWT request frame sent by a non-AP STA includes at least two TWT IEs where TWT Setup Commands of all of the TWT IEs indicate a Request TWT and nonzero TWT fields. Based at least in part on these TWT request frames, the second device (e.g., the AP) may respond with a TWT response frame that includes a same number of TWT IEs with a TWT Setup Command that indicates either Accept TWT or Reject TWT. In some aspects, each Link ID Bitmap of the TWT IEs has only one bit equal to 1 (e.g., as with a TWT request).

In some aspects, no TWT agreement exists for links identified in a Link ID Bitmap within a TWT IE with Reject TWT, and a TWT agreement exists for links identified in a Link ID Bitmap within a TWT IE with Accept TWT. In some aspects, the TWT agreement may use TWT parameters identified in the TWT response frame.

Each TWT IE with Accept TWT may indicate TWT parameters, such as TWT fields of the TWT IEs in reference to the TSF time of the link identified in the TWT IE, with TWT fields across the links pointing to the same global start time. In some aspects, TWT Wake Interval mantissa and TWT Wake Interval exponent field may be equal (e.g., within a threshold difference) for all of the TWT IEs requested for alignment. In some aspects, the TWT Wake Interval mantissa and TWT Wake Interval exponent field may be related based at least in part on having a common denominator (e.g., being a multiple of the common denominator).

In some aspects, a communication protocol may require TWT fields of TWT IEs with Accept TWT to point to the same global start time. The values may be in reference to TSF times of the links identified in the respective TWT IEs. TWT fields that point to future TWTs may be used (e.g., multiples of the TWT Wake interval) to account for intra-AP delays.

In some aspects, TWT request and TWT response frames negotiating broadcast TWTs (e.g., B-TWTs) may include one or more TWT IEs, and follow similar rules to an Individual-TWT (I-TWT) case, with one or more modifications. For example, a B-TWT IE may include one or more B-TWT parameter sets, with the TWT field pointing to a partial TSF time (e.g., a time relative to a start-up of an associated AP or a rest time at which the AP TSF time returns to zero) rather than a global TSF time. In some aspects, this may be based at least in part on the TWT field being only 2 octets long. In some aspects, resolution of these TWTs may be 1 time unit (TU), hence alignment across links is at a 1 TU level of granularity. In some aspects, the TWT wake intervals may be configured to be multiples of 1 TU in addition to being multiples of a common denominator. Additionally, or alternatively, one or more constraints associated with IEs may be applied at a B-TWT Parameter Set level as opposed to the IE level.

Based at least in part on TWT timing alignment of multiple links between the first wireless device and the second wireless device (e.g., an AP MLD), the first wireless device and the second wireless device may reduce an amount of time during which the first wireless device has an active TWT SP for at least one of the links. In this way, the first wireless device may conserve power resources that may have otherwise been consumed if the TWT SPs were not aligned.

FIG.5is a diagram of an example500associated with TWT alignment, in accordance with the present disclosure. As shown inFIG.5, a first MLD (e.g., one or more STAs associated with the first MLD) may communicate with a second MLD (e.g., one or more APs). In some aspects, the first MLD and the second MLD may be part of a wireless network (e.g., wireless communication system100). The first MLD and the second MLD may have established a wireless connection (e.g., via one or more links using one or more pairs of STAs and APs) prior to operations shown inFIG.5. The first MLD or an STA of the first MLD may be referred to as a first wireless device. The second MLD or an AP of the second MLD may be referred to as a second wireless device.

As shown by reference number505, the first MLD may receive, and the second MLD may transmit, an indication of a TWT start time associated with a second link. For example, an STA of the first MLD may receive a communication from an AP of the second MLD associated with the second link. In some aspects, the second link may be a link between the first MLD (e.g., a second STA of the first MLD) and a wireless device (e.g., a second AP of the second MLD).

As shown by reference number510, the first MLD may identify a TWT start time associated with the second link. In some aspects, the first MLD may identify the TWT start time associated with the second link based at least in part on receiving the indication as described in connection with reference number505. In some aspects, the first MLD may identify the TWT start time associated with the second link independently from (e.g., in absence of) receiving the indication, as described in connection with reference number505.

In some aspects, the first MLD may identify the TWT start time associated with the second link based at least in part on receiving a beacon broadcast by an AP associated with the second link. In some aspects, the first MLD may identify the TWT start time associated with the second link based at least in part on a time stamp of the beacon. In some aspects, the TWT start time associated with the second link may be a requested TWT start time associated with the second link, as identified in a time domain of the AP associated with the second link.

As shown by reference number515, the first MLD may transmit a request to configure a TWT schedule for a first link with TWT alignment associated with the second link. For example, the first MLD may transmit the request including an indication for TWT alignment with a TWT schedule of the second link. In some aspects, the indication for the TWT alignment may be indicated within a field that is configured to indicate a TWT start time. In some aspects, the indication for the TWT alignment may include, within the field that is configured to indicate the TWT start time, a non-zero value or an indication of a requested TWT start time for the first link.

In some aspects, the request to configure the TWT schedule with alignment associated with the second link may indicate a request to be aligned with the second link. In some aspects, the request to configure the TWT schedule with alignment associated with the second link may indicate a TWT start time and/or periodicity requested for the first link based at least in part on identification of the TWT start time associated with the second link as indicated in connection with reference number510.

In some aspects, the request to configure the TWT schedule with alignment associated with the second link may indicate a TWT start time and/or periodicity requested for the first link based at least in part on the TWT start time and/or periodicity being aligned with a requested TWT start time and/or periodicity associated with the second link. For example, the first MLD may transmit the request to configure the TWT schedule for the first link along with a request to configure a TWT schedule for the second link, with an indication to align the TWT start times of the first link and the second link. In some aspects, the request to align the start times of the first link and the second link may include an indication of a first start time for the first link in a time domain of a first AP (e.g., of the second MLD) associated with the first link, and an indication of a second start time for the second link in a time domain of a second AP (e.g., of the second MLD) associated with the second link. In some aspects, an absolute time in the time domain of the first AP satisfies a threshold relative to the TWT start time, associated with the second link, associated with a time in a time domain of the second AP.

In some aspects, a difference in time between the requested TWT start time and the TWT start time associated with the second link may satisfy a threshold. For example, the difference in time may be less than or equal to an alignment threshold such that the TWT start times are substantially equal in a global time domain (e.g., possibly different in local time domains of APs associated with the first link or the second link).

In some aspects, TWT alignment includes satisfaction of a first threshold by a first difference in time between the TWT start time associated with the first link and a TWT start time associated with the second link. In some aspects, TWT alignment includes satisfaction of a second threshold by a second difference in time between the TWT start time and a subsequent TWT start time associated with a subsequent TWT period associated with the second link. For example, the TWT start time of the first link may have timing alignment with a subsequent TWT start time, but not all TWT start times, associated with the second link. In some aspects, the periodicities and/or TWT wake times may have durations that are multiples of a common denominator. For example, a first periodicity may be 12 TUs and a second periodicity may be 8 TUs, with a common denominator of 4. In some aspects, the multiples may be limited in size (e.g., less than 10). In some aspects, TWT alignment includes satisfaction of a third threshold by a third difference in time between a subsequent TWT start time associated with a subsequent TWT period associated with the first link and the TWT start time associated with the second link. In some aspects, TWT alignment includes satisfaction of a fourth threshold by a fourth difference between a first TWT wake interval mantissa and a first exponent field of the first link, and a second TWT wake interval mantissa and a second exponent field of the second link.

In some aspects, TWT alignment includes a time offset between occasions of the TWT start time and occasions of an additional start time associated with the second link. In some aspects, the time offset may be based at least in part on a TWT service period associated with the first TWT schedule (e.g., with an offset configured to start a second TWT start time of the second link after completion of a TWT SP of a first TWT wake interval of the first link). For example, the first link may be TWT aligned with the second link to avoid or reduce simultaneous TWT SPs. In some aspects, the first MLD may be configured to communicate via only one link at a time (e.g., based at least in part on hardware or other resource limitations). In this way, the first MLD may be able to hop between links during concurrency times of other links, with non-overlapping TWT SPs.

In some aspects, timing alignment includes satisfaction of a threshold by a first difference in time between a first TWT periodicity of the first link and a second TWT periodicity of the second link. In some aspects, timing alignment includes satisfaction of a threshold by a second difference in time between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link. In some aspects, timing alignment includes satisfaction of a threshold by a third difference in time between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link.

As shown by reference number520, the first MLD may receive, and the second MLD may transmit, a response indicating a TWT start time associated with the first link. In some aspects, the TWT start time may be based at least in part on the indication for TWT alignment with the TWT schedule of the second link. For example, the second MLD may transmit an indication of acceptance of a requested start time as indicated in the request to configure the TWT schedule for the first link with the TWT alignment associated with the second link, as described in connection with reference number515. In some aspects, the indication of the TWT start time may be in a same field of the response as the indication of alignment with the second link in the request to configure the TWT schedule for the first link (e.g., a TWT start time field).

In some aspects, the response indicating the TWT start time within the field indicates a TWT start time as identified by the second MLD (e.g., the first AP) as satisfying a first threshold relative to the TWT start time associated with the second link, the requested TWT start time (e.g., a confirmation of the requested start time), or the TWT start time as identified by the second MLD (e.g., the first AP) as satisfying a second threshold relative to the requested TWT start time.

In some aspects, the first service period duration of the first link is independent from the second service period duration of the second link. In some aspects, the TWT start time is an absolute time (e.g., relative to a start-up time of the second wireless device). In some aspects, the TWT start time is relative to a start-up time or a reference time in a time domain of the second wireless device (e.g., a partial time stamp). In some aspects, the TWT start time is relative to the reference time based at least in part on a number of bits available to indicate the TWT start time. For example, if a TWT field includes two octets, the field configured to indicate the TWT start time may indicate a selection of one of 216TUs. If a TU is 1 second, the TWT field can only indicate a TWT start time with a unique value of the field for about 18 hours and 12 minutes. To support an indication on a subsequent day or after an amount of time associated with a maximum number of unique values of the field, the TWT field may indicate a TWT start time relative to a reference time (e.g., relative to a maximum value of the TWT start time field, relative to a relative to a start of a day, or relative to a time in the time domain of the second wireless device, among other examples).

A reset time may be used instead of a start-up time. The reset time may be a time at which the time in the time domain of the second wireless device resets to zero based at least in part on reaching a maximum time in a time counter. In some aspects, the first link and/or the second link is associated with a broadcast TWT.

In some aspects, the second MLD may transmit the response indicating the start time (e.g., a first start time associated with the first link) based at least in part on receiving the request to configure the TWT schedule for the first link. In some aspects, the second MLD may transmit the response indicating the start time independently from (e.g., in the absence of) receiving the request to configure the TWT schedule for the first link. For example, the second MLD may transmit the response indicating the start time as, or included in, an individually addressed solicited response, a solicited response based at least in part on reception of a request to configure a TWT schedule for the first link, and/or a broadcast response, among other examples.

As shown by reference number525, the first MLD and the second MLD may communicate using the first link and the second link. For example, the first MLD and the second MLD may communicate with time alignment (also referred to as “timing alignment” of the first link and the second link. In some aspects, the first MLD may communicate with the second wireless device via the first link using the first TWT start time in the first link and/or using the second TWT start time in the second link. In some aspects, the first MLD may initiate a TWT teardown of one or more of the first TWT schedule or the second TWT schedule based at least in part on receiving the response. For example, the first MLD may initiate the TWT teardown to reset a configuration of the first link or the second link.

Based at least in part on TWT timing alignment of multiple links between the first MLD (e.g., a first wireless device) and the second MLD (e.g., a second wireless device), the first MLD and the second MLD may reduce an amount of time during which the first MLD has an active TWT SP for at least one of the links. In this way, the first MLD may conserve power resources that may have otherwise been consumed if the TWT SPs were not aligned.

FIG.6is an example600of a configuration of multi-link communications by MLDs. As shown inFIG.6, an AP MLD multiple links with a non-AP MLD. The multiple links may be associated with different frequency bands.

As shown inFIG.6, the AP MLD may communicate with the non-AP MLD via a first link602, a second link604, and a third link606. The first link602may be associated with a link between a first STA of the non-AP MLD and a first wireless device of the AP MLD. Similarly, the second link604may be associated with a link between a second STA of the non-AP MLD and a second wireless device of the AP MLD, and the third link606may be associated with a link between a third STA of the non-AP MLD and a third wireless device of the AP MLD.

The non-AP and the AP may perform TWT setup608. The TWT setup608may include a cross-link TWT signaling mechanism to support negotiation of multiple TWT agreements associated with the links602,604, and606. The TWT setup608may indicate a request for time alignment among the links602,604, and606.

As shown inFIG.6, the first link602may be configured with a TWT service period (SP)610and a TWT wake interval612. The TWT SP610may be configured to begin at a start time of the TWT wake interval612. Similarly, the second link604may be configured with a TWT SP614and a TWT wake interval616, and the third link606may be configured with a TWT SP618and a TWT wake interval620.

As shown inFIG.6, based at least in part on TWT timing of the first link602, the second link604, and the third link606being aligned, the non-AP MLD and the AP MLD may have active TWT SPs that at least partially overlap. In this way, the first wireless device may conserve power resources that may have otherwise been consumed if the TWT SPs were unaligned (e.g., start times of the TWTs were unaligned).

FIG.7is an example700of a configuration of multi-link communications by MLDs. As shown inFIG.7, an AP MLD multiple links with a non-AP MLD. The multiple links may be associated with different frequency bands.

As shown inFIG.7, the AP MLD may communicate with the non-AP MLD via a first link702, a second link704, and a third link706. The first link702may be associated with a link between a first STA of the non-AP MLD and a first wireless device of the AP MLD. Similarly, the second link704may be associated with a link between a second STA of the non-AP MLD and a second wireless device of the AP MLD, and the third link706may be associated with a link between a third STA of the non-AP MLD and a third wireless device of the AP MLD.

The non-AP and the AP may perform TWT setup708. The TWT setup708may include a cross-link TWT signaling mechanism to support negotiation of multiple TWT agreements associated with the links702,704, and706. The TWT setup708may indicate a request for time alignment among the links702,704, and706.

As shown inFIG.7, the first link702may be configured with a TWT service period (SP)710and a TWT wake interval712. The TWT SP710may be configured to begin at a start time of the TWT wake interval712. Similarly, the second link704may be configured with a TWT SP714and a TWT wake interval716, and the third link706may be configured with a TWT SP718and a TWT wake interval720.

As shown inFIG.7, based at least in part on TWT timing of the first link702, the second link704, and the third link706being aligned, the non-AP MLD and the AP MLD may have active TWT SPs that at least partially overlap periodically. For example, every second TWT SP710at least partially overlaps with every TWT SP714, and with every third TWT SP718. In this way, the first wireless device may conserve power resources that may have otherwise been consumed if the TWT SPs were unaligned (e.g., start times of the TWTs were unaligned) or that overlapped with a periodicity that is larger than a threshold number of TWT wake intervals (e.g., 4, 8, 10, 12).

FIG.8is a diagram illustrating an example process800performed, for example, by a first wireless device, in accordance with the present disclosure. Example process800is an example where the first wireless device (e.g., a first MLD and/or a first STA of a non-AP MLD) performs operations associated with TWT alignment.

As shown inFIG.8, in some aspects, process800may include transmitting, to a second wireless device, a request to configure a TWT schedule for a first link associated with the second wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time (block810). For example, the first wireless device (e.g., using communication manager1008and/or transmission component1004, depicted inFIG.10) may transmit, to a second wireless device, a request to configure a TWT schedule for a first link associated with the second wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time, as described above.

As further shown inFIG.8, in some aspects, process800may include receiving, from the second wireless device, a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link (block820). For example, the first wireless device (e.g., using communication manager1008and/or reception component1002, depicted inFIG.10) may receive, from the second wireless device, a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link, as described above.

In some aspects, block810may be omitted and the first wireless device may communicate based at least in part on receiving the response (e.g., an unsolicited response).

In a first aspect, the indication within the field that is configured to indicate the TWT start time comprises one or more of a non-zero value, or an indication of a requested TWT start time for the first link.

In a second aspect, alone or in combination with the first aspect, a difference in time between the requested TWT start time and an additional TWT start time associated with the second link satisfies a threshold.

In a third aspect, alone or in combination with one or more of the first and second aspects, the requested TWT start time for the first link indicates a time in a time domain of the second wireless device.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, absolute time in the time domain of the second wireless device satisfies a threshold relative to an additional TWT start time, associated with the second link, associated with a time in an additional time domain of the third wireless device.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the response indicating the TWT start time within the field indicates one or more of the TWT start time as identified by the second wireless device as satisfying a first threshold relative to an additional TWT start time associated with the second link, the requested TWT start time, or the TWT start time as identified by the second wireless device as satisfying a second threshold relative to the requested TWT start time.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, TWT alignment comprises one or more of satisfaction of a first threshold by a first difference in time between the TWT start time and an additional TWT start time associated with the second link, satisfaction of a second threshold by a second difference in time between the TWT start time and a subsequent TWT start time associated with a subsequent TWT period associated with the second link, satisfaction of a third threshold by a third difference in time between a subsequent TWT start time associated with a subsequent TWT period associated with the first link and the additional TWT start time associated with the second link, satisfaction of a fourth threshold by a fourth difference between a first TWT wake interval mantissa and a first exponent field of the first link and a second TWT wake interval mantissa and a second exponent field of the second link, or a time offset between occasions of the TWT start time and occasions of an additional start time associated with the second link.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the time offset is based at least in part on a TWT service period associated with the first TWT schedule.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, TWT alignment comprises one or more of satisfaction of a threshold by a first difference in time between a first TWT periodicity of the first link and a second TWT periodicity of the second link, satisfaction of a threshold by a second difference in time between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link, or satisfaction of a threshold by a third difference in time between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process800includes identifying an additional TWT start time associated with the second link based at least in part on an indication by the third wireless device or based at least in part on an indication by the second wireless device.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the first link is configured with a first service period duration and the second link is configured with a second service period duration, and the first service period duration is independent from the second service period duration.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the TWT start time is an absolute time, or the TWT start time is relative to a start-up time or a reference time in a time domain of the second wireless device.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the first link is associated with a broadcast TWT.

FIG.9is a diagram illustrating an example process900performed, for example, by a second wireless device, in accordance with the present disclosure. Example process900is an example where the second wireless device (e.g., second MLD, an AP of an AP MLD, among other examples) performs operations associated with TWT alignment.

As shown inFIG.9, in some aspects, process900may include receiving a request to configure a TWT schedule for a first link associated with a first wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with the first wireless device and a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time (block910). For example, the second wireless device (e.g., using communication manager1108and/or reception component1102, depicted inFIG.11) may receive a request to configure a TWT schedule for a first link associated with a first wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with the first wireless device and a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time, as described above.

As further shown inFIG.9, in some aspects, process900may include transmitting a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link (block920). For example, the second wireless device (e.g., using communication manager1108and/or transmission component1104, depicted inFIG.11) may transmit a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link, as described above.

In some aspects, block910may be omitted and the second wireless device may communicate based at least in part on transmitting the response (e.g., an unsolicited response).

In a first aspect, the indication within the field that is configured to indicate the TWT start time comprises one or more of a non-zero value, or an indication of a requested TWT start time for the first link.

In a second aspect, alone or in combination with the first aspect, a difference in time between the requested TWT start time and an additional TWT start time associated with the second link satisfies a threshold.

In a third aspect, alone or in combination with one or more of the first and second aspects, the requested TWT start time for the first link indicates a time in a time domain of the second wireless device.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the time in the time domain of the second wireless device satisfies a threshold relative to an additional TWT start time, associated with the second link, associated with a time in an additional time domain of the third wireless device.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the response indicating the TWT start time within the field indicates one or more of the TWT start time as identified by the second wireless device as satisfying a first threshold relative to an additional TWT start time associated with the second link, the requested TWT start time, or the TWT start time as identified by the second wireless device as satisfying a second threshold relative to the requested TWT start time.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, TWT alignment comprises one or more of satisfaction of a first threshold by a first difference in time between the TWT start time and an additional TWT start time associated with the second link, satisfaction of a second threshold by a second difference in time between the TWT start time and a subsequent TWT start time associated with a subsequent TWT period associated with the second link, satisfaction of a third threshold by a third difference in time between a subsequent TWT start time associated with a subsequent TWT period associated with the first link and the additional TWT start time associated with the second link, or satisfaction of a fourth threshold by a fourth difference between a first TWT wake interval mantissa and a first exponent field of the first link and a second TWT wake interval mantissa and a second exponent field of the second link, or a time offset between occasions of the TWT start time and occasions of an additional start time associated with the second link.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the time offset is based at least in part on a TWT service period associated with the first TWT schedule.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, TWT alignment comprises one or more of satisfaction of a threshold by a first difference in time between a first TWT periodicity of the first link and a second TWT periodicity of the second link, satisfaction of a threshold by a second difference in time between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link, or satisfaction of a threshold by a third difference in time between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process900includes identifying an additional TWT start time associated with the second link based at least in part on the second wireless device and the third wireless device being associated with a same AP multi-link device.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the first link is configured with a first service period duration and the second link is configured with a second service period duration, and the first service period duration is independent from the second service period duration.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the TWT start time is an absolute time, or the TWT start time is relative to a start-up time or a reference time in a time domain of the second wireless device.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the first link is associated with a broadcast TWT.

The transmission component1004may transmit, to a second wireless device, a request to configure a TWT schedule for a first link associated with the second wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time. The reception component1002may receive, from the second wireless device, a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link.

The communication manager1008may identify an additional TWT start time associated with the second link based at least in part on an indication by the third wireless device or based at least in part on an indication by the second wireless device.

FIG.11is a diagram of an example apparatus1100for wireless communication, in accordance with the present disclosure. The apparatus1100may be a second wireless device, or a second wireless device may include the apparatus1100. In some aspects, the apparatus1100includes a reception component1102and a transmission component1104, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1100may communicate with another apparatus1106(such as a STA, an AP, or another wireless communication device) using the reception component1102and the transmission component1104. As further shown, the apparatus1100may include a communication manager1108

The reception component1102may receive a request to configure a TWT schedule for a first link associated with a first wireless device, the request including an indication for TWT alignment with a TWT schedule of a second link associated with the first wireless device and a third wireless device, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time. The transmission component1104may transmit a response indicating a TWT start time within the field, the TWT start time based at least in part on the indication for TWT alignment with the TWT schedule of the second link.

The communication manager1108may identify an additional TWT start time associated with the second link based at least in part on the second wireless device and the third wireless device being associated with a same AP multi-link device.

The following provides an overview of a first set of some Aspects of the present disclosure:Aspect 1: A method of wireless communication performed by a first wireless device, comprising: receiving, from a second wireless device, a response indicating a first TWT start time of a first TWT schedule for a first link associated with the second wireless device, the response further indicating TWT alignment with a second TWT schedule for a second link having a second TWT start time, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time; communicating with the second wireless device via the first link based at least in part on the response.Aspect 2: The method of Aspect 1, wherein the response comprises one or more of: an individually addressed unsolicited response, a broadcast response, or a solicited response based at least in part on reception of a request to configure a TWT schedule for the first link.Aspect 3: The method of any of Aspects 1-2, wherein communicating with the second wireless device via the first link based at least in part on the response comprises one or more of: communicating using the first TWT start time in the first link; communicating using the second TWT start time in the second link; or initiating a TWT teardown of one or more of the first TWT schedule or the second TWT schedule.Aspect 4: The method of any of Aspects 1-3, wherein the indication within the field that is configured to indicate the TWT start time comprises one or more of: a non-zero value, or an indication of a requested TWT start time for the first link.Aspect 5: The method of Aspect 4, wherein a difference in time between the requested TWT start time and the second TWT start time associated with the second link satisfies a threshold.Aspect 6: The method of Aspect 4, wherein the requested TWT start time for the first link indicates a time in a time domain of the second wireless device.Aspect 7: The method of Aspect 6, wherein the time in the time domain of the second wireless device satisfies a threshold relative to an additional TWT start time, associated with the second link, associated with a time in an additional time domain of a third wireless device.Aspect 8: The method of Aspect 4, wherein the response indicating the first TWT start time within the field indicates one or more of: the first TWT start time as identified by the second wireless device as satisfying a first threshold relative to the second TWT start time associated with the second link, the requested TWT start time, or the first TWT start time as identified by the second wireless device as satisfying a second threshold relative to the requested TWT start time.Aspect 9: The method of any of Aspects 1-8, wherein TWT alignment comprises one or more of: satisfaction of a first threshold by a first difference in time between the first TWT start time and the second TWT start time, satisfaction of a second threshold by a second difference in time between the first TWT start time and a subsequent TWT start time associated with a subsequent TWT period associated with the second link, satisfaction of a third threshold by a third difference in time between a subsequent TWT start time associated with a subsequent TWT period associated with the first link and the second TWT start time associated with the second link, satisfaction of a fourth threshold by a fourth difference between a first TWT wake interval mantissa and a first exponent field of the first link and a second TWT wake interval mantissa and a second exponent field of the second link, or a time offset between occasions of the first TWT start time and occasions of the second TWT start time associated with the second link.Aspect 10: The method of Aspect 9, wherein the time offset is based at least in part on a TWT service period associated with the first TWT schedule.Aspect 11: The method of any of Aspects 1-10, wherein TWT alignment comprises one or more of: satisfaction of a threshold by a first difference in time between a first TWT periodicity of the first link and a second TWT periodicity of the second link, satisfaction of a threshold by a second difference in time between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link, or satisfaction of a threshold by a third difference in time between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link.Aspect 12: The method of any of Aspects 1-11, wherein the first link is configured with a first service period duration and the second link is configured with a second service period duration, and wherein the first service period duration is independent from the second service period duration.Aspect 13: The method of any of Aspects 1-12, wherein the first TWT start time is an absolute time, or wherein the first TWT start time is relative to a start-up time or a reference time in a time domain of the second wireless device.Aspect 14: A method of wireless communication performed by a second wireless device, comprising: transmitting, to a first wireless device, a response indicating a first TWT start time of a first TWT schedule for a first link associated with the first wireless device, the response further indicating TWT alignment with a second TWT schedule for a second link having a second TWT start time, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time; and communicating with the first wireless device via the first link based at least in part on the response.Aspect 15: The method of Aspect 14, wherein the response comprises one or more of: an individually addressed unsolicited response, a broadcast response, or a solicited response based at least in part on reception of a request to configure a TWT schedule for the first link.Aspect 16: The method of any of Aspects 14-15, wherein communicating with the second wireless device via the first link based at least in part on the response comprises one or more of: communicating using the first TWT start time in the first link; communicating using the second TWT start time in the second link; or initiating a TWT teardown of one or more of the first TWT schedule or the second TWT schedule.Aspect 17: The method of any of Aspects 14-16, wherein the indication within the field that is configured to indicate the TWT start time comprises one or more of: a non-zero value, or an indication of a requested TWT start time for the first link.Aspect 18: The method of Aspect 17, wherein a difference in time between the requested TWT start time and the second TWT start time associated with the second link satisfies a threshold.Aspect 19: The method of Aspect 17, wherein the requested TWT start time for the first link indicates a time in a time domain of the second wireless device.Aspect 20: The method of Aspect 19, wherein the time in the time domain of the second wireless device satisfies a threshold relative to an additional TWT start time, associated with the second link, associated with a time in an additional time domain of a third wireless device.Aspect 21: The method of Aspect 17, wherein the response indicating the first TWT start time within the field indicates one or more of: the first TWT start time as identified by the second wireless device as satisfying a first threshold relative to the second TWT start time associated with the second link, the requested TWT start time, or the first TWT start time as identified by the second wireless device as satisfying a second threshold relative to the requested TWT start time.Aspect 22: The method of any of Aspects 14-21, wherein TWT alignment comprises one or more of: satisfaction of a first threshold by a first difference in time between the first TWT start time and the second TWT start time, satisfaction of a second threshold by a second difference in time between the first TWT start time and a subsequent TWT start time associated with a subsequent TWT period associated with the second link, satisfaction of a third threshold by a third difference in time between a subsequent TWT start time associated with a subsequent TWT period associated with the first link and the second TWT start time associated with the second link, or satisfaction of a fourth threshold by a fourth difference between a first TWT wake interval mantissa and a first exponent field of the first link and a second TWT wake interval mantissa and a second exponent field of the second link, or a time offset between occasions of the first TWT start time and occasions of the second TWT start time associated with the second link.Aspect 23: The method of Aspect 22, wherein the time offset is based at least in part on a TWT service period associated with the first TWT schedule.Aspect 24: The method of any of Aspects 14-23, wherein TWT alignment comprises one or more of: satisfaction of a threshold by a first difference in time between a first TWT periodicity of the first link and a second TWT periodicity of the second link, satisfaction of a threshold by a second difference in time between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link, or satisfaction of a threshold by a third difference in time between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link.Aspect 25: The method of any of Aspects 14-24, wherein the first link is configured with a first service period duration and the second link is configured with a second service period duration, and wherein the first service period duration is independent from the second service period duration.Aspect 26: The method of any of Aspects 14-25, wherein the first TWT start time is an absolute time, or wherein the first TWT start time is relative to a start-up time or a reference time in a time domain of the second wireless device.Aspect 27: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-26.Aspect 28: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-26.Aspect 29: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-26.Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-26.Aspect 31: 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-26.

The following provides an overview of a second set of some Aspects of the present disclosure:

The following provides an overview of some Aspects of the present disclosure:Aspect 1: A method of wireless communication performed by a first wireless device, comprising: receiving, from a second wireless device, a response indicating a first target wake time (TWT) start time of a first TWT schedule for a first link associated with the second wireless device, the response further indicating TWT alignment with a second TWT schedule for a second link having a second TWT start time, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time; and communicating with the second wireless device via the first link based at least in part on the response.Aspect 2: The method of Aspect 1, wherein the response comprises one or more of: an individually addressed unsolicited response, a broadcast response, or a solicited response based at least in part on reception of a request to configure a TWT schedule for the first link.Aspect 3: The method of any of Aspects 1-2, wherein communicating with the second wireless device via the first link based at least in part on the response comprises one or more of: communicating using the first TWT start time in the first link; communicating using the second TWT start time in the second link; or initiating a TWT teardown of one or more of the first TWT schedule or the second TWT schedule.Aspect 4: The method of any of Aspects 1-3, wherein the indication within the field that is configured to indicate the TWT start time comprises one or more of: a non-zero value, or an indication of a requested TWT start time for the first link.Aspect 5: The method of Aspect 4, wherein a difference in time between the requested TWT start time and the second TWT start time associated with the second link satisfies a threshold.Aspect 6: The method of Aspect 4, wherein the requested TWT start time for the first link indicates a time in a time domain of the second wireless device.Aspect 7: The method of Aspect 6, wherein the time in the time domain of the second wireless device satisfies a threshold relative to an additional TWT start time, associated with the second link, associated with a time in an additional time domain of a third wireless device.Aspect 8: The method of Aspect 4, wherein the response indicating the first TWT start time within the field indicates one or more of: the first TWT start time as identified by the second wireless device as satisfying a first threshold relative to the second TWT start time associated with the second link, the requested TWT start time, or the first TWT start time as identified by the second wireless device as satisfying a second threshold relative to the requested TWT start time.Aspect 9: The method of any of Aspects 1-8, wherein the TWT alignment comprises one or more of: satisfaction of a first threshold by a first difference in time between the first TWT start time and the second TWT start time, satisfaction of a second threshold by a second difference in time between the first TWT start time and a subsequent TWT start time associated with a subsequent TWT period associated with the second link, satisfaction of a third threshold by a third difference in time between a subsequent TWT start time associated with a subsequent TWT period associated with the first link and the second TWT start time associated with the second link, satisfaction of a fourth threshold by a fourth difference between a first TWT wake interval mantissa and a first exponent field of the first link and a second TWT wake interval mantissa and a second exponent field of the second link, or a time offset between occasions of the first TWT start time and occasions of the second TWT start time associated with the second link.Aspect 10: The method of Aspect 9, wherein the time offset is based at least in part on a TWT service period associated with the first TWT schedule.Aspect 11: The method of any of Aspects 1-10, wherein TWT alignment comprises one or more of: satisfaction of a threshold by a first difference in time between a first TWT periodicity of the first link and a second TWT periodicity of the second link, satisfaction of a threshold by a second difference in time between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link, or satisfaction of a threshold by a third difference in time between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link.Aspect 12: The method of any of Aspects 1-11, wherein the first link is configured with a first service period duration and the second link is configured with a second service period duration, and wherein the first service period duration is independent from the second service period duration.Aspect 13: The method of any of Aspects 1-12, wherein the first TWT start time is an absolute time, or wherein the first TWT start time is relative to a start-up time or a reference time in a time domain of the second wireless device.Aspect 14: A method of wireless communication performed by a second wireless device, comprising: transmitting, to a first wireless device, a response indicating a first target wake time (TWT) start time of a first TWT schedule for a first link associated with the first wireless device, the response further indicating TWT alignment with a second TWT schedule for a second link having a second TWT start time, the indication for the TWT alignment indicated within a field that is configured to indicate a TWT start time; and communicating with the first wireless device via the first link based at least in part on the response.Aspect 15: The method of Aspect 14, wherein the response comprises one or more of: an individually addressed unsolicited response, a broadcast response, or a solicited response based at least in part on reception of a request to configure a TWT schedule for the first link.Aspect 16: The method of any of Aspects 14-15, wherein communicating with the second wireless device via the first link based at least in part on the response comprises one or more of: communicating using the first TWT start time in the first link; communicating using the second TWT start time in the second link; or initiating a TWT teardown of one or more of the first TWT schedule or the second TWT schedule.Aspect 17: The method of any of Aspects 14-16, wherein the indication within the field that is configured to indicate the TWT start time comprises one or more of: a non-zero value, or an indication of a requested TWT start time for the first link.Aspect 18: The method of Aspect 17, wherein a difference in time between the requested TWT start time and the second TWT start time associated with the second link satisfies a threshold.Aspect 19: The method of Aspect 17, wherein the requested TWT start time for the first link indicates a time in a time domain of the second wireless device.Aspect 20: The method of Aspect 19, wherein the time in the time domain of the second wireless device satisfies a threshold relative to an additional TWT start time, associated with the second link, associated with a time in an additional time domain of a third wireless device.Aspect 21: The method of Aspect 17, wherein the response indicating the first TWT start time within the field indicates one or more of: the first TWT start time as identified by the second wireless device as satisfying a first threshold relative to the second TWT start time associated with the second link, the requested TWT start time, or the first TWT start time as identified by the second wireless device as satisfying a second threshold relative to the requested TWT start time.Aspect 22: The method of any of Aspects 14-21, wherein the TWT alignment comprises one or more of: satisfaction of a first threshold by a first difference in time between the first TWT start time and the second TWT start time, satisfaction of a second threshold by a second difference in time between the first TWT start time and a subsequent TWT start time associated with a subsequent TWT period associated with the second link, satisfaction of a third threshold by a third difference in time between a subsequent TWT start time associated with a subsequent TWT period associated with the first link and the second TWT start time associated with the second link, satisfaction of a fourth threshold by a fourth difference between a first TWT wake interval mantissa and a first exponent field of the first link and a second TWT wake interval mantissa and a second exponent field of the second link, or a time offset between occasions of the first TWT start time and occasions of the second TWT start time associated with the second link.Aspect 23: The method of Aspect 22, wherein the time offset is based at least in part on a TWT service period associated with the first TWT schedule.Aspect 24: The method of any of Aspects 14-23, wherein the TWT alignment comprises one or more of: satisfaction of a threshold by a first difference in time between a first TWT periodicity of the first link and a second TWT periodicity of the second link, satisfaction of a threshold by a second difference in time between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link, or satisfaction of a threshold by a third difference in time between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link.Aspect 25: The method of any of Aspects 14-24, wherein the first link is configured with a first service period duration and the second link is configured with a second service period duration, and wherein the first service period duration is independent from the second service period duration.Aspect 26: The method of any of Aspects 14-25, wherein the first TWT start time is an absolute time, or wherein the first TWT start time is relative to a start-up time or a reference time in a time domain of the second wireless device.Aspect 27: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-26.Aspect 28: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-26.Aspect 29: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-26.Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-26.Aspect 31: 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-26.