Target wakeup time (TWT) renenegotiation

By detecting WLAN link changes in wireless devices and renegotiating TWT parameters and TTP values, the problem of limited range and susceptibility to traditional Bluetooth and BLE technologies is solved, and the uninterrupted Bluetooth audio data streaming playback is achieved, which enhances users Experience.

CN118947150APending Publication Date: 2024-11-12QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380029895.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-01
Filing Date
2023-03-20
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

Traditional Bluetooth and BLE technologies have problems such as limited scope, limited data capacity throughput, and susceptibility to Wi-Fi interference, which affect the user experience.

Method used

By sending Bluetooth-encoded audio frames through the WLAN link in a wireless device, renegotiate the target wake-up time (TWT) parameters and play time (TTP) values ​​after detection link changes, dynamically adjust the TWT session to adapt to channel conditions changes, ensuring audio Continuity of data flow.

Benefits of technology

It realizes the uninterrupted playback of Bluetooth-encoded audio frames during different TWT sessions, improving the reliability and user experience of audio data streams, and avoiding audio stream interruptions due to channel changes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118947150A_ABST
    Figure CN118947150A_ABST
Patent Text Reader

Abstract

This disclosure describes techniques for renegotiating target wake time (TWT) parameters for transmitting Bluetooth encoded audio frames over one or more Wi-Fi channels. In some implementations, a software-enabled access point (soft AP) paired with a peripheral device based on a Bluetooth protocol and associated with the peripheral device via a WLAN link sends one or more first Bluetooth-encoded audio frames to the peripheral device over the WLAN link during a first TWT session indicating a current play time (TTP) value for audio data. The soft AP detects a change in the WLAN link and obtains a new TWT parameter and a new TTP value in response to the detected change. The soft AP indicates the new TWT parameter and the new TTP value to the peripheral device in conjunction with dismantling the first TWT session, and establishes a second TWT session with the peripheral device based at least in part on the new TWT parameter.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 711,954, entitled “TARGET WAKE TIME (TWT) RENEGOTIATION,” filed by UPPALA et al. on April 1, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly to renegotiating target wake time (TWT) parameters for sending Bluetooth encoded audio frames over one or more Wi-Fi channels. Background Art

[0004] A wireless personal area network (WPAN) is a short-range wireless network typically established by a user to interconnect various personal devices, sensors, and / or appliances located within a certain distance or area of ​​the user. (BT) protocol, Low Energy Protocol or A WPAN based on the WLAN protocol can provide wireless connectivity to peripheral devices within a specific distance (such as 5 meters, 10 meters, 20 meters, 100 meters, etc.) of a user.

[0005] Bluetooth is a short-range wireless communication protocol that supports a WPAN between a central device (such as a host device) and at least one peripheral device (such as a client device).The power consumption associated with Bluetooth communications may make Bluetooth impractical in certain applications.

[0006] To address the power consumption issues associated with Bluetooth, the Low energy consumption (BLE) and is used in various applications where data transfer occurs relatively infrequently. Specifically, BLE utilizes infrequent data transfer by using low duty cycle operation and placing one or both of the central device and the peripheral device in sleep mode between data transmissions, thereby saving power. Example applications using BLE include battery-driven sensors and actuators in various medical, industrial, consumer and fitness applications. BLE can also be used to connect devices, such as smart phones, tablets and laptops that support BLE. Although traditional Bluetooth and BLE provide certain advantages, there is a need for further improvement of Bluetooth and BLE technology. For example, traditional Bluetooth and BLE have limited range, limited data capacity throughput, and are susceptible to interference from other devices communicating in the same frequency band (such as Wi-Fi communications). Summary of the invention

[0007] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0008] An innovative aspect of the subject matter described in the present disclosure can be implemented as a method for wireless communication by a wireless device. In some specific implementations, the method includes operating the wireless device as a wireless station (STA) associated with a wireless local area network (WLAN), and also operating as a software-enabled access point (soft AP) paired with a peripheral device based on a Bluetooth protocol, and the peripheral device is associated with the soft AP via a WLAN link. The method includes sending one or more first Bluetooth encoded audio frames to the peripheral device via a WLAN link during a first target wake time (TWT) session on the WLAN link, and the one or more first Bluetooth encoded audio frames indicate a current play time (TTP) value for audio data. The method includes detecting a change in the WLAN link, and obtaining one or more new TWT parameters and a new TTP value in response to detecting a change in the WLAN link, the new TTP value being greater than the current TTP value. The method includes indicating one or more new TWT parameters and a new TTP value to the peripheral device in conjunction with dismantling the first TWT session, and establishing a second TWT session with the peripheral device on the WLAN link based at least in part on the one or more new TWT parameters. In some aspects, the peripheral device may include a first earbud and a second earbud, each of the first earbud and the second earbud being associated with a soft AP, and each of the first earbud and the second earbud being paired with the soft AP via a Bluetooth connection.

[0009] In various implementations, the detected change in the WLAN link may include one or more of the following: a degradation in channel conditions on the WLAN link, a decrease in a channel quality indicator (QCI) of the WLAN link, a decrease in a modulation and coding scheme (MCS) associated with sending Bluetooth coded audio frames over the WLAN link, an increase in a packet error rate (PER) associated with the WLAN link, an increase in latency associated with sending Bluetooth coded audio frames over the WLAN link, or an increase in the number of retransmission attempts of one or more Bluetooth coded audio frames over the WLAN link. In some cases, the time period between the first time indicated by the current TTP value and the second time indicated by the new TTP value may be based at least in part on a duration associated with establishing a second TWT session. In some aspects, the time period may be approximately 250 milliseconds.

[0010] In some cases, the WLAN link includes one or more wireless channels in the 2.4 GHz band, the 5 GHz band, or the 6 GHz band. In other cases, the WLAN link includes at least one of the following: a peer-to-peer (P2P) link, a tunnel direct link setup (TDLS) link, a Wi-Fi direct link, a link associated with a group owner (GO), or a link associated with a neighbor area network (NAN).

[0011] The method may also include sending one or more second Bluetooth encoded audio frames to the peripheral device via the WLAN link during the second TWT session, the one or more second Bluetooth encoded audio frames carrying the new TTP value. In some cases, the new TTP value is based at least in part on the size of a buffer associated with buffering the one or more second Bluetooth encoded audio frames in the peripheral device.

[0012] In various specific implementations, indicating new TWT parameters to the peripheral device may include: transmitting a Bluetooth protocol message to the peripheral device through a Bluetooth connection established between the wireless device and the peripheral device, the Bluetooth protocol message carrying the one or more new TWT parameters to the peripheral device. In some cases, the one or more new TWT parameters may include at least one of a TWT wake-up duration, a TWT wake-up interval, a TWT wake-up time, a minimum data rate, an average data rate, a delay boundary, or a user priority (UP) for the TWT session.

[0013] In some implementations, indicating the new TTP value to the peripheral device may include: after detecting the change in the WLAN link, embedding the new TTP value into at least one Bluetooth encoded audio frame sent to the peripheral device via the WLAN link. In other implementations, indicating the new TTP value to the peripheral device may include: suspending the transmission of audio data for a certain period of time in response to detecting the change in the WLAN link, and after the expiration of the period of time, sending one or more additional Bluetooth encoded audio frames to the peripheral device via the WLAN link, at least one of the additional Bluetooth encoded audio frames carrying the new TTP value. In some other implementations, indicating the new TTP value to the peripheral device may include: transmitting a Bluetooth protocol message to the peripheral device via the Bluetooth connection in response to the detected change in the WLAN link, the Bluetooth protocol message carrying the new TTP value for the audio data.

[0014] Another innovative aspect of the subject matter described in the present disclosure may be implemented in a wireless device. In some specific implementations, the wireless device may include one or more processors, and a memory coupled to the one or more processors. In some specific implementations, the memory stores processor-readable code, which, when executed by one or more processors, is configured to operate the wireless device as a STA associated with a WLAN, and also as a soft AP paired with a peripheral device based on a Bluetooth protocol, and the peripheral device is associated with the soft AP via a WLAN link. The execution of the processor-readable code may be configured to send one or more first Bluetooth encoded audio frames to a peripheral device via a WLAN link during a first TWT session on the WLAN link, and the one or more first Bluetooth encoded audio frames indicate a TTP value for audio data. The execution of the processor-readable code may be configured to detect changes in the WLAN link, and obtain one or more new TWT parameters and a new TTP value in response to detecting changes in the WLAN link, and the new TTP value is greater than the current TTP value. Execution of the processor readable code may be configured to indicate one or more new TWT parameters and a new TTP value to the peripheral device in conjunction with tearing down the first TWT session, and to establish a second TWT session with the peripheral device over the WLAN link based at least in part on the one or more new TWT parameters. In some aspects, the peripheral device may include a first earbud and a second earbud, each of the first earbud and the second earbud being associated with a soft AP, and each of the first earbud and the second earbud being paired with the soft AP via a Bluetooth connection.

[0015] In various implementations, the detected change in the WLAN link may include one or more of the following: a degradation in channel conditions on the WLAN link, a decrease in the CQI of the WLAN link, a decrease in the MCS associated with sending Bluetooth encoded audio frames over the WLAN link, an increase in the PER associated with the WLAN link, an increase in the latency associated with sending Bluetooth encoded audio frames over the WLAN link, or an increase in the number of retransmission attempts of one or more Bluetooth encoded audio frames over the WLAN link. In some cases, the time period between the first time indicated by the current TTP value and the second time indicated by the new TTP value may be based at least in part on a duration associated with establishing a second TWT session. In some aspects, the time period may be approximately 250 milliseconds.

[0016] In some cases, the WLAN link includes one or more wireless channels in the 2.4 GHz band, the 5 GHz band, or the 6 GHz band. In other cases, the WLAN link includes at least one of the following: a P2P link, a TDLS link, a Wi-Fi direct link, a link associated with a GO, or a link associated with a NAN.

[0017] Execution of the processor readable code may be configured to send one or more second Bluetooth encoded audio frames to the peripheral device via the WLAN link during the second TWT session, the one or more second Bluetooth encoded audio frames carrying the new TTP value. In some cases, the new TTP value may be based at least in part on the size of a buffer associated with buffering the one or more second Bluetooth encoded audio frames in the peripheral device.

[0018] In various embodiments, executing the processor readable code to indicate new TWT parameters to the peripheral device can be configured to transmit a Bluetooth protocol message to the peripheral device through a Bluetooth connection established between the wireless device and the peripheral device, and the Bluetooth protocol message carries the one or more new TWT parameters to the peripheral device. In some cases, the one or more new TWT parameters may include at least one of a TWT wake-up duration, a TWT wake-up interval, a TWT wake-up time, a minimum data rate, an average data rate, a delay boundary, or a user priority (UP) for a TWT session.

[0019] In some implementations, executing the processor-readable code to indicate the new TTP value to the peripheral device may be configured to embed the new TTP value into at least one Bluetooth encoded audio frame sent to the peripheral device via the WLAN link after detecting a change in the WLAN link. In other implementations, executing the processor-readable code to indicate the new TTP value to the peripheral device may be configured to suspend the transmission of audio data for a certain period of time in response to detecting a change in the WLAN link, and after the expiration of the period of time, send one or more additional Bluetooth encoded audio frames to the peripheral device via the WLAN link, at least one of the additional Bluetooth encoded audio frames carrying the new TTP value. In some other implementations, executing the processor-readable code to indicate the new TTP value to the peripheral device may be configured to transmit a Bluetooth protocol message to the peripheral device via the Bluetooth connection in response to the detected change in the WLAN link, the Bluetooth protocol message carrying the new TTP value for the audio data.

[0020] The details of one or more specific implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description herein. Other features, aspects, and advantages will become apparent from the specification, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 A pictorial diagram of an example wireless personal area network (WPAN) is shown in accordance with various aspects of the present disclosure.

[0022] Figure 2 A block diagram of a wireless device according to various aspects of the present disclosure is shown.

[0023] Figure 3 A block diagram of a Bluetooth over Internet Protocol (BToIP) protocol stack is shown in accordance with various aspects of the present disclosure.

[0024] FIG. 4A to FIG. 4B An example topology of a wireless network supporting wireless communications using the BToIP protocol disclosed herein is shown.

[0025] FIG. 5A to FIG. 5B Example topologies of other wireless networks supporting wireless communications using the BToIP protocol disclosed herein are shown.

[0026] Figure 6 Communications between a wireless device and a peripheral device over a Bluetooth connection and a WLAN link are depicted according to various aspects of the present disclosure.

[0027] Figure 7 A block diagram of another example wireless device in accordance with various aspects of the present disclosure is shown.

[0028] Fig. 8A A sequence diagram depicting example wireless communications supporting re-negotiation of target wake time (TWT) parameters between a wireless device and a peripheral device in accordance with various aspects of the present disclosure is shown.

[0029] Figure 8B A sequence diagram depicting another example wireless communication supporting a wireless device and a peripheral device to renegotiate one or more TWT parameters according to various aspects of the present disclosure is shown.

[0030] Figures 9 to 15 A flow chart illustrating example operations for supporting wireless communications for re-negotiation of TWT parameters between a wireless device and a peripheral device in accordance with various aspects of the present disclosure is shown.

[0031] Fig.16 Example TWT elements that can be used for wireless communications that support renegotiation of TWT parameters are shown.

[0032] Fig.17 A conceptual data flow diagram illustrating the flow of data between different parts / components in an example apparatus is shown.

[0033] Fig.18 Diagrams illustrating examples of hardware implementations for apparatus employing a processing system are shown.

[0034] The same reference numbers and designations in different drawings indicate the same elements. DETAILED DESCRIPTION

[0035] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the detailed description includes specific details. However, it is apparent to those skilled in the art that these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0036] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0037] By way of example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether it is called software, firmware, middleware, microcode, hardware description language or other names, software should be widely interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0038] Therefore, in one or more example embodiments, the described functions can be implemented with hardware, software, or any combination thereof. If implemented with software, the functions can be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the aforementioned types, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0039] Communications based on traditional Bluetooth and BLE suffer from several limitations, which may limit the user experience and negatively affect the user experience. For example, the range of traditional Bluetooth and BLE is limited by single-hop radio frequency (RF) transmission. Additionally, traditional Bluetooth and BLE have limited data capacity, which may have several negative effects on the user experience. For example, the limited data capacity of traditional Bluetooth and BLE may result in limited audio quality or a quality level that is unacceptable to the user. In addition, traditional Bluetooth and BLE support radio frequency communications operating in the globally accepted 2.4 GHz industrial, scientific and medical (ISM) band. However, Bluetooth and BLE devices operating only in the 2.4 GHz band may suffer from interference from other devices (such as Wi-Fi devices) communicating with each other in the 2.4 GHz band.

[0040] To address these limitations, wireless devices may be configured to operate using Bluetooth (BT) over Internet Protocol (BToIP), which allows Bluetooth and BLE data to be communicated over wireless networks based on or at least compatible with Internet Protocol (IP) packets and Transmission Control Protocol / IP (TCP / IP) packets. For example, a wireless device configured according to the present disclosure may send and receive Bluetooth and BLE data over one or more channels associated with a wireless local area network (WLAN) by encapsulating the Bluetooth or BLE data in frames or packets formatted according to the IEEE 802.11 family of wireless communication standards. In this way, wireless devices can communicate with each other not only in the 2.4 GHz band, but also in the 5 GHz, 6 GHz bands, and other suitable bands.

[0041] In some other specific implementations, the wireless device may be configured to operate using a Bluetooth (BT) over WLAN (BToWLAN) protocol that allows a WLAN-compliant data packet (such as an IEEE 802.11-compliant PPDU) to include an encapsulated Ethernet frame carrying encoded audio data intended for one or more associated Bluetooth-enabled peripheral devices. The Ethernet frame may be a new Ethernet type that indicates that the Ethernet frame carries audio data intended for one or more Bluetooth peripheral devices. The new Ethernet type may also signal that the Ethernet frame is a non-IP-based Ethernet frame that does not need to pass through a TCP / IP stack before being sent to one or more Bluetooth peripheral devices, thereby avoiding the latency associated with the TCP / IP stack.

[0042] In some specific implementations, the wireless device described herein may use the TWT operation described in the IEEE 802.11 wireless communication standard family to send Bluetooth encoded audio frames to a peripheral device over a WLAN link. For example, the 802.11ax revision of the IEEE 802.11 standard describes TWT operations that allow non-AP devices to manage activities in the WLAN by scheduling non-AP devices to operate at different times to minimize medium contention and reduce the amount of time required for corresponding non-AP devices utilizing power management mode to be awakened. The 802.11be revision of the IEEE 802.11 standard describes a restricted TWT (r-TWT) service period (SP) that can be allocated for delay-sensitive services. For example, non-legacy devices that support r-TWT operations and obtain a transmit opportunity (TXOP) outside of an r-TWT SP must terminate their corresponding TXOPs before the start of any r-TWT SP of which they are not members. In addition, services from all legacy devices during the r-TWT SP can be suppressed by scheduling a silent interval to overlap with the r-TWT SP. Therefore, r-TWT SP can provide more predictable latency, reduced worst-case latency, or reduced jitter, with higher reliability for latency-sensitive services.

[0043] When a wireless device sends a data stream over a WLAN link during a TWT SP, the wireless device must comply with the TWT parameters negotiated during the setup of the TWTSP. The values ​​of at least some of the negotiated TWT parameters may be based on the channel conditions or channel quality of the WLAN link when the TWTSP is setup or scheduled. The channel conditions and channel quality of the WLAN link may change during the sending of the data stream over the WLAN link, particularly for wireless devices such as STAs and soft APs that may move or rotate during the sending of the data stream. These changes in the channel conditions or channel quality of the WLAN link may make one or more of the negotiated TWT parameters unsuitable for sending the remainder of the data stream over the WLAN link. Currently, there is no mechanism by which wireless devices belonging to a TWTSP can change or adjust TWT parameters to compensate for changes in the channel conditions or channel quality of the WLAN link.

[0044] Specific implementations of the subject matter described in the present disclosure can be used to renegotiate one or more TWT parameters associated with TWT operations based on changes in a WLAN link. In some specific implementations, a wireless device operating as a software-enabled access point (soft AP) that is paired with a peripheral device via a Bluetooth connection and associated with the peripheral device via a WLAN link can send one or more first Bluetooth encoded audio frames to the peripheral device via the WLAN link during a first TWT session. The one or more first Bluetooth encoded audio frames may indicate a current play time (TTP) value for a corresponding audio stream sent to the peripheral device. The wireless device can detect changes in the WLAN link, and can obtain one or more new TWT parameters and a new TTP value in response to detecting a change in the WLAN link. The new TTP value can be based at least in part on the duration associated with the wireless device and the peripheral device establishing a new TWT session with each other on the WLAN link. In some aspects, the new TTP value can also be based on the size of a data buffer responsible for buffering received audio data in the peripheral device or the available space therein.

[0045] The wireless device may indicate one or more new TWT parameters and a new TTP value to the peripheral device in conjunction with tearing down the first TWT session. In some aspects, the wireless device may transmit a Bluetooth protocol message carrying the one or more new TWT parameters to the peripheral device via a Bluetooth connection. In some cases, the wireless device may embed the new TTP value in one or more additional Bluetooth encoded audio frames sent to the peripheral device during the first TWT session. In other cases, the wireless device may transmit a Bluetooth protocol message carrying the new TTP value to the peripheral device via a Bluetooth connection. The wireless device may establish a second TWT session with the peripheral device based at least in part on the one or more new TWT parameters. The wireless device may then send one or more second Bluetooth encoded audio frames carrying the new TTP value to the peripheral device via a WLAN link.

[0046] Specific implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. When the channel condition or channel quality of the WLAN link changes, the wireless device can dynamically adjust the TWT parameters used for TWT operation in a manner that compensates for the changed channel condition or channel quality of the WLAN link by renegotiating one or more of the TWT parameters with the peripheral device. In addition, by obtaining a new TTP value based at least in part on a duration associated with establishing a new TWT session and indicating the new TTP value to the peripheral device, the wireless device can send Bluetooth encoded audio frames to the peripheral device over the WLAN link during different TWT sessions without interrupting the delivery of the audio stream to the peripheral device. In this way, aspects of the present disclosure can ensure that the peripheral device is able to play audio data extracted from Bluetooth encoded audio frames received during different TWT sessions for the user without interrupting or adversely affecting the user's experience.

[0047] Figure 1 A pictorial diagram of an example wireless personal area network (WPAN) 100 is shown according to some implementations. Within the WPAN 100, a central device 102 may use a BLE protocol or a modified BLE protocol to connect to one or more peripheral devices 104, 106, 108, 110, 112, 114 and establish a BLE communication link 116 therewith. The BLE protocol is part of the BT core specification and implements radio frequency communications operating within the globally accepted 2.4 GHz Industrial, Scientific, and Medical (ISM) band.

[0048] The central device 102 may include suitable logic, circuitry, interfaces, processors, and / or code that may be operable to communicate with one or more peripheral devices 104, 106, 108, 110, 112, or 114 using the BLE protocol or a modified BLE protocol as described herein. The central device 102 may operate as an initiator to request establishment of a link layer (LL) connection with an intended peripheral device 104, 106, 108, 110, 112, or 114. A link manager may be operable to control operations between a BToIP application controller in the central device 102 and a BToIP application controller in each of the intended peripheral devices 104, 106, 108, 110, 112, and / or 114.

[0049] After establishing the requested link layer connection, the central device 102 may become a host device, and the selected or intended peripheral device 104, 106, 108, 110, 112, or 114 may be paired with the central device 102 through the established link layer connection. As a host device, the central device 102 may be able to support multiple link layer connections with various peripheral devices 104, 106, 108, 110, 112, or 114 operating as client devices at one time. Specifically, the central device 102 may manage various aspects of data packet communication in the link layer connection with one or more of the associated peripheral devices 104, 106, 108, 110, 112, or 114. For example, the central device 102 may determine a schedule of operations in the link layer connection with one or more peripheral devices 104, 106, 108, 110, 112, or 114. The central device 102 may also initiate a sequence of link layer protocol data unit (PDU) interchanges through the link layer connection. The link layer connection may be configured to run periodic connection events in a dedicated data channel.The exchange of link layer data PDU transmissions between the central device 102 and one or more of the peripheral devices 104, 106, 108, 110, 112, or 114 may occur within a connection event.

[0050] In some implementations, the central device 102 may be configured to send a first link layer data PDU to the intended peripheral device 104, 106, 108, 110, 112, or 114 in each connection event. In other implementations, the central device 102 may utilize a polling scheme to poll the intended peripheral device 104, 106, 108, 110, 112, or 114 for link layer data PDU transmission during a connection event. The intended peripheral device 104, 106, 108, 110, 112, or 114 may transmit the link layer data PDU upon receiving the packetized link layer data PDU from the central device 102. In some other implementations, the peripheral device 104, 106, 108, 110, 112, or 114 may transmit the link layer data PDU to the central device 102 without first receiving the link layer data PDU from the central device 102.

[0051] Examples of central device 102 may include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a mobile station (STA), a laptop, a personal computer (PC), a desktop computer, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device (such as a smart watch, wireless headphones, etc.), a vehicle, an electric meter, a gas pump, an oven, a thermostat, a hearing aid, a body-worn blood glucose unit, an Internet of Things (IoT) device, or any other similarly functional device.

[0052] Examples of one or more peripheral devices 104, 106, 108, 110, 112, or 114 may include a cellular phone, a smart phone, a SIP phone, a STA, a laptop, a PC, a desktop computer, a PDA, a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet, a smart device, a wearable device (such as a smart watch, wireless headphones, etc.), a vehicle, an electric meter, a gas pump, an oven, a thermostat, a hearing aid, a body-worn blood glucose unit, an IoT device, or any other similarly functional device. Although the central device 102 is illustrated as communicating with six peripheral devices 104, 106, 108, 110, 112, or 114 in the WPAN 100, the central device 102 may communicate with more than six or less than six peripheral devices within the WPAN 100 without departing from the scope of the present disclosure.

[0053] Devices implementing the BT protocol, such as the central device 102, may operate according to one radio mode, such as basic rate (BR) / enhanced data rate (EDR), and devices implementing the BLE protocol may operate according to the BLE radio mode. In some aspects, the central device 102 may be configured with dual radio modes and thus may be capable of operating according to either the BR / EDR mode or the BLE mode, for example, based on the type of short-range wireless communication in which the device may engage.

[0054] For example, the central device 102 may operate according to the BR / EDR mode for a continuous stream of data, for a broadcast network, for a mesh network, and / or for some other applications where a relatively higher data rate may be more appropriate. However, the device may operate according to the BLE mode for short burst data transmissions (such as for some other applications where power savings may be desired and / or a relatively lower data rate may be acceptable). In other aspects, the central device 102 may operate according to one or more other radio modes, including a proprietary radio mode. Examples of other radio modes may include a high-speed radio mode, a low-energy radio mode, an isochronous radio mode, and the like.

[0055] Figure 2 200 is a block diagram of a wireless device 200 according to some implementations. In some cases, the wireless device 200 may be Figure 1 In other cases, the wireless device 200 may be Figure 1 The wireless device 200 is an example of one or more peripheral devices in the peripheral devices 104, 106, 108, 110, 112, or 114. In some aspects, the wireless device 200 can be a Bluetooth enabled device (such as a BLE device).

[0056] As shown, the wireless device 200 may include a processing element, such as a processor 202, that may execute program instructions for the wireless device 200. The wireless device 200 may also include a display circuit 204 that may perform graphics processing and present information to a user via a display 242. The processor 202 may also be coupled to a memory management unit (MMU) 240, which may be configured to receive addresses from the processor 202 and translate these addresses into address locations in a memory (such as a memory 206, a ROM 208, or a flash memory 210) and / or an address location in other circuits or devices (such as a display circuit 204, a radio 230, a connector interface 220, and / or a display 242). The MMU 240 may also be configured to perform memory protection and page table translation or setup. In some aspects, the MMU 240 may be included as part of the processor 202.

[0057] The processor 202 may be coupled to other circuits of the wireless device 200. For example, the wireless device 200 may include various types of memory, a connector interface 220 through which the wireless device 200 may communicate with a computer system, and a wireless communication subsystem that may send and receive data to and from other devices based on one or more wireless communication standards or protocols. For example, in some aspects, the wireless communication subsystem may include, but is not limited to, a WLAN subsystem, a Bluetooth subsystem, or a cellular subsystem such as an LTE or 5G NR subsystem. The wireless device 200 may include multiple antennas 235a, 235b, 235c, or 235d for performing wireless communications with wireless devices in, for example, a WPAN.

[0058] The wireless device 200 may be configured to implement part or all of the techniques described herein by executing program instructions stored on a memory medium (such as a non-transitory computer-readable storage medium) and / or by hardware or firmware operations. In other embodiments, the techniques described herein may be implemented at least in part by programmable hardware elements (such as a field programmable gate array (FPGA) and / or an application specific integrated circuit (ASIC)).

[0059] In some aspects, radio 230 may include a separate controller configured to control communications for various corresponding radio access technology (RAT) protocols. Figure 2 As shown, the radio component 230 may include a WLAN controller 250 for managing WLAN communications, a Bluetooth controller 252 for managing Bluetooth and BLE, and a WWAN controller 256 for managing WWAN communications. In certain aspects, the wireless device 200 may store and execute a WLAN software driver for controlling WLAN operations performed by the WLAN controller 250, a Bluetooth software driver for controlling Bluetooth operations performed by the Bluetooth controller 252, and / or a WWAN software driver for controlling WWAN operations performed by the WWAN controller 256.

[0060] In some implementations, a first coexistence interface 254, such as a wired interface, may be used to communicate information between the WLAN controller 250 and the Bluetooth controller 252. In some other implementations, a second coexistence interface 258 may be used to communicate information between the WLAN controller 250 and the WWAN controller 256. In some other implementations, a third coexistence interface 260 may be used to communicate information between the Bluetooth controller 252 and the WWAN controller 256.

[0061] In some aspects, one or more of the WLAN controller 250, the Bluetooth controller 252, and / or the WWAN controller 256 may be implemented as hardware, software, firmware, or some combination thereof.

[0062] In some configurations, the WLAN controller 250 may be configured to use all antennas 235a, 235b, 235c and 235d to communicate with a second device in the WPAN using a WLAN link. In some other configurations, the Bluetooth controller 252 may be configured to use one or more antennas in the antennas 235a, 235b, 235c and 235d to communicate with at least one second device in the WPAN. In some other configurations, the WWAN controller 256 may be configured to use all antennas 235a, 235b, 235c and 235d to communicate with a second device in the WPAN. The WLAN controller 250, the Bluetooth controller 252 and / or the WWAN controller 256 may be configured to adjust the wake-up time interval and downtime of the device.

[0063] Figure 3 A block diagram of a BToIP protocol stack 300 according to some specific implementations is shown. The BToIP protocol stack 300 may be referred to as Figure 2 The BToIP protocol stack 300 may be implemented by one or more of the processor 202, memory 206, flash memory 210, ROM 208, radio component 230, and / or Bluetooth controller 252 described above. In some specific implementations, the BToIP protocol stack 300 may be organized into three blocks, namely, an application block 302, a host block 304, and a controller block 306. The application block 302 may be a user application that interfaces with other blocks and / or layers of the BToIP protocol stack 300. In some aspects, the application block 302 may include one or more applications and one or more Bluetooth profiles that allow the applications to communicate using Bluetooth (BT) and BLE. The host block 304 may include upper layers of the BToIP protocol stack 300, and the controller block 306 may include lower layers of the BToIP protocol stack 300. The host block 304 may use a host controller interface (HCI) (such as QHCI 354) to communicate with a controller (such as Figure 2 QHCI 354 may also be used as an interface between the controller block 306 and the host block 304, which allows a wide range of hosts to interface with the controller block 306. In some aspects, the controller block 306 may be used for hardware interface management, link establishment, and link management.

[0064] The application block 302 may include a higher level application layer (App) 308, a profile layer (Profile) 364, and a BToIP service layer 352. The host block 304 may include a generic access profile (GAP) 310, a generic attribute protocol (GATT) 312, a security manager (SM) 314, an attribute protocol (ATT) 316, a logical link control and adaptation protocol (L2CAP) 318, and a QHCI 354. In some aspects, the host block 304 may also include a BToIP application controller (BToIP AC) 356 and a TCP / IP stack 358. The controller block 306 may include a link layer (LL) 322, a link manager protocol (LMP) 324, a BT / BLE physical layer (PHY) 326, a WLAN MAC 330, and a WLAN physical layer (WLAN PHY) 332.

[0065] In order to support IoT applications, audio applications and other applications, BT / BLE PHY 326 can be configured to support wider communication bandwidth and data rate than PHY associated with conventional Bluetooth or BLE protocol stack. For example, in some aspects, BT / BLEPHY 326 can define a mechanism for sending a bit stream through a physical link connecting a BLE device. The bit stream can be grouped into code words or symbols and converted into a PDU sent through a wireless medium. BT / BLE PHY 326 can provide electrical, mechanical and program interfaces for wireless media. Specifically, BT / BLE PHY 326 can specify frequency band, channel bandwidth, modulation and coding scheme (MCS), cyclic shift diversity (CSD) and other physical aspects of wireless transmission. WLAN PHY 332 can define a mechanism for sending a bit stream through a physical WLAN link connecting two or more devices (such as a WLAN device). BT / BLE PHY 326 and WLANPHY 330 can provide electrical, mechanical and program interfaces to the transmission medium. The shape and characteristics of the electrical connectors, the frequency band used for transmission, the modulation scheme, and similar low-level parameters may be dictated by the BT / BLE PHY 326 and the WLAN PHY 330 .

[0066] LMP 324 can be responsible for low-level communications on BT / BLE PHY 326. LMP 324 can manage the sequence and timing of link layer data PDUs sent and received, and communicate with other devices about connection parameters and data flow control using link layer protocols. In some aspects, LMP 324 can provide gatekeeping functionality to limit exposure and data exchange with other devices. In some specific implementations, LMP 324 can maintain a list of allowed devices and ignore all requests for baseband PDU exchange from devices that are not on the list. LMP 324 can use QHCI 354 to communicate with the upper layers of BToIP protocol stack 300. In some aspects, LMP 324 can be used to generate baseband PDUs and / or empty packets (such as empty PDUs), which can be sent using an LMP communication link established using LMP 324 with another traditional BT device (such as a BR / EDR device).

[0067] LL 322 may be responsible for low-level communications on BT / BLE PHY 326. LL 322 may manage the sequence and timing of LL data PDUs sent and received, and communicate with other devices about connection parameters and data flow control using the LL protocol. LL 322 may provide gatekeeping functionality to limit exposure and data exchange with other devices. If filtering is configured, LL 322 may maintain a list of allowed devices and ignore all requests for data PDU exchange from devices not on the list. LL 322 may use QHCI 354 to communicate with the upper layers of the BToIP protocol stack 300. In some aspects, LL 322 may be used to generate LL data PDUs and / or empty packets (such as empty PDUs), which may be sent using an LL communication link established with another BLE device using LL 322.

[0068] L2CAP 318 may encapsulate multiple protocols from upper layers into link layer data PDUs and / or QLL setup PDUs (and vice versa). L2CAP 318 may also segment large link layer data PDUs and / or QLL setup PDUs from upper layers into segments that fit into the maximum payload size (such as 27 bytes) on the transmission side. Similarly, L2CAP 318 may receive multiple link layer data PDUs and / or QLL setup PDUs that have been segmented, and L2CAP 318 may combine the segments into a single link layer data PDU and / or QLL setup PDU that may be transmitted to upper layers.

[0069] ATT 316 may be a client / server protocol based on attributes associated with BLE devices configured for specific purposes, such as monitoring heart rate, monitoring temperature, broadcasting advertisements, etc. Attributes may be discovered, read, and written by other BLE-enabled devices. The set of operations performed on ATT 316 may include, but are not limited to, error handling, server configuration, finding information, read operations, write operations, queued writes, etc. ATT 316 may form the basis for data exchange between BLE devices.

[0070] SM 314 may be responsible for device pairing and key distribution. The security manager protocol implemented by SM 314 may define how to perform communication with the SM of the corresponding BLE device. SM 314 may provide additional cryptographic functions that may be used by other components of the modified BLE protocol stack 300. The architecture of SM 314 used in BLE may be designed to minimize the recourse requirements for peripheral devices by transferring work to the central device. SM 314 provides a mechanism that not only encrypts data but also provides data authentication.

[0071] GATT 312 describes a service framework using an attribute protocol for discovering services and for reading and writing characteristic values ​​on a corresponding BLE device. GATT 312 interfaces with application 308 through an application's profile. The application 308 profile defines a collection of attributes to be used in BLE communication and any permissions associated with the attribute. One of the benefits of BT technology is device interoperability. To ensure interoperability, it may not be enough to use a standardized wireless protocol to transfer bytes of information, and therefore a shared data representation level may be required. In other words, a BLE device can use the same data interpretation to transmit or receive data in the same format based on the expected device functionality. The attribute profile used by GATT 312 can act as a bridge between the modified BLE protocol stack and the application and functionality of the BLE device (at least from the perspective of the wireless connection point), and is defined by a profile.

[0072] GAP 310 may provide an interface for application 308 to initiate, establish, and manage connections with corresponding BT / BLE devices. Profile layer 364 may include a set of BT / BLE profiles, including but not limited to A2DP, AVRCP, HFP, etc. The profiles of profile layer 364 may operate on L2CAP 318. BToIP service 352 may determine peripheral devices (such as Figure 1The BToIP service 352 may be configured to exchange features (such as control point notifications) with the second device based on some triggers, events, and / or conditions detected or determined by the first device (such as via the processor 202 of the first device). The exchanged features (such as control point notifications) may indicate to the second device one or more actions that the second device can perform.

[0073] The QHCI 354 may determine whether to send Bluetooth packets using the traditional Bluetooth protocol or the BToIP protocol disclosed herein. The BToIP protocol bearer may be a software-enabled access point (soft AP) or an access point (AP). The BToIP protocol bearer may operate on multiple globally accepted ISM bands, including but not limited to the 2.4 GHz ISM band, the 5 GHz ISM band, the 6 GHz ISM band, and the like. In some implementations, the device's WLAN radio and / or the device's App layer 308 may be configured to select one of the globally accepted ISM bands on which the BToIP protocol bearer operates.

[0074] If QHCI 354 determines that the Bluetooth packets and / or payloads are to be sent via the BToIP protocol, QHCI 354 may route the Bluetooth packets and / or payloads to BToIP AC 356. In some aspects, QHCI 354 may indicate to BToIP AC 356 that the Bluetooth packets and / or payloads are to be sent using the BToIP protocol.

[0075] The BToIP AC 356 may be configured to encapsulate data packets in a manner that indicates that the data packets are to be sent over a WLAN channel or link using the BToIP protocol. For example, the BToIP AC 356 may add a header to each data packet to be sent using the BToIP protocol, the header indicating that the corresponding data packet is formatted to be sent based on the BToIP protocol. The BToIP AC 356 may also be configured to decapsulate data packets received using the BToIP protocol and forward the decapsulated data packets to other layers of the BToIP protocol stack 300. In some aspects, the BToIP AC 356 may decapsulate received BToIP packets by stripping the BToIP header from the received BToIP packets and forwarding the decapsulated data to other layers of the BToIP protocol stack 300.

[0076] The TCP / IP stack 358 may encapsulate the BToIP packet with a TCP / IP or TCP / UDP header and forward the encapsulated BToIP packet to the WLAN MAC 330. The TCP / IP stack 358 may decapsulate packets received via a BToIP link and forward the decapsulated data to other layers of the BToIP protocol stack 300. The WLAN PHY 332 may send BToIP packets to and receive BToIP packets from a peripheral device over a WLAN channel or link. In some aspects, the WLAN MAC 330 may be responsible for low-level communications through the WLAN PHY 332.

[0077] FIG. 4A to FIG. 4B An example topology of a wireless network using the BToIP disclosed herein to support wireless communications is shown. For example, Figure 4A An example wireless network 400A is shown that includes a STA 410 and a pair of earbuds 420 that can be paired with each other via a Bluetooth connection. In some implementations, the STA 410 can be Figure 1 An example of a central device 102, and the peripheral device 420 may be Figure 1 4. In various aspects, the STA 410 and the earbud 420 are also connected via a communication link 430, through which the STA 410 and the earbud 420 can exchange data and other information with each other based on the BToIP disclosed herein. As discussed, BToIP allows the STA 410 to send Bluetooth encoded data (such as an audio stream or a video stream) to the earbud 420 via the communication link 430 using frames or packets that conform to the IEEE 802.11 family of wireless communication standards.

[0078] The communication link 430 may be any suitable contention-based communication link that allows the STA 410 and the peripheral device 420 to communicate with each other using WLAN-compliant data packets. In some aspects, the communication link 430 may be a Wi-Fi link, such as, but not limited to, a P2P link, a TDLS link, or a Wi-Fi direct link. In some cases, the STA 410 may implement a soft AP that operates on the same wireless channel as the STA 410, and the earbud 420 may be associated with the soft AP. In this way, the earbud 420 may be associated with the soft AP, which may allow the STA 410 to communicate directly with the earbud 420 via the communication link 430 without having to tunnel through an access point (AP).

[0079] Figure 4B Shown includes reference Figure 4A An example wireless network 400B of STA 410 and earbud 420 is depicted. Wireless network 400B is similar to Figure 4A The wireless network 400A is different Figure 4B4. In the example of FIG. 4, the first earbud and the second earbud (P and S, respectively) have direct communication links 430A and 430B, respectively, with STA 410. In this example, STA 410 may concurrently send data streams to each of the first earbud (P) and the second earbud (S) via respective communication links 430A and 430B.

[0080] FIG. 5A to FIG. 5B Example topologies of other wireless networks 500A and 500B supporting wireless communications using BToIP as disclosed herein are shown. Figure 5A The wireless network 500A is shown as including a STA 510, a pair of earbuds 520 paired with the STA 510 via a Bluetooth connection, and an AP 530. In some implementations, the STA 510 may be Figure 1 An example of a central device 102, and the earbud 520 may be Figure 1 530 can operate a BSS on one or more wireless channels and can provide a wireless coverage area 535 for WLAN communication through one or more wireless channels. STA 510 can be associated with AP 530 and can receive data streams directly from AP 530 through one or more WLAN channels 531. STA 510 can also provide a wireless coverage area 511 for Bluetooth communication with earbud 520.

[0081] exist Figure 5A In the example of , the earbud 520 is located outside the Bluetooth coverage area 511 provided by the STA 510, and thus the STA 510 may not be able to send data streams to the earbud 520 via the Bluetooth connection. In various aspects, the earbud 520 may also be associated with the AP 530. Specifically, the earbud 520 may operate as a client device of the AP 530 and may receive data streams directly from the AP 530 through one or more WLAN channels 531 based on the BToIP disclosed herein.

[0082] Figure 5B Shown includes reference Figure 5A An example wireless network 500B of STA 510 and earbud 520 is depicted. Figure 5BIn the example of , the earbud 520 is located within the wireless coverage area 512 provided by the STA 510. Thus, the STA 510 and the earbud 520 can use the communication link 540 to communicate directly with each other in the absence of an AP. In various aspects, the communication link 540 allows the STA 510 and the earbud 520 to exchange data and other information with each other based on the BToIP protocol disclosed herein. The communication link 540 can be any suitable contention-based communication link that allows the STA 510 and the earbud 520 to communicate with each other using data packets that conform to the WLAN. In some aspects, the communication link 540 can be a Wi-Fi link, such as (but not limited to) a P2P link, a TDLS link, or a Wi-Fi direct link.

[0083] Figure 6 Depicted is communication 600 between a wireless device 610 and a peripheral device 620 via a Bluetooth connection 630 and a WLAN link 640 in accordance with various aspects of the present disclosure. In some implementations, the wireless device 610 may be Figure 1 The central device 102 or Figure 2 An example of a wireless device 200, and the peripheral device 620 may be Figure 1 104, 106, 108, 110, 112, or 114. In some cases, peripheral device 620 may be a pair of earbuds, such as FIG. 4A to FIG. 4B Earplugs 420 or FIG. 5A to FIG. 5B The earplug 520 of the present invention. The WLAN link 640 may be one or more wireless channels operated by or associated with a WLAN (or any other suitable wireless network). In various aspects, the wireless channel may be in a 2.4 GHz band, a 5 GHz band, a 6 GHz band, or a 60 GHz band. In some cases, the WLAN link 640 may be a P2P link, a TDLS link, a Wi-Fi direct link, a link associated with a group owner (GO), or a link associated with a neighbor area network (NAN). The Bluetooth connection 630 may be any suitable Bluetooth-compliant link or channel, including, but not limited to, an asynchronous connectionless (ACL) link, a logical link control and adaptation protocol (L2CAP) link, an advanced audio distribution profile (A2DP) link, a synchronous connection-oriented (SCO) link, or an isochronous (ISO) link.

[0084] The wireless device 610 is shown to include an encoder 612 and a transmit buffer 614. The encoder 612 may be configured to encode data such as audio or video data using a specified bit rate. The transmit buffer 614 may be configured to queue data packets to be sent to the peripheral device 620 via the Bluetooth connection 630 or the WLAN link 640. In some specific implementations, for example, based on whether the transmission is via the Bluetooth connection 630 or the WLAN link 640 and / or the channel conditions of the link or connection, the data packets to be sent to the peripheral device 620 may have a predefined size. In some aspects, the data encoded by the encoder 612 may be packetized into data packets of a predefined size. The wireless device 610 may dequeue the data packets from the transmit buffer 614 and send the data packets to the peripheral device 620 via the Bluetooth connection 630 or the WLAN link 640.

[0085] The peripheral device 620 is shown to include a receive buffer 622 and a decoder 624. Data packets received via the Bluetooth connection 630 or the WLAN link 640 may be queued or otherwise stored in the receive buffer 622. The data packets may be output from the receive buffer 622 and forwarded to the decoder 624. In some aspects, the decoder 624 may decode data (such as audio and / or video data) carried in the payload of the queued data packets and forward the decoded data to upper layers of the protocol stack for processing and playback to a user.

[0086] In some implementations, the encoder 612 can encode a first encoder / decoder (codec) frame using a first bit rate and forward the first codec frame to a transmit buffer 614 to packetize it for transmission to the peripheral device 620 via the Bluetooth connection 630 or the WLAN link 640. For situations where the first codec frame is too large to be packetized within a data packet of a predefined size, a first portion of the first codec frame that is within the range of the data packet can be dequeued from the transmit buffer 614 and transmitted to the peripheral device 620 via the Bluetooth connection 630 or the WLAN link 640. A second portion of the first codec frame that is not within the range of the data packet transmitted to the peripheral device 620 can be transmitted to the peripheral device 620 in a subsequent data packet.

[0087] The peripheral device 620 may queue the received data packets in the receive buffer 622, and may forward the first portion of the first codec frame to the decoder 624 for decoding. In some cases, the decoder 624 may not be able to decode the first portion of the first codec frame without the second portion of the first codec frame. The resulting delay in decoding the first codec frame may cause "jitter" in the playback of the audio and / or video data carried in the first codec frame, which may adversely affect the user experience. In some cases, the delay in delivering the first codec frame to the peripheral device 620 in a timely manner may be reduced by increasing the bit rate used to encode the data. In other cases, the delay in delivering the first codec frame to the peripheral device 620 in a timely manner may be reduced by increasing the transmit power level used to send data packets to the peripheral device 620 via the Bluetooth connection 630.

[0088] Figure 7 1 is a block diagram of another example wireless device 700 according to various aspects of the present disclosure. In some implementations, the wireless device 700 may be Figure 1 Central device 102, Figure 2 The wireless device 200 or Figure 6 610. In some cases, the wireless device 700 may operate as a STA that can send and receive data to and from an associated AP 780 via a wireless channel 781 of a WLAN while also operating as a soft AP that can send and receive data to and from a peripheral device 620 via a WLAN link 640 using the BToIP protocol disclosed herein. In some cases, the peripheral device 620 may be paired with the wireless device 700 based on a Bluetooth or BLE protocol. For example, in some aspects, the peripheral device 620 may be a pair of earbuds or headphones that may exchange Bluetooth encoded data and other signals with the wireless device 700 via a Bluetooth connection 630 using a Bluetooth or BLE protocol, and may also exchange Bluetooth encoded data and other information with the wireless device 700 via a WLAN link 640 using the BToIP protocol disclosed herein.

[0089] The wireless device 700 may include an application processing subsystem 710, an audio subsystem 720, a WLAN subsystem 730, a Bluetooth subsystem 740, and a host controller interface (HCI) 750. Figure 3The application processing subsystem 710 of at least some parts of the application layer and host block of the BToIP protocol stack 300 is shown to include a media player 711, an application layer (App) 712, a Bluetooth stack 713, and an audio interface 714. The media player 711 can be a suitable device or component capable of generating or receiving multimedia content including, for example, real-time audio streaming, real-time video streaming, real-time game streaming, and other delay-sensitive services. It can be Figure 3 The application layer 712 of one specific implementation of the application block 302 includes at least one Bluetooth profile that defines a set of attributes and associated permissions to be used in Bluetooth or BLE communications. In some aspects, the application layer 712 may include processing resources including (but not limited to) Figure 2 The memory 206, ROM 208 and flash memory 210 of the Bluetooth stack 713 can be Figure 3 A specific implementation of the BToIP protocol stack 300.

[0090] The Bluetooth transmission driver 716 may include a split audio and packetization module 716A and a BToIP AC 716B. The split audio and packetization module 716A may be responsible for packetizing data (such as audio and / or video data) into Bluetooth frames that may be sent to the peripheral device 620 using the Bluetooth / BLE protocol or the BToIP protocol disclosed herein. Figure 3 An example of a BToIP AC 356 BToIP AC 716B may be configured to encapsulate Bluetooth packets in a manner that indicates whether the Bluetooth packets will be sent using the Bluetooth / BLE protocol or the BToIP protocol disclosed herein, as described in reference to Figure 3 For example, the BToIP AC 716B may add a header to the Bluetooth packet indicating that the Bluetooth packet will be sent to the peripheral device 620 using the BToIP protocol disclosed herein. The BToIP AC 716B may also be configured to decapsulate data packets received via the WLAN link 640 and forward the decapsulated data to other layers of the Bluetooth stack 713. Figure 7 In the example of , BToIP AC 716B is shown as being provided in the host, but in other specific implementations, BToIP AC 716B may be provided within WLAN subsystem 730.

[0091] The Bluetooth transport driver 716 is connected to the audio subsystem 720 via an audio and control link 760. In some cases, the audio and control link 760 can be used to transmit encoded audio / video data and control signals between the Bluetooth transport driver 716 and the audio / video DSP within the audio subsystem 720. The TCP / IP stack 717 allows the wireless device 700 to exchange data and control information with a corresponding layer of a TCP / IP stack implemented in the peripheral device 620. For example, the TCP / IP stack 717 can be used to format frames or packets for transmission based on the TCP / IP transmission protocol, and can be used to extract data from frames or packets received based on the TCP / IP transmission protocol.

[0092] The WLAN stack 718 allows the wireless device 700 to exchange data and control information with a corresponding layer of a WLAN stack implemented in the AP 780 and / or with a corresponding layer of a WLAN stack implemented in the peripheral device 620. For example, the WLAN stack 718 may be used to format a frame or packet to be sent as a PPDU compliant with IEEE 802.11 to the AP 780 through the WLAN channel 781, and may be used to extract data from the PPDU compliant with IEEE 802.11 received from the AP 780 through the WLAN channel 781. In some cases, the WLAN stack 718, the TCP / IP stack 717, and the UART controller 719 may correspond to the kernel space of the application processing subsystem 710. The UART 741 managed by the UART controller 719 provides a 3-wire interface (such as a transmit line, a receive line, and a ground line) between the application processing subsystem 710 and the Bluetooth subsystem 730. The bus 731 provides a connection between the WLAN stack 718 and the WLAN subsystem 730. The bus 731 may be any suitable bus, signal line, or signaling that may be used to exchange PPDUs, control information, and other signals between the WLAN stack 718 and the WLAN subsystem 730. For example, in some aspects, the bus 731 may be a PCIe bus, a sound line, an inter-IC sound (I2S) bus, or the like.

[0093] The audio subsystem 720 may include an encoder / decoder 722, one or more digital signal processors (DSPs) 724, and one or more codecs 726. The encoder / decoder 722 may be used to sample audio / video data extracted from one or more PPDUs received via one or more WLAN channels 781 and processed in the application processing block 710 based at least in part on a Bluetooth profile. In some implementations, the encoder / decoder 722 may segment the sampled audio / video data into payloads that may be embedded into one or more Bluetooth packets for transmission to the peripheral device 620 via the Bluetooth connection 630. In some other implementations, the encoder / decoder 722 may segment the sampled audio / video data into Ethernet frames or packets that may be encapsulated into IEEE 802.11 compliant PPDUs for transmission to the peripheral device 620 via the WLAN link 640. In some cases, the DSP 724 and / or the codec 726 may employ one or more encoding or decoding algorithms in conjunction with sampling the audio data.

[0094] The WLAN subsystem 730 may include a WLAN baseband circuit and firmware block 732, a MAC layer 734, and a PHY 736. The WLAN firmware may control the operation of the WLAN subsystem 730 and may determine the protocol and configuration of one or both of the MAC layer 734 or the PHY 736. The WLAN baseband circuit may decode and / or process received data at a baseband frequency and may process and encode outgoing data at a baseband frequency. The MAC layer 734 and the PHY 736 are jointly responsible for embedding outgoing data into a MAC frame (such as an MSDU), encapsulating the MAC frame into a data packet (such as a PPDU), and sending the data packet to one or more other wireless devices over a WLAN channel 781. The MAC layer 734 and the PHY 736 are also jointly responsible for receiving a data packet (such as a PPDU) over the WLAN channel 781, extracting data from a MAC frame encapsulated in the received data packet, and decoding the extracted data.

[0095] Specifically, when the WLAN subsystem 730 is in a receive mode, the PHY 736 may be used to receive, demodulate, and down-convert a PPDU received via the WLAN channel 781, and the MAC layer 734 may be used to decode data encapsulated in the received PPDU. The MAC layer 734 may also forward the decoded data to the application processing subsystem 710 via the HCI 750. When the WLAN subsystem 730 is in a transmit mode, the MAC layer 734 may be used to construct and format a MAC frame to carry data provided by an upper layer, and the PHY 736 may encapsulate the MAC frame in one or more PPDUs for transmission via the WLAN channel 781. In some aspects, the PHY 736 may define a mechanism for transmitting an A / V bitstream to the peripheral device 620 via the WLAN link 640 based on the BToIP protocol disclosed herein.

[0096] The Bluetooth subsystem 740 may include a Bluetooth baseband circuit and firmware block 742, an Advanced Audio Distribution Profile (A2DP) circuit 744, and a PHY 746. The Bluetooth baseband circuit and firmware block 742 may be used to generate a baseband signal for constructing and deconstructing a data frame based on a Bluetooth or BLE protocol. The Bluetooth baseband circuit and firmware block 742 may also be used to generate a carrier signal for up-converting the baseband signal during data transmission and for down-converting the received data signal to the baseband. The A2DP circuit 744 may be used to control or manage the A2DP link between the wireless device 700 and the peripheral device 620. Specifically, when the Bluetooth subsystem 740 is in a receiving mode, the PHY 746 may be used to receive, demodulate, and down-convert the data packets received via the Bluetooth connection 630, and forward these data packets to the application processing subsystem 710. When the Bluetooth subsystem 740 is in a transmit mode, the PHY 746 may be used to encapsulate data provided from an upper layer into one or more Bluetooth frames or packets for transmission to the peripheral device 620 via the Bluetooth connection 630 .

[0097] In various aspects, the wireless device 700 may include a WLAN link 761 connected between the audio subsystem 720 and the WLAN subsystem 730. The WLAN link 761 may provide a direct link or channel through which Bluetooth encoded audio / video data may be transmitted from the audio subsystem 720 to the WLAN subsystem 730 without passing through or accessing the application processing subsystem 710. Specifically, the WLAN link 761 may allow the Bluetooth encoded data to be forwarded directly from the audio subsystem 720 to the WLAN subsystem 730 for transmission to the peripheral device 620 via the WLAN channel 640 without consuming processing cycles of the application processor, thereby avoiding latency associated with the application processor and also avoiding latency associated with the TCP / IP stack 717. In this way, the WLAN link 761 may reduce jitter and latency by routing the Bluetooth encoded data directly from the audio subsystem 720 to the WLAN subsystem 730.

[0098] In some cases, the wireless device 700 can use the target wake time (TWT) operation specified by 802.11ax, 802.11be, and later amendments to the IEEE 802.11 family of wireless communication standards to send data streams to the peripheral device 620. In other cases, the wireless device 700 can use the restricted TWT (r-TWT) operation specified by 802.11be and later amendments to the IEEE 802.11 family of wireless communication standards to send data streams to the peripheral device 620. The restricted TWT operation allows the wireless device 700 to establish one or more r-TWT service periods (SPs) that can be used to provide more predictable latency, reduced worst-case latency, reduced jitter, and higher reliability for latency-sensitive traffic. For example, all peripheral devices that support restricted TWT operation are TXOP holders outside of any r-TWT SP, and they are not members that end their corresponding TXOPs before the start of the r-TWT SP. In some aspects, membership in the r-TWT SP may be reserved specifically for peripheral devices associated with latency-sensitive traffic.

[0099] Fig. 8A A sequence diagram depicting an example wireless communication 800 that supports renegotiation of one or more TWT parameters between a wireless device and a peripheral device according to various aspects of the present disclosure is shown. The wireless communication 800 may be performed between a wireless device 810 and a peripheral device 820. The wireless device 810 may be Figure 1 Central device 102, Figure 2 A wireless device 200, Figure 6 The wireless device 610 or Figure 7810. In some cases, the wireless device 810 can operate as a STA associated with a WLAN and also operate as a soft AP that pairs with peripheral devices based on the Bluetooth protocol. The peripheral device 820 can be associated with the soft AP of the wireless device 810 via the WLAN link 830 and can be paired with the soft AP via the Bluetooth connection 840.

[0100] In some cases, peripheral device 820 may be Figure 1 The peripheral device 104, 106, 108, 110, 112 or 114, FIG. 4A to FIG. 4B Earplugs 420, FIG. 5A to FIG. 5B Earplugs 520 or Figure 6 to Figure 7 An example of one or more of the peripheral devices 620. Fig. 8A In the example of , the peripheral device 820 is shown as a pair of earbuds, the pair of earbuds including a first earbud and a second earbud. The first earbud can be closer to the wireless device 810 than the second earbud, and thus the data packet sent by the wireless device 810 can reach the first earbud before reaching the second earbud. In some aspects, the first earbud can be designated as the primary earbud and the second earbud can be designated as the secondary earbud.

[0101] The wireless device 810 may include at least a Bluetooth subsystem 811 and a WLAN subsystem 812 coupled to each other. Fig. 8A 8, but the Bluetooth subsystem 811 may include a Bluetooth host, a Bluetooth MAC, and a Bluetooth PHY, and the WLAN subsystem 812 may include a WLAN host and WLAN hardware. The Bluetooth host may operate in conjunction with the Bluetooth MAC and PHY to allow the wireless device 810 to communicate with the peripheral device 820 via the Bluetooth connection 840. The WLAN host and the WLAN firmware may be used to format WLAN-compliant packets (such as one or more of the PPDUs described in the IEEE 802.11 wireless communication standard family), encode the WLAN-compliant packets, and send the WLAN-compliant packets to the peripheral device 820 via the WLAN link 830. The WLAN host and the WLAN firmware may also be used to decode packets received from the peripheral device 820 via the WLAN link 830.

[0102] Prior to time t1, the wireless device 810 may establish a first TWT session with the peripheral device 820 over the WLAN link 830. As discussed, the TWT session may reduce the worst-case latency and jitter of a data stream sent to the peripheral device 820 over the WLAN link. In some cases, the first TWT session may be a restricted TWT (r-TWT) operation specified by 802.11be and later revisions of the IEEE 802.11 family of wireless communication standards. The r-TWT operation allows the wireless device 810 to establish one or more r-TWT service periods (SPs) that may be used to provide more predictable latency, reduced worst-case latency, reduced jitter, higher reliability, and / or enhanced channel protection for latency-sensitive services. In some aspects, latency-sensitive services that may include audio streams may be sent from the wireless device 810 to the peripheral device 820 over a P2P link (not shown for simplicity).

[0103] For example, at time t1, the WLAN subsystem 812 sends one or more first Bluetooth encoded audio frames to the first earbud and the second earbud of the peripheral device 820 via the WLAN link 830 during the first TWT session. The one or more first Bluetooth encoded audio frames may carry audio data associated with an audio stream sent from the soft AP of the wireless device 810 to the first earbud and the second earbud of the peripheral device 820 via the WLAN link 830. The one or more first Bluetooth encoded audio frames may indicate a current TTP value for the audio stream. As discussed, the TTP value may be used by the first earbud and the second earbud of the peripheral device 820 to determine a time instance at which the audio data carried by the Bluetooth encoded audio frame will be played to the user of the peripheral device 820.

[0104] After time t1, the wireless device 810 detects a change in the WLAN link 830 that may affect the quality of the audio stream and / or may adversely affect the user experience. As discussed, the detected change in the WLAN link 830 may include one or more of the following: a degradation of channel conditions on the WLAN link 830, a decrease in a channel quality indicator (QCI) of the WLAN link 830, a decrease in the MCS used to send Bluetooth coded audio frames to the peripheral device 820 via the WLAN link 830, an increase in a packet error rate (PER) associated with the WLAN link 830, an increase in latency associated with sending Bluetooth coded audio frames via the WLAN link 830, or an increase in the number of retransmission attempts of one or more Bluetooth coded audio frames via the WLAN link 830.

[0105] In some implementations, the wireless device 810 may select, determine, or otherwise obtain one or more new TWT parameters based on the detected change in the WLAN link 830. In some cases, the one or more new TWT parameters may include at least one of a TWT wake-up duration, a TWT wake-up interval, a TWT wake-up time, a minimum data rate, an average data rate, a delay boundary, or a user priority (UP) for the TWT session. By updating one or more TWT parameters based on the detected change in the WLAN link 830, the wireless device 810 can adjust various parameters of the TWT session with the peripheral device 820 in a manner that compensates for the detected change in the WLAN link 830.

[0106] In some cases, the wireless device 810 may select, determine, or obtain one or more new TWT parameters in response to deteriorating conditions on the WLAN link 830. For example, in some aspects, when one or more of a decrease in MCS, an increase in PER, or an increase in the number of retransmission attempts is detected, the wireless device 810 may increase the minimum data rate and the average data rate. For another example, when an increase in the latency associated with the WLAN link 830 is detected, the wireless device 810 may reduce the delay boundary. For another example, when one or both of a degradation in channel conditions or a decrease in the CQI of the WLAN link 830 is detected, the wireless device 810 may increase the TWT wake-up duration and / or reduce the TWT wake-up interval.

[0107] In other cases, the wireless device 810 may select, determine, or otherwise obtain one or more new TWT parameters in response to improving conditions on the WLAN link 830. For example, in some aspects, when one or more of an increase in MCS, a decrease in PER, or a decrease in the number of retransmission attempts is detected, the wireless device 810 may increase the minimum data rate and the average data rate. For another example, when a decrease in latency associated with the WLAN link 830 is detected, the wireless device 810 may reduce the delay bound. For another example, when one or both of improved channel conditions or an increase in the CQI of the WLAN link 830 are detected, the wireless device 810 may reduce the TWT wake-up duration and / or increase the TWT wake-up interval.

[0108] The wireless device 810 may also select, determine or obtain a new TTP value in response to detecting a change in the WLAN link 830. In some specific implementations, the Bluetooth subsystem 811 may select or determine a new TTP value based on the duration associated with establishing a new TWT session with the peripheral device 820 via the WLAN link 830. Specifically, in some cases, the Bluetooth subsystem 811 may select a TTP value so that the time period between the first time indicated by the current TTP value and the second time indicated by the new TTP value is equal to or greater than the duration associated with establishing a new TWT session. For example, in an example implementation in which the wireless device 810 and the peripheral device 820 require approximately 25 milliseconds (ms) to establish a new TWT session with each other, the Bluetooth subsystem 811 may select a TTP value so that the time period between the first time indicated by the current TTP value and the second time indicated by the new TTP value is at least 25ms. In this way, various aspects of the present invention can ensure that the peripheral device 820 can play audio data received via the WLAN link 830 for the user during different TWT sessions without interrupting or reducing the quality of the audio stream.

[0109] In various implementations, the new TTP value may also be based at least in part on the size or available space of a data buffer used by the peripheral device 820 to store audio data extracted from Bluetooth encoded audio frames received from the wireless device 810 via the WLAN link 830. In some cases, as the available space in the data buffer increases, the TTP value may increase, for example, to allow the wireless device 810 and the peripheral device 820 more time to establish a new TWT session based on one or more new TWT parameters. Conversely, as the available space in the data buffer decreases, the TTP value may decrease, for example, to ensure that there is sufficient available space in the data buffer for the peripheral device 820 to store audio data extracted from Bluetooth encoded audio frames received from the wireless device 810 via the WLAN link 830.

[0110] At time t2, the wireless device 810 uses the WLAN subsystem 812 to transmit an update message indicating one or more new TWT parameters to the Bluetooth subsystem 811 of the wireless device 810. In some cases, the update message may indicate that the WLAN subsystem 812 desires to renegotiate at least one of the TWT parameters associated with the first TWT session. In response, at time t3, the Bluetooth subsystem 811 transmits a Bluetooth message indicating one or more new TWT parameters to the peripheral device 820 via the Bluetooth connection 840.

[0111] The peripheral device 820 receives the Bluetooth message and updates its TWT parameters to include one or more new TWT parameters carried in the Bluetooth message. In some cases, a first earbud of the peripheral device 820 receives the Bluetooth message, updates its TWT parameters to include the one or more new TWT parameters, and transmits a message indicating the one or more new TWT parameters to a second earbud of the peripheral device 820. In response, the second earbud updates its TWT parameters to include the one or more new TWT parameters. In this way, the wireless device 810 can use the Bluetooth connection 840 as a side channel to transmit TWT parameters and other control information to the peripheral device 820.

[0112] In some implementations, the receipt of a Bluetooth message indicating one or more new TWT parameters may be associated with an implicit instruction to request a new TWT session with the wireless device 810 based on the new TWT parameters. In some cases, the implicit instruction may instruct the peripheral device 820 to request a new TWT session after receiving a TWT teardown frame from the wireless device 810. In other implementations, the wireless device 810 may send an explicit instruction for the peripheral device 820 to request a new TWT session based on the new TWT parameters in response to receiving the TWT teardown frame. In some aspects, the wireless device 810 may transmit a Bluetooth message carrying the explicit instruction to the peripheral device 820 via the Bluetooth connection 840.

[0113] At time t4, the wireless device 810 uses the WLAN subsystem 812 to send one or more additional Bluetooth encoded audio frames to the first earplug and the second earplug of the peripheral device 820 through the WLAN link 830 during the first TWT session. The one or more additional Bluetooth encoded audio frames carry audio data associated with the audio stream and can indicate a new TTP value obtained by the wireless device 810. Each of the first earplug and the second earplug of the peripheral device 820 receives one or more additional Bluetooth encoded audio frames and updates its TTP value based on the new TTP value. Then, the first earplug and the second earplug of the peripheral device 820 can play the audio data associated with the received audio stream to the user based on the new TTP value. In some other cases, the first earplug of the peripheral device 820 receives one or more additional Bluetooth encoded audio frames, updates its TTP value based on the new TTP value, and transmits a message indicating the new TTP value to the second earplug of the peripheral device 820. In response to this, the second earplug updates its TTP value based on the new TTP value. By including a new TTP value in one or more Bluetooth encoded audio frames sent to peripheral device 820 during a first TWT session (e.g., at time t4), aspects of the present disclosure can provide an early indication to the first earbud and the second earbud of peripheral device 820 of the new TTP value to be used during the new TWT session.

[0114] In some other implementations, the wireless device 810 may suspend the transmission of Bluetooth encoded audio frames to the peripheral device 820 for a certain period of time in response to detecting a change in the WLAN link 830. In some cases, the period of time may correspond to a period of time associated with a difference between the TTP value carried in the Bluetooth encoded audio frame sent to the peripheral device 820 at time t1 and the new TTP value. Then, after the expiration of the period of time, the wireless device 810 may use the WLAN subsystem 812 to send one or more additional Bluetooth encoded audio frames carrying the new TTP value to the first earbud and the second earbud of the peripheral device 820 via the WLAN link 830.

[0115] At time t5, the wireless device 810 sends a TWT teardown frame to the peripheral device 820 via the WLAN link 830 using the WLAN subsystem 812. In some specific implementations, the TWT teardown frame is sent to both the first earbud and the second earbud via the WLAN link 830. Each of the first earbud and the second earbud of the peripheral device 820 receives the TWT teardown frame and terminates the first TWT session with the wireless device 810. In some cases, the receipt of the TWT teardown frame may be associated with an implicit instruction to request a new TWT session with the wireless device 810 based on new TWT parameters. In other cases, the wireless device 810 may send an explicit instruction for the peripheral device 820 to request a new TWT session based on the new TWT parameters in response to receiving the TWT teardown frame. In some aspects, the wireless device 810 may transmit a Bluetooth message carrying the explicit instruction to the peripheral device 820 via the Bluetooth connection 840.

[0116] At time t6, each of the first earbud and the second earbud of the peripheral device 820 sends a corresponding TWT request frame to the wireless device 810 via the WLAN link 830. In other aspects, one of the first earbud and the second earbud of the peripheral device 820 (such as the designated primary earbud of the peripheral device 820) may send a TWT request frame to the wireless device 810 on behalf of the peripheral device 820. In some cases, the TWT request frame may only indicate new TWT parameters. In other cases, the TWT request frame may indicate a complete set of TWT parameters (including one or more new TWT parameters). The WLAN subsystem 812 of the wireless device 810 receives the TWT request frame transmitted by the first earbud and the second earbud of the peripheral device 820, and accepts the TWT parameters indicated in the corresponding TWT request frame. At time t7, the wireless device 810 uses the WLAN subsystem 812 to send a TWT response frame to each of the first earbud and the second earbud of the peripheral device 820 via the WLAN link 830. The TWT response frame may indicate that the wireless device 810 accepts the TWT parameters provided by the first earbud and the second earbud of the peripheral device 820. The wireless device 810 then establishes a second TWT session with the first earbud and the second earbud of the peripheral device 820 over the WLAN link 830 based at least in part on the one or more new TWT parameters.

[0117] At time t8, the wireless device 810 uses the WLAN subsystem 812 to send one or more Bluetooth encoded audio frames to the first earbud and the second earbud of the peripheral device 820 over the WLAN link 830 during the second TWT session. The one or more Bluetooth encoded audio frames carry audio data associated with the audio stream and can indicate a new TTP value. Each of the first earbud and the second earbud of the peripheral device 820 receives the one or more Bluetooth encoded audio frames and can continue to play the audio data associated with the received audio stream to the user based on the new TTP value.

[0118] Figure 8B A sequence diagram depicting another example wireless communication 850 that supports renegotiation of one or more TWT parameters between a wireless device and a peripheral device according to various aspects of the present disclosure is shown. The wireless communication 850 may be referenced at Fig. 8A The example wireless communication 850 is performed between the wireless device 810 and the peripheral device 820. In some implementations, the example wireless communication 850 is similar to the example wireless communication 800 described with reference to the diagram 800 except for the manner in which the wireless device 810 indicates the new TTP value to the peripheral device 820.

[0119] Specifically, at time t4, the wireless device 810 transmits a Bluetooth message indicating a new TTP value to the peripheral device 820 via the Bluetooth connection 840 using the Bluetooth subsystem 811. The peripheral device 820 receives the Bluetooth message and updates its TTP value based on the new TTP value. Then, the peripheral device 820 can play the audio data associated with the received audio stream to the user based on the new TTP value. In some cases, the first earplug of the peripheral device 820 receives the Bluetooth message, updates its TTP value based on the new TTP value, and transmits a message indicating the new TTP value to the second earplug of the peripheral device 820. In response to this, the second earplug updates its TTP value based on the new TTP value. In this way, the wireless device 810 can use the Bluetooth connection as a side link to convey the TTP value (and other parameters, control signals, etc.) to the peripheral device 820.

[0120] Fig. 9 A flow chart illustrating example operations 900 for supporting wireless communication of a wireless device and a peripheral device to renegotiate TWT parameters in accordance with various aspects of the present disclosure is shown. Operations 900 may be performed by a wireless device such as Figure 1 Central device 102, Figure 2 A wireless device 200, Figure 6 A wireless device 610, or Figure 7 In various implementations, the wireless device may be a smartphone, a cell phone, or other suitable device that can transmit audio, video, and other traffic to the peripheral device. In some implementations, the peripheral device may be or may include earphones, headphones, earbuds, or other remote devices. In some cases, the peripheral device may be Figure 1 The peripheral device 104, 106, 108, 110, 112 or 114, FIG. 4A to FIG. 4B Earplugs 420, FIG. 5A to FIG. 5B Earplugs 520 or Figure 6 and Figure 7 An example of one or more of the peripheral devices 620.

[0121] For example, at 902, the wireless device operates as a wireless station (STA) associated with a wireless local area network (WLAN), and also operates as a software-enabled access point (soft AP) paired with a peripheral device based on a Bluetooth protocol, and the peripheral device is associated with the soft AP via a WLAN link. At 904, the wireless device sends one or more first Bluetooth encoded audio frames to the peripheral device via the WLAN link during a first target wake time (TWT) session on the WLAN link, and the one or more first Bluetooth encoded audio frames indicate a current play time (TTP) value for audio data. At 906, the wireless device detects a change in the WLAN link. At 908, the wireless device obtains one or more new TWT parameters and a new TTP value in response to detecting a change in the WLAN link, and the new TTP value is greater than the current TTP value. At 910, the wireless device indicates one or more new TWT parameters and a new TTP value to the peripheral device in conjunction with dismantling the first TWT session. At 912, the wireless device establishes a second TWT session with the peripheral device on the WLAN link based at least in part on the one or more new TWT parameters.

[0122] In various embodiments, the new TTP value may be based at least in part on the size of a buffer associated with buffering one or more second Bluetooth encoded audio frames in the peripheral device. In some cases, the time period between the first time indicated by the current TTP value and the second time indicated by the new TTP value may be based at least in part on the duration associated with establishing a second TWT session with the peripheral device over the WLAN link. In some aspects, the time period may be approximately 250 milliseconds.

[0123] In various implementations, the detected change may include one or more of the following: a degradation of channel conditions on the WLAN link, a decrease in a channel quality indicator (QCI) of the WLAN link, a decrease in a modulation and coding scheme (MCS) associated with sending Bluetooth coded audio frames over the WLAN link, an increase in a packet error rate (PER) associated with the WLAN link, an increase in latency associated with sending Bluetooth coded audio frames over the WLAN link, or an increase in the number of retransmission attempts of one or more Bluetooth coded audio frames over the WLAN link.

[0124] In some cases, the WLAN link may include one or more wireless channels in a sub-GHz band, a 2.4 GHz band, a 5 GHz band, or a 6 GHz band. In other cases, the WLAN link may include at least one of the following: a peer-to-peer (P2P) link, a tunnel direct link setup (TDLS) link, a Wi-Fi direct link, a link associated with a group owner (GO), or a link associated with a neighbor area network (NAN).

[0125] Fig.10 1 is a flow chart illustrating another example operation 1000 for supporting wireless communication of a wireless device and a peripheral device to renegotiate TWT parameters in accordance with various aspects of the present disclosure. Operation 1000 may be performed by a wireless device such as Figure 1 Central device 102, Figure 2 A wireless device 200, Figure 6 Wireless device 610, Figure 7 The wireless device 700, or reference Fig. 9 In some cases, the peripheral device may be Figure 1 The peripheral device 104, 106, 108, 110, 112 or 114, FIG. 4A to FIG. 4B Earplugs 420, FIG. 5A to FIG. 5B Earplugs 520, Figure 6 and Figure 7 Peripheral device 620, or reference Fig. 9 Examples of one or more of the peripheral devices described.

[0126] In some cases, operation 1000 may be performed at Fig. 9 . For example, at 1002, the wireless device sends one or more second Bluetooth encoded audio frames to the peripheral device via the WLAN link during the second TWT session, and the one or more second Bluetooth encoded audio frames carry the new TTP value. In this way, the wireless device can resume the transmission of the audio stream to the peripheral device without interrupting the audio stream by including the new TTP value in the Bluetooth encoded audio frame. In some aspects, the new TTP value can be based at least in part on the size or available space of a receive buffer responsible for buffering audio data received by the peripheral device from the wireless device.

[0127] Fig.11 1 is a flow chart illustrating another example operation 1100 for supporting wireless communication of a wireless device and a peripheral device to renegotiate TWT parameters in accordance with various aspects of the present disclosure. Operation 1100 may be performed by a wireless device such as Figure 1 Central device 102, Figure 2 A wireless device 200, Figure 6 Wireless device 610, Figure 7 The wireless device 700, or reference Fig. 9 In some cases, the peripheral device may be Figure 1 The peripheral device 104, 106, 108, 110, 112 or 114, FIG. 4A to FIG. 4B Earplugs 420, FIG. 5A to FIG. 5B Earplugs 520, Figure 6 and Figure 7 Peripheral device 620, or reference Fig. 9 Examples of one or more of the peripheral devices described.

[0128] In some cases, operation 1100 may be (e.g., in Fig. 9 An example of obtaining one or more new TWT parameters at 908 of the present invention. For example, at 1102, the wireless device updates one or more TWT parameters associated with a first TWT session based on a detected change in the WLAN link. In some cases, the wireless device may update the TWT parameters based on one or more of the following: degradation of the channel condition on the WLAN link, reduction in the channel quality indicator (QCI) of the WLAN link, reduction in the modulation and coding scheme (MCS) associated with sending Bluetooth encoded audio frames over the WLAN link, increase in the packet error rate (PER) associated with the WLAN link, increase in the latency associated with sending Bluetooth encoded audio frames over the WLAN link, or increase in the number of retransmission attempts of one or more Bluetooth encoded audio frames over the WLAN link. The updated TWT parameters may be used as new TWT parameters for a new TWT session on the WLAN link between the wireless device and the peripheral device.

[0129] Fig.12 A flow chart illustrating another example operation 1200 for supporting wireless communication of a wireless device and a peripheral device to renegotiate TWT parameters in accordance with various aspects of the present disclosure is shown. Operation 1200 may be performed by a wireless device such as Figure 1 Central device 102, Figure 2 A wireless device 200, Figure 6 Wireless device 610, Figure 7 The wireless device 700, or reference Fig. 9 In some cases, the peripheral device may be Figure 1 The peripheral device 104, 106, 108, 110, 112 or 114, FIG. 4A to FIG. 4B Earplugs 420, FIG. 5A to FIG. 5B Earplugs 520, Figure 6 and Figure 7 Peripheral device 620, or reference Fig. 9 Examples of one or more of the peripheral devices described.

[0130] In some cases, operation 1200 may be performed (e.g., Fig. 9An example of indicating new TWT parameters to a peripheral device at 910 of the wireless device. For example, at 1202, the wireless device transmits a Bluetooth protocol message to the peripheral device via a Bluetooth connection established between the wireless device and the peripheral device, the Bluetooth protocol message carrying the one or more new TWT parameters to the peripheral device. In this way, the wireless device can use the Bluetooth connection as a side link control channel through which the new TWT parameters (and other information) can be provided to the peripheral device.

[0131] Fig.13 A flowchart illustrating another example operation 1300 for supporting wireless communication of a wireless device and a peripheral device to renegotiate TWT parameters in accordance with various aspects of the present disclosure is shown. Operation 1300 may be performed by a wireless device such as Figure 1 Central device 102, Figure 2 A wireless device 200, Figure 6 Wireless device 610, Figure 7 The wireless device 700, or reference Fig. 9 In some cases, the peripheral device may be Figure 1 The peripheral device 104, 106, 108, 110, 112 or 114, FIG. 4A to FIG. 4B Earplugs 420, FIG. 5A to FIG. 5B Earplugs 520, Figure 6 and Figure 7 Peripheral device 620, or reference Fig. 9 Examples of one or more of the peripheral devices described.

[0132] In some cases, operation 1300 may be (in Fig. 9 An example of indicating a new TTP value to a peripheral device at 910 of the wireless device. For example, at 1302, the wireless device, after detecting a change in the WLAN link, embeds the new TTP value into at least one Bluetooth encoded audio frame sent to the peripheral device via the WLAN link. The peripheral device may receive the at least one Bluetooth encoded audio frame and may update its TTP value using the new TTP value embedded in the at least one Bluetooth encoded audio frame.

[0133] Fig.14 A flow chart illustrating another example operation 1400 for supporting wireless communication of a wireless device and a peripheral device to renegotiate TWT parameters in accordance with various aspects of the present disclosure is shown. Operation 1400 may be performed by a wireless device such as Figure 1 Central device 102, Figure 2 A wireless device 200, Figure 6 Wireless device 610, Figure 7 The wireless device 700, or reference Fig. 9In some cases, the peripheral device may be Figure 1 The peripheral device 104, 106, 108, 110, 112 or 114, FIG. 4A to FIG. 4B Earplugs 420, FIG. 5A to FIG. 5B Earplugs 520, Figure 6 and Figure 7 Peripheral device 620, or reference Fig. 9 Examples of one or more of the peripheral devices described.

[0134] In some cases, operation 1400 may be (in Fig. 9 An example of indicating a new TTP value to a peripheral device at 910 of the wireless device. For example, at 1402, the wireless device suspends the transmission of audio data for a certain period of time in response to detecting a change in the WLAN link. At 1404, the wireless device sends one or more additional Bluetooth encoded audio frames to the peripheral device via the WLAN link after the time period expires, at least one of the additional Bluetooth encoded audio frames carrying the new TTP value. In some cases, one or more additional Bluetooth encoded audio frames may be sent to the peripheral device during the first TWT session. In this way, the peripheral device can update its TTP value with the new TTP value during the first TWT session, thereby synchronizing the TTP value used by the peripheral device with the TTP value used by the wireless device before the second TWT session between the wireless device and the peripheral device begins.

[0135] Fig.15 1 is a flow chart illustrating another example operation 1500 for supporting wireless communication of a wireless device and a peripheral device to renegotiate TWT parameters in accordance with various aspects of the present disclosure. Operation 1500 may be performed by a wireless device such as Figure 1 Central device 102, Figure 2 A wireless device 200, Figure 6 Wireless device 610, Figure 7 The wireless device 700, or reference Fig. 9 In some cases, the peripheral device may be Figure 1 The peripheral device 104, 106, 108, 110, 112 or 114, FIG. 4A to FIG. 4B Earplugs 420, FIG. 5A to FIG. 5B Earplugs 520, Figure 6 and Figure 7 Peripheral device 620, or reference Fig. 9 Examples of one or more of the peripheral devices described.

[0136] In some cases, operation 1500 may be performed (e.g., Fig. 9The wireless device may be configured to detect a change in the WLAN link by transmitting a Bluetooth protocol message to the peripheral device via the Bluetooth connection, the Bluetooth protocol message carrying the new TTP value for the audio data. In this way, the wireless device may use the Bluetooth connection as a sidelink control channel through which the new TTP value (and other information) may be provided to the peripheral device.

[0137] Fig.16 An example TWT element 1600 that can be used for wireless communication supporting renegotiation of TWT parameters is shown. The TWT element 1600 may include an element ID field 1602, a length field 1604, a control field 1606, and a TWT parameter information field 1608. The element ID field 1602 indicates that the element is a TWT element. The length field 1604 indicates the length of the TWT element 1600. The control field 1606 includes various control information for the restricted TWT session announced by the TWT element 1600. The TWT parameter information field 1608 contains a single individual TWT parameter set field or one or more broadcast TWT parameter set fields. In some cases, the TWT element 1600 may be used to FIG. 8A to FIG. 8B In one or both of the TWT request frame or the TWT response frame.

[0138] As shown, the TWT parameter information field 1608 carries a separate TWT parameter set field 1610, which includes a request type field 1611, a target wake-up time field 1612, a TWT group assignment field 1613, a nominal minimum TWT wake-up duration field 1614, a TWT wake-up interval tail field 1615, a TWT channel field 1616, and an optional NDP paging field 1617. The request type field 1611 indicates the type of TWT session requested. The target wake-up time field 1612 carries an unsigned integer corresponding to the TSF time for the STA to request wake-up. TWT group assignment field 1613. The nominal minimum TWT wake-up duration field 1614 indicates the minimum amount of time that the expected TWT requesting STA or TWT scheduled STA remains in the wake-up state or mode. The TWT wake-up interval tail field 1615 can be set to a non-zero value for periodic TWT and set to a zero value for non-periodic TWT. The TWT channel field 1616 indicates the wireless channel on which the corresponding TWT operation is established or scheduled. The NDP Paging subfield 1617 may be used together with the Request Type field 1611 to indicate NDP paging.

[0139] As shown, the request type field 1610 includes a TWT request subfield 1622, a TWT setup command subfield 1624, a trigger subfield 1626, an implicit subfield 1628, a stream type subfield 1630, a TWT stream identifier subfield 1632, a TWT wake-up interval index subfield 1634, and a TWT protection subfield 1636. The TWT request subfield 1622 may carry a value indicating whether the corresponding TWT information element is sent by the scheduled STA or the scheduling STA. The TWT setup command subfield 1624 may carry a value indicating the type of TWT command carried in the TWT information element. The trigger subfield 1626 indicates whether the TWTSP indicated by the TWT element 1600 includes a trigger frame. For example, the trigger subfield 1626 is set to 1 to indicate that at least one trigger frame is sent during the TWT SP, otherwise it is set to 0.

[0140] The implicit subfield 1628 is set to 1 to indicate implicit TWT operation, and is set to 0 to indicate explicit TWT operation. The stream type subfield 1630 indicates the type of interaction between the TWT requesting STA or the TWT scheduled STA and the TWT responding STA or the TWT scheduling AP at the TWT. For example, setting the stream type subfield 1630 to a value of 0 indicates an announced TWT, in which the TWT requesting STA or the TWT scheduled STA transmits a PS-poll or APSD trigger frame to signal its wake-up state. Setting the stream type subfield 1630 to a value of 1 indicates an unannounced TWT, in which the TWT responding STA or the TWT scheduling AP will transmit a frame to the TWT requesting STA or the TWT scheduled STA at the TWT without waiting to receive a PS-poll or APSD trigger frame.

[0141] The TWT stream identifier subfield 1632 contains a 3-bit value that uniquely identifies specific information for the TWT request from other requests made between the same TWT requesting STA and TWT responding STA pair. The TWT wake-up interval index subfield 1634 carries a value from which the TWT wake-up interval can be obtained. In some cases, the TWT wake-up interval index subfield 1634 is set to the value of the exponent of the TWT wake-up interval value in microseconds, with a base of 2. The TWT protection subfield 1636 indicates whether the TWT requesting STA requests the TWT responding STA to provide protection for the TWT SP set corresponding to the value carried in the TWT stream identifier subfield 1632.

[0142] Fig.171700 is a conceptual data flow diagram illustrating data flow between different parts and / or components of an example apparatus 1702. In some implementations, the apparatus 1702 can be a wireless device that operates as a STA associated with a WLAN while also operating as a soft AP associated with a peripheral device 1750. The apparatus 1702 includes a receiving component 1704 that receives a data packet from another wireless communication device, such as an AP associated with a WLAN. The apparatus 1702 also includes an application processor 1706, an audio subsystem 1708, a WLAN subsystem 1710, a Bluetooth subsystem 1712, a TWT component 1714, and a transmitting component 1716.

[0143] The application processor 1706 extracts the audio data from the received data packets, attaches or applies the Bluetooth profile to the extracted audio data, and routes the extracted audio data to the audio subsystem 1708. The audio subsystem 1708 encodes the audio data and routes the encoded audio data to the WLAN subsystem 1710 via a direct link 1730. As discussed, the direct link 1730 allows the encoded audio data to be routed directly to the WLAN subsystem 1710 without passing through the application processor 1706 and without accessing the TCP / IP stack within or associated with the application processor 1706, thereby avoiding the latency associated with the application processor 1706 and the TCP / IP stack, respectively. The WLAN subsystem 1710 embeds the Bluetooth encoded audio frames into one or more IEEE 802.11 compatible data packets (such as PPDUs).

[0144] The Bluetooth subsystem 1712 may establish a Bluetooth session or connection with the peripheral device 1750 and may facilitate the use of Bluetooth communications (e.g., as one or more Bluetooth frames or packets) to send data and other information to the peripheral device 1750. For example, in some cases, the device 1702 may transmit a new TTP value to the peripheral device 1750 over the Bluetooth connection in one or more Bluetooth messages. In other cases, the device 1702 may transmit a new TWT parameter to the peripheral device 1750 over the Bluetooth connection in one or more Bluetooth messages.

[0145] The TWT component 1714 may be used by the device 1702 to establish one or more TWT sessions with the peripheral device 1750 via the WLAN link. In some cases, the TWT component 1714 may be used by the device 1702 to determine or obtain one or more new TWT parameters based on a detected change in the WLAN link. As discussed, the detected change in the WLAN link may include one or more of the following: a degradation of channel conditions on the WLAN link, a decrease in a channel quality indicator (QCI) of the WLAN link, a decrease in a modulation and coding scheme (MCS) associated with sending Bluetooth encoded audio frames via the WLAN link, an increase in a packet error rate (PER) associated with the WLAN link, an increase in latency associated with sending Bluetooth encoded audio frames via the WLAN link, or an increase in the number of retransmission attempts of one or more Bluetooth encoded audio frames via the WLAN link.

[0146] The sending component 1716 is coupled to the WLAN subsystem 1710 and the Bluetooth subsystem 1712, and can be used to send frames or packets provided by the WLAN subsystem 1710 and / or the Bluetooth subsystem 1712 to other wireless communication devices. Specifically, the sending component 1716 can be used to send WLAN frames or packets provided by the WLAN subsystem 1710 to the peripheral device 1750 through one or more WLAN channels, and can be used to send Bluetooth encoded audio frames provided by the Bluetooth subsystem 1712 to the peripheral device 1750 through a Bluetooth connection. In some specific implementations, the sending component 1716 can be used to send Bluetooth encoded audio frames encapsulated in one or more WLAN-compliant PPDUs to the peripheral device 1750 through the WLAN link. In some cases, various aspects of the sending component 1716 can be integrated into each of the WLAN subsystem 1710 and the Bluetooth subsystem 1712.

[0147] Means 1702 may include executing Figures 9 to 15 The operations in the flowchart are appended to each operation. Therefore, Figures 9 to 15 Each block in the flowchart of can be performed by a component, and the device 1702 may include one or more of those components. These components can be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0148] Fig.181800 is a diagram illustrating an example of a hardware implementation for an apparatus 1702' employing a processing system 1814. The processing system 1814 may be implemented using a bus architecture generally represented by a bus 1824. The bus 1824 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1814 and the overall design constraints. The bus 1824 links together various circuits including one or more processors and / or hardware components represented by the processor 1804, components 1704, 1706, 1708, 1710, 1712, 1714, and 1716, and computer readable media / memory 1806. The bus 1824 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0149] The processing system 1814 may be coupled to the transceiver 1810. The transceiver 1810 is coupled to one or more antennas 1820. The transceiver 1810 provides components for communicating with various other devices over a transmission medium. The transceiver 1810 receives signals from the one or more antennas 1820, extracts information from the received signals, and provides the extracted information to the processing system 1814, specifically the receiving component 1704. In addition, the transceiver 1810 receives information from the processing system 1814, specifically the transmitting component 1716, and generates signals to be applied to the one or more antennas 1820 based on the received information. The processing system 1814 includes a processor 1804, which is coupled to a computer-readable medium / memory 1806. The processor 1804 is responsible for general processing, including executing software stored on the computer-readable medium / memory 1806. The software, when executed by the processor 1804, causes the processing system 1814 to perform the various functions described above for any particular device. The computer-readable medium / memory 1806 may also be used to store data that is manipulated by the processor 1804 when executing software. The processing system 1814 also includes at least one of the components 1704, 1706, 1708, 1710, 1712, 1714, and 1716. These components may be software components that run in the processor 1804, reside / stored in the computer-readable medium / memory 1806, one or more hardware components coupled to the processor 1804, or some combination thereof.

[0150] In some configurations, the device 1702 / 1702' for wireless communication may include components for all of the component limitations described herein. The aforementioned components may be one or more of the aforementioned components of the processor 202, the radio component 230, the MMU 240, the WLAN controller 250, the Bluetooth controller 252, the WWAN controller 256, the processing system 1814 of the device 1702 and / or the device 1702' configured to perform the functions recited by the aforementioned components.

[0151] In one configuration, the apparatus 1702 / 1702' for wireless communication includes: a component for operating the wireless device as a wireless station (STA) associated with a WLAN, and also as a soft AP paired with a peripheral device based on a Bluetooth protocol, and the peripheral device is associated with the soft AP via a WLAN link. The apparatus 1702 / 1702' for wireless communication may also include: a component for sending one or more first Bluetooth encoded audio frames to the peripheral device via the WLAN link during a first TWT session on the WLAN link, the one or more first Bluetooth encoded audio frames indicating a TTP value for audio data. The apparatus 1702 / 1702' for wireless communication may also include: a component for detecting a change in the WLAN link; and a component for obtaining one or more new TWT parameters and a new TTP value in response to detecting a change in the WLAN link, the new TTP value being greater than a current TTP value. The apparatus 1702 / 1702' for wireless communication may also include: a component for indicating one or more new TWT parameters and a new TTP value to the peripheral device in conjunction with the removal of the first TWT session; and a component for establishing a second TWT session with the peripheral device over the WLAN link based at least in part on the one or more new TWT parameters. The aforementioned components may be one or more of the aforementioned components of the processing system 1814 of the apparatus 1802 and / or the apparatus 1702' configured to perform the functions described by the aforementioned components. As described above, the processing system 1814 may include Figure 2 processor 202, memory 206, flash memory 210 and / or ROM 208.

[0152] Specific implementation examples are described in the following numbered clauses:

[0153] 1. A method for wireless communication by a wireless device, the method comprising:

[0154] operating the wireless device as a wireless station (STA) associated with a wireless local area network (WLAN) and also as a software-enabled access point (soft AP) paired with a peripheral device based on a Bluetooth protocol, the peripheral device being associated with the soft AP via a WLAN link;

[0155] sending one or more first Bluetooth encoded audio frames to the peripheral device over the WLAN link during a first target wake time (TWT) session over the WLAN link, the one or more first Bluetooth encoded audio frames indicating a current time to play (TTP) value for audio data;

[0156] detecting a change of the WLAN link;

[0157] obtaining one or more new TWT parameters and a new TTP value in response to detecting the change in the WLAN link, the new TTP value being greater than a current TTP value; indicating the one or more new TWT parameters and the new TTP value to the peripheral device in conjunction with tearing down the first TWT session; and

[0158] A second TWT session is established with the peripheral device over the WLAN link based at least in part on the one or more new TWT parameters.

[0159] 2. The method according to clause 1, further comprising:

[0160] During the second TWT session, one or more second Bluetooth coded audio frames are sent to the peripheral device via the WLAN link, and the one or more second Bluetooth coded audio frames carry the new TTP value.

[0161] 3. The method of clause 2, wherein the new TTP value is based at least in part on a size of a buffer associated with buffering the one or more second Bluetooth encoded audio frames in the peripheral device.

[0162] 4. A method according to any one or more of clauses 1 to 3, wherein the time period between a first time indicated by the current TTP value and a second time indicated by the new TTP value is based at least in part on a duration associated with establishing the second TWT session.

[0163] 5. The method of clause 4, wherein the time period is approximately 250 milliseconds.

[0164] 6. A method according to any one or more of clauses 1 to 5, wherein indicating the new TWT parameters to the peripheral device comprises:

[0165] A Bluetooth protocol message is transmitted to the peripheral device via a Bluetooth connection established between the wireless device and the peripheral device, wherein the Bluetooth protocol message carries the one or more new TWT parameters to the peripheral device.

[0166] 7. A method according to any one or more of clauses 1 to 6, wherein the one or more new TWT parameters include at least one of a TWT wake-up duration, a TWT wake-up interval, a TWT wake-up time, a minimum data rate, an average data rate, a delay boundary, or a user priority (UP) for the TWT session.

[0167] 8. A method according to any one or more of clauses 1 to 7, wherein obtaining the one or more new TWT parameters comprises:

[0168] One or more TWT parameters associated with the first TWT session are updated based on the detected change in the WLAN link.

[0169] 9. A method according to any one or more of clauses 1 to 8, wherein the detected change comprises one or more of the following: a degradation of channel conditions on the WLAN link, a decrease in a channel quality indicator (QCI) of the WLAN link, a decrease in a modulation and coding scheme (MCS) associated with sending Bluetooth coded audio frames over the WLAN link, an increase in a packet error rate (PER) associated with the WLAN link, an increase in a latency associated with sending the Bluetooth coded audio frames over the WLAN link, or an increase in a number of retransmission attempts of one or more Bluetooth coded audio frames over the WLAN link.

[0170] 10. The method of any one or more of clauses 1 to 9, wherein indicating the new TTP value to the peripheral device comprises:

[0171] After detecting the change of the WLAN link, the new TTP value is embedded into at least one Bluetooth encoded audio frame sent to the peripheral device over the WLAN link.

[0172] 11. The method of any one or more of clauses 1 to 9, wherein indicating the new TTP value to the peripheral device comprises:

[0173] suspending transmission of the audio data for a period of time in response to detecting the change in the WLAN link; and

[0174] After the time period expires, one or more additional Bluetooth coded audio frames are sent to the peripheral device via the WLAN link, at least one of the additional Bluetooth coded audio frames carrying the new TTP value.

[0175] 12. The method of any one or more of clauses 1 to 9, wherein indicating the new TTP value to the peripheral device comprises:

[0176] A Bluetooth protocol message is transmitted to the peripheral device over the Bluetooth connection in response to the detected change of the WLAN link, the Bluetooth protocol message carrying the new TTP value for the audio data.

[0177] 13. A method as recited in any one or more of clauses 1 to 12, wherein the WLAN link comprises one or more wireless channels in a sub-GHz band, a 2.4 GHz band, a 5 GHz band, or a 6 GHz band.

[0178] 14. A method according to any one or more of clauses 1 to 13, wherein the peripheral device includes a first earbud and a second earbud, each of the first earbud and the second earbud is associated with the soft AP, and each of the first earbud and the second earbud is paired with the soft AP via the Bluetooth connection.

[0179] 15. A wireless device, comprising:

[0180] one or more processors; and

[0181] a memory coupled to the one or more processors and storing processor-readable code that, when executed by the one or more processors, is configured to:

[0182] operating the wireless device as a wireless station (STA) associated with a wireless local area network (WLAN) and also as a software-enabled access point (soft AP) paired with a peripheral device based on a Bluetooth protocol, the peripheral device being associated with the soft AP via a WLAN link;

[0183] sending one or more first Bluetooth encoded audio frames to the peripheral device over the WLAN link during a first target wake time (TWT) session over the WLAN link, the one or more first Bluetooth encoded audio frames indicating a current time to play (TTP) value for audio data;

[0184] detecting a change of the WLAN link;

[0185] obtaining one or more new TWT parameters and a new TTP value in response to detecting the change in the WLAN link, the new TTP value being greater than a current TTP value;

[0186] indicating the one or more new TWT parameters and the new TTP value to the peripheral device in conjunction with tearing down the first TWT session; and

[0187] A second TWT session is established with the peripheral device over the WLAN link based at least in part on the one or more new TWT parameters.

[0188] 16. The wireless device of clause 15, wherein execution of the processor readable code is further configured to:

[0189] During the second TWT session, one or more second Bluetooth coded audio frames are sent to the peripheral device via the WLAN link, and the one or more second Bluetooth coded audio frames carry the new TTP value.

[0190] 17. The wireless device of clause 16, wherein the new TTP value is based at least in part on a size of a buffer associated with buffering the one or more second Bluetooth encoded audio frames in the peripheral device.

[0191] 18. A wireless device according to any one or more of clauses 15 to 17, wherein the time period between a first time indicated by the current TTP value and a second time indicated by the new TTP value is based at least in part on a duration associated with establishing the second TWT session.

[0192] 19. The wireless device of clause 18, wherein the time period is approximately 250 milliseconds.

[0193] 20. A wireless device as described in any one or more of clauses 15 to 19, wherein the processor readable code is executed to indicate that the new TWT parameters are configured to:

[0194] A Bluetooth protocol message is transmitted to the peripheral device via a Bluetooth connection established between the wireless device and the peripheral device, wherein the Bluetooth protocol message carries the one or more new TWT parameters to the peripheral device.

[0195] 21. A wireless device according to any one or more of clauses 15 to 20, wherein the one or more new TWT parameters include a TWT wake-up duration, a TWT wake-up interval,

[0196] At least one of a TWT wake-up time, a minimum data rate, an average data rate, a delay boundary, or a user priority (UP) for the TWT session.

[0197] 22. A wireless device according to any one or more of clauses 15 to 21, wherein execution of the processor readable code to obtain the one or more new TWT parameters is configured to:

[0198] One or more TWT parameters associated with the first TWT session are updated based on the detected change in the WLAN link.

[0199] 23. A wireless device according to any one or more of clauses 15 to 22, wherein the detected change comprises one or more of the following: a degradation of channel conditions on the WLAN link, a decrease in a channel quality indicator (QCI) of the WLAN link, a decrease in a modulation and coding scheme (MCS) associated with sending Bluetooth coded audio frames over the WLAN link, an increase in a packet error rate (PER) associated with the WLAN link, an increase in a latency associated with sending the Bluetooth coded audio frames over the WLAN link, or an increase in a number of retransmission attempts of one or more Bluetooth coded audio frames over the WLAN link.

[0200] 24. A wireless device as described in any one or more of clauses 15 to 23, wherein execution of the processor readable code indicates that the new TTP value is configured to:

[0201] After detecting the change of the WLAN link, the new TTP value is embedded into at least one Bluetooth encoded audio frame sent to the peripheral device over the WLAN link.

[0202] 25. A wireless device as described in any one or more of clauses 15 to 23, wherein execution of the processor readable code indicates that the new TTP value is configured to:

[0203] suspending transmission of the audio data for a period of time in response to detecting the change in the WLAN link; and

[0204] After the time period expires, one or more additional Bluetooth coded audio frames are sent to the peripheral device via the WLAN link, at least one of the additional Bluetooth coded audio frames carrying the new TTP value.

[0205] 26. A wireless device as described in any one or more of clauses 15 to 23, wherein execution of the processor readable code indicates that the new TTP value is configured to:

[0206] A Bluetooth protocol message is transmitted to the peripheral device over the Bluetooth connection in response to the detected change of the WLAN link, the Bluetooth protocol message carrying the new TTP value for the audio data.

[0207] 27. A wireless device as described in any one or more of clauses 15 to 26, wherein the WLAN link comprises one or more wireless channels in a sub-GHz band, a 2.4 GHz band, a 5 GHz band, or a 6 GHz band.

[0208] 28. A wireless device according to any one or more of clauses 15 to 27, wherein the peripheral device includes a first earbud and a second earbud, each of the first earbud and the second earbud is associated with the soft AP, and each of the first earbud and the second earbud is paired with the soft AP via the Bluetooth connection.

[0209] 29. A wireless device, comprising:

[0210] means for operating the wireless device as a wireless station (STA) associated with a wireless local area network (WLAN) and also as a software-enabled access point (soft AP) paired with a peripheral device based on a Bluetooth protocol, the peripheral device being associated with the soft AP via a WLAN link;

[0211] means for transmitting one or more first Bluetooth encoded audio frames to the peripheral device over the WLAN link during a first target wake time (TWT) session over the WLAN link, the one or more first Bluetooth encoded audio frames indicating a current time to play (TTP) value for audio data;

[0212] means for detecting a change of said WLAN link;

[0213] means for obtaining one or more new TWT parameters and a new TTP value in response to detecting the change in the WLAN link, the new TTP value being greater than a current TTP value;

[0214] means for indicating the one or more new TWT parameters and the new TTP value to the peripheral device in conjunction with tearing down the first TWT session; and

[0215] Means for establishing a second TWT session with the peripheral device over the WLAN link based at least in part on the one or more new TWT parameters.

[0216] 30. A non-transitory computer readable storage medium storing processor readable code that, when executed by one or more processors of a wireless device, causes the wireless device to perform operations comprising:

[0217] operating the wireless device as a wireless station (STA) associated with a wireless local area network (WLAN) and also as a software-enabled access point (soft AP) paired with a peripheral device based on a Bluetooth protocol, the peripheral device being associated with the soft AP via a WLAN link;

[0218] sending one or more first Bluetooth encoded audio frames to the peripheral device over the WLAN link during a first target wake time (TWT) session over the WLAN link, the one or more first Bluetooth encoded audio frames indicating a current time to play (TTP) value for audio data;

[0219] detecting a change of the WLAN link;

[0220] obtaining one or more new TWT parameters and a new TTP value in response to detecting the change in the WLAN link, the new TTP value being greater than a current TTP value; indicating the one or more new TWT parameters and the new TTP value to the peripheral device in conjunction with tearing down the first TWT session; and

[0221] A second TWT session is established with the peripheral device over the WLAN link based at least in part on the one or more new TWT parameters.

[0222] As used herein, a phrase referring to "at least one of" or "one or more of" a list of items refers to any combination of those items, including single members. For example, "at least one of a, b, or c" is intended to cover the following possibilities: only a, only b, only c, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a, b, and c.

[0223] The various illustrative components, logical components, logical blocks, modules, circuits, operations, and algorithmic processes described in conjunction with the specific implementations disclosed herein may be implemented as electronic hardware, firmware, software, or a combination of hardware, firmware, or software, including the structures disclosed in this specification and their structural equivalents. This interchangeability of hardware, firmware, and software has been generally described in terms of functionality and is exemplified in the various illustrative components, blocks, modules, circuits, and processes described herein. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system.

[0224] Various modifications to the specific implementations described in this disclosure will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other specific implementations without departing from the spirit or scope of the disclosure. Therefore, the claims are not intended to be limited to the specific implementations shown herein, but are to be accorded the widest scope consistent with the disclosure, the principles and novel features disclosed herein.

[0225] Additionally, various features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, individual features described in the context of a single implementation may also be implemented in multiple implementations individually or in any suitable subcombination. Thus, while features may be described herein as functioning in a particular combination, and even initially claimed as such, one or more features from a claimed combination may in some cases be deleted from the combination, and the claimed combination may be directed to a subcombination or variations of the subcombination.

[0226] Similarly, although operations are depicted in a specific order in the accompanying drawings, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all illustrated operations to achieve the desired result. In addition, the accompanying drawings may schematically depict one or more example processes in the form of a flow chart or a flow diagram. However, other operations not depicted can be incorporated into the example processes schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously or between any operations in the illustrated operations. In some environments, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the specific implementation described herein should not be understood as requiring such separation in all specific implementations, and it should be understood that the described program components and systems generally can be integrated together in a single software product or encapsulated in multiple software products.

Claims

1. A method for wireless communication by a wireless device, the method comprising: operating the wireless device as a wireless station (STA) associated with a wireless local area network (WLAN) and also as a software-enabled access point (soft AP) paired with a peripheral device based on a Bluetooth protocol, the peripheral device being associated with the soft AP via a WLAN link; sending one or more first Bluetooth encoded audio frames to the peripheral device over the WLAN link during a first target wake time (TWT) session over the WLAN link, the one or more first Bluetooth encoded audio frames indicating a current time to play (TTP) value for audio data; detecting a change of the WLAN link; obtaining one or more new TWT parameters and a new TTP value in response to detecting the change in the WLAN link, the new TTP value being greater than the current TTP value; indicating the one or more new TWT parameters and the new TTP value to the peripheral device in conjunction with tearing down the first TWT session; as well as A second TWT session is established with the peripheral device over the WLAN link based at least in part on the one or more new TWT parameters.

2. The method according to claim 1, further comprising: During the second TWT session, one or more second Bluetooth coded audio frames are sent to the peripheral device via the WLAN link, and the one or more second Bluetooth coded audio frames carry the new TTP value.

3. The method of claim 2, wherein the new TTP value is based at least in part on a size of a buffer associated with buffering the one or more second Bluetooth encoded audio frames in the peripheral device.

4. The method of claim 1, wherein a time period between a first time indicated by the current TTP value and a second time indicated by the new TTP value is based at least in part on a duration associated with establishing the second TWT session. The method of claim 4 , wherein the time period is approximately 250 milliseconds.

6. The method of claim 1 , wherein indicating the new TWT parameters to the peripheral device comprises: A Bluetooth protocol message is transmitted to the peripheral device via a Bluetooth connection established between the wireless device and the peripheral device, wherein the Bluetooth protocol message carries the one or more new TWT parameters to the peripheral device.

7. The method according to claim 1, wherein the one or more new TWT parameters include at least one of a TWT wake-up duration, a TWT wake-up interval, a TWT wake-up time, a minimum data rate, an average data rate, a delay boundary, or a user priority (UP) for the TWT session.

8. The method of claim 1 , wherein obtaining the one or more new TWT parameters comprises: One or more TWT parameters associated with the first TWT session are updated based on the detected change in the WLAN link.

9. The method of claim 1 , wherein the detected change comprises one or more of: a degradation in channel conditions on the WLAN link, a decrease in a channel quality indicator (QCI) of the WLAN link, a decrease in a modulation and coding scheme (MCS) associated with sending Bluetooth coded audio frames over the WLAN link, an increase in a packet error rate (PER) associated with the WLAN link, an increase in a latency associated with sending the Bluetooth coded audio frames over the WLAN link, or an increase in a number of retransmission attempts of one or more Bluetooth coded audio frames over the WLAN link.

10. The method of claim 1, wherein indicating the new TTP value to the peripheral device comprises: After detecting the change of the WLAN link, the new TTP value is embedded into at least one Bluetooth encoded audio frame sent to the peripheral device over the WLAN link.

11. The method of claim 1 , wherein indicating the new TTP value to the peripheral device comprises: suspending transmission of the audio data for a certain period of time in response to detecting the change in the WLAN link; as well as After the time period expires, one or more additional Bluetooth coded audio frames are sent to the peripheral device via the WLAN link, at least one of the additional Bluetooth coded audio frames carrying the new TTP value.

12. The method of claim 1 , wherein indicating the new TTP value to the peripheral device comprises: A Bluetooth protocol message is transmitted to the peripheral device over the Bluetooth connection in response to the detected change of the WLAN link, the Bluetooth protocol message carrying the new TTP value for the audio data.

13. The method of claim 1, wherein the WLAN link comprises one or more wireless channels in a sub-GHz band, a 2.4 GHz band, a 5 GHz band, or a 6 GHz band.

14. The method of claim 1, wherein the peripheral device comprises a first earbud and a second earbud, each of the first earbud and the second earbud being associated with the soft AP, and each of the first earbud and the second earbud being paired with the soft AP via a Bluetooth connection.

15. A wireless device, comprising: one or more processors; and a memory coupled to the one or more processors and storing processor-readable code that, when executed by the one or more processors, is configured to: operating the wireless device as a wireless station (STA) associated with a wireless local area network (WLAN) and also as a software-enabled access point (soft AP) paired with a peripheral device based on a Bluetooth protocol, the peripheral device being associated with the soft AP via a WLAN link; sending one or more first Bluetooth encoded audio frames to the peripheral device over the WLAN link during a first target wake time (TWT) session over the WLAN link, the one or more first Bluetooth encoded audio frames indicating a current time to play (TTP) value for audio data; detecting a change of the WLAN link; obtaining one or more new TWT parameters and a new TTP value in response to detecting the change in the WLAN link, the new TTP value being greater than the current TTP value; indicating the one or more new TWT parameters and the new TTP value to the peripheral device in conjunction with tearing down the first TWT session; as well as A second TWT session is established with the peripheral device over the WLAN link based at least in part on the one or more new TWT parameters.

16. The wireless device of claim 15, wherein execution of the processor readable code is further configured to: During the second TWT session, one or more second Bluetooth coded audio frames are sent to the peripheral device via the WLAN link, and the one or more second Bluetooth coded audio frames carry the new TTP value.

17. The wireless device of claim 16, wherein the new TTP value is based at least in part on a size of a buffer associated with buffering the one or more second Bluetooth encoded audio frames in the peripheral device.

18. A wireless device according to claim 15, wherein a time period between a first time indicated by the current TTP value and a second time indicated by the new TTP value is based at least in part on a duration associated with establishing the second TWT session.

19. The wireless device of claim 18, wherein the time period is approximately 250 milliseconds.

20. The wireless device of claim 15, wherein the processor readable code is executed to indicate that the new TWT parameters are configured as: A Bluetooth protocol message is transmitted to the peripheral device via a Bluetooth connection established between the wireless device and the peripheral device, wherein the Bluetooth protocol message carries the one or more new TWT parameters to the peripheral device.

21. A wireless device according to claim 15, wherein the one or more new TWT parameters include at least one of a TWT wake-up duration, a TWT wake-up interval, a TWT wake-up time, a minimum data rate, an average data rate, a delay boundary, or a user priority (UP) for the TWT session.

22. The wireless device of claim 15, wherein executing the processor readable code to obtain the one or more new TWT parameters is configured to: One or more TWT parameters associated with the first TWT session are updated based on the detected change in the WLAN link.

23. The wireless device of claim 15, wherein the detected change comprises one or more of: a degradation in channel conditions on the WLAN link, a decrease in a channel quality indicator (QCI) of the WLAN link, a decrease in a modulation and coding scheme (MCS) associated with sending Bluetooth coded audio frames over the WLAN link, an increase in a packet error rate (PER) associated with the WLAN link, an increase in a latency associated with sending the Bluetooth coded audio frames over the WLAN link, or an increase in a number of retransmission attempts of one or more Bluetooth coded audio frames over the WLAN link.

24. The wireless device of claim 15, wherein the processor readable code is executed to indicate that the new TTP value is configured as: After detecting the change of the WLAN link, the new TTP value is embedded into at least one Bluetooth encoded audio frame sent to the peripheral device over the WLAN link.

25. The wireless device of claim 15, wherein the processor readable code is executed to indicate that the new TTP value is configured as: suspending transmission of the audio data for a period of time in response to detecting the change in the WLAN link; and After the time period expires, one or more additional Bluetooth coded audio frames are sent to the peripheral device via the WLAN link, at least one of the additional Bluetooth coded audio frames carrying the new TTP value.

26. The wireless device of claim 15, wherein the processor readable code is executed to indicate that the new TTP value is configured as: A Bluetooth protocol message is transmitted to the peripheral device over the Bluetooth connection in response to the detected change of the WLAN link, the Bluetooth protocol message carrying the new TTP value for the audio data.

27. The wireless device of claim 15, wherein the WLAN link comprises one or more wireless channels in a sub-GHz band, a 2.4 GHz band, a 5 GHz band, or a 6 GHz band.

28. The wireless device of claim 15, wherein the peripheral device comprises a first earbud and a second earbud, each of the first earbud and the second earbud being associated with the soft AP, and each of the first earbud and the second earbud being paired with the soft AP via a Bluetooth connection.

29. A wireless device, comprising: means for operating the wireless device as a wireless station (STA) associated with a wireless local area network (WLAN) and also as a software-enabled access point (soft AP) paired with a peripheral device based on a Bluetooth protocol, the peripheral device being associated with the soft AP via a WLAN link; means for transmitting one or more first Bluetooth encoded audio frames to the peripheral device over the WLAN link during a first target wake time (TWT) session over the WLAN link, the one or more first Bluetooth encoded audio frames indicating a current time to play (TTP) value for audio data; means for detecting a change of said WLAN link; means for obtaining one or more new TWT parameters and a new TTP value in response to detecting the change in the WLAN link, the new TTP value being greater than the current TTP value; means for indicating to the peripheral device the one or more new TWT parameters and the new TTP value in conjunction with tearing down the first TWT session; as well as Means for establishing a second TWT session with the peripheral device over the WLAN link based at least in part on the one or more new TWT parameters.

30. A non-transitory computer readable storage medium storing processor readable code that, when executed by one or more processors of a wireless device, causes the wireless device to perform operations comprising: operating the wireless device as a wireless station (STA) associated with a wireless local area network (WLAN) and also as a software-enabled access point (soft AP) paired with a peripheral device based on a Bluetooth protocol, the peripheral device being associated with the soft AP via a WLAN link; sending one or more first Bluetooth encoded audio frames to the peripheral device over the WLAN link during a first target wake time (TWT) session over the WLAN link, the one or more first Bluetooth encoded audio frames indicating a current time to play (TTP) value for audio data; detecting a change of the WLAN link; obtaining one or more new TWT parameters and a new TTP value in response to detecting the change in the WLAN link, the new TTP value being greater than the current TTP value; indicating the one or more new TWT parameters and the new TTP value to the peripheral device in conjunction with tearing down the first TWT session; as well as A second TWT session is established with the peripheral device over the WLAN link based at least in part on the one or more new TWT parameters.