Shared sub-events for protocol data units associated with different streams
By sharing sub-events in the wireless communication system, sending PDUs associated with different streams, and activating a low-power mode at the receiving device, the problems of bandwidth utilization and power consumption in short-range communication are solved, achieving more efficient wireless communication.
Patent Information
- Application Number
- CN202280093792.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-04
- Filing Date
- 2022-06-16
- Publication Date
- 2024-11-19
AI Technical Summary
Existing wireless communication systems struggle to efficiently utilize bandwidth and conserve device power in short-range communication, especially in multi-user communication scenarios, particularly when communication demands are uneven across different streams.
By sharing sub-events between the initiating and receiving devices, Protocol Data Units (PDUs) associated with different streams are sent, and a low-power mode is activated at the receiving device, optimizing bandwidth usage and power consumption.
It improves bandwidth utilization efficiency, reduces device latency and power consumption, and achieves more efficient wireless communication without requiring modifications to the receiver's software and hardware.
Smart Images

Figure CN118985122A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims the priority of Indian Provisional Application No. 202241020281, filed on April 4, 2022, entitled “SHARED SUBEVENTS FOR PROTOCOLDATA UNITS ASSOCIATED WITH DIFFERENT STREAMS” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field
[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for using shared sub-events for protocol data units associated with different flows. Background Art
[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Low Energy (LE) is a Special Interest Group (SIG) An enhanced set of classic standards, and using similar Classic 2.4GHz radio frequency.
[0005] A connection may include an initiator supporting communications with one recipient or multiple recipients. A recipient may communicate with a base station via a unidirectional connection isochronous stream (CIS) and / or a bidirectional CIS. "Unidirectional" refers to a communication link from an initiator to a recipient or from a recipient to an initiator, and "bidirectional" refers to a communication link from an initiator to a recipient and from a recipient to an initiator.
[0006] The above technology has been adopted in various devices to provide a common protocol that enables different initiator devices and recipient devices to communicate at a city, country, region and / or global level. As the demand for short-range (e.g., within 100 meters) wireless communication continues to increase, And further improvements in other radio access technologies remain useful. Summary of the invention
[0007] Some aspects described herein relate to an apparatus for wireless communication at an initiator device. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a protocol data unit (PDU) associated with a first stream during a first sub-event within a portion of an event shared between a first stream and a second stream. Additionally or alternatively, the one or more processors may be configured to send a PDU associated with a second stream during a second sub-event within the portion of an event shared between the first stream and the second stream.
[0008] Some aspects described herein relate to an apparatus for wireless communication at a recipient device. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to activate a low power mode during one or more first sub-events within an event shared between a second stream and a first stream for a recipient device. The one or more processors may be further configured to listen to a PDU associated with the first stream during one or more second sub-events within the event.
[0009] Some aspects described herein relate to a method of wireless communication performed by an initiator device. The method may include sending a PDU associated with a first stream during a first sub-event within a portion of an event shared between the first stream and a second stream. Additionally or alternatively, the method may include sending a PDU associated with a second stream during a second sub-event within the portion of the event shared between the first stream and the second stream.
[0010] Some aspects described herein relate to a method of wireless communication performed by a recipient device. The method may include activating a low power mode during one or more first sub-events within an event shared between a second stream and a first stream for the recipient device. The method may also include listening to a PDU associated with the first stream during one or more second sub-events within the event.
[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by an initiator device. The one or more instructions, when executed by one or more processors of the initiator device, may cause the initiator device to send a PDU associated with a first stream during a first sub-event within a portion of an event shared between the first stream and the second stream. Additionally or alternatively, the instruction set, when executed by one or more processors of the initiator device, may cause the initiator device to send a PDU associated with a second stream during a second sub-event within the portion of the event shared between the first stream and the second stream.
[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a recipient device. The instruction set, when executed by one or more processors of the recipient device, can cause the recipient device to activate a low power mode during one or more first sub-events within an event shared between a second stream and a first stream for the recipient device. The instruction set, when executed by one or more processors of the recipient device, can also cause the recipient device to listen to a PDU associated with the first stream during one or more second sub-events within the event.
[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a PDU associated with a first stream during a first sub-event within a portion of an event shared between the first stream and a second stream. Additionally or alternatively, the apparatus may include means for sending a PDU associated with a second stream during a second sub-event within the portion of the event shared between the first stream and the second stream.
[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for activating a low power mode during one or more first sub-events within an event shared between a second stream and a first stream for the apparatus. The apparatus may include means for listening to a PDU associated with the first stream during one or more second sub-events within the event.
[0015] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to and as illustrated by the accompanying drawings and description.
[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood from the following description. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.
[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and / or artificial intelligence devices). Various 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. The equipment including the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] In order to fully understand the above features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are shown in the accompanying drawings). However, it should be noted that the accompanying drawings only show certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.
[0019] Figure 1 This is an example of the An example diagram of a network.
[0020] Figure 2 is an example of the An illustration of an example of an initiator device communicating with recipient devices in a network.
[0021] Figure 3 is a diagram illustrating an example of equal time intervals according to the present disclosure.
[0022] Figure 4A and Figure 4B is a diagram illustrating an example associated with a sub-event packaging scheme according to the present disclosure.
[0023] Figure 5A , Figure 5B , Figure 5C and Figure 5Dis a diagram illustrating an example associated with sharing sub-events between isochronous streams according to the present disclosure.
[0024] Fig. 6A and Figure 6B is a diagram illustrating an example associated with configuring a shared sub-event between isochronous streams according to the present disclosure.
[0025] Figure 7 is a diagram illustrating an example associated with a time offset within a shared sub-event between isochronous streams according to the present disclosure.
[0026] Fig. 8A and Figure 8B is a diagram illustrating an example associated with power saving during a shared sub-event between isochronous flows according to the present disclosure.
[0027] Fig. 9 is a diagram illustrating an example associated with a protocol data unit (PDU) structure for an isochronous flow according to the present disclosure.
[0028] Fig.10 and Fig.11 is a diagram illustrating an example process associated with using a shared sub-event for PDUs associated with different flows according to the present disclosure.
[0029] Fig.12 and Fig.13 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION
[0030] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented in the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functions, or structures and functions other than the various aspects of the present disclosure set forth herein or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of the claims.
[0031] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0032] Although aspects may be used herein generally with LE technology, but aspects of the present disclosure may be applicable to other technologies, such as classic.
[0033] Figure 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be The network may include Elements of a network. The wireless network 100 may include an initiator device 110 (shown as user equipment (UE) 110), one recipient device 120 or multiple recipient devices 120 (shown as earbuds 120a and earbuds 120b), and / or other network entities. The initiator device 110 is an entity that communicates with the recipient device 120. The initiator device 110 (sometimes referred to as a client or central device) may include, for example, a UE and / or another type of controller device. The recipient device 120 (sometimes referred to as a server device or peripheral device) may include, for example, earbuds, microphones, cameras, and / or another type of accessory device.
[0034] The UE 110 and the earbuds 120 may be used Procedures (such as LE protocol) on a channel. For example, the UE 110 may send data to the earbud 120 for the earbud 120 to decode (e.g., generate audio accordingly). Additionally or alternatively, the earbud 120 may send data (e.g., based on the received audio) to the UE 110 for forwarding to a server and / or another remote device via a network 165 (e.g., the Internet, a long term evolution (LTE) network, a 5G or new radio (NR) network, and / or another type of network). Thus, the UE 110 may be connected to the network 165 via a wired and / or wireless connection with the network controller 130. The network controller 130 may communicate with the UE 110 via a wireless communication link (e.g., using a competing standard such as the 802.11 standard (also referred to as the “IEEE 802.11 protocol”) of the Institute of Electrical and Electronics Engineers (IEEE) Local Area Network / Metropolitan Area Network (LAN / MAN) Standards Committee or a standard and / or a wired communication link promulgated by the Third Generation Partnership Project (3GPP).
[0035] UE 110 may be stationary or mobile. UE 110 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium. Similarly, earbuds 120 may be dispersed throughout wireless network 100, and each earbud 120 may be stationary or mobile.
[0036] Some recipient devices may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs, such as robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a base station, another device (e.g., a remote device), or some other entity. Some recipient devices may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband Iot) devices. The recipient device may be included inside a housing that houses components of the recipient device, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.
[0037] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may operate on one or more frequencies. Thus, the devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating frequency bands. In the case of wireless communications, the operating frequency band is typically the Industrial, Scientific, and Medical (ISM) band (eg, the 2.400 GHz-2.4835 GHz band).
[0038] In some aspects, recipient device 120 may include communication manager 140. As described in more detail elsewhere herein, communication manager 140 may activate a low power mode during one or more first sub-events within an event shared between a first stream for a recipient device and a second stream for an additional recipient device, and listen for protocol data units (PDUs) associated with the first stream during one or more second sub-events within the event. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.
[0039] In some aspects, the initiator device 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a PDU associated with the first stream during a first sub-event within a portion of the event shared between the first stream and the second stream, and / or send a PDU associated with the second stream during a second sub-event within a portion of the event shared between the first stream and the second stream. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.
[0040] As indicated above, Figure 1 Other examples can be found in the Figure 1 The content described is different.
[0041] Figure 2 2 is a diagram illustrating an example 200 of an initiator device 110 communicating with a recipient device 120 in a wireless network 100 according to the present disclosure. The initiator device 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The recipient device 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).
[0042] At the initiator device 110, the transmit processor 220 may receive data intended for a recipient device 120 (or a set of recipient devices 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the recipient device 120 based at least in part on one or more channel quality indicators (CQIs) received from the recipient device 120. The initiator device 110 may process (e.g., encode and modulate) the data for the recipient device 120 based at least in part on the MCS selected for the recipient 120, and provide data symbols for the recipient device 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).
[0043] At the recipient device 120, a set of antennas 252 (illustrated as antennas 252a through 252r) may receive downlink signals from the initiator device 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), illustrated as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (illustrated as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) a received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the recipient device 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the recipient device 120 may be included in the housing 284.
[0044] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, a WiFi device and / or a base station in a cellular network, etc. The network controller 130 may communicate with the initiator device 110 via the communication unit 294.
[0045] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.
[0046] On the uplink, at the recipient device 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RS SI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the initiator device 110. In some examples, the modem 254 of the recipient device 120 may include a modulator and a demodulator. In some examples, the recipient device 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (eg, with reference to Figure 5A , Figure 5B , Figure 5C , Fig. 6A , Figure 6B , Figure 7 , Fig. 8A , Figure 8B and Figures 9 to 13 ).
[0047] At the initiator device 110, uplink signals from the recipient device 120 and / or other recipient devices may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the recipient device 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The initiator device 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The initiator device 110 may include a scheduler 246 to schedule one or more recipient devices 120 for downlink and / or uplink communications. In some examples, the modem 232 of the initiator device 110 may include a modulator and a demodulator. In some examples, the initiator device 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., reference 20 to FIG. 1 ). Figure 5A , Figure 5B , Figure 5C , Fig. 6A , Figure 6B , Figure 7 , Fig. 8A , Figure 8B and Figures 9 to 13 ).
[0048] The controller / processor 240 of the initiator device 110, the controller / processor 280 of the recipient device 120, and / or Figure 2 Any other component of may perform one or more techniques associated with using shared sub-events for PDUs associated with different flows, as described in more detail elsewhere herein. For example, the controller / processor 240 of the initiator device 110, the controller / processor 280 of the recipient device 120, and / or Figure 2 Any other component of the Fig.10 The process of 1000 Fig.11The operations of process 1100 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for initiator device 110 and recipient device 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of initiator device 110 and / or recipient device 120, may cause the one or more processors, recipient device 120, and / or initiator device 110 to perform or direct, for example Fig.10 The process of 1000 Fig.11 The process 1100 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.
[0049] In some aspects, the initiator device 110 may include: means for transmitting a PDU associated with the first stream during a first sub-event within a portion of an event shared between the first stream and the second stream; and / or means for transmitting a PDU associated with the second stream during a second sub-event within a portion of an event shared between the first stream and the second stream. In some aspects, the means for the initiator device 110 to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.
[0050] In some aspects, the recipient device 120 may include a means for activating a low power mode during one or more first sub-events within an event shared between a first stream for the recipient device and a second stream for an additional recipient device; and / or a means for listening to a PDU associated with the first stream during one or more second sub-events within the event. In some aspects, the means for the recipient device 120 to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.
[0051] Although Figure 2The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.
[0052] As indicated above, Figure 2 Other examples can be found in the Figure 2 The content described is different.
[0053] Figure 3 is a diagram illustrating an example 300 of equal time intervals according to the present disclosure. In example 300, an initiator 110 may communicate with a first recipient 120a on a bidirectional CIS and with a second recipient 120b on a unidirectional CIS. Although described using one bidirectional CIS and one unidirectional CIS, the description is similarly applicable to two bidirectional CISs or two unidirectional CISs. Additionally or alternatively, although described using two recipients, the description is similarly applicable to additional recipients associated with the additional CIS (e.g., three recipients, four recipients, etc.). Alternatively, although described using two recipient devices, the CIS may be associated with the same recipient device (e.g., a headphone device that uses a first CIS for a left earbud and a second CIS for a right earbud).
[0054] The CIS with recipients 120a and 120b may be logically organized into a connected isochronous group (CIG). Figure 3 As shown in , the initiator 110 may send data 301a (e.g., in the form of a PDU) to the recipient 120a during the first sub-event within the CIG event. Because the CIS associated with the recipient 120a is bidirectional, the recipient 120a may respond to the PDU from the initiator 110 with data 305a (e.g., in the form of a PDU) during the first sub-event. Therefore, the initiator 110 may send an acknowledgement (ACK) PDU 307a based on receiving the data 305a (or send a negative acknowledgement (NACK) PDU based on not receiving the data 305a). Alternatively, the initiator 110 may prohibit sending the ACK 307a (or NACK PDU), but allow the recipient 120a to enter the synchronization timeout mode.
[0055] In some aspects, when the initiator 110 does not have data to send in the first sub-event, the initiator 110 may still send an empty PDU to the recipient 120a to provide the recipient 120a with an opportunity to reply with data. Alternatively, when the recipient 120a does not have data to send in the first sub-event, the recipient 120a may send an ACK PDU based on receiving the data 301a (or send a NACK PDU based on not receiving the data 301a) in place of the data 305a. For example, the recipient 120a may send an ACK PDU (or a NACK PDU) similarly to that described for the recipient 120b.
[0056] Thus, the CIS associated with the recipient 120a may be characterized by an equal time interval 303 between the start of a first sub-event for the CIS within one CIG event and the start of a corresponding sub-event for the CIS within a subsequent CIG event. When data 301a is not received during the first sub-event, the initiator 110 will attempt to resend the data 301a in one or more subsequent sub-events until the data 301a is received (or until the CIG event ends, whichever is earlier). At the end of the CIG event, the initiator 110 may discard the data 301a (e.g., when the refresh timeout for the data 301a is set to 1, such as 1 CIG event). Thus, if Figure 3 As shown in , the initiator 110 may send data 301b during the first sub-event of the subsequent CIG event. Alternatively, the initiator 110 may resend the data 301a during one or more sub-events of the subsequent CIG event (e.g., when the refresh timeout for the data 301a is greater than 1, such as 2 CIG events, 3 CIG events, etc.). Similarly, the recipient 120a may send data 305b or may resend data 305a during the subsequent CIG event. Therefore, the initiator 110 may send an ACK PDU 307b based on receiving the data 305b or the resent data 305a (or send a NACK PDU based on not receiving the data 305b or the resent data 305a).
[0057] like Figure 3 As further shown in FIG. 1 , the initiator 110 may send data 309a (e.g., in the form of a PDU) to the recipient 120b during a second sub-event within the CIG event. Because the CIS associated with the recipient 120b is unidirectional, the recipient 120b may respond to the PDU from the initiator 110 with an ACK PDU 313a based on receiving the data 309a (or with a NACK PDU based on not receiving the data 309a).
[0058] Thus, the CIS associated with recipient 120b may be characterized by an equal time interval 311 between the start of a second sub-event for the CIS within one CIG event and the start of a corresponding sub-event for the CIS within a subsequent CIG event. When data 309a is not received during the second sub-event, initiator 110 will attempt to resend data 309a in one or more subsequent sub-events until data 309a is received (or until the CIG event ends, whichever is earlier). At the end of the CIG event, initiator 110 may discard data 309a (e.g., when the refresh timeout for data 309a is set to 1, such as 1 CIG event). Thus, if Figure 3 As shown in , the initiator 110 may send the data 309b during the second sub-event of the subsequent CIG event. Alternatively, the initiator 110 may resend the data 309a during one or more sub-events of the subsequent CIG event (e.g., when the refresh timeout for the data 309a is greater than 1, such as 2 CIG events, 3 CIG events, etc.). Therefore, the recipient 120b may send an ACK PDU 313b based on receiving the data 309b or the resent data 309a (or send a NACK PDU based on not receiving the data 309b or the resent data 309a).
[0059] As indicated above, Figure 3 Other examples can be found in the Figure 3 The content described is different.
[0060] Figure 4A 4 is a diagram illustrating an example 400 associated with a sequential packaging scheme for sub-events according to the present disclosure. Figure 4A As shown in , example 400 includes a first CIS (labeled “CIS 0”) between a first recipient (e.g., recipient 120a) and an initiator (e.g., initiator 110) and a second CIS (labeled “CIS 1”) between a second recipient (e.g., recipient 120b) and initiator 110. Although described using a bidirectional CIS, the description is equally applicable to a unidirectional CIS or a combination of a unidirectional and bidirectional CIS. Additionally or alternatively, although described using two recipients, the description is similarly applicable to additional recipients associated with the additional CIS (e.g., three recipients, four recipients, etc.). Alternatively, although described using two recipient devices, the CIS may be associated with the same recipient device (e.g., a headphone device that uses the first CIS for the left earbud and the second CIS for the right earbud).
[0061] like Figure 4AAs shown in , each CIG event of the first CIS includes a first number of sub-events (e.g., shown as three sub-events in example 400, each of which includes a transmission ("Tx") and a reception ("Rx")). Therefore, the duration associated with the first CIS event includes the sub-events associated with the first CIS event within the CIG event. In addition, the start of the initial sub-event associated with the first CIS serves as an anchor point within each CIG event. Therefore, the equal time interval 303 spans the anchor points in subsequent CIG events (e.g., CIG event x+1 after CIG event x, where x is an integer).
[0062] Similarly, each CIG event of the second CIS includes a second number of sub-events (e.g., shown as three sub-events in example 400, each of which includes Tx and Rx). Therefore, the duration associated with the second CIS event includes the sub-events associated with the second CIS event within the CIG event. In addition, the start of the initial sub-event associated with the second CIS serves as an anchor point within each CIG event. Therefore, the equal time interval 311 spans the anchor point in the subsequent CIG event (e.g., the CIG event count after CIG event x is 1, where x is an integer).
[0063] Because a CIG event includes all sub-events of a first CIS followed by all sub-events of a second CIS, example 400 is referred to as "sequential."
[0064] Figure 4B is a diagram illustrating example 450 associated with an interleaved packaging scheme for sub-events according to the present disclosure. Similar to example 400, example 450 includes a first CIS (labeled as "CIS 0") between a first recipient (e.g., recipient 120a) and an initiator (e.g., initiator 110) and a second CIS (labeled as "CIS1") between a second recipient (e.g., recipient 120b) and initiator 110. Although described using a bidirectional CIS, the description is equally applicable to a unidirectional CIS or a combination of a unidirectional and bidirectional CIS. Additionally or alternatively, although described using two recipients, the description is similarly applicable to additional recipients associated with the additional CIS (e.g., three recipients, four recipients, etc.). Alternatively, although described using two recipient devices, the CIS may be associated with the same recipient device (e.g., a headphone device that uses the first CIS for the left earbud and the second CIS for the right earbud).
[0065] like Figure 4BAs shown in , each CIG event of the first CIS includes a first set of sub-events (e.g., shown as three sub-events in example 450, each of which includes Tx and Rx). Therefore, the duration associated with the first CIS event includes the sub-events associated with the first CIS event within the CIG event. In addition, the start of the initial sub-event associated with the first CIS serves as an anchor point within each CIG event. Therefore, the equal time interval 303 spans the anchor point in the subsequent CIG event (e.g., the CIG event count after CIG event x is 1, where x is an integer).
[0066] Similarly, each CIG event of the second CIS includes a second set of sub-events (e.g., shown as three sub-events in example 450, each of which includes Tx and Rx). Therefore, the duration associated with the second CIS event includes the sub-events associated with the second CIS event within the CIG event. In addition, the start of the initial sub-event associated with the second CIS acts as an anchor point within each CIG event. Therefore, the equal time interval 311 spans the anchor point in the subsequent CIG event (e.g., the CIG event count after CIG event x is 1, where x is an integer).
[0067] Because the first set of sub-events of the first CIS alternates with the second set of sub-events of the second CIS, example 450 is referred to as "interleaved."
[0068] Some of the techniques and devices described herein enable one or more sub-events within an event (e.g., a CIG event) to be shared between two or more streams (e.g., CIS). As a result, the bandwidth of the CIS is used more compactly, which allows other devices (e.g., WiFi devices or other contention-based protocol devices) and / or other Bluetooth-based services (e.g., low energy (LE) asynchronous connectionless (ACL) links and / or basic rate / enhanced data rate (BR / EDR) links, etc.) to more efficiently utilize the unoccupied bandwidth of the CIS. As a result, latency for other devices is reduced, power and processing resources are saved at other devices, and throughput to other devices and / or other services (e.g., WiFi) is increased. In addition, because sub-events can be shared without modifying the behavior of the recipient device, the initiator device can improve bandwidth usage without requiring software and hardware changes at the recipient device.
[0069] Some techniques and apparatuses described herein further enable a recipient device to activate a low power mode based on a schedule by an initiator device within one or more sub-events shared (e.g., with a different portion of the recipient device and / or one or more additional recipient devices). Thus, power is saved at the recipient device.
[0070] As indicated above, FIG. 4A to FIG. 4B Other examples can be found in the FIG. 4A to FIG. 4B The content described is different.
[0071] Figure 5A is a diagram illustrating an example 500 associated with sharing sub-events between isochronous streams according to the present disclosure. Figure 5A As shown in , example 500 includes a CIG event 501, which includes eight sub-events. For example, the number of sub-events (NSE) variables associated with each CIS stream can be set to five. Although described in conjunction with a total of eight sub-events, the description is similarly applicable to fewer sub-events (e.g., seven sub-events, six sub-events, etc.) or additional sub-events (e.g., nine sub-events, ten sub-events, etc.). In addition, although described in conjunction with two CIS streams with an equal number of sub-events, the description is similarly applicable to CIS streams with different numbers of sub-events. Alternatively, although described using two recipient devices, the CIS may be associated with the same recipient device (e.g., a headphone device that uses a first CIS for a left earbud and a second CIS for a right earbud).
[0072] like Figure 5A As shown in , the first CIS 503a is associated with sub-event 505a, sub-event 505b, sub-event 505c, sub-event 505d, and sub-event 505e. In example 500, sub-events 505a, 505b, and 505c are within a portion of CIG event 501 that is not shared with the second CIS 503b. Therefore, the initiator device (e.g., initiator 110) can use the first CIS 503a to send a PDU to the first recipient device (e.g., recipient 120a) during sub-event 505a, sub-event 505b, or sub-event 505c.
[0073] Similarly, the second CIS 503b is associated with sub-event 507a, sub-event 507b, sub-event 507c, sub-event 507d, and sub-event 507e. In example 500, sub-events 507c, 507d, and 507e are within a portion of CIG event 501 that is not shared with the first CIS 503a. Therefore, the initiator 110 can use the second CIS 503b to send a PDU to a second recipient device (e.g., recipient 120b) during sub-event 507c, sub-event 507d, or sub-event 507e.
[0074] like Figure 5AAs further shown in FIG. 5 , sub-events 505d and 505e of the first CIS 503a and sub-events 507a and 507b of the second CIS 503b are within a portion of the CIG event 501 that is shared between the first CIS 503a and the second CIS 503b. Therefore, the initiator 110 can use the first CIS 503a to send a PDU to the first recipient 120a or use the second CIS 503b to send a PDU to the second recipient 120b during sub-events 505d / 507a or sub-events 505e / 507b.
[0075] Although described in conjunction with some sub-events that are not shared, the description similarly applies to CIG events in which all sub-events are shared between the first CIS and the second CIS (e.g., as described in conjunction with Figure 6B described above).
[0076] In some aspects, the initiator 110 may select which CIS (e.g., the first CIS 503a or the second CIS 503b) to provide in a shared sub-event (e.g., sub-event 505d / 507a or sub-event 505e / 507b) based on which CIS has a buffered PDU that contains a closer refresh point. For example, the first CIS 503a may have a buffered PDU that does not time out until a subsequent CIG event, while the second CIS 503b has a buffered PDU that times out in the CIG event 501 (e.g., at the end of the CIG event 501). Therefore, the initiator 110 may send a buffered PDU for the second CIS 503b in sub-event 507a (or sub-event 507b). Similarly, the second CIS 503b may have a buffered PDU that does not time out until a subsequent CIG event, while the first CIS 503a has a buffered PDU that times out in the CIG event 501 (e.g., at the end of the CIG event 501). Thus, the initiator 110 may send the buffered PDU for the first CIS 503a in the sub-event 505d (or the sub-event 505e). In the case of a tie (e.g., equal refresh points for the buffered PDUs), the initiator 110 may randomly (or at least pseudo-randomly) select between the first CIS 503a and the second CIS 503b, or may provide the first CIS 503a and the second CIS 503b in a polling manner (e.g., alternating between the first CIS 503a and the second CIS 503b in a sub-event whenever a refresh point tie occurs). Alternatively, in the case of a tie, the initiator 110 may select between the first CIS 503a and the second CIS 503b based on historical data. For example, when the number of NACK PDUs received using the first CIS 503a satisfies the NACK threshold and / or when the RSRP and / or another measurement associated with the signal strength of the first CIS 503a satisfies the signal strength threshold, the initiator 110 may select the first CIS 503a, etc. Similarly, when the number of NACK PDUs received using the second CIS 503b satisfies the NACK threshold and / or when the RSRP and / or another measurement associated with the signal strength of the second CIS 503b satisfies the signal strength threshold, the initiator 110 may select the second CIS 503b, etc.
[0077] Alternatively, the initiator 110 may provide the CIS in a round-robin fashion across all shared sub-events. Thus, in example 500, the initiator 110 may provide the first CIS 503a in sub-event 505d, the second CIS 503b in sub-event 507b, and so on across subsequent shared sub-events. Alternatively, the initiator 110 may select randomly (or at least pseudo-randomly) between the CISs across all shared sub-events.
[0078] Alternatively, the initiator 110 may provide CIS in a polling manner or randomly (or at least pseudo-randomly) for an initial number of shared sub-events, and then provide CIS for subsequent shared sub-events based on historical data (e.g., as described above). The initial number of shared sub-events may be programmed (and / or otherwise preconfigured) into the initiator 110, or may be dynamically determined (e.g., based on the number of CIS in the CIG and / or the amount of data sent in all CIS and / or across each CIS, etc.). Alternatively, the initiator 110 may provide CIS in a polling manner or randomly (or at least pseudo-randomly) for an initial number of shared sub-events, and then provide CIS for subsequent shared sub-events based on the closest refresh point (e.g., as described above). Similarly, the initiator 110 may provide CIS based on historical data for the initial number of shared sub-events (e.g., as described above) and / or the closest refresh point (e.g., as described above), and then provide CIS for subsequent shared sub-events in a polling manner or randomly (or at least pseudo-randomly).
[0079] Figure 5B 5 is a diagram illustrating an example 510 associated with sharing sub-events between isochronous streams according to the present disclosure. Figure 5B As shown in , example 510 includes CIG event 511, which includes eleven sub-events. For example, the NSE variable associated with each CIS stream can be set to five. Although described in conjunction with a total of eleven sub-events, the description is similarly applicable to fewer sub-events (e.g., ten sub-events, nine sub-events, etc.) or additional sub-events (e.g., twelve sub-events, thirteen sub-events, etc.). In addition, although described in conjunction with all CIS streams having an equal number of sub-events, the description is similarly applicable to two or more CIS streams having different numbers of sub-events.
[0080] like Figure 5B As shown in , the first CIS 513a is associated with sub-event 515a, sub-event 515b, sub-event 515c, sub-event 515d, and sub-event 505e. In example 510, sub-events 515a, 515b, and 515c are within a portion of CIG event 501 that is not shared with the second CIS 513b or the third CIS 513c. Therefore, the initiator device (e.g., initiator 110) can use the first CIS 513a to send a PDU to the first recipient device (e.g., recipient 120a) during sub-event 515a, sub-event 515b, or sub-event 515c.
[0081] Similarly, the second CIS 513b is associated with sub-event 517a, sub-event 517b, sub-event 517c, sub-event 517d, and sub-event 517e. In example 510, sub-event 517c is within a portion of CIG event 511 that is not shared with the first CIS 513a or the third CIS 513c. Therefore, the initiator 110 can use the second CIS 513b to send a PDU to a second recipient device (e.g., recipient 120b) during sub-event 517c.
[0082] Similarly, the third CIS 513c is associated with sub-event 519a, sub-event 519b, sub-event 519c, sub-event 519d, and sub-event 519e. In example 510, sub-events 519c, 519d, and 519e are within a portion of CIG event 511 that is not shared with the first CIS 513a or the second CIS 513b. Therefore, the initiator 110 can use the third CIS 513c to send a PDU to a third recipient device (e.g., recipient 120c) during sub-event 519c, sub-event 519d, or sub-event 519e.
[0083] like Figure 5B As further shown in FIG. 5 , sub-events 515d and 515e of the first CIS 513a and sub-events 517a and 517b of the second CIS 513b are within a portion of the CIG event 511 shared between the first CIS 513a and the second CIS 513b. Therefore, the initiator 110 can use the first CIS 513a to send a PDU to the first recipient 120a or use the second CIS 513b to send a PDU to the second recipient 120b during sub-events 515d / 517a or sub-events 515e / 517b.
[0084] Similarly, sub-events 517d and 517e of the second CIS 513b and sub-events 519a and 519b of the third CIS 513c are within a portion of the CIG event 511 shared between the second CIS 513b and the third CIS 513c. Therefore, the initiator 110 can use the second CIS 513b to send a PDU to the second recipient 120b or use the third CIS 513c to send a PDU to the third recipient 120c during sub-events 517d / 519a or sub-events 517e / 519b.
[0085] Although described using sub-events shared between the first CIS 513a and the second CIS 513b and sub-events shared between the second CIS 513b and the third CIS 513c, the description additionally or alternatively applies to sub-events shared between the first CIS 513a and the third CIS 513c and / or sub-events shared between the first CIS 513a, the second CIS 513b and the third CIS 513c.
[0086] Figure 5C 5 is a diagram illustrating example 520 associated with sharing sub-events between isochronous streams according to the present disclosure. Example 520 is similar to example 510, except that the number of sub-events shared by the second CIS 513b and the third CIS 513c is different from the number of sub-events shared by the first CIS 513a and the second CIS 513b. In example 520, the second CIS 513b and the third CIS 513c share one sub-event 517e / 519a, while the first CIS 513a and the second CIS 513b share two sub-events 515d / 517a and 515e / 517b. Other examples may include additional sub-events shared between the second CIS 513b and the third CIS 513c, additional sub-events shared between the first CIS 513a and the second CIS 513b, or one sub-event shared between the first CIS 513a and the second CIS 513b.
[0087] In examples 510 and 520, the initiator 110 may schedule PDUs in a shared sub-event similar to that described above in conjunction with the two CISs of example 500. Although described using two or three CISs, the description is similarly applicable to additional CISs (e.g., four CISs, five CISs, etc.) that at least partially overlap within a CIG event. In addition, although described using a CIS included in a CIG, the description is similarly applicable to a CIS that is not explicitly included in a CIG.
[0088] Figure 5D5 is a diagram illustrating example 530 associated with sharing sub-events between isochronous streams according to the present disclosure. Example 530 is similar to example 500, except that the first CIS 533a and the second CIS 533b are associated with different CIG events (e.g., CIG event 531a and CIG event 531b, respectively). In example 530, the first CIS 533a and the second CIS 532b share two sub-events 535d / 537a and 535e / 537b, while the first CIS 533a and the second CIS 533b. Other examples may include additional sub-events shared between the first CIS 533a and the second CIS 533b or a sub-event shared between the first CIS 533a and the second CIS 533b. Therefore, the CIS may be associated with different CIGs and / or different recipient devices, but still include shared sub-events, as long as the CIG is associated with the same initiator device.
[0089] By using such as combining FIG. 5A to FIG. 5D The described technology, one or more sub-events within an event (e.g., a CIG event) are shared between two or more streams (e.g., CIS). Therefore, the bandwidth of the CIS is used more compactly, which allows other devices (e.g., WiFi devices or other contention-based protocol devices) to more effectively utilize the unoccupied bandwidth of the CIS. Therefore, the latency of other devices is reduced, and power and processing resources are saved at other devices. In addition, because sub-events can be shared without modifying the behavior of the recipient device, the initiator device can improve bandwidth usage without requiring software and hardware changes at the recipient device.
[0090] As indicated above, FIG. 5A to FIG. 5D Other examples can be found in the FIG. 5A to FIG. 5D The content described is different.
[0091] Fig. 6A 6 is a diagram illustrating an example 600 associated with configuring a shared sub-event between isochronous streams according to the present disclosure. Fig. 6A As shown in , example 600 includes a CIG event having a length 601 of ten sub-events. In addition, the CIG includes at least two CISs, each of which has a length 603 of eight sub-events. Therefore, in order to configure the amount of overlap between CISs (e.g., as combined FIG. 5A to FIG. 5C As described above, an initiator device (eg, initiator 110) may use offset 605. In example 600, offset 605 is two sub-events, such that each CIS includes two sub-events that are not shared with another CIS.
[0092] Figure 6B650 is a diagram illustrating an example 650 associated with configuring shared sub-events between isochronous streams according to the present disclosure. Example 650 is similar to example 600, but includes a zero offset. Therefore, all sub-events within a CIG event are shared so that each CIS has a length 653 of ten sub-events (i.e., equal to the length 601 of the CIG event).
[0093] As indicated above, FIG. 6A to FIG. 6B Other examples can be found in the FIG. 6A to FIG. 6B The content described is different.
[0094] Figure 7 is a diagram illustrating an example 700 associated with a PDU structure for an isochronous flow according to the present disclosure. Figure 7 As shown in , example 700 includes CIG event 701, which includes eight sub-events. For example, the NSE variable associated with each CIS stream can be set to five. Although described in conjunction with a total of eight sub-events, the description is similarly applicable to fewer sub-events (e.g., seven sub-events, six sub-events, etc.) or additional sub-events (e.g., nine sub-events, ten sub-events, etc.). In addition, although described in conjunction with two CIS streams having an equal number of sub-events, the description is similarly applicable to CIS streams having different numbers of sub-events.
[0095] like Figure 7 As shown in , the first CIS 703a is associated with sub-event 705a, sub-event 705b, sub-event 705c, sub-event 705d, and sub-event 705e. Similar to example 500, sub-events 705a, 705b, and 705c in example 700 are within a portion of CIG event 701 that is not shared with the second CIS 703b. Therefore, the initiator device (e.g., initiator 110) can use the first CIS 703a to send a PDU to the first recipient device (e.g., recipient 120a) during sub-event 705a, sub-event 705b, or sub-event 705c.
[0096] Similarly, the second CIS 703b is associated with sub-event 707a, sub-event 707b, sub-event 707c, sub-event 707d, and sub-event 707e. Similar to example 500, sub-events 707c, 707d, and 707e in example 700 are within a portion of CIG event 701 that is not shared with the first CIS 703a. Therefore, the initiator 110 can use the second CIS 703b to send a PDU to a second recipient device (e.g., recipient 120b) during sub-event 707c, sub-event 707d, or sub-event 707e.
[0097] Although described using two recipient devices, the first CIS 703a and the second CIS 703b may be associated with the same recipient device (eg, a headphone device using the first CIS 703a for the left earbud and the second CIS 703b for the right earbud).
[0098] like Figure 7 As further shown in , sub-events 705d and 705e of the first CIS 703a and sub-events 707a and 707b of the second CIS 703b are within a portion of the CIG event 701 that is shared between the first CIS 703a and the second CIS 703b. Therefore, the initiator 110 may use the first CIS 703a to send the PDU to the first recipient 120a during sub-event 705d or sub-event 705e. Alternatively, the initiator 110 may use the second CIS 703b to send the PDU to the second recipient 120b during sub-event 707a or sub-event 707b. When sending using the second CIS 703b, the initiator 110 applies an offset 709 (e.g., determined in microseconds (μs)) relative to when sending using the first CIS 703a. Therefore, the PDU for the second CIS 703b may start later in the shared sub-event than the PDU for the first CIS 703a. The initiator 110 may schedule the PDUs in the shared sub-event, such as in conjunction with FIG. 5A to FIG. 5C described.
[0099] The offset 709 may allow the initiator 110 to perform a switch from the first CIS 703a to the second CIS 703b (or in some implementations, from the second CIS 703b to the first CIS 703a). For example, the initiator 110 may wait to receive an ACK PDU (or NACK PDU) for a PDU sent using the first CIS 703a before deciding whether to use sub-event 705d for the first CIS 703a or sub-event 707a for the second CIS 703b. Thus, the initiator 110 may use the offset 709 to apply changes to hardware (e.g., an antenna, a demodulator, and / or another similar type of hardware) to use the second CIS 703b for transmission instead of the first CIS 703a after receiving the ACK PDU associated with the first CIS 703a. Alternatively, as in combination with Fig. 9 As described, when no PDU is received using the first CIS 703a at the beginning of sub-event 705d, the same recipient device listening to both the first CIS 703a and the second CIS 703b can use offset 709 to apply changes to hardware (e.g., an antenna, a demodulator, and / or another similar type of hardware) to listen to the second CIS 703b at the beginning of sub-event 707a.
[0100] Although described in conjunction with some sub-events that are not shared, the description similarly applies to CIG events in which all sub-events are shared between the first CIS and the second CIS (e.g., as described in conjunction with Figure 6B Additionally or alternatively, although described using two CISs, the description applies similarly to additional CISs (e.g., three CISs, four CISs, etc.) that share sub-events within a CIG event. For example, the PDU for the third CIS may be further offset in time relative to the PDU for the first CIS and the PDU for the second CIS. Alternatively, the PDU for the third CIS may be aligned with the PDU for the second CIS, but still offset from the PDU for the first CIS, or may be aligned with the PDU for the first CIS and therefore offset from the PDU for the second CIS. In addition, although described using a CIS included in a CIG, the description applies similarly to a CIS that is not explicitly included in the CIG.
[0101] As indicated above, Figure 7 Other examples can be found in the Figure 7 The content described is different.
[0102] Fig. 8A 8 is a diagram illustrating an example 800 associated with power conservation during a shared sub-event between isochronous streams according to the present disclosure. Fig. 8A As shown in , example 800 includes CIG event 801, which includes eight sub-events. Figure 6B As described, all sub-events are shared between the first CIS 803a and the second CIS 803b. Although described in conjunction with a total of eight sub-events, the description is similarly applicable to fewer sub-events (e.g., seven sub-events, six sub-events, etc.) or additional sub-events (e.g., nine sub-events, ten sub-events, etc.). In addition, although described in conjunction with two CIS streams with an equal number of sub-events, the description is similarly applicable to CIS streams with different numbers of sub-events.
[0103] like Fig. 8AAs shown in FIG. 1 , a first recipient device (e.g., recipient 120a) associated with a first CIS 803a may know that a shared sub-event is divided into a dedicated area 809a associated with the first CIS 803a, a dedicated area 809b associated with a second CIS 803b, and an overlap area 811 shared by the first CIS 803a and the second CIS 803b. For example, the recipient 120a and the initiator 110 may use a sharing formula (or another algorithm) to determine the dedicated areas 809a and 809b. Alternatively, the initiator 110 may send a control PDU to the recipient 120a to indicate the dedicated areas 809a and 809b. Thus, even though all sub-events are shared between the first CIS 803a and the second CIS 803b, the recipient 120a may activate a low power mode during sub-events 807a and 807b within the dedicated region 809b (e.g., by reducing the clocking speed of the processor and / or another hardware component and / or by powering off the antenna and / or another hardware component). Thus, the recipient 120a listens for PDUs associated with the CIS 803a during sub-events 805a and 805b in the dedicated region 809a and during sub-events 805c, 805d, 805e, and 805f in the overlap region 811. The initiator 110 may schedule the PDUs in the overlap region 811, as described in conjunction with FIG. 5A to FIG. 5C described.
[0104] Similarly, a second recipient device (e.g., recipient 120b) associated with the second CIS 803b may know that a shared sub-event is divided into a dedicated area 809a associated with the first CIS 803a, a dedicated area 809b associated with the second CIS 803b, and an overlap area 811 shared by the first CIS 803a and the second CIS 803b. For example, the recipient 120b and the initiator 110 may use a sharing formula (or another algorithm) to determine the dedicated areas 809a and 809b. Alternatively, the initiator 110 may send a control PDU to the recipient 120b to indicate the dedicated areas 809a and 809b. Therefore, even if all sub-events are shared between the first CIS 803a and the second CIS 803b, the recipient 120b may activate a low power mode during the sub-events 805a and 805b within the dedicated area 809a. Therefore, recipient 120b listens for PDUs associated with CIS 803b during sub-events 807a and 807b in dedicated region 809b and during sub-events 807c, 807d, 807e, and 807f in overlap region 811. Initiator 110 may schedule PDUs in overlap region 811, such as in conjunction with FIG. 5A to FIG. 5C described.
[0105] In the example 800, sub-events 805a and 805b associated with the first CIS 803a are sequential with respect to sub-events 807a and 807b associated with the second CIS 803b. Figure 8B is a diagram illustrating example 850 associated with power saving during shared sub-events between isochronous streams according to the present disclosure. Example 850 is similar to example 800, but sub-events 805a and 805b associated with a first CIS 803a are interleaved with sub-events 807a and 807b associated with a second CIS 803b.
[0106] Although described using two recipient devices, the CIS may be associated with the same recipient device (e.g., a headphone device using the first CIS 803a for the left earbud and the second CIS 803b for the right earbud). In addition, although described using a CIS included in a CIG, the description similarly applies to a CIS not explicitly included in a CIG.
[0107] As indicated above, FIG. 8A to FIG. 8B Other examples can be found in the FIG. 8A to FIG. 8B The content described is different.
[0108] Fig. 9 is a diagram illustrating an example 900 associated with a PDU structure for an isochronous flow according to the present disclosure. Fig. 9 As shown in , an initiator device (e.g., initiator 110) may send (e.g., to a recipient device such as recipient 120) a signal encoding a data structure having a preamble 901 (e.g., including one or two octets), an access address 903 (e.g., four octets), an isochronous PDU 905 (e.g., between two octets and 257 octets, or in another example, between two octets and 1026 octets), and a cyclic redundancy check (CRC) 907 (e.g., three octets). Fig. 9 As further shown in , the isochronous PDU 905 may include a header 909 (e.g., sixteen bits) and a payload 911 (e.g., between zero octets for a null PDU and 251 octets for a payload such as a digitally encoded audio signal). In some aspects, the isochronous PDU 905 may include a message integrity check (MIC) 913 (e.g., 32 bits).
[0109] Typically, each CIS is associated with a unique access address. Thus, initiator 110 may send a PDU during a shared sub-event (eg, as described herein) and indicate which CIS the PDU is intended for by encoding the access address associated with the CIS in the data structure of the PDU.
[0110] In some aspects, the shared sub-events may be associated with different CISs explicitly (e.g., as indicated by the initiator 110) or implicitly (e.g., by a rule, such as when (number of SEs)%(number of CISs)=0). For example, a first shared sub-event may be associated with a first CIS, a second shared sub-event may be associated with a second CIS, and so on. In another example, a first set of shared sub-events may be associated with a first CIS, a second set of subsequent sub-events may be associated with a second CIS, and so on. Thus, the initiator 110 may assign a secondary access address (different from the primary access address associated with the first CIS and the primary access address associated with the second CIS) to the first CIS, the secondary access address indicating when a PDU is sent to the first CIS in a shared sub-event that is not associated with the first CIS. Similarly, the initiator 110 may assign a secondary access address (different from the primary access address associated with the first CIS and the primary access address associated with the second CIS) to the second CIS, the secondary access address indicating when a PDU is sent to the second CIS in a shared sub-event that is not associated with the second CIS.
[0111] Additionally or alternatively, the first CIS and the second CIS may share an access address. Thus, when a shared sub-event is associated with a CIS of a recipient (and the PDU includes a shared access address) or when the PDU includes a secondary access address of the CIS instead of a shared access address (e.g., as described above), the recipient may determine that the PDU sent in the shared sub-event is intended for the recipient. Additionally or alternatively, the recipient may determine that the PDU sent in the shared sub-event is intended for the recipient based on one or more additional bits included in the header 909. In an example with two CISs, when the PDU is for the first CIS, one additional bit may be set to "1", and when the PDU is for the second CIS, one additional bit may be set to "0". In an example with four CISs, two additional bits may indicate the CIS (e.g., by using "00" for the first CIS, "01" for the second CIS, "10" for the third CIS, and "11" for the fourth CIS). Additionally or alternatively, the initiator 110 may indicate which CIS the PDU is intended for using the MIC 913. Thus, based on the PDUs that pass the MIC test, a recipient may determine that the PDUs sent in a shared sub-event are intended for that recipient.
[0112] Additionally or alternatively, the initiator 110 may associate the PDU intended for the second CIS with a time offset relative to the PDU intended for the first CIS. Figure 7 As described, PDUs intended for the second CIS may be sent during a shared sub-event at a later time than PDUs intended for the first CIS would be sent during the same shared sub-event.
[0113] Although described using two CISs, the description is similarly applicable to additional CISs (e.g., three CISs, four CISs, etc.) of sub-events within a shared CIG event. Other aspects may be used for only two CISs. For example, the initiator 110 may associate the first CIS with a CRC and the second CIS with the inversion of the CRC. Therefore, the recipient may determine that the PDU sent in the shared sub-event is intended for the recipient based on whether the CRC is inverted. In addition, although described using a CIS included in a CIG, the description is similarly applicable to a CIS that is not explicitly included in the CIG.
[0114] In some aspects (e.g., for a headphone device as a recipient device), two CISs may be used by the same recipient device, as compared to earbuds (whose CISs are used by different recipient devices). For a single recipient device, the same access address may be used for both CISs, as described above, where one or more techniques as described herein are used to distinguish the CISs. Additionally, as described in conjunction with Figure 7 As described, a single recipient device may use an offset to allow the same hardware component (eg, the same antenna, the same demodulator, and / or another similar type of hardware) to listen to both CISs using the offset.
[0115] As indicated above, Fig. 9 Other examples can be found in the Fig. 9 Different from what is described.
[0116] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by an initiator device according to the present disclosure. The example process 1000 is a diagram in which an initiator device (e.g., initiator device 110 and / or Fig.12 An example of a device 1200) performing operations associated with using a shared sub-event for PDUs associated with different flows.
[0117] like Fig.10 As shown in , in some aspects, process 1000 may include sending a PDU associated with a first stream during a first sub-event within a portion of an event shared between the first stream and a second stream (1010). For example, an initiator device (e.g., using Fig.12 The communication manager 150 and / or sending component 1204 depicted in FIG. 1 may send a PDU associated with the first stream during a first sub-event within a portion of an event shared between the first stream and a second stream, as described herein.
[0118] Additionally or alternatively, and if Fig.10As further shown in the process 1000, the process 1000 may include sending the PDU associated with the second flow during a second sub-event within the portion of the event shared between the first flow and the second flow (1020). For example, the initiator device (e.g., using the communication manager 150 and / or the sending component 1204) may send the PDU associated with the second flow during the second sub-event within the portion of the event shared between the first flow and the second flow, as described herein.
[0119] Process 1000 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.
[0120] In a first aspect, the first flow includes a first CIS within a CIG, and the second flow includes a second CIS within the CIG.
[0121] In a second aspect, either alone or in combination with the first aspect, process 1000 also includes sending (e.g., using communication manager 150 and / or sending component 1204) a PDU associated with the third stream during a third sub-event within a portion of the event shared between the third stream and at least one of the first stream or the second stream.
[0122] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1000 also includes sending (e.g., using communications manager 150 and / or sending component 1204) a PDU associated with the first stream during a third sub-event within a portion of the event that is not shared with the second stream.
[0123] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1000 also includes sending (e.g., using communication manager 150 and / or sending component 1204) a PDU associated with the second stream during a third sub-event within a portion of the event that is not shared with the first stream.
[0124] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, at least one of the first sub-event or the second sub-event is shifted in time when used for the second stream relative to when used for the first stream.
[0125] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the portion of the event shared between the first stream and the second stream is based at least in part on an offset value.
[0126] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 1000 further comprises determining to send (e.g., using) at least in part based on a refresh point associated with the PDU associated with the first flow. Fig.12 The communication manager 150 and / or determining component 1208 depicted in FIG. 10A ) is configured to determine the PDU associated with the first flow.
[0127] In an eighth aspect, either alone or in combination with one or more of aspects one to seven, process 1000 further comprises determining to send (e.g., using communications manager 150 and / or determining component 1208) the PDU associated with the first stream based at least in part on a polling schedule associated with at least the first stream and the second stream.
[0128] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the first flow is associated with a first access address and the second flow is associated with a second access address.
[0129] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the first sub-event is associated with the second flow, and the PDU associated with the first flow includes a third access address.
[0130] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the second sub-event is associated with the first flow, and the PDU associated with the second flow includes a third access address.
[0131] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the first flow and the second flow are associated with the same access address.
[0132] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the PDU associated with the second flow includes one or more bits in a header indicating that the PDU is for the second flow.
[0133] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the PDU associated with the second flow is associated with a MIC to indicate that the PDU is for the second flow.
[0134] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the PDU associated with the second flow is associated with a reverse CRC to indicate that the PDU is for the second flow.
[0135] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the PDU associated with the second flow is associated with a time offset relative to the PDU associated with the second flow.
[0136] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more of the blocks in the process 1000 may be performed in parallel.
[0137] Fig.11 1 is a diagram illustrating an example process 1100 performed, for example, by a recipient device according to the present disclosure. The example process 1100 is a diagram in which a recipient device (e.g., recipient device 120 and / or Fig.13 An example of a device 1300) performing operations associated with using a shared sub-event for PDUs associated with different flows.
[0138] like Fig.11 As shown in , in some aspects, process 1100 may include activating a low power mode during one or more first sub-events within an event shared between a second stream and a first stream for the recipient device (block 1110). For example, a recipient device (e.g., using Fig.13 The communication manager 140 and / or power management component 1308 depicted in FIG. 1 may activate a low power mode during one or more first sub-events within an event shared between a second stream and a first stream for a recipient device, as described herein.
[0139] like Fig.11 As further shown in FIG. 1 , in some aspects, process 1100 may include listening for PDUs associated with the first flow during one or more second sub-events within the event (block 1120). For example, a recipient device (e.g., using Fig.13 The communication manager 140 and / or receiving component 1302 depicted in FIG. 1 may listen for PDUs associated with the first flow during one or more second sub-events within the event, as described herein.
[0140] 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.
[0141] In a first aspect, the first flow includes a first CIS within a CIG, and the second flow includes a second CIS within the CIG.
[0142] In a second aspect, alone or in combination with the first aspect, the one or more second sub-events are associated with the recipient device and are sequential with respect to the one or more first sub-events.
[0143] In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more second sub-events are associated with the recipient device and interleaved with the one or more first sub-events.
[0144] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the second flow is associated with the recipient device.
[0145] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the second flow is associated with an additional recipient device.
[0146] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be performed in parallel.
[0147] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication. Apparatus 1200 may be an initiator device, or an initiator device may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a recipient device or another wireless communication device) using receiving component 1202 and transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 150. Communication manager 150 may include a determining component 1208, among other things.
[0148] In some aspects, the apparatus 1200 may be configured to perform Figure 5A , Figure 5B , Figure 5C , Fig. 6A , Figure 6B , Figure 7 , Fig. 8A , Figure 8B and Fig. 9 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more of the processes described herein (such as Fig.10 In some aspects, Fig.12The device 1200 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more of the components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.
[0149] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described initiator devices.
[0150] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described initiator device. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.
[0151] In some aspects, the sending component 1204 can send the PDU associated with the first stream during a first sub-event within a portion of the event shared between the first stream and the second stream (e.g., to a first recipient device). Additionally or alternatively, the sending component 1204 can send the PDU associated with the second stream during a second sub-event within the portion of the event shared between the first stream and the second stream (e.g., to a second recipient device).
[0152] In some aspects, sending component 1204 may additionally send a PDU associated with the third stream (e.g., to a third recipient device) during a third sub-event within a portion of the event shared between the third stream and at least one of the first stream or the second stream.
[0153] Additionally or alternatively, the sending component 1204 can send the PDU associated with the first stream during a third sub-event within a portion of the event that is not shared with the second stream (e.g., to the first recipient device). Additionally or alternatively, the sending component 1204 can send the PDU associated with the second stream during a third sub-event within a portion of the event that is not shared with the first stream (e.g., to the second recipient device).
[0154] In some aspects, determining component 1208 may determine to send the PDU associated with the first stream based at least in part on a refresh point associated with the PDU associated with the first stream. Additionally or alternatively, determining component 1208 may determine to send the PDU associated with the first stream based at least in part on a polling schedule associated with at least the first stream and the second stream. Determining component 1208 may include combining Figure 2 A transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof of the described initiator device.
[0155] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The illustrated set (one or more) of components may be described as being executable by Fig.12 Another group of components shown performs one or more functions.
[0156] Fig.131 is a diagram of an example apparatus 1300 for wireless communication. Apparatus 1300 may be a recipient device, or a recipient device may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a transmitting component 1304 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as an initiator device or another wireless communication device) using receiving component 1302 and transmitting component 1304. As further shown, apparatus 1300 may include a communication manager 140. Communication manager 140 may include a power management component 1308, among other things.
[0157] In some aspects, the apparatus 1300 may be configured to perform Figure 5A , Figure 5B , Figure 5C , Fig. 6A , Figure 6B , Figure 7 , Fig. 8A , Figure 8B and Fig. 9 Additionally or alternatively, the apparatus 1300 may be configured to perform one or more of the processes described herein (such as Fig.11 In some aspects, Fig.13 The device 1300 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more of the components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.
[0158] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1300. In some aspects, the receiving component 1302 may include combining Figure 2The recipient device described may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.
[0159] Transmit component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and may provide the generated communications to transmit component 1304 for transmission to device 1306. In some aspects, transmit component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1306. In some aspects, transmit component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described recipient device. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.
[0160] In some aspects, power management component 1308 may activate the low power mode during one or more first sub-events within an event shared between the second stream and the first stream for device 1300. Power management component 1308 may include in conjunction with Figure 2 The MIMO detector, receiving processor, controller / processor, memory, or combination thereof of the described recipient device. The second stream can be associated with the device 1300 or with an additional device (e.g., an additional recipient device). In addition, the receiving component 1302 can listen to the PDU associated with the first stream during one or more second sub-events within the event.
[0161] Fig.13 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.13 Two or more components shown may be implemented in a single component, or Fig.13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The illustrated set (one or more) of components may be described as being executable by Fig.13 Another group of components shown performs one or more functions.
[0162] The following provides an overview of some aspects of the disclosure:
[0163] Aspect 1: A method of wireless communication performed by an initiator device, the method comprising: sending a protocol data unit (PDU) associated with the first stream during a first sub-event within a portion of an event shared between the first stream and the second stream; sending a PDU associated with the second stream during a second sub-event within the portion of the event shared between the first stream and the second stream; or a combination thereof.
[0164] Aspect 2: The method according to aspect 1, wherein the first flow comprises a first connected isochronous flow (CIS) within a connected isochronous group (CIG), and the second flow comprises a second CIS within the CIG.
[0165] Aspect 3: According to the method described in any one of Aspects 1 to 2, the method also includes: sending a PDU associated with the third stream during a third sub-event within a portion of the event shared between the third stream and at least one of the first stream or the second stream.
[0166] Aspect 4: The method according to any one of aspects 1 to 3, further comprising: sending a PDU associated with the first flow during a third sub-event within a portion of the event that is not shared with the second flow.
[0167] Aspect 5: The method according to any one of aspects 1 to 4, further comprising: sending a PDU associated with the second flow during a third sub-event within a portion of the event that is not shared with the first flow.
[0168] Aspect 6: The method according to any one of aspects 1 to 5, wherein at least one of the first sub-event or the second sub-event is shifted in time when used for the second stream relative to when used for the first stream.
[0169] Aspect 7: The method according to any one of aspects 1 to 6, wherein the portion of the event shared between the first stream and the second stream is based at least in part on an offset value.
[0170] Aspect 8: The method according to any one of aspects 1 to 7, the method further comprising: determining to send the PDU associated with the first flow based at least in part on a refresh point associated with the PDU associated with the first flow.
[0171] Aspect 9: The method according to any one of aspects 1 to 8, the method further comprising: determining to send the PDU associated with the first flow based at least in part on a polling schedule associated with at least the first flow and the second flow.
[0172] Aspect 10: The method according to any one of aspects 1 to 9, wherein the first flow is associated with a first access address and the second flow is associated with a second access address.
[0173] Aspect 11: The method according to aspect 10, wherein the first sub-event is associated with the second flow, and the PDU associated with the first flow includes a third access address.
[0174] Aspect 12: The method according to any one of aspects 10 to 11, wherein the second sub-event is associated with the first flow, and the PDU associated with the second flow includes a third access address.
[0175] Aspect 13: The method according to any one of aspects 1 to 9, wherein the first flow and the second flow are associated with the same access address.
[0176] Aspect 14: The method according to any one of aspects 1 to 13, wherein the PDU associated with the second flow includes one or more bits in a header indicating that the PDU is for the second flow.
[0177] Aspect 15: The method according to any one of aspects 1 to 14, wherein the PDU associated with the second flow is associated with a message integrity check (MIC) to indicate that the PDU is for the second flow.
[0178] Aspect 16: The method according to any one of aspects 1 to 15, wherein the PDU associated with the second flow is associated with a reverse cyclic redundancy check (CRC) to indicate that the PDU is for the second flow.
[0179] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the PDU associated with the second flow is associated with a time offset relative to the PDU associated with the second flow.
[0180] Aspect 18: A method of wireless communication performed by a recipient device, the method comprising: activating a low power mode during one or more first sub-events within an event shared between a second stream and a first stream for the recipient device; and listening to a protocol data unit (PDU) associated with the first stream during one or more second sub-events within the event.
[0181] Aspect 19: The method according to aspect 18, wherein the first flow comprises a first connected isochronous flow (CIS) within a connected isochronous group (CIG), and the second flow comprises a second CIS within the CIG.
[0182] Aspect 20: The method according to any one of aspects 18 to 19, wherein the one or more second sub-events are associated with the recipient device and are sequential with respect to the one or more first sub-events.
[0183] Aspect 21: The method according to any one of aspects 18 to 19, wherein the one or more second sub-events are associated with the recipient device and are interleaved with the one or more first sub-events.
[0184] Aspect 22: The method according to any one of aspects 18 to 21, wherein the second flow is associated with the recipient device.
[0185] Aspect 23: The method according to any one of aspects 18 to 21, wherein the second flow is associated with an additional recipient device.
[0186] Aspect 22: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 17.
[0187] Aspect 23: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 17.
[0188] Aspect 24: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 17.
[0189] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 17.
[0190] Aspect 26: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 17.
[0191] Aspect 27: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 18 to 21.
[0192] Aspect 28: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 18 to 21.
[0193] Aspect 29: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 18 to 21.
[0194] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 18 to 21.
[0195] Aspect 31: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 18 to 21.
[0196] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.
[0197] As used herein, the term "component" is intended to be broadly interpreted 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 broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, "processors" are implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems or methods described herein can be implemented by different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the various aspects. Therefore, the operation and behavior of the systems and / or methods are not described herein with reference to specific software codes, because it will be understood by those skilled in the art that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.
[0198] As used herein, "satisfies a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.
[0199] Although the specific combination of features is 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 can be combined in a manner that is not specifically listed in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of the list of items" refers to any combination of these items (which includes 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, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).
[0200] Any element, action or instruction used herein should not be interpreted as critical or essential unless clearly stated. In addition, as used herein, the article "a" is intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more items connected to the article "the" and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items and can be used interchangeably with "one or more". If you only want to refer to one item, the phrase "only one" or similar terms will be used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element having" A can also have B). In addition, unless otherwise explicitly stated, the phrase "based on" is intended to mean "based at least in part on". Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless expressly stated otherwise (e.g., if used in conjunction with "either" or "only one of").
Claims
1. An apparatus for wireless communication at an initiator device, the apparatus comprising: Memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to: sending a protocol data unit (PDU) associated with the first stream during a first sub-event within a portion of an event shared between the first stream and a second stream; sending a PDU associated with the second stream during a second sub-event within the portion of the event shared between the first stream and the second stream; or A combination of them.
2. The apparatus of claim 1, wherein the first flow comprises a first connected isochronous flow (CIS) within a connected isochronous group (CIG), and the second flow comprises a second CIS within the CIG.
3. The apparatus of claim 1 , wherein the one or more processors are further configured to: A PDU associated with the third stream is sent during a third sub-event within a portion of the event that is shared between the third stream and at least one of the first stream or the second stream.
4. The apparatus of claim 1 , wherein the one or more processors are further configured to: PDUs associated with the first stream are sent during a third sub-event within a portion of the event not shared with the second stream.
5. The apparatus of claim 1 , wherein the one or more processors are further configured to: PDUs associated with the second stream are sent during a third sub-event within a portion of the event not shared with the first stream.
6. The device of claim 1, wherein at least one of the first sub-event or the second sub-event is shifted in time when used for the second stream relative to when used for the first stream.
7. The apparatus of claim 1, wherein the portion of the event shared between the first stream and the second stream is based at least in part on an offset value.
8. The apparatus of claim 1, wherein the one or more processors are further configured to: The determination to transmit the PDU associated with the first flow is based at least in part on a refresh point associated with the PDU associated with the first flow.
9. The apparatus of claim 1, wherein the one or more processors are further configured to: The determination to transmit the PDU associated with the first flow is based at least in part on a polling schedule associated with at least the first flow and the second flow.
10. The apparatus of claim 1, wherein the first flow is associated with a first access address and the second flow is associated with a second access address.
11. The apparatus of claim 1, wherein the first sub-event is associated with the second flow, and the PDU associated with the first flow includes a third access address.
12. The apparatus of claim 1, wherein the second sub-event is associated with the first flow, and the PDU associated with the second flow includes a third access address.
13. The apparatus of claim 1, wherein the first flow and the second flow are associated with a same access address.
14. The apparatus of claim 1, wherein the PDU associated with the second flow includes one or more bits in a header indicating that the PDU is for the second flow.
15. The apparatus of claim 1, wherein the PDU associated with the second flow is associated with a message integrity check (MIC) to indicate that the PDU is for the second flow.
16. The apparatus of claim 1, wherein the PDU associated with the second flow is associated with a reverse cyclic redundancy check (CRC) to indicate that the PDU is for the second flow.
17. The apparatus of claim 1, wherein the PDU associated with the second flow is associated with a time offset relative to the PDU associated with the second flow.
18. An apparatus for wireless communication at a recipient device, the apparatus comprising: Memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to: activating a low power mode during one or more first sub-events within an event shared between a second stream and a first stream for the recipient device; as well as Protocol data units (PDUs) associated with the first flow are listened to during one or more second sub-events within the event.
19. The apparatus of claim 18, wherein the first flow comprises a first connected isochronous flow (CIS) within a connected isochronous group (CIG), and the second flow comprises a second CIS within the CIG.
20. The apparatus of claim 18, wherein the one or more second sub-events are associated with the recipient device and are sequential with respect to the one or more first sub-events.
21. The apparatus of claim 18, wherein the one or more second sub-events are associated with the recipient device and are interleaved with the one or more first sub-events.
22. The apparatus of claim 18, wherein the second flow is associated with the recipient device.
23. The apparatus of claim 18, wherein the second flow is associated with an additional recipient device.
24. A method of wireless communication performed by an initiator device, the method comprising: sending a protocol data unit (PDU) associated with the first stream during a first sub-event within a portion of an event shared between the first stream and a second stream; sending a PDU associated with the second stream during a second sub-event within the portion of the event shared between the first stream and the second stream; or A combination of them.
25. The method according to claim 24, further comprising: A PDU associated with the third stream is sent during a third sub-event within a portion of the event that is shared between the third stream and at least one of the first stream or the second stream.
26. The method according to claim 24, further comprising: PDUs associated with the first stream are sent during a third sub-event within a portion of the event not shared with the second stream.
27. The method according to claim 24, further comprising: PDUs associated with the second stream are sent during a third sub-event within a portion of the event not shared with the first stream.
28. The method according to claim 24, further comprising: The determination to transmit the PDU associated with the first flow is based at least in part on a refresh point associated with the PDU associated with the first flow.
29. The method of claim 24, further comprising: The determination to transmit the PDU associated with the first flow is based at least in part on a polling schedule associated with at least the first flow and the second flow.
30. A method of wireless communication performed by a recipient device, the method comprising: activating a low power mode during one or more first sub-events within an event shared between a second stream and a first stream for the recipient device; as well as Protocol data units (PDUs) associated with the first flow are listened to during one or more second sub-events within the event.
