Low power packet scheduling

Abstract

Various aspects of this disclosure relate generally to wireless communication. In some aspects, the wireless device can receive data packets on an isochronous (ISO) link. The wireless device can transmit low-power (LE) packets with feedback of the data packets. Numerous other aspects are described.

Description

Cross-references to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 510,279, filed November 15, 2023, entitled “LOW ENERGY PACKETSCHEDULING,” which is assigned to the assignee of this patent application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0002] All aspects of this disclosure relate to wireless communication and techniques and apparatus associated with low-power packets transmitted and received by peripheral devices. Background Technology

[0003] 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. For example, based on communication protocols such as Bluetooth... ® (BT) protocol, Bluetooth Low Energy protocol or Zigbee ® WPAN (Wireless PAN Protocol) provides wireless connectivity to peripheral devices within a specific distance (e.g., 5 meters, 10 meters, 20 meters, 100 meters) from each other. Bluetooth is a short-range wireless communication protocol that supports WPAN between a central device (such as a host device or source device) and at least one peripheral device (such as a client device or destination device). However, the power consumption associated with Bluetooth communication, which operates at the Basic Rate (BR) and / or Enhanced Data Rate (EDR) physical layers, may make WPAN communication impractical in some applications.

[0004] Therefore, to address the power consumption challenges associated with Bluetooth BR / EDR (sometimes referred to as Bluetooth Classic or Bluetooth Legacy), Bluetooth Low Energy (BLE) (also referred to herein as WPAN LE) was developed and is used in a variety of applications where data transmission is relatively infrequent and / or to implement WPAN communication with low power consumption. For example, BLE saves power by utilizing infrequent data transmissions through low duty cycle operation and by putting one or both of the central device and peripheral devices into sleep mode between data transmissions. Example applications using BLE include battery-powered sensors and actuators in a variety of medical, industrial, consumer, and fitness applications. BLE can also be used for connecting devices such as BLE-enabled smartphones, tablets, laptops, earphones, etc. While legacy Bluetooth and BLE offer certain advantages, there is a need for further improvements to Bluetooth and BLE technologies. For example, legacy Bluetooth and BLE have limited range, limited data throughput, and are susceptible to interference from other devices communicating in the same frequency band, such as via wireless local area networks (WLANs). Summary of the Invention

[0005] Some aspects described herein relate to a method for performing wireless communication by a wireless device. The method may include receiving data packets on an isochronous (ISO) link. The method may also include transmitting low-power (LE) packets with feedback of the data packets.

[0006] Some aspects described herein relate to a method for performing wireless communication by a wireless device. The method may include transmitting a first set of ISO data packets on an ISO link. The method may include receiving a second set of ISO data packets on the ISO link. The method may include receiving a first set of feedback packets from the first set of ISO data packets. The method may include transmitting a second set of feedback packets from the second set of ISO data packets. The method may include transmitting the LE packet earlier than a pre-scheduled LE event for transmitting the LE packet.

[0007] Some aspects described herein relate to an apparatus for wireless communication at a wireless device. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to enable the wireless device to receive data packets on an ISO link. The one or more processors may be configured individually or collectively to enable the wireless device to transmit LE packets with feedback of the data packets.

[0008] Some aspects described herein relate to an apparatus for wireless communication at a wireless device. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to cause the wireless device to transmit a first set of ISO data packets on an ISO link. The one or more processors may be individually or collectively configured to cause the wireless device to receive a second set of ISO data packets on the ISO link. The one or more processors may be configured to receive a first set of feedback packets from the first set of ISO data packets. The one or more processors may be individually or collectively configured to cause the wireless device to transmit a second set of feedback packets from the second set of ISO data packets. The one or more processors may be individually or collectively configured to cause the wireless device to transmit the LE packet earlier than a pre-scheduled LE event for transmitting the LE packet.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a wireless device. When executed by one or more processors of the wireless device, the set of instructions enables the wireless device to receive data packets on an ISO link. When executed by one or more processors of the wireless device, the set of instructions also enables the wireless device to transmit LE packets with feedback of the data packets.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a wireless device. When executed by one or more processors of the wireless device, the set of instructions enables the wireless device to transmit a first set of ISO data packets on an ISO link. When executed by one or more processors of the wireless device, the set of instructions enables the wireless device to receive a second set of ISO data packets on the ISO link. When executed by one or more processors of the wireless device, the set of instructions enables the wireless device to receive a first set of feedback packets of the first set of ISO data packets. When executed by one or more processors of the wireless device, the set of instructions enables the wireless device to transmit a second set of feedback packets of the second set of ISO data packets. When executed by one or more processors of the wireless device, the set of instructions enables the wireless device to transmit an LE packet earlier than a pre-scheduled LE event for transmitting an LE packet.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving data packets on an ISO link. The apparatus may also include components for transmitting LE packets with feedback of the data packets.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting a first set of ISO data packets on an ISO link. The apparatus may include components for receiving a second set of ISO data packets on the ISO link. The apparatus may include components for receiving a first set of feedback packets of the first set of ISO data packets. The apparatus may include components for transmitting a second set of feedback packets of the second set of ISO data packets. The apparatus may include components for transmitting an LE packet earlier than a pre-scheduled LE event for transmitting LE packets.

[0013] The aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, central equipment, peripheral equipment, wireless communication equipment, access points, mobile stations, and / or processing systems as generally described herein with reference to the accompanying drawings and description.

[0014] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings provided is for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0015] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of various sizes, shapes, and configurations. Attached Figure Description

[0016] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the invention, briefly outlined above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as other equally valid aspects are permissible in this description. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 This is a diagram illustrating an example of a Wireless Personal Area Network (WPAN) according to the present disclosure.

[0018] Figure 2 This is a diagram illustrating an example of a wireless communication device according to the present disclosure.

[0019] Figure 3 This is a diagram illustrating an example of a protocol stack according to this disclosure.

[0020] Figure 4 This is an illustration of an example of data packets being transmitted from a wireless communication device to a peripheral device via a WPAN connection according to this disclosure.

[0021] Figure 5 This is a diagram illustrating an example of a wireless communication device according to the present disclosure.

[0022] Figure 6This is a diagram illustrating an example of using an isochronous (ISO) link according to this disclosure.

[0023] Figure 7 This is a diagram illustrating an example of using an ISO link according to this disclosure.

[0024] Figure 8 This is a diagram illustrating an example of an interleaved ISO link according to this disclosure.

[0025] Figure 9 This is a diagram illustrating an example of using an ISO link according to this disclosure.

[0026] Figure 10 This is a diagram illustrating an example of using an ISO link according to this disclosure.

[0027] Figure 11 This is a diagram illustrating an example process performed, for example, at a wireless device or a device of a wireless device, according to this disclosure.

[0028] Figure 12 This is a diagram illustrating an example process performed, for example, at a wireless device or a device of a wireless device, according to this disclosure.

[0029] Figure 13 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0030] In a Wireless Personal Area Network (WPAN) (such as a Bluetooth (BT) network or a Bluetooth Low Energy (BLE) network), wireless audio or video can be streamed from a central device (e.g., a mobile phone, smartphone, game console) to one or more peripheral devices (e.g., a left earbud, a right earbud, an extended reality (XR) headset, XR glasses, wearable devices, portable speakers). The central device can stream audio or video to the peripheral devices over a Low Energy (LE) Isochronous (ISO) link (e.g., a connected ISO (CIS) link). For example, the central device can send ISO data (e.g., audio data, video data) in ISO data packets over an ISO link. The peripheral devices can also send ISO data (e.g., controller input) in ISO data packets to the central device. The central device and the peripheral devices can send feedback (e.g., ISO acknowledgment (ACK)) for the ISO data packets.

[0031] LE packets may include sensor data from peripheral devices or control information from a central device. Peripheral devices may collect sensor data (e.g., orientation data, proximity data) and transmit this sensor data (e.g., LE data) along with any other LE data in the LE packet to the central device. The central device may transmit LE control information (e.g., LE control) from the LE packet to the peripheral devices. LE packets may be pre-scheduled for transmission during LE events. Anchor points may mark the start of an LE event.

[0032] In use cases such as spatial audio or XR, LE packets are expected to be delivered on time for optimal user experience. Sensor data on earbuds, XR headsets, or XR glasses can be sampled at high speeds to create accurate output for the user with low latency. Therefore, applications may request aggressive LE parameters over ISO links. For example, there might be a 20 ms LE interval for delivering sensor data from peripherals or control messages from a central device, and a 7.5 ms or 10 ms ISO interval for ISO data. These interval times present several problems. The central device may not have enough continuous time for WiFi activity from both the central device and / or peripherals. When multiple links are involved, switching back and forth between WiFi and other signaling can lead to scheduling problems, as this can fragment WiFi usage time and / or bandwidth. Latency may increase due to bandwidth fragmentation or insufficiency, and signaling resources may not be used efficiently. Furthermore, in addition to streaming media and sensor exchange, there may not be enough bandwidth for other operations, such as proximity applications that continuously announce the status of peripherals, connecting to another computer, or earbud scanning. Peripherals may not be able to easily schedule multiple links to support multi-point use cases.

[0033] According to the various aspects described herein, a device may transmit LE packets (within one or more LE sub-events of an LE interval) earlier than a pre-scheduled LE event, such as by utilizing feedback for ISO data packets in an ISO sub-event. For example, LE data or control information may be carried on an ISO ACK in an ISO sub-event. In some aspects, the transmitting device may send an indication that the LE packet will be transmitted in an ISO sub-event earlier than a pre-scheduled LE event. In some aspects, the transmitting device may transmit the LE packet once all ISO data and feedback have been exchanged, which may be in the next ISO sub-event. Transmitting LE packets in an earlier ISO event rather than a later pre-scheduled LE event can result in lower bandwidth requirements and a higher probability of obtaining a larger time window of ISO or LE inactivity that can be used for applications on other signaling (e.g., WiFi, other links) or central devices.

[0034] The detailed description below, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as representing the only configuration in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts can 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.

[0035] Various apparatuses and methods will now be used to present several aspects of a telecommunications system. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “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 system as a whole.

[0036] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including 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, system-on-a-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 the various functionalities described throughout this disclosure. One or more processors in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0037] Therefore, in one or more example embodiments, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium accessible by a computer. By way of example, and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the foregoing types, or any other medium capable of storing computer-executable code having instructions or data structures accessible by a computer.

[0038] Figure 1 This is an illustration of an example of a WPAN 100 according to some specific implementations. Within the WPAN 100, a central device 102 (which may be referred to herein as a source device or other suitable terminology) can connect to one or more peripheral devices (such as a smartwatch 104, a Bluetooth portable speaker 106, a wireless headset 108, a head-mounted device (HMD), or an XR reality headset 110, a wireless earbud 112, and / or a wireless game controller 114) (which may be referred to herein as a destination device or other suitable terminology) using the BLE protocol or a modified BLE protocol and can establish a communication link 116 with the one or more peripheral devices. The BLE protocol is part of the BT core specification and enables radio frequency communication operating within the globally accepted 2.4 GHz Industrial, Scientific, and Medical (ISM) band.

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

[0040] In some respects, after establishing a requested LL connection, the central device 102 can become a host device, and selected or anticipated peripheral devices 104, 106, 108, 110, 112, and / or 114 can be paired with the central device 102 through the established LL connection. As a host device, the central device 102 can support multiple concurrent LL connections with various peripheral devices 104, 106, 108, 110, 112, and / or 114 operating as client devices. For example, the central device 102 can manage various aspects of data packet communication in LL connections with one or more associated peripheral devices 104, 106, 108, 110, 112, and / or 114. For example, the central device 102 can determine the operation scheduling in LL connections with one or more peripheral devices 104, 106, 108, 110, 112, and / or 114. The central device 102 can also initiate LL Protocol Data Unit (PDU) exchange sequences through the LL connection. The LL connection can be configured to operate periodic connection events in a dedicated data channel. LL data PDU transmissions between the central device 102 and one or more peripheral devices 104, 106, 108, 110, 112, and / or 114 can occur within the connection event.

[0041] In some aspects, the central device 102 may be configured to send a first LL data PDU to the intended peripheral devices 104, 106, 108, 110, 112, and / or 114 in each connection event. Additionally or alternatively, in some aspects, the central device 102 may use a polling scheme to poll the intended peripheral devices 104, 106, 108, 110, 112, and / or 114 for LL data PDU transmission during a connection event. The intended peripheral devices 104, 106, 108, 110, 112, and / or 114 may send the LL data PDU upon receiving a packet carrying the LL data PDU from the central device 102. In some other aspects, the peripheral devices 104, 106, 108, 110, 112, and / or 114 may send the LL data PDU to the central device 102 without first receiving the LL data PDU from the central device 102.

[0042] Examples of central device 102 may include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, mobile stations (STA), laptops, personal computers (PCs), desktop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players, cameras, game consoles, tablets, smart devices, wearable devices (such as smartwatches or wireless headphones), vehicles, vehicle infotainment systems or in-vehicle kits, electricity meters, gas pumps, ovens, thermostats, hearing aids, wearable blood glucose units, Internet of Things (IoT) devices, etc.

[0043] Examples of one or more peripheral devices 104, 106, 108, 110, 112, and / or 114 may include cellular phones, smartphones, SIP phones, STAs, laptops, PCs, desktop computers, PDAs, satellite radios, GPS devices, multimedia devices, video devices, digital audio players, cameras, game consoles, tablets, smart devices, wearable devices (e.g., smartwatches, wireless headphones, or wireless in-ear headphones), vehicles, vehicle infotainment systems or in-vehicle kits, electric meters, gas pumps, ovens, thermostats, hearing aids, wearable blood glucose meters, IoT devices, etc. While central device 102 is in Figure 1 The central device 102 is exemplified as communicating with six peripheral devices 104, 106, 108, 110, 112 and 114 in WPAN 100, and the central device 102 may communicate with more or fewer than six peripheral devices in WPAN 100 without departing from the scope of this disclosure.

[0044] In some aspects, a device implementing the BT protocol (e.g., central device 102) may operate according to a first radio mode (e.g., a Basic Rate (BR) / Enhanced Data Rate (EDR) radio mode), and a device implementing the BLE protocol may operate according to a second radio mode (e.g., a BLE radio mode). In some aspects, central device 102 may be configured to utilize dual radio modes, and thus may be able to operate according to either the BR / EDR mode or the BLE mode, for example, based on the type of short-range wireless communication that central device 102 may participate in.

[0045] For example, in some aspects, the central device 102 may operate according to BR / EDR mode for continuous data streaming, for broadcast networks, for mesh networks, and / or for some other applications where relatively higher data rates may be more suitable. Additionally or alternatively, the central device 102 may operate according to BLE mode for short burst data transmissions (such as for some other applications where power savings and / or relatively lower data rates may be acceptable). Additionally or alternatively, in some aspects, the central device 102 may operate according to one or more other radio modes, such as proprietary radio modes. Examples of other radio modes may include high-speed radio modes, low-power radio modes, and / or isochronous radio modes, etc.

[0046] In some respects, as described in more detail elsewhere herein, the auxiliary wireless device (e.g., among peripheral devices 104, 106, 108, 110, 112, and 114) can track a first retransmission metric based on the number of retransmitted packets received by the auxiliary wireless device from a source device (such as central device 102). The auxiliary wireless device can receive an acknowledgment assistance request from the destination wireless device (e.g., among peripheral devices 104, 106, 108, 110, 112, and 114) indicating a second retransmission metric for the destination wireless device. The auxiliary wireless device can send a response to the acknowledgment assistance request to the destination wireless device based on the corresponding values ​​of the first and second retransmission metrics. Additionally or alternatively, the auxiliary wireless device can perform one or more other operations described herein.

[0047] In some respects, as described in more detail elsewhere herein, the destination wireless device (e.g., among peripheral devices 104, 106, 108, 110, 112, and 114) may track a first retransmission metric based on the number of retransmitted packets received by the destination wireless device from a source device (such as central device 102). The destination wireless device may send an acknowledgment assistance request to an auxiliary wireless device (e.g., among peripheral devices 104, 106, 108, 110, 112, and 114) indicating the first retransmission metric tracked by the destination wireless device. The destination wireless device may receive a response to the acknowledgment assistance request from the auxiliary wireless device based on corresponding values ​​of the first retransmission metric tracked by the destination wireless device and a second retransmission metric tracked by the auxiliary wireless device. Additionally or alternatively, the destination wireless device may perform one or more other operations described herein.

[0048] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0049] Figure 2 This is a diagram illustrating an example of a wireless communication device 200 according to the present disclosure. In some aspects, the wireless communication device 200 may be... Figure 1 The example shown is a central device 102. Additionally or alternatively, the wireless communication device 200 may be... Figure 1 Examples of one or more of the peripheral devices 104, 106, 108, 110, 112, or 114 illustrated herein. In some aspects, the wireless communication device 200 may be a Bluetooth-enabled device (such as a BLE device).

[0050] like Figure 2As shown, the wireless communication device 200 may include processing elements, such as a processor 202 capable of executing program instructions for the wireless communication device 200. The wireless communication device 200 may also include a display 242 capable of performing graphics processing and presenting information to a user. 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 locations in memory (such as memory 206, ROM 208, or flash memory 210) and / or address locations in other circuitry or devices (such as display circuitry 204, radio components 230, connector interface 220, and / or 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.

[0051] Processor 202 may be coupled to other circuitry of wireless communication device 200. For example, wireless communication device 200 may include various memory types, a connector interface 220 through which wireless communication device 200 can communicate with a computer system, and a wireless communication subsystem capable of sending data to and receiving data 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 wireless local area network (WLAN) subsystem, a WPAN subsystem, and / or a cellular subsystem (such as a Long Term Evolution (LTE) or New Radio (NR) subsystem). Wireless communication device 200 may include multiple antennas 235a, 235b, 235c, and / or 235d for performing wireless communication with wireless communication devices, such as those in a WPAN. In some aspects, the WPAN may be an extended PAN (XPAN).

[0052] Wireless communication device 200 may be configured to implement some 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 operation. In other embodiments, the techniques described herein may be implemented at least in part by programmable hardware elements (such as FPGAs and / or application-specific integrated circuits (ASICs)).

[0053] In some aspects, radio component 230 may include a separate controller configured to control communications for various corresponding radio access technology (RAT) protocols. For example, such as Figure 2As shown, the radio component 230 may include a WLAN controller 250 for managing WLAN communications, a WPAN controller 252 for managing Bluetooth, BLE, and / or other suitable WPAN communications, and a WWAN controller 256 for managing wide area network (WWAN) communications. In some aspects, the wireless communication device 200 may store and execute WLAN software drivers for controlling WLAN operations performed by the WLAN controller 250, WPAN software drivers for controlling WPAN operations performed by the WPAN controller 252, and / or WWAN software drivers for controlling WWAN operations performed by the WWAN controller 256.

[0054] In some aspects, a first coexistence interface 254 (such as a wired interface) may be used to transmit information between the WLAN controller 250 and the WPAN controller 252. Additionally or alternatively, in some aspects, a second coexistence interface 258 may be used to transmit information between the WLAN controller 250 and the WWAN controller 256. Additionally or alternatively, in some aspects, a third coexistence interface 260 may be used to transmit information between the WPAN controller 252 and the WWAN controller 256.

[0055] In some respects, one or more of the WLAN controller 250, WPAN controller 252 and / or WWAN controller 256 may be implemented as hardware, software, firmware or any suitable combination thereof.

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

[0057] Short-range wireless communication protocols (such as BT, BLE, and / or BR / EDR) may include and / or use one or more other communication protocols, for example, to establish and maintain communication links. See also: Figure 1Wireless communication device 200 can establish a communication link 116 with one or more peripheral devices, such as wireless headset 112, according to at least one communication protocol for short-range wireless communication. In some aspects, communication link 116 may include a communication link conforming to protocols included and / or used together, such as BT, BLE, BR / EDR, etc. In one aspect, communication link 116 may include asynchronous connection-oriented logic (ACL) transmission, sometimes referred to as an ACL link. When operating as an ACL link, communication link 116 may allow central device 102 (e.g., a source device) to connect or "pair" with peripheral devices such as headset 112. This connection is asynchronous because the two devices may not need to synchronize their data communication with each other in time to allow data packet communication via communication link 116.

[0058] In some aspects, the Logical Link Control and Adaptation Protocol (L2CAP) can be implemented in the BT protocol stack (for simplicity, see below). Figure 2 (Not shown in the image) is used within the context of an L2CAP connection. An L2CAP connection can be established after an ACL link has been established. References to L2CAP in this disclosure can be further applied to Enhanced L2CAP (EL2CAP), which may be an enhanced version of the L2CAP protocol that allows multiple logical data channels to be multiplexed over a single radio connection.

[0059] In some aspects, communication link 116 may include an Advanced Audio Distribution Profile (A2DP) link. For example, an A2DP link may provide a point-to-point link between a source device (such as central device 102) and a destination device (such as headset 112). Using an A2DP link, data packets, including audio, may be transmitted on an ACL channel, and other information (e.g., for controlling the audio stream) may be transmitted on a separate control channel. Data packets may occur non-periodically.

[0060] In some aspects, communication link 116 may support synchronous logical transmission mechanisms between source devices (such as central device 102) and peripheral devices (such as headset 112). For example, communication link 116 may include a Synchronous Connection-Oriented (SCO) link, which uses time slots reserved for BT communication to provide a symmetrical point-to-point link between the source device and the peripheral device. In some aspects, the SCO link may not support retransmission of data packets, which may be unsatisfactory in audio streaming and / or voice call use cases where dropped audio or voice packets can degrade the user experience quality.

[0061] In some aspects, communication link 116 may include an extended SCO (eSCO) link. The eSCO link can provide a symmetric or asymmetric point-to-point link between the source device and peripheral devices using time slots reserved for BT communication, and can also provide a retransmission window after the reserved time slots. Because a retransmission window can be used to facilitate retransmission, the eSCO link is suitable for audio streaming and / or voice call use cases, as dropped audio or voice packets can be retransmitted, thus increasing the probability of successfully receiving data packets.

[0062] In some respects, Figure 1 The communication link 116 shown may include an ISO link. When operating as an ISO link, communication link 116 may combine some features of both synchronous and asynchronous links. For example, a stream on an ISO link may begin with a start packet, and then data packets may be sent asynchronously. On an ISO link, the number of retransmission attempts by the transmitting device can be limited. Therefore, if the receiving device cannot decode a data packet within a limited number of retransmission attempts, the data packet may be discarded, and the receiving device may continue receiving the stream without any data from the discarded data packet.

[0063] In some aspects, the wireless device includes components for receiving data packets on an ISO link; and / or components for transmitting LE packets with feedback of the data packets. In some aspects, components for the first peripheral device to perform the operations described herein may include, in particular, one or more of, for example, a WPAN controller 252, a memory 206, an antenna 235, a processor 202, and / or an MMU 240.

[0064] In some aspects, the wireless device includes components for transmitting a first set of ISO data packets on an ISO link; components for receiving a second set of ISO data packets on the ISO link; components for receiving a first set of feedback packets of the first set of ISO data packets; components for transmitting a second set of feedback packets of the second set of ISO data packets; and / or components for transmitting the LE packet earlier than a pre-scheduled LE event for transmitting the LE packet.

[0065] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0066] Figure 3 This is a diagram illustrating example 300 of a protocol stack (e.g., WPAN and / or Bluetooth protocol stack) according to this disclosure. In some aspects, protocol stack 300 can be used in wireless communication devices (such as...) Figure 1This can be implemented in one or more of the central device 102 or peripheral devices 104, 106, 108, 110, 112, or 114. For example, the protocol stack 300 can be implemented by... Figure 2 It may be implemented using one or more of the processor 202, memory 206, flash memory 210, ROM 208, radio component 230, and / or WPAN controller 252 illustrated herein. In some aspects, the protocol stack 300 may be organized into three layers, including an application layer 310, a host layer 320, and a controller layer 330.

[0067] In some aspects, application layer 310 may be a user application layer that interfaces with other blocks and / or layers of protocol stack 300. In some aspects, application layer 310 may include one or more applications 312 and one or more Bluetooth profiles 314 that allow one or more applications 312 to use Bluetooth and / or BLE communication. Host layer 320 may include upper layers of protocol stack 300 and may use host controller interface (HCI) 340 to communicate with controllers in wireless communication devices (such as…). Figure 2 The host layer 320 may communicate with the WPAN controller 252. In some aspects, the host layer 320 may include a host stack 321, which may be used for application layer interface management to allow application 312 to access WPAN communication.

[0068] The controller layer 330 may include lower layers of the protocol stack 300. In some aspects, the controller layer 330 can be used for hardware interface management, link establishment, and link management. Figure 3 As shown, the controller layer 330 may include a link manager (LM) 332, a link layer 334, and a physical (PHY) layer 336. The PHY layer 336 may include, for example, radio components and / or a baseband processor. In some aspects, the PHY layer 336 may define mechanisms for transmitting bit streams via physical links or channels connecting WPAN devices. The bit stream may be encoded into codewords or symbols and may be converted into data packets for transmission over a wireless transmission medium. The PHY layer 336 may provide electrical, mechanical, and / or procedural interfaces to the wireless transmission medium. The PHY layer 336 may be responsible for modulating data into radio frequency (RF) signals for over-the-air transmission and demodulating data. The PHY layer 336 may describe the physical characteristics of transmitters / receivers (or transceivers) included in wireless communication devices. Physical characteristics may include modulation characteristics, RF tolerance, and / or sensitivity levels, etc.

[0069] In some aspects, link layer 334 is responsible for low-level communication on top of PHY layer 336. Link layer 334 manages the sequencing and timing of data packets for sending and receiving, and uses the LL protocol to communicate with other devices regarding connection parameters and data flow control. Link layer 334 also provides gatekeeping functionality for limiting exposure and data exchange with other devices. If filtering is configured, link layer 334 maintains a list of allowed devices and can ignore all requests for data exchange from devices not on the allowed list. Link layer 334 also reduces power consumption. In some aspects, link layer 334 may include proprietary LLs that can be used to discover peer devices and establish secure communication channels with them. In some aspects, link layer 334 may be responsible for transmitting data packets between devices in a WPAN. Each data packet may include an access address that specifies the type of logical transport used to carry the data packet. Logical transports can exist between master and slave devices. Additionally, some logical transports may carry multiple logical links.

[0070] The link manager 332 is responsible for establishing and configuring links, as well as managing power change requests and other tasks. Each type of logical link (such as ACL links, A2DP links, SCO links, eSCO links, ISO links, etc.) can be associated with a specific packet type. For example, an SCO link can provide reserved channel bandwidth for communication between a central device and a peripheral device and can support periodic exchange of data packets without retransmissions. An eSCO link can provide reserved channel bandwidth for communication between a source device and a peripheral device and can support periodic exchange of data packets with retransmissions. An ACL link can exist between a source device and a peripheral device from the beginning of establishing a connection, and the data packets of an ACL link can include encoded information in addition to the payload.

[0071] Link Manager 332 can communicate with Host Layer 320 using HCI 340. In some respects, Link Manager 332 can translate commands associated with HCI 340 into controller-level operations, such as baseband-level operations. HCI 340 can act as a boundary between lower layers, such as between Controller Layer 330, Host Layer 320, and Application Layer 310. The BT specification can define a standard HCI to support BT systems implemented across two independent processors. For example, a BT system on a computer can use the processor of the BT system to implement the lower layers of Protocol Stack 300 (such as PHY Layer 336, Link Layer 334, and / or Link Manager 332), and can use the processor of the BT components to implement other layers of Protocol Stack 300 (such as Host Layer 320 and Application Layer 310).

[0072] exist Figure 3In this diagram, host layer 320 is shown as including a Generic Access Profile (GAP) 322, a Generic Attribute Protocol (GATT) 324, a Security Manager (SM) 326, an Attribute Protocol (ATT) 328, and an L2CAP layer 329. GAP 322 provides an interface for application 312 to initiate, establish, and manage connections with other WPAN (e.g., BT or BLE) devices. GATT 324 provides a service framework for using the Attribute Protocol to discover services and to read and write attribute values ​​on peer devices. GATT 324 can interface with application 312, for example, through a profile that can define sets of attributes and any permitted attributes required for use in BT or BLE communication.

[0073] Security Manager 326 is responsible for device pairing and key distribution. The Security Manager protocol implemented by Security Manager 326 defines how communication with the corresponding BLE device's Security Manager is performed. Security Manager 326 provides additional cryptographic functions that can be used by other components of the protocol stack 300. The architecture of Security Manager 326 used in WPAN communication is designed to minimize recourse requirements to peripheral devices by offloading work to a potentially more robust central device. BLE uses a pairing mechanism for key distribution. Security Manager 326 provides mechanisms for encrypting data and for providing data authentication.

[0074] The ATT 328 includes a client / server protocol based on attributes associated with BLE devices configured for a specific purpose. Examples may include monitoring heart rate, temperature, broadcasting announcements, etc. Attributes can be discovered, read, and written by peer devices. The set of operations performed on the ATT 328 may include error handling, server configuration, finding information, read operations, write operations, and / or queuing writes. The ATT 328 can form the basis for data exchange between BT devices and BLE devices.

[0075] L2CAP layer 329 can be implemented above HCI 340 and can communicate with controller layer 330 via HCI 340. L2CAP layer 329 can be responsible for establishing connections across one or more existing logical links and for requesting additional links (if none exist). L2CAP layer 329 can also enable multiplexing between different higher-layer protocols, for example to allow different applications to use a single link, such as a logical link, including ACL links. In some implementations, L2CAP layer 329 can encapsulate multiple protocols from the upper layers into a data packet format (and vice versa). L2CAP layer 329 can also decompose packets from the upper layers with large data payloads into multiple packets with data payloads segmented into smaller data payloads that fit the maximum payload size on the sending side (e.g., twenty-seven (27) bytes).

[0076] In some standards and protocols such as BLE and / or BR / EDR, the central device 102 can detect errors and / or dropped / missing / unreceived packets by using Cyclic Redundancy Check (CRC) verification and by using Message Integrity Code (MIC) verification. MIC verification can be used when packets are encrypted. For example, a CRC verification failure can indicate one or more errors in a received packet, and a MIC verification failure can indicate that another packet has not yet been received (but a CRC verification failure can also indicate that another packet has not yet been received, and / or a MIC verification failure can also indicate one or more errors in a received packet).

[0077] CRC verification and MIC verification can be based on: generating CRC values ​​and MICs respectively based on the received packets, and comparing these generated CRC values ​​and MICs respectively with the CRC values ​​and MICs included in the received packets. Specifically, a receiving device such as headset 112 that receives packets can first generate a CRC value or CRC checksum based on the received packets (such as based on the payload and (if applicable) MIC included in the received packets). The receiving device can compare the generated CRC value with the CRC value included in the received packets. If the generated CRC value matches the CRC value included in the received packets, the received packets can be verified against the CRC. The CRC-verified received packets can then be decrypted. However, if the generated CRC value does not match the CRC value included in the received packets, the receiving device can determine that the received packets failed CRC verification. If the receiving device determines that the received packets failed CRC verification, the received packets may contain errors and / or may be corrupted. In one configuration, the receiving device can discard received packets that failed CRC verification. Alternatively, in another configuration, the receiving device may attempt to recover the received packets, for example, using one or more error correction techniques.

[0078] If the received packet is encrypted and verified by CRC, the receiving device can decrypt the received packet to obtain the decrypted payload and the decrypted MIC. For MIC verification, the receiving device can generate a MIC based on the decrypted payload and compare the generated MIC with the MIC obtained from the decrypted received packet. If the generated MIC matches the decrypted MIC, the receiving device can determine that the received packet has been successfully decrypted. When the received packet is successfully decrypted, the decoded and decrypted payload of the received packet can be provided to another layer of the receiving device, such as the receiver's decoder-decoder (codec), which can output the payload data of the received packet as, for example, audio by the receiver through the speaker of the headset 112.

[0079] If the generated MIC does not match the decryption MIC of the received packet, the receiving device can determine that the received packet has not been successfully decrypted. When a received packet is not successfully decrypted, it may be that a different packet is missing, or that the received packet may be erroneous or otherwise corrupted. In one configuration, the receiving device may discard received packets that failed MIC verification. Alternatively, in another configuration, the receiving device may attempt to recover the received packets.

[0080] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0081] Figure 4 This is an illustration of an example transmission 400 of data packets from source device 410 to destination device 420 over a WPAN connection 430 according to this disclosure. In some aspects, source device 410 may be... Figure 1 Central equipment 102 and / or Figure 2 One example of a wireless communication device 200, and the receiving device 420 may be... Figure 1 Examples of one or more peripheral devices selected from peripheral devices 104, 106, 108, 110, 112, or 114. In some aspects, the destination device 420 may be a wireless earbud, a pair of wireless earbuds, a wireless portable speaker, or another suitable device. The WPAN connection 430 may be any suitable Bluetooth or BLE connection or link. In some cases, the WPAN connection 430 may be one or more of an ACL link, an L2CAP link, an A2DP link, an SCO link, or an ISO link.

[0082] like Figure 4As shown, source device 410 may include encoder 412 and transmit buffer 414. Encoder 412 may be configured to encode data (such as audio or video data) using a specified bit rate. Transmit buffer 414 may be configured to queue data packets to be transmitted over WPAN connection 430 to destination device 420. In some implementations, data packets to be transmitted over WPAN connection 430 may have a predefined size, for example, based on the type of WPAN connection 430 and / or the channel conditions associated with WPAN connection 430. In some aspects, data encoded by encoder 412 may be packetized into data packets of a predefined size. Source device 410 may dequeue data packets from transmit buffer 414 and transmit data packets over WPAN connection 430 to destination device 420.

[0083] like Figure 4 As further shown, the destination device 420 may include a receive buffer 422 and a decoder 424. Data packets received by the destination device 420 on the WPAN connection 430 may be queued or otherwise stored in the receive buffer 422. Data packets may be output from the receive buffer 422 and forwarded to the decoder 424. In some aspects, the decoder 424 may decode the data (such as audio and / or video data) carried in the payload of the queued data packets and forward the decoded data to the upper layers of the protocol stack for processing and playback to the user. In some specific implementations, the encoder 412 may use a first bit rate to encode a first encoder / decoder (codec) frame and forward the first codec frame to the transmit buffer 414 for packetization for transmission to the destination device 420 on the WPAN connection 430. The destination device 420 may queue received data packets in the receive buffer 422 and may forward a first portion of the first codec frame to the decoder 424 for decoding.

[0084] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0085] Figure 5 This is a diagram illustrating an example 500 of a wireless communication device 500 according to the present disclosure. In some aspects, the wireless communication device 500 may be... Figure 1 Central equipment 102 Figure 2 Wireless communication device 200 or Figure 4 Example of source device 410. In example 500, wireless communication device 500 is depicted as having a... Figure 4 The established WPAN connection 430 (e.g., Bluetooth communication connection) of the host device 420.

[0086] The wireless communication device 500 may include an application processing subsystem 510, an audio subsystem 520, a WPAN subsystem 530, and an HCI 540. It can be used with... Figure 3 The application processing subsystem 510, corresponding to at least some portions of the application layer 310 and host layer 320 of the protocol stack 300, is shown as including a media player 511, an application layer 512, a WPAN stack 513, and an audio interface 514. The media player 511 can be any suitable device or component capable of generating or receiving multimedia content, including, for example, real-time audio streams, real-time video streams, real-time game streams, and / or latency-sensitive traffic. Figure 3 One specific implementation of application layer 310 includes application layer 512, which includes at least one Bluetooth profile defining attribute collection and associated permissions to be used in Bluetooth or BLE communication. In some aspects, application layer 512 may include processing resources, including, for example... Figure 2 The memory 206, ROM 208, and / or flash memory 210. The WPAN stack 513 can be... Figure 3 This is a specific implementation of the protocol stack 300.

[0087] In some aspects, such as Figure 5 As shown, the application processing subsystem 510 may include a WPAN transport driver 516, which may include an audio splitting and packetization module (not shown for simplicity) that can packetize data (such as audio and / or video data) into Bluetooth frames that can be transmitted to the destination device 420 using Bluetooth and / or BLE protocols. In some aspects, the WPAN transport driver 516 may be connected to the audio subsystem 520 via an audio and control link 550. In some aspects, the audio and control link 550 may be used to transmit encoded audio / video data and control signals between the WPAN transport driver 516 and the audio / video DSP within the audio subsystem 520. The WPAN transport driver 516 is also connected to a Universal Asynchronous Receiver-Transmitter (UART) controller 518, which provides control over information transmission via the WPAN connection 430.

[0088] The audio subsystem 520 may include an encoder / decoder 522, one or more DSPs 524, and one or more codecs 526. The encoder / decoder 522 may be used to sample audio / video data extracted from one or more packets received from another wireless communication device. The extracted audio / video data may be processed in the application processing subsystem 510, at least in part, based on a Bluetooth profile. In some implementations, the encoder / decoder 522 may segment the sampled audio / video data into payloads that can be embedded within one or more Bluetooth packets for transmission from the WPAN connection 430 to the destination device 420. In some cases, the DSP 524 and / or codec 526 may combine sampling of the audio data to employ one or more encoding or decoding algorithms.

[0089] WPAN subsystem 530 may include baseband component 532 (e.g., Bluetooth baseband component), firmware component 534, A2DP component 536, and PHY component 538. Baseband component 532 and firmware component 534 can be used to generate baseband signals for constructing and deconstructing data frames based on Bluetooth or BLE protocols. Baseband component 532 and firmware component 534 can also be used to generate carrier signals for up-converting baseband signals during data transmission and for down-converting received data signals to baseband. A2DP component 536 can be used to control or manage the A2DP link between wireless communication device 500 and destination device 420. Specifically, when WPAN subsystem 530 is in receive mode, PHY component 538 can be used to receive, demodulate, and down-convert data packets received on WPAN connection 430, and forward these data packets to application processing subsystem 510. When the WPAN subsystem 530 is in transmit mode, the PHY component 538 can be used to encapsulate data provided from the upper layer into one or more Bluetooth frames or packets for transmission to the destination device 420 over the WPAN connection 430.

[0090] Communication can be based on Target Wake-up Time (TWT) with synchronous end-to-end (E2E) timing. TWT involves scheduling the use of wake-ups for communication and power-downs for power saving.

[0091] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0092] Figure 6 These are illustrations of examples 600 and 602 illustrating the use of ISO links according to this disclosure.

[0093] Central device 610 (e.g., mobile phone, smartphone, game console) can support peripheral links with peripheral device 620 (e.g., earphones, XR headsets, XR glasses, wearable devices, portable speakers), such as BR / EDR Bluetooth audio links (BREDR), BLE links, A2DP links, or proprietary links. Central device 610 can stream audio or video over an LE ISO link. As shown in Example 600, central device 610 can send ISO data 612 (e.g., audio data, video data) in ISO data packets over an ISO link. Peripheral device 620 can send ISO data 614 (e.g., controller input) in ISO data packets to central device 610. Central device 610 can send feedback for ISO data 614 (e.g., ISO ACK 616). Peripheral device 620 can send feedback for ISO data packets of ISO data 612 (e.g., ISO ACK 618). The number of sub-events (NSE) can be 3, and BN can be 1.

[0094] LE packets may include sensor data from peripheral devices or control information from a central device. The central device 610 may send LE control information (e.g., LE control 622) from the LE packet to the peripheral device 620. The peripheral device 620 may collect sensor data (e.g., orientation data, proximity data) and send the sensor data (e.g., LE data 624) along with any other LE data in the LE packet to the central device 610. LE packets may be pre-scheduled for transmission during LE events. Anchor point 626 may mark the start of an LE event. LE events may also be referred to as asynchronous connection links (ACLs).

[0095] In use cases such as spatial audio or XR, LE packets are expected to be delivered on time for optimal user experience. Sensor data on earbuds, XR headsets, or XR glasses can be sampled at high speeds to create accurate output for the user with low latency. Therefore, applications may request aggressive LE parameters over ISO links. For example, there might be a 20ms LE interval to transmit sensor data from peripheral device 620 or deliver control messages from central device 610, along with 7.5ms or 10ms ISO intervals. These interval times present several problems. Central device 610 may not have sufficient continuous time for WiFi activity of central device 610 and / or peripheral device 620. When multiple links are involved, switching back and forth between WiFi and other signaling can cause scheduling problems, as this can fragment the bandwidth used by WiFi. Latency may increase due to bandwidth fragmentation or insufficiency, and signaling resources may not be used efficiently. Furthermore, in addition to streaming media and sensor exchange, there may not be enough bandwidth for other operations, such as proximity applications that continuously announce the status of peripheral devices, connecting to another computer, or earbud scanning. Peripheral device 620 may not be able to easily schedule multiple links to support multi-point use cases. One solution is not to schedule LE links, but this will further increase the latency of LE packets.

[0096] Based on the various aspects described herein, the device may send LE packets earlier than expected, for example, by utilizing feedback to ISO data packets. For instance, LE data or control information may be carried on an ISO ACK, which may be located in an ISO sub-event earlier than a pre-scheduled LE event. The pre-scheduled LE event may not necessarily be explicitly scheduled by the central device, but may include sub-events or times of LE packets anticipated based on LE intervals greater than the ISO data interval.

[0097] Example 602 illustrates a central device 610 transmitting feedback and LE data together (e.g., ISO ACK and LE control 628). A peripheral device 620 may also transmit feedback and LE data together (e.g., ISO ACK and LE data 630). Example 600 illustrates that LE packets can be scheduled to be transmitted in sub-event 1 immediately following sub-event 0 when ISO data is exchanged (or in an ISO sub-event following a previous ISO sub-event after all ISO data packets have been received). In some aspects, the transmitting device may send an indication (e.g., bits reserved for future use) that the LE packet will be transmitted in an ISO sub-event earlier than the LE event. The anchor point associated with the LE event (when the LE packet is to be transmitted) may be moved ahead to the beginning of the earlier ISO sub-event. There may be no empty sub-events between the exchange of ISO data and feedback and the exchange of LE packets. Sending LE packets in an earlier ISO event rather than a later LE event results in lower bandwidth requirements and a higher probability of obtaining a larger time window of ISO or LE inactivity that can be used for other signaling (e.g., WiFi, other links) or applications on the central device 610.

[0098] In some scenarios, devices may use an encrypted packet counter to encrypt and decrypt LE packets. In some aspects, the device can adjust the encrypted packet counter value to account for the maximum number of LE packets to be sent within an ISO interval. This allows the device to "steal" LE packets during ISO events with minimal changes to the device's controller layer.

[0099] For example, if two unique ISO data packets can be exchanged in each ISO event (e.g., bit count (BN=2)), then in ISO event 0, the packet counter can be expected to start from 0. After transmitting two ISO data packets in event 0, the packet counter can start from 2 in event 1. In event 2, the packet counter can start from 4. In event 3, the packet counter can start from 6, and so on. However, if the transmitting device transmits additional LE packets in the ISO event, the existing calculation will not work. The packet counter can be adjusted to account for the maximum possible LE data packets that can be accommodated in each ISO event. If the maximum possible LE packets in an ISO event is 2, then the packet counter for each ISO event can start in a multiple of 4. Event 0 might start with a packet count of 0. Event 1 might start with a packet count of 4. Event 2 might start with a packet count of 8, and so on. Other multiples can be used.

[0100] By sending LE packets earlier, the central device can skip scheduled LE links and spend more time on WiFi operation due to the larger time window of LE inactivity. More aggressive LE parameter values ​​can be avoided due to the reduced LE packet latency. The overall bandwidth requirements for ISO data and LE data / control information are also reduced.

[0101] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0102] Figure 7 These are illustrations of examples 700 and 702 illustrating the use of ISO links according to this disclosure. Example 700 relates to a use case for spatial audio.

[0103] Example 700 illustrates the transmission of ISO data packet 704 during sub-event 0 and the transmission of LE packet 706 during the LE event. Example 702 illustrates the transmission of LE packet 708 during sub-event 1, which precedes the pre-scheduled LE event.

[0104] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0105] Figure 8 This is a diagram illustrating example 800 of an interleaved ISO link according to this disclosure. Example 800 illustrates the transmission of ISO data packets in an interleaved mode, for example, when each earbud in a pair of earphones receives an audio streaming transmission.

[0106] Central device 810 (e.g., a smartphone) may exchange ISO data packets 802 with peripheral device 820 (e.g., a left earphone) in sub-event 0 of CIS link 0. Then, central device 810 may exchange ISO data packets 804 with peripheral device 830 (e.g., a right earphone) in sub-event 0 of CIS link 1.

[0107] Central device 810 can exchange LE packets 806 with peripheral device 820 in sub-event 1 of CIS link 0. Central device 810 can exchange LE packets 808 with peripheral device 830 in sub-event 1 of CIS link 1. LE packets can be exchanged before a pre-scheduled LE event.

[0108] In some aspects, such as for a pair of earbuds, when the earbuds have data to send on the ISO link, the central device or the main earbud may only use feedback (e.g., ACK) to schedule the last ISO sub-event. When the earbuds have no data to send, the device may carry LE packets with ISO data.

[0109] As indicated above, Figure 8 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The examples described are different.

[0110] Figure 9 This is a diagram illustrating example 900 of using an ISO link according to this disclosure.

[0111] In some respects, the transmitting device (e.g., central device 910 or peripheral device 920) may use an increased-size sub-event to include ISO data packets and LE packets in the same ISO sub-event sent to the receiving device (e.g., peripheral device 920 or central device 910). The ISO sub-event may no longer be dedicated to ISO data packets. The increased size may be based at least in part on the maximum number of LE data packets or a host configuration value. If no more ISO data is to be sent, the transmitting device may send LE packets. The transmitting device does not need to wait for an empty ISO sub-event to send feedback or LE packets. Example 900 illustrates ISO data packets and LE packets in the same ISO sub-event (sub-event 0) for the transmitting device.

[0112] As indicated above, Figure 9 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 9 The examples described are different.

[0113] Figure 10 This is a diagram illustrating example 1000 using an ISO link according to this disclosure.

[0114] Example 1000 illustrates a central device 610 sending ISO data packet 1002 (as part of a first set of ISO data packets) and a peripheral device sending an ISO data packet with ACK 1004 (as part of a first set of feedback packets) (as part of a second set of ISO data packets). A set of ISO data packets may include one or more ISO data packets. The central device 610 may also send ACK 1006 (as part of a second set of feedback packets). Multiple ISO data packets (and feedback) may be exchanged in one or more ISO sub-events. A set of feedback packets may include one or more feedback packets.

[0115] In some respects, once all ISO data packets scheduled in an ISO sub-event have been successfully transmitted in both directions, the transmitting device can send an LE packet. Example 1000 shows that a central device 610 can send an LE packet 1008, and a peripheral device 620 can send an LE packet 1010 with an ACK.

[0116] In some respects, if there is an LE packet to be transmitted and both the sending and receiving devices support an indication to send the LE packet before a pre-scheduled LE event, the sending device may send the indication. This indication may be the LE Packet Data Available (LDA) bit 1012. The sending device may send the LDA bit 1012 in the extended ISO data packet header. Example 1000 shows that either device may send this indication. The device may begin sending the LE packet from the next available ISO sub-event. The anchor point associated with the LE event may be moved ahead to the beginning of the next available ISO sub-event. The LE packet may be sent using regular LE link parameters (typically used or configured with ISO data parameters), such as access address, acknowledgment and flow control parameters (sequence number (SN) and next expected sequence number (NESN) bits) and / or encryption parameters (packet counter).

[0117] LE packets can be sent faster by sending them after all streaming data and feedback have been exchanged, rather than waiting for pre-scheduled LE events. This provides a larger inactivity window, allowing the central device to skip scheduling LE links and spend more time operating the WiFi. It avoids gaps between the final ISO data feedback and the LE packet. Scheduling in ISO interleaving mode is more efficient, and more aggressive LE parameter values ​​can be avoided due to reduced LE packet latency.

[0118] As indicated above, Figure 10 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 10 The examples described are different.

[0119] Figure 11 This is a diagram illustrating an example process 1100 performed, for example, at a wireless device or a device of a wireless device according to the present disclosure. Example process 1100 is an example of a device or wireless device (e.g., a central device, a peripheral device) performing operations associated with low-power packet scheduling.

[0120] like Figure 11 As shown, in some aspects, process 1100 may include receiving data packets on an ISO link (block 1110). For example, a wireless device (e.g., using the method depicted in the diagram) Figure 13 The receiving component 1302 and / or communication manager 1306 in the system can receive data packets on the ISO link, as described above.

[0121] like Figure 11 As further shown, in some aspects, process 1100 may include sending an LE packet (box 1120) containing a feedback of the data packet. For example, a wireless device (e.g., using the diagram depicting...) Figure 13 The transmitting component 1304 and / or the communication manager 1306 in the middle can transmit an LE packet with feedback of the data packet, as described above.

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

[0123] In the first aspect, sending the LE packet includes sending the LE packet earlier than a pre-scheduled LE event for sending the LE packet.

[0124] In a second aspect, alone or in combination with the first aspect, process 1100 includes sending an indication that the LE packet will be sent in an ISO sub-event, which is earlier than a pre-scheduled LE event for sending the LE packet.

[0125] In the third aspect, alone or in combination with one or more of the first and second aspects, the ISO sub-event occurs after the previous ISO sub-event in which all ISO data packets have been received.

[0126] In the fourth aspect, alone or in combination with one or more of the first to third aspects, process 1100 includes adjusting the group counter start value for each ISO event.

[0127] In the fifth aspect, sending the LE packet, alone or in combination with one or more of the first to fourth aspects, includes sending the LE packet in the same ISO sub-event as the ISO data packet is received.

[0128] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 1100 includes increasing the size of the ISO sub-event configured for the ISO interval.

[0129] In the seventh aspect, sending the LE packet, alone or in combination with one or more of the first to sixth aspects, includes sending the LE packet based at least in part on the determination that there is no more data to be sent or received on the ISO link.

[0130] although Figure 11 An example box of process 1100 is shown, but in some respects, process 1100 may include... Figure 11The boxes depicted herein are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1100 may be executed in parallel.

[0131] Figure 12 This is a diagram illustrating an example process 1200 performed, for example, at a wireless device or a device of a wireless device according to the present disclosure. Example process 1200 is an example of a device or wireless device (e.g., a central device, a peripheral device) performing operations associated with low-power packet scheduling.

[0132] like Figure 12 As shown, in some aspects, process 1200 may include transmitting a first set of ISO data packets over an ISO link (box 1210). For example, a wireless device (e.g., using the method depicted in...) Figure 13 The receiving component 1304 and / or the communication manager 1306 in the ISO link can send the first set of ISO data packets, as described above.

[0133] like Figure 12 As further shown, in some aspects, process 1200 may include receiving a second set of ISO data packets on the ISO link (box 1220). For example, a wireless device (e.g., using the one depicted in...) Figure 13 The receiving component 1302 and / or the communication manager 1306 in the ISO link can receive a second set of ISO data packets, as described above.

[0134] like Figure 12 Further shown, in some aspects, process 1200 may include receiving a first set of feedback packets (box 1230) of the first set of ISO data packets. For example, a wireless device (e.g., using the diagram depicting...) Figure 13 The transmitting component 1302 and / or the communication manager 1306 in the first set of ISO data packets can receive the first set of feedback packets as described above.

[0135] like Figure 12 Further shown, in some aspects, process 1200 may include sending a second set of feedback packets (box 1240) of the second set of ISO data packets. For example, a wireless device (e.g., using the diagram depicting...) Figure 13 The transmitting component 1304 and / or the communication manager 1306 in the middle can transmit the second set of feedback packets of the second set of ISO data packets, as described above.

[0136] like Figure 12 Further shown, in some aspects, process 1200 may include transmitting the LE packet earlier than a pre-scheduled LE event for transmitting the LE packet (box 1250). For example, a wireless device (e.g., using the one depicted in...) Figure 13The sending component 1304 and / or the communication manager 1306 in the middle may send the LE packet earlier than the LE event pre-scheduled for sending the LE packet, as described above.

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

[0138] In a first aspect, process 1200 includes moving the LE anchor point associated with the LE event to the start time of the next ISO sub-event.

[0139] In the second aspect, either alone or in combination with the first aspect, sending the LE packet includes sending the LE packet in the next ISO sub-event following the ISO sub-event in which the last feedback packet of the second set of feedback packets is sent.

[0140] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1200 includes sending an indication that the LE packet will be sent in an ISO sub-event, which is earlier than the LE event pre-scheduled for sending the LE packet.

[0141] In the fourth aspect, sending the LE packet, alone or in combination with one or more of the first to third aspects, includes sending the LE packet with regular LE link parameters.

[0142] although Figure 12 An example box of process 1200 is shown, but in some respects, process 1200 may include... Figure 12 The boxes depicted in the text are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1200 may be executed in parallel.

[0143] Figure 13 This is a diagram of an example device 1300 for wireless communication according to the present disclosure. Device 1300 may be a wireless device (e.g., a central device, a peripheral device), or a wireless device may include device 1300. In some aspects, device 1300 includes a receiving component 1302, a transmitting component 1304, and / or a communication manager 1306 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1306 is combined with... Figure 2 The described WPAN controller 252 or other communication manager of the central device. As shown, device 1300 can communicate with another device 1308 (such as a UE or network node (such as a CU, DU, RU or base station)) using receiving component 1302 and transmitting component 1304.

[0144] In some respects, device 1300 can be configured to perform the functions described herein. Figures 1 to 10 One or more operations described herein. Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Figure 11 Process 1100 Figure 12 The process 1200 or a combination thereof. In some respects, Figure 13 The illustrated device 1300 and / or one or more components may include a combination Figure 2 One or more components of the described wireless device. Additionally or alternatively, Figure 13 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in this set may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0145] Receiver 1302 may receive communications from device 1308, such as reference signals, control information, data communications, or combinations thereof. Receiver 1302 may provide the received communications to one or more other components of device 1300. In some aspects, receiver 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications, and may provide the processed signals to one or more other components of device 1300. In some aspects, receiver 1302 may include combinations of... Figure 2 The described wireless device includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0146] Transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1308. In some aspects, one or more other components of device 1300 may generate communications and provide the generated communications to transmitting component 1304 for transmission to device 1308. In some aspects, transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and transmit the processed signals to device 1308. In some aspects, transmitting component 1304 may include combinations of... Figure 2The described wireless device includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1304 may co-located with the receive component 1302 in one or more transceivers.

[0147] The communication manager 1306 may support the operation of the receiving component 1302 and / or the transmitting component 1304. For example, the communication manager 1306 may receive information associated with configuring communication reception for the receiving component 1302 and / or configuring communication transmission for the transmitting component 1304. Additionally or alternatively, the communication manager 1306 may generate and / or provide control information to the receiving component 1302 and / or the transmitting component 1304 to control the reception and / or transmission of communication.

[0148] In some respects, receiving component 1302 can receive data packets on an ISO link. Transmitting component 1304 can transmit LE packets with feedback of the data packets.

[0149] The transmitting component 1304 can transmit an indication that the LE packet will be transmitted in an ISO sub-event, which is earlier than a pre-scheduled LE event for transmitting the LE packet.

[0150] The Communication Manager 1306 can adjust the starting value of the group counter for each ISO event. The Communication Manager 1306 can also increase the size of ISO sub-events configured for ISO intervals.

[0151] In some respects, transmitting component 1304 may transmit a first set of ISO data packets on the ISO link. Receiving component 1302 may receive a second set of ISO data packets on the same ISO link. Receiving component 1302 may receive a first set of feedback packets for the first set of ISO data packets. Transmitting component 1304 may transmit a second set of feedback packets for the second set of ISO data packets. Transmitting component 1304 may transmit the LE packet earlier than a pre-scheduled LE event for transmitting the LE packet.

[0152] The communication manager 1306 can move the LE anchor point associated with the LE event to the start time of the next ISO sub-event. The sending component 1304 can send an indication that the LE packet will be sent in an ISO sub-event earlier than the LE event pre-scheduled for sending the LE packet.

[0153] Figure 13 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 13The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 13 The two or more components shown can be implemented within a single component, or Figure 13 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 13 The set (one or more) components shown are executable and described as being composed of Figure 13 The other set of components shown performs one or more functions.

[0154] The following provides an overview of some aspects of this disclosure: Aspect 1: A method of wireless communication performed by a wireless device, the method comprising: receiving data packets on an isochronous (ISO) link; and transmitting low-power (LE) packets having feedback of said data packets.

[0155] Aspect 2: According to the method of aspect 1, sending the LE packet includes sending the LE packet earlier than a pre-scheduled LE event for sending the LE packet.

[0156] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising sending an indication that the LE packet will be sent in an ISO sub-event, the ISO sub-event being earlier than a pre-scheduled LE event for sending the LE packet.

[0157] Aspect 4: According to the method of aspect 3, the ISO sub-event is after the previous ISO sub-event in which all ISO data packets are received.

[0158] Aspect 5: The method according to any one of aspects 1 to 4, the method further includes adjusting the group counter start value for each ISO event.

[0159] Aspect 6: The method according to any one of Aspects 1 to 5, wherein sending the LE packet includes sending the LE packet in the same ISO sub-event as the ISO data packet is received.

[0160] Aspect 7: According to the method of aspect 6, the method further includes increasing the size of ISO sub-events configured for ISO intervals.

[0161] Aspect 8: According to the method of aspect 6, sending the LE packet includes sending the LE packet based at least in part on the determination that there is no more data to be sent or received on the ISO link.

[0162] Aspect 9: A method of wireless communication performed by a wireless device, the method comprising: transmitting a first set of ISO data packets on an isochronous (ISO) link; receiving a second set of ISO data packets on the ISO link; receiving a first set of feedback packets of the first set of ISO data packets; transmitting a second set of feedback packets of the second set of ISO data packets; and transmitting the LE packets earlier than a pre-scheduled LE event for transmitting low-power (LE) packets.

[0163] Aspect 10: According to the method of aspect 9, the method further includes moving the LE anchor point associated with the LE event to the start time of the next ISO sub-event.

[0164] Aspect 11: The method according to any one of Aspects 9 to 10, wherein sending the LE packet includes sending the LE packet in the next ISO sub-event following the ISO sub-event in which the last feedback packet of the second set of feedback packets is sent.

[0165] Aspect 12: The method according to any one of Aspects 9 to 11, the method further comprising sending an indication that the LE packet will be sent in an ISO sub-event, the ISO sub-event being earlier than the LE event pre-scheduled for sending the LE packet.

[0166] Aspect 13: The method according to any one of Aspects 9 to 12, wherein sending the LE packet includes sending the LE packet with conventional LE link parameters.

[0167] Aspect 14: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 13.

[0168] Aspect 15: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 13.

[0169] Aspect 16: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 13.

[0170] Aspect 17: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 13.

[0171] Aspect 18: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 13.

[0172] Aspect 19: A device for wireless communication, the device comprising: a processing system including one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 13.

[0173] Aspect 20: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 13.

[0174] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0175] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent to those skilled in the art that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting in any way. Therefore, no specific software code is referenced in this document to describe the operation and behavior of the systems and / or methods, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0176] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0177] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically set forth in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the set of claims. As used herein, the phrase referring to “at least one of” the list of items means any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0178] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “have,” “possess,” “have,” etc., are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., in the case of its use in conjunction with “any” or “only one”).

Claims

1. An apparatus for conducting wireless communication at a wireless device, the apparatus comprising: One or more memory units; and One or more processors, coupled to one or more memories, wherein the one or more processors are individually or collectively configured to enable the wireless device to: Receive data packets on an isochronous (ISO) link; and Send a low-power (LE) packet with feedback of the data packet.

2. The apparatus of claim 1, wherein, in order to transmit the LE packet, the one or more processors are individually or jointly configured to cause the wireless device to transmit the LE packet earlier than a pre-scheduled LE event for transmitting the LE packet.

3. The apparatus of claim 1, wherein the one or more processors are individually or jointly configured to cause the wireless device to send an indication that the LE packet will be sent in an ISO sub-event, the ISO sub-event preceding a pre-scheduled LE event for sending the LE packet.

4. The apparatus of claim 3, wherein the ISO sub-event occurs after a previous ISO sub-event in which all ISO data packets have been received.

5. The apparatus of claim 1, wherein the one or more processors are individually or collectively configured to cause the wireless device to adjust the packet counter start value for each ISO event.

6. The apparatus of claim 1, wherein, in order to transmit the LE packet, the one or more processors are individually or jointly configured to cause the wireless device to transmit the LE packet in the same ISO sub-event upon receiving the ISO data packet.

7. The apparatus of claim 6, wherein the one or more processors are individually or collectively configured to cause the wireless device to increase the size of ISO sub-events configured for ISO intervals.

8. The apparatus of claim 6, wherein, in order to transmit the LE packet, the one or more processors are configured to cause the wireless device to transmit the LE packet at least in part based on a determination that there is no further data to be transmitted or received on the ISO link.

9. An apparatus for conducting wireless communication at a wireless device, the apparatus comprising: One or more memory units; and One or more processors, coupled to one or more memories, wherein the one or more processors are individually or collectively configured to enable the wireless device to: Send the first set of ISO data packets on the isochronous (ISO) link; Receive a second set of ISO data packets on the ISO link; Receive the first set of feedback packets from the first set of ISO data packets; Send the second set of feedback packets from the second set of ISO data packets; as well as The LE packet is sent earlier than the LE event pre-scheduled for sending low-power (LE) packets.

10. The apparatus of claim 9, wherein the one or more processors are individually or collectively configured to cause the wireless device to move the LE anchor point associated with the LE event to the start time of the next ISO sub-event.

11. The apparatus of claim 9, wherein, in order to transmit the LE packet, the one or more processors are individually or jointly configured to cause the wireless device to transmit the LE packet in the next ISO sub-event following the ISO sub-event in which the last feedback packet of the second set of feedback packets is transmitted.

12. The apparatus of claim 9, wherein the one or more processors are individually or jointly configured to cause the wireless device to send an indication that the LE packet will be sent in an ISO sub-event, the ISO sub-event preceding a pre-scheduled LE event for sending the LE packet.

13. The apparatus of claim 9, wherein, in order to transmit the LE packet, the one or more processors are individually or collectively configured to cause the wireless device to transmit the LE packet with conventional LE link parameters.

14. A method for wireless communication performed by a wireless device, the method comprising: Receive data packets on the isochronous (ISO) link; as well as Send a low-power (LE) packet with feedback of the data packet.

15. The method of claim 14, wherein sending the LE packet includes sending the LE packet earlier than a pre-scheduled LE event for sending the LE packet.

16. The method of claim 14, further comprising sending an indication that the LE packet will be sent in an ISO sub-event, the ISO sub-event being earlier than a pre-scheduled LE event for sending the LE packet.

17. The method of claim 16, wherein the ISO sub-event is after a previous ISO sub-event in which all ISO data packets have been received.

18. The method of claim 14, further comprising adjusting the group counter start value for each ISO event.

19. The method of claim 14, wherein sending the LE packet includes sending the LE packet in the same ISO sub-event as receiving the ISO data packet.

20. The method of claim 19, further comprising increasing the size of ISO sub-events configured for ISO intervals.

21. The method of claim 19, wherein sending the LE packet comprises sending the LE packet at least in part based on a determination that there is no further data to be sent or received on the ISO link.

22. A method for wireless communication performed by a wireless device, the method comprising: Send the first set of ISO data packets on the isochronous (ISO) link; Receive a second set of ISO data packets on the ISO link; Receive the first set of feedback packets from the first set of ISO data packets; Send the second set of feedback packets from the second set of ISO data packets; as well as The LE packet is sent earlier than the LE event pre-scheduled for sending low-power (LE) packets.

23. The method of claim 22, further comprising moving the LE anchor point associated with the LE event to the start time of the next ISO sub-event.

24. The method of claim 22, wherein sending the LE packet comprises sending the LE packet in the next ISO sub-event following the ISO sub-event in which the last feedback packet of the second set of feedback packets is sent.

25. The method of claim 22, further comprising sending an indication that the LE packet will be sent in an ISO sub-event, the ISO sub-event preceding a pre-scheduled LE event for sending the LE packet.

26. The method of claim 22, wherein sending the LE packet comprises sending the LE packet with conventional LE link parameters.

Images