Target wake-up time calibration

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a first wireless device may send a request to a second wireless device to configure a target wake-up time (TWT) schedule for a first link associated with the second wireless device, the request including an indication of a TWT calibration for the TWT schedule with a second link associated with a third wireless device, the indication for the TWT calibration is indicated within a field 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 an indication of a TWT calibration for a TWT schedule with the second link. Numerous other aspects are described.

Description

[0001] Cross - Reference to Related Applications

[0002] This patent application claims the priority of U.S. Provisional Patent Application No. 63 / 382,617, entitled "TARGET WAKE TIME ALIGNMENT", filed on November 7, 2022, and U.S. Non - Provisional Patent Application No. 18 / 180,294, entitled "ALTERNATIVE TWO - STEP RACH PROCEDURE", filed on March 8, 2023, which are hereby incorporated by reference in their entirety. Technical Field

[0003] Aspects of the present disclosure generally relate to wireless communication and techniques and apparatuses for target wake time calibration. Background Art

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

[0005] The AP can be coupled to a network such as the Internet and can enable mobile devices to communicate via the network (or communicate with other devices coupled to the access point). Wireless devices can communicate bidirectionally with network devices. For example, in a WLAN, a device can communicate with an associated AP via a downlink (e.g., the communication link from the AP to the device) and an uplink (e.g., the communication link from the device to the AP). A wireless personal area network (WPAN) that can include a Bluetooth connection can provide a short - range wireless connection between two or more paired wireless devices. For example, a wireless device such as a cellular phone can utilize WPAN communication to exchange information such as audio signals with wireless earphones. Summary of the Invention

[0006] Some aspects described herein relate to a method of wireless communication performed by a first wireless device. The method may include sending a request for a target wake time (TWT) schedule for a first link configured to be associated with a second wireless device, the request including an indication of TWT calibration for the TWT schedule of a second link associated with a third wireless device, the indication of TWT calibration being indicated within a field configured to indicate a TWT start time. The method may include receiving, from the second wireless device, a response indicating the TWT start time within the field, the TWT start time being at least partially based on the indication of TWT calibration for the TWT schedule of the second link.

[0007] Some aspects described herein relate to a method of wireless communication performed by a second wireless device. The method may include receiving a request for a TWT schedule for a first link configured to be associated with a first wireless device, the request including an indication of TWT calibration for the TWT schedule of a second link associated with the first wireless device and a third wireless device, the indication of TWT calibration being indicated within a field configured to indicate a TWT start time. The method may include sending a response indicating the TWT start time within the field, the TWT start time being at least partially based on the indication of TWT calibration for the TWT schedule of the second link.

[0008] 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 send a request for a TWT schedule for a first link configured to be associated with a second wireless device, the request including an indication of TWT calibration for the TWT schedule of a second link associated with a third wireless device, the indication of TWT calibration being indicated within a field 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 the TWT start time within the field, the TWT start time being at least partially based on the indication of TWT calibration for the TWT schedule of the second link.

[0009] 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 for a TWT schedule for a first link configured to be associated with a first wireless device, the request including an indication of TWT calibration for a TWT schedule for a second link associated with the first wireless device and a third wireless device, the indication of the TWT calibration being indicated within a field configured to indicate a TWT start time. The one or more processors may be configured to send a response indicating the TWT start time within the field, the TWT start time being at least partially based on the indication of the TWT calibration for the TWT schedule for the second link.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a first wireless device. When executed by one or more processors of the first wireless device, the instruction set may cause the first wireless device to send a request for a TWT schedule for a first link configured to be associated with a second wireless device, the request including an indication of TWT calibration for a TWT schedule for a second link associated with a third wireless device, the indication of the TWT calibration being indicated within a field configured to indicate a TWT start time. When executed by one or more processors of the first wireless device, the instruction set may cause the first wireless device to receive a response indicating the TWT start time within the field, the TWT start time being at least partially based on the indication of the TWT calibration for the TWT schedule for the second link.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a second wireless device. When executed by one or more processors of the second wireless device, the instruction set may cause the second wireless device to receive a request for a TWT schedule for a first link configured to be associated with a first wireless device, the request including an indication of TWT calibration for a TWT schedule for a second link associated with the first wireless device and a third wireless device, the indication of the TWT calibration being indicated within a field configured to indicate a TWT start time. When executed by one or more processors of the second wireless device, the instruction set may cause the second wireless device to send a response indicating the TWT start time within the field, the TWT start time being at least partially based on the indication of the TWT calibration for the TWT schedule for the second link.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a request for a TWT schedule configured for a first link associated with a second wireless device, the request including an indication of TWT calibration for a TWT schedule of a second link associated with a third wireless device, the indication of the TWT calibration being indicated within a field configured to indicate a TWT start time. The apparatus may include means for receiving, from the second wireless device, a response indicating the TWT start time within the field, the TWT start time being at least partially based on the indication of the TWT calibration for the TWT schedule of the second link.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a request for a TWT schedule configured for a first link associated with a first wireless device, the request including an indication of TWT calibration for a TWT schedule of a second link associated with the first wireless device and a third wireless device, the indication of the TWT calibration being indicated within a field configured to indicate a TWT start time. The apparatus may include means for sending a response indicating the TWT start time within the field, the TWT start time being at least partially based on the indication of the TWT calibration for the TWT schedule of the second link.

[0014] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems substantially as described herein with reference to the figures and the description and as illustrated in the figures and the description.

[0015] The features and technical advantages of examples in accordance with the present disclosure have been outlined rather broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying figures, the characteristics (both the organization and method of operation) of the concepts disclosed herein, as well as the associated advantages, will be better understood. Each of the figures is provided for the purpose of illustration and description and not as a definition of the limits of the claims.

[0016] While aspects are described herein by way of illustration of some examples, those skilled in the art will understand that these aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via integrated chip embodiments or other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features can include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a variety of devices, components, systems, distributed arrangements, and / or end-user devices of various different sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] To obtain a more specific description of the above features of the present disclosure in detail, a more detailed description of what was briefly outlined above can be obtained by referring to the aspects, some of which are illustrated in the drawings. However, it should be noted that the drawings only illustrate certain typical aspects of the present disclosure and should not be considered as limiting its scope, since the description may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1 A wireless communication system configured according to the present disclosure is shown.

[0019] Figure 2 An example of a wireless communication system supporting low-latency parameter updates for an extended personal audio network according to the present disclosure is shown.

[0020] Figure 3 is an example of a link establishment procedure for a multi-link device (MLD).

[0021] Figure 4 is an example of a configuration of multi-link communication via an MLD.

[0022] Figure 5 is a diagram of an example associated with TWT calibration according to the present disclosure.

[0023] Figure 6 is an example of a configuration of multi-link communication via an MLD.

[0024] Figure 7 This is an example of the configuration of multi-link communication via MLD.

[0025] Figure 8 This is a diagram showing an example process performed, for example, by a first wireless device according to the present disclosure.

[0026] Figure 9 This is a diagram showing an example process performed, for example, by a second wireless device according to the present disclosure.

[0027] Figure 10 This is a diagram of an exemplary apparatus for wireless communication according to the present disclosure.

[0028] Figure 11 This is a diagram of an exemplary apparatus for wireless communication according to the present disclosure. Detailed Description

[0029] Aspects of the present disclosure are described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art. Those skilled in the art should understand that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently of any other aspect of the present disclosure or in combination with any other aspect of the present disclosure. For example, any number of the aspects set forth herein may be used to implement an apparatus or practice a method. Additionally, the scope of the present disclosure is intended to cover such an apparatus or method practiced using other structures, functions, or combinations of structures and functions in addition to or different from the aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of the claims.

[0030] Certain aspects of a telecommunications system will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and are illustrated in the drawings by various boxes, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether the elements are implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system.

[0031] In some networks, a wireless communication device (WCD) may support applications associated with low latency or lossless audio to one or more other devices (e.g., one or more personal audio devices). For example, the 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., peripherals) of a user. In a scenario where a user uses two peripherals, the wireless communication device may support an extended personal audio network (XPAN), through which the wireless communication device may communicate with the two peripherals. To meet the latency or lossless criteria associated with the application or use case, the XPAN device may employ target wake time (TWT) techniques for communication between the wireless communication device and the peripherals. In some systems, the peripherals and the wireless communication device may exchange one or more Bluetooth messages and achieve a complete TWT teardown between the wireless communication device and each peripheral. This exchange of Bluetooth messages and TWT teardown may introduce too much latency for some applications such as ULL gaming or streaming lossless audio applications.

[0032] 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 peripherals (e.g., earbuds or audio devices) may use a downlink audio data packet to carry updated TWT parameters or any other XPAN-related parameters that the wireless communication device and the peripherals may indicate via wireless signaling. Additionally or alternatively, the wireless communication device may embed a set of updated parameters in a padding portion of the audio data packet and may send the audio data packet to the peripherals. The peripherals may each acknowledge the audio data packet sent by the wireless communication device, and the wireless communication device may communicate according to the updated parameters based on acknowledgments received from each of the peripherals.

[0033] Figure 1FIG. 0 illustrates a wireless communication system 100 (also referred to as a wireless local area network (WLAN) or Wi-Fi network) configured in accordance with the present disclosure. The wireless communication system 100 may include an AP 105 and a plurality of associated devices 115 (such as stations (STAs) SAPs), which may represent devices such as mobile stations, personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptop computers, display devices (e.g., TVs, computer monitors, etc.), printers, and the like. The AP 105 and the associated devices 115 (e.g., associated STAs) may represent a basic service set (BSS) or an extended service set (ESS). Various devices 115 in the network can communicate with each other via the AP 105. Also shown is the coverage area 110 of the AP 105, which may represent the basic service area (BSA) of the wireless communication system 100. Extended network stations (not shown) associated with the wireless communication system 100 may be connected to a wired or wireless distribution system, which may allow multiple APs 105 to be connected in an ESS.

[0034] Although not shown in Figure 1 FIG. 5, the device 115 may be located at the intersection of more than one coverage area 110 and may be associated with more than one AP 105. A single AP 105 and an associated set of devices 115 may be referred to as a BSS. An ESS is a collection of connected BSSs. A distribution system (not shown) may be used to connect the APs 105 in an ESS. In some cases, the coverage area 110 of the AP 105 may be divided into sectors (also not shown). The wireless communication system 100 may include different types of APs 105 (e.g., metropolitan area networks, home networks, etc.) having varying and overlapping coverage areas 110. Two devices 115 may also communicate directly via a direct wireless communication link 125, regardless of whether the two devices 115 are in the same coverage area 110. Examples of direct wireless communication links 120 may include Wi-Fi direct connections, Wi-Fi tunnel direct link setup (TDLS) links, and other group connections. The devices 115 and the AP 105 may communicate according to WLAN radio and baseband protocols for the physical layer and MAC layer from IEEE 802.11 and its various 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 embodiments, peer-to-peer connections or ad hoc networks may be implemented within the wireless communication system 100.

[0035] In some cases, device 115 (or AP 105) can be detected by central AP 105, but not by other devices 115 within the coverage area 110 of central AP 105. For example, one device 115 can be at one end of the coverage area 110 of central AP 105, while another device 115 can be at the other end. Thus, both devices 115 can communicate with AP 105, but may not receive transmissions from the other. This can lead to conflicting transmissions of the two devices 115 in a contention-based environment (e.g., Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA)), because the devices 115 may not refrain from transmitting over one another. Devices 115 whose transmissions are not recognizable but are within the same coverage area 110 can be referred to as hidden nodes. CSMA / CA can be supplemented by exchanging Request to Send (RTS) packets sent by the transmitting device 115 (or AP 105) and Clear to Send (CTS) packets sent by the receiving device 115 (or AP 105). This can warn other devices within the range of the sender and receiver not to transmit for the duration of the primary transmission. Thus, RTS and / or CTS can help mitigate the hidden node problem.

[0036] Wireless communication system 100 can include AP 105, device 115 (e.g., which can be referred to as a source device or a central device), and paired devices 115 that implement WLAN communication (e.g., Wi-Fi communication) and / or Bluetooth communication (e.g., which can be referred to as a receiving device or a peripheral device). For example, device 115 can include a cellular phone, a user equipment (UE), a STA, a mobile station, a PDA, other handheld devices, a netbook, a notebook computer, a tablet computer, a laptop computer, or some other suitable term. The paired devices 115 can include Bluetooth-enabled devices capable of pairing with other Bluetooth-enabled devices (e.g., such as device 115), and the other Bluetooth-enabled devices can include wireless audio devices (e.g., headphones, earbuds, speakers, headsets, earphones), display devices (e.g., TV, computer monitor), microphones, meters, valves, etc.

[0037] "Bluetooth communication" can refer to a short - range communication protocol and can be used to connect and exchange information between device 115 and paired device 115 (e.g., between a mobile phone, computer, digital camera, wireless headphones, speaker, keyboard, mouse, or other input peripheral device and similar devices). Bluetooth systems (e.g., aspects of wireless communication system 100) can be organized using a master - slave relationship that employs a time - division duplex protocol having, for example, a defined time slot of 625 microseconds, where transmissions alternate between a master device (e.g., device 115) and one or more slave devices (e.g., paired devices 115). In some examples, "device 115" can generally refer to the master device, and "paired device 115" can refer to the slave devices in wireless communication system 100. Thus, in some examples, based on the Bluetooth role configuration of the device, the device can be referred to as device 115 or paired device 115. That is, designating a device as device 115 or paired device 115 may not necessarily indicate a difference in device capabilities, but can refer to or indicate the role that the device plays in wireless communication system 100. Generally, "device 115" can refer to a wireless communication device capable of wirelessly exchanging data signals with another device (e.g., paired device 115), and "paired device 115" can refer to a device operating in a slave role, or a short - range wireless communication device capable of exchanging data signals with device 115 (e.g., using the Bluetooth communication protocol).

[0038] A communication link 125 can be established between two Bluetooth-enabled devices (e.g., between device 115 and a paired device 115) and can provide communication or services (e.g., according to some Bluetooth profiles). A controller stack can be responsible for establishing the communication link 125, such as an asynchronous connection-oriented link (or asynchronous connection-oriented connection), a synchronous connection-oriented (SCO) link (or SCO connection), an extended synchronous connection-oriented (eSCO) link (or eSCO connection), other logical transport channel links, etc. For example, a Bluetooth connection can be an eSCO connection for a voice call (e.g., which can allow retransmission), an asynchronous connectionless (ACL) connection for music streaming (e.g., the Advanced Audio Distribution Profile (A2DP)), etc. eSCO packets can be sent in predetermined time slots (e.g., 6 Bluetooth time slots per eSCO). When establishing a Bluetooth link, a regular interval between eSCO packets can be specified. eSCO packets to / from a particular device (e.g., paired device 115) are acknowledged and can be retransmitted if not acknowledged during a retransmission window. Additionally, an ACL connection (e.g., the A2DP profile) can be used to stream audio between device 115 and a paired device 115. In some cases, an ACL connection can occupy 1, 3, or 5 Bluetooth time slots for data or voice. Other Bluetooth profiles supported by Bluetooth-enabled devices can include Bluetooth Low Energy (BLE) (e.g., providing significantly reduced power consumption and cost while maintaining a similar communication range), the Human Interface Device (HID) profile (e.g., providing a low-latency link with low power requirements), etc.

[0039] In some examples, a device can be capable of both Bluetooth and WLAN communication. For example, WLAN and Bluetooth components can be co-located within the device such that the device can communicate according to Bluetooth and WLAN communication protocols since each technology can provide different benefits or can improve the user experience under different conditions. In some examples, Bluetooth and WLAN communication can share the same medium, such as the same unlicensed frequency medium. In such examples, device 115 can support WLAN communication via AP 105 (e.g., on communication link 120). AP 105 and the associated device 115 can represent a BSS or an ESS. Individual devices 115 in the network can be capable of communicating with each other via AP 105. In some cases, AP 105 can be associated with a coverage area, which can represent a BSA.

[0040] Device 115 and AP 105 may communicate according to WLAN radio and baseband protocols for the physical layer and MAC layer from IEEE 802.11 and its 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 embodiments, peer-to-peer connections or ad hoc networks may be implemented within system 100, and devices may communicate with each other via communication link 120 (e.g., Wi-Fi Direct connection, Wi-Fi TDLS link, peer-to-peer communication link, or other peer or group connection). AP 105 may be coupled to a network (such as the Internet) and may enable device 115 to communicate via the network (or communicate with other devices 115 coupled to AP 105). Device 115 may communicate bidirectionally with network devices. For example, in a WLAN, device 115 may communicate with an associated AP 105 via a downlink (e.g., a communication link from AP105 to device 115) and an uplink (e.g., a communication link from device 115 to AP 105).

[0041] In some examples, the content, media, audio, etc. exchanged between device 115 and a paired device 115 may originate from the WLAN. For example, in some examples, device 115 may receive audio from AP 105 (e.g., via WLAN communication), and device 115 may then relay or transfer the audio to the paired device 115 (e.g., via Bluetooth communication). In some examples, certain types of Bluetooth communication (e.g., such as high-quality or high-definition (HD) Bluetooth) may require enhanced quality of service. For example, in some examples, latency-sensitive Bluetooth traffic may have a higher priority than WLAN traffic.

[0042] In some deployments, a wireless communication device may support applications associated with low latency or lossless audio with one or more other devices (e.g., one or more personal audio devices). For example, the 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., peripherals) of a user. In a scenario where a user uses two peripherals (e.g., wireless earbuds 130-a and wireless earbuds 130-b), the wireless communication device may support XPAN, via which the wireless communication device may communicate with the two peripherals.

[0043] To meet the latency or lossless criteria associated with an application or use case, an XPAN device may employ TWT techniques to communicate between a wireless communication device and a peripheral device. Initial or default TWT parameters may be set at an expected value for an ideal (e.g., interference-free or near interference-free) condition and may be updated in response to a changed channel condition or a changed concurrent scenario at the wireless communication device. In some systems, the peripheral device and the wireless communication device may exchange one or more Bluetooth messages and effect a complete TWT tear-down between the wireless communication device and each peripheral device. This exchange of Bluetooth messages and TWT tear-down may introduce too much latency for some applications such as ULL gaming or streaming lossless audio applications.

[0044] In some implementations, the wireless communication device (which may be device 115 (e.g., a handset) or AP 105) and a set of peripheral devices may use downlink audio data packets to carry updated TWT parameters or any other XPAN-related parameters that the wireless communication device and the peripheral device may indicate via wireless signaling.

[0045] Figure 2 An example of a wireless communication system 200 that supports low-latency parameter updates for an extended personal audio network in accordance with the present disclosure is shown. The wireless communication system 200 may implement or be implemented to implement aspects of the wireless communication system 100. For example, the wireless communication system 200 shows communication between AP 105, device 115 (e.g., a handset or handheld device), and the user 205's wireless earbuds 130-a and wireless earbuds 130-b (e.g., examples of audio devices and / or peripheral devices), which may be examples of the corresponding devices as Figure 1 shown and referenced Figure 1 described. In some embodiments, device 115, wireless earbuds 130-a, and wireless earbuds 130-b may support a signaling-based mechanism according to which device 115 may send an indication of a set of updated parameters to each of wireless earbuds 130-a and wireless earbuds 130-b via one or more audio data packets.

[0046] In some deployments, device 115 may communicate with AP 105 via one or both of link 210-a and link 210-b, which may be examples of infrastructure links between AP 105 and device 115. Link 210-a may be an example of a 2.4 GHz link between AP 105 and device 115, and link 210-b may be an example of a 5 GHz link or a 6 GHz link between AP 105 and device 115. Additionally, device 115 may wirelessly communicate with each of wireless earbuds 130-a and wireless earbuds 130-b, where each of wireless earbuds 130-a and wireless earbuds 130-b may be associated with the XPAN of device 115. For example, device 115 may communicate with wireless earbuds 130-a via link 215-a and may communicate with wireless earbuds 130-b via link 215-b, where link 215-a and link 215-b may be referred to as or understood as XPAN links. Link 215-a may be an example of a 5 GHz link or a 6 GHz link, and link 215-b may be an example of a 5 GHz link or a 6 GHz link. Additionally, in some examples, device 115 may communicate with wireless earbuds 130-a via communication link 220, which may be an example of a Bluetooth link between device 115 and wireless earbuds 130-a. Wireless earbuds 130-a and wireless earbuds 130-b (which may be examples of secondary earbuds) may communicate with each other via link 225, which may be an example of a Bluetooth link between wireless earbuds 130-a and wireless earbuds 130-b.

[0047] In some cases, device 115, wireless earbuds 130-a, and wireless earbuds 130-b may support or belong to XPAN and may use XPAN to support one or more applications or use cases, such as those associated with latency or lossless audio constraints or standards. For example, device 115 may support ULL gaming and one or more use cases of streaming lossless audio to wireless earbuds 130-a and wireless earbuds 130-b (e.g., personal devices of device 115). For such applications, it may be expected that device 115 maintains end-to-end latency below a relatively strict latency target (e.g., 40 ms for ULL gaming). Additionally, device 115 may also be tasked with handling (e.g., gracefully handling) the coexistence of XPAN traffic (e.g., traffic to and from one or both of wireless earbuds 130-a and wireless earbuds 130-b) with other concurrent scenarios that the user 205 or the system may initiate. Such other concurrent scenarios may include scan concurrency for channel selection, STA infrastructure link concurrency for online gaming or other traffic to or from AP 105, or neighbor awareness networking (NAN) discovery and NAN data transfer, or any combination thereof.

[0048] It may be expected that device 115 meets latency constraints for various applications or use cases (e.g., ultra-low latency constraints for the ULL gaming use case) and also facilitates the coexistence between XPAN and other concurrent scenarios on device 115. To meet latency constraints associated with, for example, ULL gaming, power constraints of wireless earbuds 130-a and wireless earbuds 130-b, and / or power and concurrency constraints at device 115, device 115 may employ TWT technology for communication between device 115 (which may act as or serve as a SAP) and each of wireless earbuds 130-a and wireless earbuds 130-b (which may act as or serve as STAs).

[0049] Example TWT parameters include TWT 230, TWT service interval (SI) 235, and TWT service period (SP) 240. TWT 230 may indicate or be associated with a timing synchronization function (TSF) time that indicates the start or beginning of the first TWT service period. TWT SI 235 may indicate the TWT interval, which may refer to the time difference between the starts or beginnings of two consecutive TWT service periods. TWT SP 240 may indicate the duration for which one or both of wireless earbuds 130-a and wireless earbuds 130-b wake up during the TWT SI 235. In some aspects, TWT SP 240 may be referred to as or understood as a TWT session. As Figure 2As shown, the TWT SI 235 can indicate the time difference between the TWT SP 240-a and the TWT 240-b. The remaining time within the TWT SI 235 excluding the TWT SP 240 can be referred to as or understood as the concurrent time 245, during which the device 115 can perform any operations (e.g., sending or receiving) associated with the concurrent scenario at the device 115. In other words, the difference between the XPAN TWT SI 235 and the XPAN TWT SP 240 can be the time remaining for the device 115 to support other concurrency (e.g., outside of any channel switching or software overhead).

[0050] For XPAN, each of the wireless earbuds 130-a and 130-b (which can be examples of TWT requesting STAs) can initiate a TWT session with the device 115 (which can be an example of a TWT responding STA). Additionally, for low latency use cases (e.g., ULL gaming use cases), the target end-to-end latency can be relatively strict (e.g., less than or equal to approximately 40 ms), which can be bound to, associated with, or expected to be within a specific range (e.g., within a range below 10 ms) of Wi-Fi latency. To achieve such Wi-Fi latency, the TWT SI 235 and the TWT SP 240 can be selected or set to specific values (e.g., the TWT SI 235 can be set to 4 ms while the TWT SP 240 is 2 ms). Additionally, for lossless audio use cases, e.g., the TWT SI 235 can be set to approximately 70 ms, where the TWT SP 240 is approximately 23 ms.

[0051] In some cases, the default or initial TWT parameter set for XPAN can be configured or set to expect an ideal (e.g., interference-free or near interference-free) condition (e.g., link condition, channel condition, or environmental condition). In some deployments, the Wi-Fi channel condition, the concurrency of the device 115, or the XPAN constraints can change over time. Such changes can trigger, be associated with, or enforce a TWT parameter update. Additionally, in applications or use cases associated with low latency (e.g., ULL gaming and streaming lossless audio), a TWT parameter update can be expected to be performed with low latency to continue to meet the XPAN constraints without compromising the user experience. As an example, for the XPAN gaming use case, the TWT SP 240 can be approximately 2 ms. The communication overhead of the updated TWT parameters or other information communicated from the device 115 to the wireless earbuds 130-a and 130-b can also be expected to be relatively small.

[0052] However, in some systems, the TWT parameter update procedure may be associated with a relatively high latency. Additionally, since the TWT session may be initiated by the wireless earbuds 130-a and the wireless earbuds 130-b (with default or initial parameters), any update to the TWT parameters triggered by a change in conditions on device 115 may involve device 115 sending the updated parameters to the wireless earbuds 130-a and the wireless earbuds 130-b, followed by a change in the TWT parameters at the wireless earbuds 130-a and the wireless earbuds 130-b.

[0053] An example TWT parameter update procedure may include a sequence of signaling steps involving one or more transmissions using a Bluetooth link, which may introduce a relatively large delay. For example, the Wi-Fi subsystem (SS) of device 115 may send a request to update one or more TWT parameters (e.g., a TWT parameter update request) to the Bluetooth host (BT host) of device 115 after detecting one or more conditions that trigger a change in one or more TWT parameters. The BT host of device 115 may use the Bluetooth link to convey the updated set of TWT parameters to the BT host of the primary earbud (e.g., the wireless earbud 130-a). Such an updated TWT configuration sent via the Bluetooth link may add approximately 80 ms of delay. The BT host of the primary earbud may internally signal the new TWT parameters to the Wi-Fi SS of the primary earbud, and the BT host of the primary earbud may use the Bluetooth link to convey the new TWT parameters to the BT host of the secondary earbud (e.g., the wireless earbud 130-b). Such an indication of the TWT configuration via the 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 internally signal the new TWT parameters to the Wi-Fi SS of the secondary earbud.

[0054] The Wi-Fi SS of the primary earbud may initiate the TWT session tear-down and parameter update process. The TWT session tear-down and parameter update process may involve transmitting a TWT tear-down message and a TWT request message carrying the new TWT parameters from the Wi-Fi SS of the primary earbud to the Wi-Fi SS of device 115 via the XPAN Wi-Fi link, and transmitting an acknowledgment (ACK) of the new TWT parameters with a TWT response message from the Wi-Fi SS of device 115 to the Wi-Fi SS of the primary earbud via the XPAN Wi-Fi link. The Wi-Fi SS of device 115 may update the BT host of device 115 that a new TWT session has been established with the primary earbud (e.g., the Wi-Fi SS may indicate a TWT session update to the BT host). Such a TWT session tear-down and parameter update process may additionally be performed between device 115 and the secondary earbud.

[0055] Figure 3 is an example 300 of a link establishment procedure for a multi-link device. As Figure 3As shown, an access point (AP) multi-link device (MLD) 302 may establish multiple links with non-AP MLDs. The multiple links may be associated with different frequency bands.

[0056] As Figure 3 shown, the AP multi-link device 302 may include or be associated with a first AP 304, a second AP 306, and a third AP 308. The non-AP multi-link device 310 may include or be associated with a station 312, a station 314, and a station 316. The station 312 may send a TWT request 318 that requests the AP MLD 302 to establish a TWT session between the first AP 304, the second AP 306, and the third AP 308 and the station 312, the station 314, and the station 316. For example, the TWT request 318 may include a bitmap indicating requests to establish TWT sessions on the links for each of the station 312, the station 314, and the station 316. The bitmap may be associated with different frequency bands that are associated with different links on which the stations operate.

[0057] The first AP 304 may send a TWT response 320 that indicates the initiation of the establishment procedure for each of the station 312, the station 314, and the station 316. At least in part based on the first AP 304 sending the TWT response 320, the AP MLD 302 and the non-AP MLD 310 may have previously performed a link establishment procedure and subsequently perform TWT establishment with each of the station 312, the station 314, and the station 316. For example, the first AP 304 and the station 312 may perform a first TWT establishment 322, the second AP 306 and the station 314 may perform a second TWT establishment 324, and the third AP 308 and the station 316 may perform a third TWT establishment 326.

[0058] As described above, Figure 3 is provided as an example. Other examples may be different from the examples described with respect to Figure 3 description.

[0059] Figure 4 is an example 400 of the configuration of multi-link communication by an MLD. As Figure 4 shown, the AP MLD may communicate with the non-AP MLD via multiple links. The multiple links may be associated with different frequency bands.

[0060] As Figure 4As shown, the AP MLD can communicate with the non-AP MLD via the first link 402, the second link 404, and the third link 406. The first link 402 can be associated with the link between the first STA of the non-AP MLD and the first wireless device of the AP MLD. Similarly, the second link 404 can be associated with the link between the second STA of the non-AP MLD and the second wireless device of the AP MLD, and the third link 406 can be associated with the link between the third STA of the non-AP MLD and the third wireless device of the AP MLD.

[0061] The non-AP STA and the AP can perform TWT setup 408. The TWT setup 408 can include a cross-link TWT signaling mechanism to support the negotiation of multiple TWT agreements associated with the links 402, 404, and 406. However, the TWT setup 408 can include the independent setup of multiple TWT agreements, where the timing of the first link 402 (e.g., TWT start time, TWT wake-up interval, and / or TWT service period duration) is configured without considering the timing of the second link 404 or the third link 406.

[0062] As Figure 4 shown, the first link 402 can be configured with a TWT service period (SP) 410 and a TWT wake-up interval 412. The TWT SP 410 can be configured to start at the start time of the TWT wake-up interval 412. Similarly, the second link 404 can be configured with a TWT SP 414 and a TWT wake-up interval 416, and the third link 406 can be configured with a TWT SP 418 and a TWT wake-up interval 420.

[0063] As Figure 4 shown, at least partially based on the uncalibrated TWT timing of the first link 402, the second link 404, and the third link 406, the non-AP MLD and the AP MLD can have an active TWT SP for at least one of these links during a time period extended relative to the SP of any of these links. In this way, the first wireless device can consume power resources that might otherwise have been saved if the TWT SP was calibrated (e.g., the start time of the TWT was calibrated). This is at least partially based on the non-AP MLD and the AP MLD maintaining active transmit and / or receive chains during the TWT SP of all links.

[0064] As described above, Figure 4 is provided as an example. Other examples can be different from the examples described with respect to Figure 4 the description.

[0065] In some aspects described herein, a first wireless device (e.g., a STA and / or a non-AP MLD) may send a request for a TWT schedule configured for a first link associated with a second wireless device. In some aspects, the request for the TWT schedule configured for the first link may include an indication (e.g., a request) for TWT calibration regarding the TWT schedule of a second link associated with a third wireless device. In some aspects, the indication for TWT calibration regarding the TWT schedule of the second link may be indicated within a field configured to indicate the TWT start time.

[0066] The second wireless device may receive the request and may configure the TWT schedule of the first link for TWT schedule time calibration with 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 the same device as the second wireless device.

[0067] In some aspects, the first wireless device may send the indication within a TWT request having an explicit request for MLD calibration. 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 the setup command field of all TWT elements (e.g., the TWT setup command field) indicates that TWT is to be requested (e.g., request TWT). In some aspects, a mixed command may not be allowed in the same request frame (e.g., from the perspective of the communication protocol).

[0068] Each bitmap field (e.g., the link ID bitmap field) of the link identifier included in the TWT element has only one bit set to 1, and a non-zero bit cannot appear more than once, unless a series of TWT parameters are being provided for that particular link. These are the links for which the first wireless device (e.g., the first STA) attached to the non-AP MLD requests TWT calibration.

[0069] Each TWT field of the TWT IE may refer to the timing synchronization function (TSF) time of the 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 use any non-zero TWT value to indicate the MLD calibration request. In some aspects, when the TWT value is set to zero, the TWT value indicates that the first wireless device is not requesting timing calibration.

[0070] In some aspects, the AP of the AP MLD can send beacons (e.g., periodically) or provide other information that provides connection and / or synchronization information associated with the AP. For example, the beacon can include a timestamp that indicates the absolute time associated with the transmission of the beacon in the domain of the associated AP. In this way, the first wireless device can identify the absolute time of the AP and can identify the desired TWT schedule in the domain of the associated AP. For example, different STAs of the first wireless device can obtain information from the associated beacon and share the information with the first wireless device (e.g., the STA associated with the first link). In some aspects, the AP can know the absolute time of other APs in the AP at least in part based on being attached to (e.g., attached to the AP MLD).

[0071] In some aspects, STAs attached to a non-AP MLD can coordinate to request that all TWTs have the same global start time (e.g., independent of the domain of the AP); however, the TWT is requested with reference to the timestamp of each AP operating in those links. In some aspects, the TWT wake-up interval specified by the TWT wake-up interval mantissa and TWT wake-up interval exponent fields of the TWT element can be equal across TWT IEs (e.g., within a threshold difference).

[0072] In some aspects, the TWT wake-up interval can be a multiple of a common denominator rather than being calibrated at the start of each TWT wake-up interval for these two links. For example, the first link can have a TWT wake-up interval that is 2 times (×2) the TWT wake-up interval of the second link. Additionally or alternatively, the third link can have a TWT wake-up interval that is 3 times the TWT wake-up interval of the second link. In this way, each link will have a common TWT start time every six TWT wake-up intervals of the second link.

[0073] In some aspects, the communication protocol can allow a non-zero TWT field in the TWT request frame that indicates the TWT setup command for requesting the TWT. In some aspects, the non-zero TWT field can indicate the TSF time at which the first wireless device requests the first TWT start time (e.g., to cause global start time calibration with one or more additional TWT start times of other links).

[0074] In some aspects, the communication protocol can require that the TWT wake-up intervals across links be multiples of a common denominator. In some aspects, the size of the multiple can be restricted to increase the frequency of time calibration. For example, the multiple can be limited to 4, 6, 8, or 12, among other examples. In some aspects, other values of TWT parameters (e.g., TWT SP duration) can depend on the link configuration.

[0075] In some aspects, a second device (e.g., an AP associated with an AP MLD) may respond to a TWT request indicating time calibration for a second link. In some aspects, a TWT request frame sent by a non-AP STA includes at least two TWT IEs, where the TWT setup commands for all TWT IEs indicate a request TWT field and a non-zero TWT field. At least partially based on these TWT request frames, the second device (e.g., the AP) may respond with a TWT response frame including the same number of TWT IEs, the TWT response frame having a TWT setup command indicating acceptance or rejection of the TWT. In some aspects, each link ID bitmap of the TWT IEs has only one bit equal to 1 (e.g., the same as the TWT request).

[0076] In some aspects, there is no TWT agreement for a link identified in a link ID bitmap within a TWT IE having a rejected TWT, and there is a TWT agreement for a link identified in a link ID bitmap within a TWT IE having an accepted TWT. In some aspects, the TWT agreement may use the TWT parameters identified in the TWT response frame.

[0077] Each TWT IE having an accepted TWT may indicate TWT parameters, such as the TWT field of the TWT IE with reference to the TSF time of the link identified in the TWT IE, where the TWT fields across these links point to the same global start time. In some aspects, the TWT wake interval mantissa and the TWT wake interval exponent fields may be equal (e.g., within a threshold difference) for all TWT IEs requested for calibration. In some aspects, the TWT wake interval mantissa and the TWT wake interval exponent fields may be related at least partially based on having a common denominator (e.g., a multiple of the common denominator).

[0078] In some aspects, the communication protocol may require the TWT fields of TWT IEs having an accepted TWT to point to the same global start time. These values may be referenced to the TSF time of the link identified in the respective TWT IE. TWT fields pointing to future TWTs (e.g., multiples of the TWT wake interval) may be used to account for latency within the AP.

[0079] In some aspects, the TWT request and TWT response frames for negotiating a broadcast TWT (e.g., B-TWT) may include one or more TWT IEs and follow rules similar to those for an individual TWT (I-TWT) scenario (with one or more modifications). For example, the B-TWT IE may include one or more B-TWT parameter sets, where the TWT field points to a partial TSF time (e.g., the time relative to the start of the associated AP or the rest time when the AP TSF time returns to zero) rather than the global TSF time. In some aspects, this may be at least partially based on the TWT field being only 2 octets long. In some aspects, the resolution of these TWTs can be 1 time unit (TU), so the cross-link calibration is at the 1-TU granularity level. In some aspects, the TWT wake-up interval can be configured to be a multiple of 1 TU in addition to being a multiple of the common denominator. Additionally or alternatively, one or more constraints associated with the IE may be applied at the B-TWT parameter set level rather than the IE level.

[0080] Based at least in part on the TWT timing calibration of multiple links (e.g., AP MLD) between a first wireless device and a second wireless device, the first wireless device and the second wireless device may reduce the amount of time during which the first wireless device has an active TWT SP for at least one of these links. In this way, the first wireless device can save power resources that might otherwise have been consumed if the TWT SP were not calibrated.

[0081] As described above, Figure 4 is provided as an example. Other examples may be different from the example described with respect to Figure 4 description.

[0082] Figure 5 is a diagram of example 500 associated with TWT calibration according to the present disclosure. As Figure 5 shown, 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 system 100). Before the operations Figure 5 shown, 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). The first MLD or the STA of the first MLD may be referred to as the first wireless device. The second MLD or the AP of the second MLD may be referred to as the second wireless device.

[0083] As indicated by reference numeral 505, a first MLD may receive an indication of a TWT start time associated with a second link, and a second MLD may send an indication of a TWT start time associated with the second link. For example, a STA of the first MLD may receive communication from an AP of the second MLD associated with the second link. In some aspects, the second link may be a link between a first MLD (e.g., a second STA of the first MLD) and a wireless device (e.g., a second AP of the second MLD).

[0084] As indicated by reference numeral 510, a first MLD may identify a TWT start time associated with a second link. In some aspects, the first MLD may identify the TWT start time associated with the second link at least in part based on receiving the indication, as described in connection with reference numeral 505. In some aspects, the first MLD may identify the TWT start time associated with the second link independently of (e.g., without) receiving the indication, as described in connection with reference numeral 505.

[0085] In some aspects, the first MLD may identify the TWT start time associated with the second link at least in part based on 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 at least in part based on a timestamp 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 the time domain of an AP associated with the second link.

[0086] As indicated by reference numeral 515, the first MLD may send a request to configure a TWT schedule for a first link having TWT calibration associated with a second link. For example, the first MLD may send a request including an indication of TWT calibration for the TWT schedule of the second link. In some aspects, the indication for TWT calibration may be indicated within a field configured to indicate a TWT start time. In some aspects, the indication for TWT calibration may include a non-zero value or an indication of a requested TWT start time for the first link within a field configured to indicate a TWT start time.

[0087] In some aspects, a request to configure a TWT schedule using calibration associated with a second link may indicate a request to calibrate with the second link. In some aspects, a request to configure a TWT schedule to have calibration associated with a second link may indicate a requested TWT start time and / or periodicity for the first link at least in part based on an identification of a TWT start time associated with the second link, as indicated in connection with reference numeral 510.

[0088] In some aspects, a request to configure a TWT schedule to have a calibration associated with a second link may indicate the TWT start time and / or periodicity requested for a first link, at least in part based on calibrating the TWT start time and / or periodicity with the requested TWT start time and / or periodicity associated with the second link. For example, a first MLD may send a request to configure the TWT schedule for the first link along with a request to configure the TWT schedule for the second link, along with an indication to calibrate the TWT start times of the first link and the second link. In some aspects, the request to calibrate the start times of the first link and the second link may include an indication of a first start time of the first link in the time domain of a first AP (e.g., of a second MLD) associated with the first link, and an indication of a second start time of the second link in the time domain of a second AP (e.g., of a second MLD) associated with the second link. In some aspects, the absolute time in the time domain of the first AP satisfies a threshold relative to the TWT start time associated with the second link, which is associated with the time in the time domain of the second AP.

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

[0090] In some aspects, TWT calibration includes a first time difference between the TWT start time associated with the first link and the TWT start time associated with the second link satisfying a first threshold. In some aspects, TWT calibration includes a second time difference between the TWT start time and a subsequent TWT start time associated with a subsequent TWT period associated with the second link satisfying a second threshold. For example, the TWT start time of the first link may have timing calibration with a subsequent TWT start time (but not all TWT start times) associated with the second link. In some aspects, the periodicity and / or the TWT wake-up time may have a duration that is a multiple of a common denominator. For example, a first period may be 12 TUs and a second period may be 8 TUs, where the common denominator is 4. In some aspects, the magnitude of the multiple may be limited (e.g., less than 10). In some aspects, TWT calibration includes a third time difference 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 satisfying a third threshold. In some aspects, TWT calibration includes a fourth difference between a first TWT wake-up interval mantissa and a first exponent field of the first link and a second TWT wake-up interval mantissa and a second exponent field of the second link satisfying a fourth threshold.

[0091] In some aspects, TWT calibration includes a time offset between the timing of the start time of the TWT and the timing of an additional start time associated with a second link. In some aspects, the time offset can be at least partially based on a TWT service period associated with a first TWT schedule (e.g., having an offset of a second TWT start time configured to start after completion of the TWT SP of a first TWT wake interval of a first link). For example, the first link can be TWT calibrated with the second link to avoid or reduce simultaneous TWT SPs. In some aspects, the first MLD can be configured to communicate via only one link at a time (e.g., at least partially based on hardware or other resource limitations). In this way, the first MLD can be able to hop between links during concurrent times of other links with non-overlapping TWT SPs.

[0092] In some aspects, timing calibration includes that a first time difference between a first TWT periodicity of a first link and a second TWT periodicity of a second link meets a threshold. In some aspects, timing calibration includes that a second time difference between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link meets a threshold. In some aspects, timing calibration includes that a third time difference between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link meets a threshold.

[0093] As indicated by reference numeral 520, the first MLD can receive a response indicating the TWT start time associated with the first link, and the second MLD can send the response. In some aspects, the TWT start time can be at least partially based on an indication of TWT calibration regarding the TWT schedule of the second link. For example, the second MLD can send an indication of acceptance of the requested start time, as indicated in a request to configure the TWT schedule for the first link using TWT calibration associated with the second link, as described in connection with reference numeral 515. In some aspects, the indication of the TWT start time can be in the same field (e.g., the TWT start time field) of the response as the indication of calibration with the second link in the request to configure the TWT schedule for the first link.

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

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

[0096] The reset time can be used instead of the start time. The reset time can be the time when the time in the time domain of the second wireless device is reset to zero at least partially based on reaching the maximum time in the time counter. In some aspects, the first link and / or the second link is associated with a broadcast TWT.

[0097] In some aspects, the second MLD may send a response indicating the start time (e.g., a first start time associated with the first link) at least partially based on receiving a request for a TWT schedule configured for the first link. In some aspects, the second MLD may send a response indicating the start time independently of (e.g., without) receiving a request for a TWT schedule configured for the first link. For example, the second MLD may send or be included in a separately addressed solicited response, a solicited response at least partially based on receiving a request for a TWT schedule configured for the first link, and / or a broadcast response, and other examples, indicating the start time.

[0098] As shown by reference numeral 525, 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 using time calibration (also referred to as "timing calibration") of the first link and the second link. In some aspects, the first MLD may communicate with a second wireless device via the first link using a first TWT start time in the first link and / or using a second TWT start time in the second link. In some aspects, the first MLD may initiate TWT tear-down of one or more of the first TWT schedule or the second TWT schedule at least in part based on receiving a response. For example, the first MLD may initiate TWT tear-down to reset the configuration of the first link or the second link.

[0099] At least in part based on TWT timing calibration of multiple links between a first MLD (e.g., a first wireless device) and a second MLD (e.g., a second wireless device), the first MLD and the second MLD may reduce the amount of time during which the first MLD has an active TWT SP for at least one of these links. In this way, the first MLD may save power resources that might otherwise be consumed if the TWT SP were not calibrated.

[0100] As described above, Figure 5 is provided as an example. Other examples may be different from the examples described with respect to Figure 5 description.

[0101] Figure 6 is an example 600 of a configuration for multi-link communication by an MLD. As Figure 6 shown, an AP MLD has multiple links with a non-AP MLD. The multiple links may be associated with different frequency bands.

[0102] As Figure 6 shown, the AP MLD may communicate with the non-AP MLD via a first link 602, a second link 604, and a third link 606. The first link 602 may 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 link 604 may 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 link 606 may be associated with a link between a third STA of the non-AP MLD and a third wireless device of the AP MLD.

[0103] The non-AP and the AP may perform TWT setup 608. The TWT setup 608 may include a cross-link TWT signaling mechanism to support negotiation of multiple TWT agreements associated with the links 602, 604, and 606. The TWT setup 608 may indicate a request for time calibration between the links 602, 604, and 606.

[0104] AsFigure 6 As shown, the first link 602 can be configured with a TWT service period (SP) 610 and a TWT wake-up interval 612. The TWT SP 610 can be configured to start at the start time of the TWT wake-up interval 612. Similarly, the second link 604 can be configured with a TWT SP 614 and a TWT wake-up interval 616, and the third link 606 can be configured with a TWT SP 618 and a TWT wake-up interval 620.

[0105] As Figure 6 shown, based at least in part on the TWT timing calibration of the first link 602, the second link 604, and the third link 606, the non-AP MLD and the AP MLD can have at least partially overlapping active TWT SPs. In this way, the first wireless device can save power resources that might otherwise have been consumed in the case where the TWT SPs are not calibrated (e.g., the start times of the TWTs are not calibrated).

[0106] As described above, Figure 6 is provided as an example. Other examples can be different from the examples described with respect to Figure 6 the description.

[0107] Figure 7 is an example 700 of the configuration of multi-link communication through the MLD. As Figure 7 shown, the AP MLD has multiple links with the non-AP MLD. The multiple links can be associated with different frequency bands.

[0108] As Figure 7 shown, the AP MLD can communicate with the non-AP MLD via a first link 702, a second link 704, and a third link 706. The first link 702 can be associated with the link between the first STA of the non-AP MLD and the first wireless device of the AP MLD. Similarly, the second link 704 can be associated with the link between the second STA of the non-AP MLD and the second wireless device of the AP MLD, and the third link 706 can be associated with the link between the third STA of the non-AP MLD and the third wireless device of the AP MLD.

[0109] The non-AP and the AP can perform TWT setup 708. The TWT setup 708 can include a cross-link TWT signaling mechanism to support the negotiation of multiple TWT agreements associated with the links 702, 704, and 706. The TWT setup 708 can indicate a request for time calibration between the links 702, 704, and 706.

[0110] As Figure 7As shown, the first link 702 can be configured with a TWT service period (SP) 710 and a TWT wake-up interval 712. The TWT SP 710 can be configured to start at the start time of the TWT wake-up interval 712. Similarly, the second link 704 can be configured with a TWT SP 714 and a TWT wake-up interval 716, and the third link 706 can be configured with a TWT SP 718 and a TWT wake-up interval 720.

[0111] As Figure 7 shown, at least partially based on the TWT timing calibration of the first link 702, the second link 704, and the third link 706, the non-AP MLD and the AP MLD can have at least partially periodically overlapping active TWT SPs. For example, every other TWT SP 710 at least partially overlaps with every other TWT SP 714 and at least partially overlaps with every other TWT SP 718. In this way, the first wireless device can save power resources that might otherwise be consumed in the case where the TWT SPs are not calibrated (e.g., the start times of the TWTs are not calibrated) or have a periodic overlap with a number of TWT wake-up intervals greater than a threshold (e.g., 4, 8, 10, 12).

[0112] As described above, Figure 7 is provided as an example. Other examples can be different from the examples described with respect to Figure 7 the description.

[0113] Figure 8 FIG. is a diagram illustrating an example process 800 performed, for example, by a first wireless device in accordance with the present disclosure. The example process 800 is an example in which a first wireless device (e.g., a first STA of a first MLD and / or non-AP MLD) performs operations associated with TWT calibration.

[0114] As Figure 8 shown, in some aspects, process 800 can include sending a request to a second wireless device to configure a TWT schedule for a first link associated with the second wireless device, the request including an indication of TWT calibration for the TWT schedule of a second link associated with a third wireless device, the indication of TWT calibration being indicated within a field configured to indicate a TWT start time (block 810). For example, the first wireless device (e.g., using Figure 10 the communication manager 1008 and / or the transmission component 1004 depicted) can send a request to the second wireless device to configure a TWT schedule for a first link associated with the second wireless device, the request including an indication of TWT calibration for the TWT schedule of a second link associated with a third wireless device, the indication of TWT calibration being indicated within a field configured to indicate a TWT start time, as described above.

[0115] As Figure 8 further shown in Figure 8 , in some aspects, process 800 may include receiving, from a second wireless device, a response indicating a TWT start time within the field, the TWT start time being at least partially based on an indication of TWT calibration with respect to TWT scheduling for a second link (block 820). For example, a first wireless device (e.g., using the communication manager 1008 and / or the receiving component 1002 depicted in Figure 10 ) may receive, from the second wireless device, a response indicating a TWT start time within the field, the TWT start time being at least partially based on an indication of TWT calibration with respect to TWT scheduling for a second link, as described above. Figure 10 In some aspects, block 810 may be omitted and the first wireless device may communicate at least partially based on receiving the response (e.g., an unsolicited response).

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

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

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

[0119]

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

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

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

[0123] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the TWT calibration includes one or more of the following: a first time difference between the TWT start time and an additional TWT start time associated with the second link satisfies a first threshold, a second time difference between the TWT start time and a subsequent TWT start time of a subsequent TWT period associated with the second link satisfies a second threshold, a third time difference value between a subsequent TWT start time associated with a subsequent TWT period of the first link and the additional TWT start time associated with the second link satisfies a third threshold, a fourth difference between a first TWT wake-up interval mantissa and a first exponent field of the first link and a second TWT wake-up interval mantissa and a second exponent field of the second link satisfies a fourth threshold, or a time offset between the timing of the TWT start time and the timing of the additional start time associated with the second link.

[0124] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the time offset is at least partially based on a TWT service period associated with a first TWT schedule.

[0125] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the TWT calibration includes one or more of the following: a first time difference between a first TWT periodicity of a first link and a second TWT periodicity of a second link satisfies a threshold, a second time difference between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link satisfies a threshold, or a third time difference between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link satisfies a threshold.

[0126] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 800 includes identifying an additional TWT start time associated with the second link at least partially based on an indication of a third wireless device or at least partially based on an indication of a second wireless device.

[0127] In a tenth aspect, either alone or in combination with one or more of the first to 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 of the second service period duration.

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

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

[0130] Although Figure 8 example boxes of process 800 are shown, in some aspects, process 800 may include additional boxes, fewer boxes, different boxes, or boxes in a different arrangement compared to those depicted in Figure 8 . Additionally or alternatively, two or more boxes of process 800 may be executed in parallel.

[0131] Figure 9 is a diagram showing an example process 900, such as performed by a second wireless device, according to the present disclosure. Example process 900 is an example in which a second wireless device (e.g., a second MLD, an AP of an AP MLD, and other examples) performs operations associated with TWT calibration.

[0132] As Figure 9 shown, in some aspects, process 900 may include receiving a request for a TWT schedule for a first link configured to be associated with a first wireless device, the request including an indication of TWT calibration for the TWT schedule of a second link associated with the first wireless device and a third wireless device, the indication of TWT calibration being indicated within a field configured to indicate a TWT start time (block 910). For example, the second wireless device (e.g., using the communication manager 1108 and / or the receiving component 1102 depicted in Figure 11 ) may receive a request for a TWT schedule for a first link configured to be associated with a first wireless device, the request including an indication of TWT calibration for the TWT schedule of a second link associated with the first wireless device and a third wireless device, the indication of TWT calibration being indicated within a field configured to indicate a TWT start time, as described above.

[0133] As Figure 9 further shown, in some aspects, process 900 may include sending a response indicating the TWT start time within the field, the TWT start time being at least partially based on the indication of TWT calibration for the TWT schedule of the second link (block 920). For example, the second wireless device (e.g., using the communication manager 1108 and / or the transmission component 1104 depicted in Figure 11 ) may send a response indicating the TWT start time within the field, the TWT start time being at least partially based on the indication of TWT calibration for the TWT schedule of the second link, as described above.

[0134] In some aspects, block 910 may be omitted and the second wireless device may communicate at least partially based on sending a response (e.g., an unsolicited response).

[0135] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other process descriptions described elsewhere herein.

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

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

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

[0139] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the time in the time domain of the second wireless device meets a threshold relative to an additional TWT start time associated with the second link, where the additional TWT start time is associated with a time in an additional time domain of a third wireless device.

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

[0141] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, TWT calibration includes one or more of the following: a first time difference between the TWT start time and an additional TWT start time associated with the second link meets a first threshold, a second time difference between the TWT start time and a subsequent TWT start time of a subsequent TWT period associated with the second link meets a second threshold, a third time difference value 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 meets a third threshold, or a fourth difference between a first TWT wake-up interval mantissa and a first exponent field of the first link and a second TWT wake-up interval mantissa and a second exponent field of the second link meets a fourth threshold, or a time offset between the timing of the TWT start time and the timing of the additional start time associated with the second link.

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

[0143] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the TWT calibration includes one or more of the following: a first time difference between a first TWT periodicity of a first link and a second TWT periodicity of a second link satisfies a threshold, a second time difference between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link satisfies a threshold, or a third time difference between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link satisfies a threshold.

[0144] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 900 includes 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 the same AP multi-link device.

[0145] In a tenth aspect, alone or in combination with one or more of the first to 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 of the second service period duration.

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

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

[0148] Although Figure 9 example boxes of process 900 are shown, in some aspects, process 900 may include additional boxes, fewer boxes, different boxes, or boxes arranged differently compared to those depicted in Figure 9 . Additionally or alternatively, two or more of the boxes of process 900 may be executed in parallel.

[0149] Figure 10FIG. is a diagram of an exemplary apparatus 1000 for wireless communication in accordance with the present disclosure. The apparatus 1000 may be a first wireless device, or the first wireless device may include the apparatus 1000. In some aspects, the apparatus 1000 includes a receiving component 1002 and a transmitting component 1004, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1000 may communicate with another apparatus 1006 (e.g., an STA, an AP, or another wireless communication device) using the receiving component 1002 and the transmitting component 1004. As further shown, the apparatus 1000 may include a communication manager 1008.

[0150] In some aspects, the apparatus 1000 may be configured to perform one or more operations described herein in connection with Figures 5 to 7 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 process 800. In some aspects, Figure 10 the apparatus 1000 and / or one or more components shown in Figure 2 may include one or more components of the first wireless device described in connection with Figure 10 Additionally or alternatively, Figure 2 one or more components shown in

[0151] The receiving component 1002 may receive communications from the apparatus 1006, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1002 may provide the received communications to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signals to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may include one or more antennas, modems, demodulators, multiple-input multiple-output (MIMO) detectors, receiving processors, controllers / processors, memories, or combinations thereof of the first wireless device described in connection with Figure 2

[0152] The transmission component 1004 can send communications to the device 1006, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 1000 can generate communications and can provide the generated communications to the transmission component 1004 for transmission to the device 1006. In some aspects, the transmission component 1004 can perform signal processing on the generated communications (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or coding, and other examples), and can send the processed signal to the device 1006. In some aspects, the transmission component 1004 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the first wireless device described in conjunction with Figure 2 In some aspects, the transmission component 1004 can be co-located with the receiving component 1002 in a transceiver.

[0153] The transmission component 1004 can send a request for a TWT schedule configured for a first link associated with a second wireless device to the second wireless device, the request including an indication of TWT calibration for the TWT schedule of a second link associated with a third wireless device, the indication of the TWT calibration being indicated within a field configured to indicate a TWT start time. The receiving component 1002 can receive a response from the second wireless device indicating the TWT start time within the field, the TWT start time being at least partially based on the indication of the TWT calibration for the TWT schedule of the second link.

[0154] The communication manager 1008 can identify an additional TWT start time associated with the second link at least partially based on an indication from the third wireless device or at least partially based on an indication from the second wireless device.

[0155] Figure 10 The number and arrangement of the components shown in Figure 10 are provided as an example. In practice, there can be additional components, fewer components, different components, or components with a different arrangement compared to the components shown in Figure 10 In addition, two or more of the components shown in Figure 10 can be implemented within a single component, or Figure 10 a single component shown in Figure 10 can be implemented as multiple distributed components. Additionally or alternatively,

[0156] Figure 11FIG. is a diagram of an exemplary apparatus 1100 for wireless communication in accordance with the present disclosure. Apparatus 1100 may be a second wireless device, or the second wireless device may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may use receiving component 1102 and transmitting component 1104 to communicate with another apparatus 1106 (such as a STA, an AP, or another wireless communication device). As further shown, apparatus 1100 may include a communication manager 1108

[0157] In some aspects, apparatus 1100 may be configured to perform one or more operations described herein in connection with Figures 5 to 7 Additionally or alternatively, apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 9 process 900. In some aspects, Figure 11 Apparatus 1100 and / or one or more components shown in Figure 2 may include one or more components of the second wireless device described in connection with Figure 11 Additionally or alternatively, one or more components shown in Figure 2 may be implemented within one or more components described in connection with

[0158] Figure 2

[0159] The receiving component 1102 may receive communications from apparatus 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of apparatus 1100. In some aspects, the receiving component 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, and other examples), and may provide the processed signals to one or more other components of apparatus 1100. In some aspects, the receiving component 1102 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the second wireless device described in connection with

[0159] The transmitting component 1104 may send communications to the device 1106, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing on the generated communications (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, and other examples), and may send the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the second wireless device described in conjunction with Figure 2 In some aspects, the transmitting component 1104 may be co-located with the receiving component 1102 in a transceiver.

[0160] The receiving component 1102 may receive a request for a TWT schedule for a first link configured to be associated with a first wireless device, the request including an indication of TWT calibration for a TWT schedule of a second link associated with the first wireless device and a third wireless device, the indication of TWT calibration being indicated within a field configured to indicate a TWT start time. The transmitting component 1104 may send a response indicating the TWT start time within the field, the TWT start time being at least partially based on the indication of TWT calibration for the TWT schedule of the second link.

[0161] The communication manager 1108 may identify an additional TWT start time associated with the second link at least partially based on the second wireless device and the third wireless device being associated with the same AP multi-link device.

[0162] Figure 11 The number and arrangement of the components shown in Figure 11 are provided as an example. In practice, there may be additional components, fewer components, different components, or components in a different arrangement compared to the components shown in Figure 11 In addition, two or more of the components shown in Figure 11 may be implemented within a single component, or Figure 11 a single component shown in Figure 11 may be implemented as multiple distributed components. Additionally or alternatively,

[0163] An overview of some aspects of the present disclosure is provided below:

[0164] 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-up time (TWT) start time for a first link associated with the second wireless device, the response further indicating a TWT calibration for a second TWT schedule for a second link having a second TWT start time, the indication of the TWT calibration being indicated within a field configured to indicate the TWT start time; and communicating with the second wireless device via the first link at least in part based on the response.

[0165] Aspect 2: The method according to Aspect 1, wherein the response comprises one or more of the following: a separately addressed unsolicited response, a broadcast response, or a solicited response at least in part based on receiving a request for a TWT schedule configured for the first link.

[0166] Aspect 3: The method according to any one of Aspects 1-2, wherein communicating with the second wireless device via the first link at least in part based on the response comprises one or more of the following: communicating in the first link using the first TWT start time; communicating in the second link using the second TWT start time; or initiating a TWT tear-down of one or more of the first TWT schedule or the second TWT schedule.

[0167] Aspect 4: The method according to any one of Aspects 1-3, wherein the indication within the field configured to indicate the TWT start time comprises one or more of the following: a non-zero value, or an indication of the requested TWT start time for the first link.

[0168] Aspect 5: The method according to Aspect 4, wherein a time difference between the requested TWT start time and a second TWT start time associated with the second link satisfies a threshold.

[0169] Aspect 6: The method according to Aspect 4, wherein the requested TWT start time of the first link indicates a time in the time domain of the second wireless device.

[0170] Aspect 7: The method according to Aspect 6, wherein the time in the time domain of the second wireless device satisfies a threshold with respect to an additional TWT start time associated with the second link and associated with a time in an additional time domain of a third wireless device.

[0171] Aspect 8: The method according to aspect 4, wherein the response indicating the first TWT start time within the field indicates one or more of the following: a first TWT start time identified by the second wireless device as meeting a first threshold relative to the second TWT start time associated with the second link, the requested TWT start time, or a first TWT start time identified by the second wireless device as meeting a second threshold relative to the requested TWT start time.

[0172] Aspect 9: The method according to any one of aspects 1-8, wherein the TWT calibration includes one or more of the following: a first time difference between the first TWT start time and the second TWT start time meets a first threshold, a second time difference between the first TWT start time and a subsequent TWT start time associated with a subsequent TWT period associated with the second link meets a second threshold, a third time difference 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 meets a third threshold, a fourth difference between the first TWT wake-up interval mantissa and the first exponent field of the first link and the second TWT wake-up interval mantissa and the second exponent field of the second link meets a fourth threshold, or a time offset between the timing of the first TWT start time associated with the second link and the timing of the second TWT start time.

[0173] Aspect 10: The method according to aspect 9, wherein the time offset is at least partially based on a TWT service period associated with the first TWT schedule.

[0174] Aspect 11: The method according to any one of aspects 1-10, wherein the TWT calibration includes one or more of the following: a first time difference between the first TWT periodicity of the first link and the second TWT periodicity of the second link meets a threshold, a second time difference between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link meets a threshold, or a third time difference between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link meets a threshold.

[0175] Aspect 12: The method according to any one 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 of the second service period duration.

[0176] Aspect 13: The method according to any one 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 time or a reference time in the time domain of the second wireless device.

[0177] Aspect 14: A method of wireless communication performed by a second wireless device, comprising: sending to a first wireless device a response indicating a first target wake-up time (TWT) schedule for a first link associated with the first wireless device, the first TWT start time, the response further indicating a TWT calibration for a second TWT schedule for a second link having a second TWT start time, the indication of the TWT calibration being indicated within a field configured to indicate the TWT start time; and communicating with the first wireless device via the first link at least in part based on the response.

[0178] Aspect 15: The method according to Aspect 14, wherein the response comprises one or more of the following: a separately addressed unsolicited response, a broadcast response, or a solicited response at least in part based on receiving a request for a TWT schedule configured for the first link.

[0179] Aspect 16: The method according to any one of Aspects 14-15, wherein communicating with the second wireless device via the first link at least in part based on the response comprises one or more of the following: 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 tear-down of one or more of the first TWT schedule or the second TWT schedule.

[0180] Aspect 17: The method according to any one of Aspects 14-16, wherein the indication within the field configured to indicate the TWT start time comprises one or more of the following: a non-zero value, or an indication of the requested TWT start time for the first link.

[0181] Aspect 18: The method according to Aspect 17, wherein the time difference between the requested TWT start time and the second TWT start time associated with the second link satisfies a threshold.

[0182] Aspect 19: The method according to Aspect 17, wherein the requested TWT start time of the first link indicates a time in the time domain of the second wireless device.

[0183] Aspect 20: The method according to 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 a second link and associated with a time in the additional time domain of a third wireless device.

[0184] Aspect 21: The method according to aspect 17, wherein the response indicating the start time of the first TWT within the field indicates one or more of the following: a first TWT start time identified by the second wireless device as meeting a first threshold relative to the start time of the second TWT associated with the second link, the requested TWT start time, or a first TWT start time identified by the second wireless device as meeting a second threshold relative to the requested TWT start time.

[0185] Aspect 22: The method according to any one of aspects 14-21, wherein the TWT calibration includes one or more of the following: a first time difference between the start time of the first TWT and the start time of the second TWT meets a first threshold, a second time difference between the start time of the first TWT and the start time of a subsequent TWT period associated with the second link meets a second threshold, a third time difference between the start time of a subsequent TWT period associated with the first link and the start time of the second TWT associated with the second link meets a third threshold, a fourth difference between the first TWT wake-up interval mantissa and the first exponent field of the first link and the second TWT wake-up interval mantissa and the second exponent field of the second link meets a fourth threshold, or a time offset between the timing of the start time of the first TWT associated with the second link and the timing of the start time of the second TWT.

[0186] Aspect 23: The method according to aspect 22, wherein the time offset is at least partially based on the TWT service period associated with the first TWT schedule.

[0187] Aspect 24: The method according to any one of aspects 14-23, wherein the TWT calibration includes one or more of the following: a first time difference between the first TWT periodicity of the first link and the second TWT periodicity of the second link meets a threshold, a second time difference between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link meets a threshold, or a third time difference between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link meets a threshold.

[0188] Aspect 25: The method according to any one 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 of the second service period duration.

[0189] Aspect 26: The method according to any one 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 time or a reference time in the time domain of the second wireless device.

[0190] Aspect 27: An apparatus for wireless communication at a device, comprising: a processor; a processor coupled to the memory; 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.

[0191] 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.

[0192] Aspect 29: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 1 - 26.

[0193] 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 according to one or more of aspects 1 - 26.

[0194] Aspect 31: A non - transitory computer - readable medium storing an instruction set for wireless communication, the instruction set 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.

[0195] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations can be made in light of the above disclosure, or can be obtained from practice of the aspects.

[0196] As used herein, the term "component" is intended to be broadly construed as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, "software" shall be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, and / or functions, among other examples. As used herein, a "processor" is implemented as a combination of hardware and / or hardware and software. It is evident that the systems and / or methods described herein can be implemented in different forms of combinations of hardware and / or hardware and software. The actual specific control hardware or software code used to implement these systems and / or methods does not limit these aspects. Accordingly, the operations and behaviors of the systems and / or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement the systems and / or methods at least in part based on the description herein.

[0197] As used herein, depending on the context, "meeting a threshold" can refer to a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0198] Even if specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. Many of these features can be combined in ways not specifically recited in the claims and / or not disclosed in the specification. The disclosure of the various aspects includes the combination of each dependent claim with every other claim in the set of claims. As used herein, the phrase "at least one" in reference to a list of items refers to any combination of those items, including a single member. By way of example, "at least one of a, b, or c" is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiple identical elements (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c). Or any other ordering of a, b, and c).

[0199] Unless expressly described as such, elements, acts, or instructions used herein should not be construed as critical or essential. Further, as used herein, the article "a" is intended to include one or more items and may be used interchangeably with "one or more." Further, as used herein, the article "the" is intended to include one or more items referred to in conjunction with the article "the" and may be used interchangeably with "one or more." Further, as used herein, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more." In the case of only Figure 1 one item, the phrase "only one" or similar language is used. Further, as used herein, the terms "has," "have," "having," etc. are intended to be open-ended terms that do not limit the elements they modify (e.g., an element "having" A may also have B). Further, unless expressly stated otherwise, the phrase "based on" is intended to mean "at least partially based on." Further, as used herein, the term "or" when used in series is intended to be inclusive and may be used interchangeably with "and / or" unless expressly stated otherwise (e.g., if used in combination with "either" or "only one of").

Claims

1. A first wireless device for wireless communication, comprising: a memory; and one or more processors coupled to the memory and configured to: receive, from a second wireless device, a response indicating a first target wake-up time (TWT) start time of a first TWT schedule for a first link associated with the second wireless device, the response further indicating a TWT calibration for a second TWT schedule of a second link having a second TWT start time, the indication of the TWT calibration being indicated within a field configured to indicate a TWT start time; and communicate with the second wireless device via the first link at least in part based on the response.

2. The first wireless device according to claim 1, wherein the response includes one or more of the following: a separately addressed unsolicited response, a broadcast response, or a solicited response at least in part based on receiving a request for a TWT schedule configured for the first link.

3. The first wireless device according to claim 1, wherein to communicate with the second wireless device via the first link at least in part based on the response, the one or more processors are configured to: communicate using the first TWT start time in the first link; communicate using the second TWT start time in the second link; or initiate a TWT tear-down of one or more of the first TWT schedule or the second TWT schedule.

4. The first wireless device according to claim 1, wherein the indication within the field configured to indicate a TWT start time includes one or more of the following: a non-zero value, or an indication of a requested TWT start time for the first link.

5. The first wireless device according to claim 4, wherein a time difference between the requested TWT start time and a second TWT start time associated with the second link satisfies a threshold.

6. The first wireless device according to claim 4, wherein the requested TWT start time for the first link indicates a time in the time domain of the second wireless device.

7. The first wireless device according to claim 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, the additional TWT start time being associated with a time in an additional time domain of a third wireless device.

8. The first wireless device according to claim 4, wherein the response indicating the first TWT start time within the field indicates one or more of the following: the first TWT start time identified by the second wireless device and satisfying a first threshold relative to a second TWT start time associated with the second link, the requested TWT start time, or the first TWT start time identified by the second wireless device and satisfying a second threshold relative to the requested TWT start time.

9. The first wireless device according to claim 1, wherein the TWT calibration includes one or more of the following: The first time difference between the start time of the first TWT and the start time of the second TWT satisfies a first threshold value. The second time difference between the start time of the first TWT and the start time of a subsequent TWT period associated with a second link satisfies a second threshold value. The third time difference between the start time of a subsequent TWT period associated with a first link and the start time of the second TWT associated with the second link satisfies a third threshold value. The fourth difference between the mantissa of the first TWT wake-up interval and the first exponent field of the first link and the mantissa of the second TWT wake-up interval and the second exponent field of the second link satisfies a fourth threshold value, or A time offset between the timing of the start time of the first TWT associated with the second link and the timing of the start time of the second TWT.

10. The first wireless device according to claim 9, wherein, the time offset is at least partially based on a TWT service period associated with the first TWT schedule.

11. The first wireless device according to claim 1, wherein, TWT calibration includes one or more of the following: The first time difference between the first TWT periodicity of the first link and the second TWT periodicity of the second link satisfies a threshold value. The second time difference between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link satisfies a threshold value, or The third time difference between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link satisfies a threshold value.

12. The first wireless device according to claim 1, 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 of the second service period duration.

13. The first wireless device according to claim 1, wherein, the start time of the first TWT is an absolute time, or wherein the start time of the first TWT is relative to a start time or a reference time in the time domain of the second wireless device.

14. A second wireless device for wireless communication, comprising: a memory; and one or more processors coupled to the memory and configured to: send a response to the first wireless device indicating a first start time of a first target wake-up time (TWT) schedule for a first link associated with the first wireless device, the response further indicating TWT calibration for a second TWT schedule for a second link having a second start time, the indication of the TWT calibration being indicated within a field configured to indicate the start time of the TWT; and communicate with the first wireless device via the first link at least partially based on the response.

15. The second wireless device according to claim 14, wherein, the response includes one or more of the following: a separately addressed unsolicited response, a broadcast response, or At least in part based on a solicited response to a request to receive a TWT schedule configured for the first link.

16. The second wireless device according to claim 14, wherein, To communicate with the second wireless device via the first link at least in part based on the response, the one or more processors are configured to: Communicate using a first TWT start time in the first link; Communicate using a second TWT start time in the second link; or Initiate a TWT cancellation of one or more of the first TWT schedule or the second TWT schedule.

17. The second wireless device according to claim 14, wherein, The indication within the field configured to indicate the TWT start time includes one or more of the following: A non-zero value, or An indication of the requested TWT start time for the first link.

18. The second wireless device according to claim 17, wherein, The time difference between the requested TWT start time and the second TWT start time associated with the second link satisfies a threshold.

19. The second wireless device according to claim 17, wherein, The requested TWT start time of the first link indicates a time in the time domain of the second wireless device.

20. The second wireless device according to claim 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, and the additional TWT start time is associated with a time in an additional time domain of a third wireless device.

21. The second wireless device according to claim 17, wherein, The response indicating the first TWT start time within the field indicates one or more of the following: The first TWT start time identified by the second wireless device that satisfies 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 identified by the second wireless device that satisfies a second threshold relative to the requested TWT start time.

22. The second wireless device according to claim 14, wherein, The TWT calibration includes one or more of the following: A first time difference between the first TWT start time and the second TWT start time satisfies a first threshold, A second time difference between the first TWT start time and a subsequent TWT start time associated with a subsequent TWT period associated with the second link satisfies a second threshold, A third time difference 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 satisfies a third threshold, A fourth difference between a first TWT wake-up interval mantissa and a first exponent field of the first link and a second TWT wake-up interval mantissa and a second exponent field of the second link satisfies a fourth threshold, or A time offset between the timing of the first TWT start time associated with the second link and the timing of the second TWT start time.

23. The second wireless device according to claim 22, wherein, the time offset is at least partially based on a TWT service period associated with the first TWT schedule.

24. The second wireless device according to claim 14, wherein, the TWT calibration includes one or more of the following: a first time difference between a first TWT periodicity of the first link and a second TWT periodicity of the second link satisfies a threshold, a second time difference between a multiple of the first TWT periodicity of the first link and the second TWT periodicity of the second link satisfies a threshold, or a third time difference between the first TWT periodicity of the first link and a multiple of the second TWT periodicity of the second link satisfies a threshold.

25. The second wireless device according to claim 14, 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 of the second service period duration.

26. The second wireless device according to claim 14, wherein, the first TWT start time is an absolute time, or wherein the first TWT start time is relative to a start time or a reference time in the time domain of the second wireless device.

27. 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 for a first target wake-up time (TWT) schedule for a first link associated with the second wireless device, the response further indicating a TWT calibration for a second TWT schedule for a second link having a second TWT start time, the indication of the TWT calibration being indicated within a field configured to indicate the TWT start time; and communicating with the second wireless device via the first link at least partially based on the response.

28. The method according to claim 27, wherein, the TWT calibration includes one or more of the following: a first time difference between the first TWT start time and the second TWT start time satisfies a first threshold, a second time difference between the first TWT start time and a subsequent TWT start time associated with a subsequent TWT period associated with the second link satisfies a second threshold, a third time difference 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 satisfies a third threshold, a fourth difference between a first TWT wake-up interval mantissa and a first exponent field of the first link and a second TWT wake-up interval mantissa and a second exponent field of the second link satisfies a fourth threshold, or a time offset between the timing of the first TWT start time associated with the second link and the timing of the second TWT start time.

29. A method of wireless communication performed by a second wireless device, comprising: sending a response to a first wireless device indicating a first target wake-up time (TWT) start time of a first TWT schedule for a first link associated with the first wireless device, the response further indicating a TWT calibration for a second TWT schedule for a second link having a second TWT start time, the indication of the TWT calibration being indicated within a field configured to indicate a TWT start time; and communicating with the first wireless device via the first link at least in part based on the response.

30. The method according to claim 29, wherein the TWT calibration includes one or more of the following: a first time difference between the first TWT start time and the second TWT start time satisfies a first threshold, a second time difference between the first TWT start time and a subsequent TWT start time associated with a subsequent TWT period associated with the second link satisfies a second threshold, a third time difference 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 satisfies a third threshold, a fourth difference between a first TWT wake-up interval mantissa and a first exponent field of the first link and a second TWT wake-up interval mantissa and a second exponent field of the second link satisfies a fourth threshold, or a time offset between the timing of the first TWT start time associated with the second link and the timing of the second TWT start time.

Images