Data burst handling

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may communicate one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts. The UE may communicate one or more data bursts in accordance with the one or more time structure parameters.

Description

Qualcomm Ref. No. 2500662WO1DATA BURST HANDLINGCROSS REFERENCE

[0001] The present Application for Patent claims priority to Indian Patent Application No. 202421085950 by MA et al., entitled “DATA BURST HANDLING,” filed November 8, 2024, which is assigned to the assignee hereof, and expressly incorporated by reference herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including data burst handling.BACKGROUND

[0003] Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE- Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).

[0004] In wireless communications, some device may communicate using data bursts. However, such approaches may be improved.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO2SUMMARY

[0005] The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0006] A method for wireless communications by a user equipment (UE) is described. The method may include communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts and communicating one or more data bursts in accordance with the one or more time structure parameters.

[0007] A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the UE to communicate one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts and communicate one or more data bursts in accordance with the one or more time structure parameters.

[0008] Another UE for wireless communications is described. The UE may include means for communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts and means for communicating one or more data bursts in accordance with the one or more time structure parameters.

[0009] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to communicate one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or moreAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO3 respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts and communicate one or more data bursts in accordance with the one or more time structure parameters.

[0010] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the one or more time structure parameters include a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

[0011] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the one or more time structure parameters may be associated with a single data burst or with multiple data bursts.

[0012] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, the one or more time structure parameters may be communicated via a core network function or, via a real time transport protocol (RTP) header extension, or via negotiation between the device and a communication endpoint.

[0013] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, communicating the one or more time structure parameters may include operations, features, means, or instructions for receiving an indication of the one or more time structure parameters from a network entity, negotiating the one or more time structure parameters with the network entity, and negotiating the one or more time structure parameters with a communication endpoint.

[0014] A method for wireless communications by a network entity is described. The method may include communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts and communicating one or more data bursts in accordance with the one or more time structure parameters.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO4

[0015] A network entity for wireless communications is described. The network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the network entity to communicate one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts and communicate one or more data bursts in accordance with the one or more time structure parameters.

[0016] Another network entity for wireless communications is described. The network entity may include means for communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts and means for communicating one or more data bursts in accordance with the one or more time structure parameters.

[0017] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to communicate one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts and communicate one or more data bursts in accordance with the one or more time structure parameters.

[0018] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the one or more time structure parameters include a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO5

[0019] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the one or more time structure parameters may be associated with a single data burst or with multiple data bursts.

[0020] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the one or more time structure parameters may be communicated via a core network function, via a real time transport protocol (RTP) header extension, or in association with negotiation between communication endpoints.

[0021] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, communicating the one or more time structure parameters may include operations, features, means, or instructions for transmitting an indication of the one or more time structure parameters to a UE and negotiating the one or more time structure parameters with the UE.

[0022] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.BRIEF DESCRIPTION OF THE DRAWINGS

[0023] FIG. 1 shows an example of a wireless communications system that supports data burst handling in accordance with one or more examples as disclosed herein.

[0024] FIG. 2 shows an example of a data burst scheme that supports data burst handling in accordance with one or more examples as disclosed herein.

[0025] FIG. 3 shows an example of a data burst scheme that supports data burst handling in accordance with one or more examples as disclosed herein.

[0026] FIG. 4 shows an example of a data burst scheme that supports data burst handling in accordance with one or more examples as disclosed herein.

[0027] FIGs. 5 and 6 show block diagrams of devices that support data burst handling in accordance with one or more examples as disclosed herein.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO6

[0028] FIG. 7 shows a block diagram of a communications manager that supports data burst handling in accordance with one or more examples as disclosed herein.

[0029] FIG. 8 shows a diagram of a system including a device that supports data burst handling in accordance with one or more examples as disclosed herein.

[0030] FIGs. 9 and 10 show block diagrams of devices that support data burst handling in accordance with one or more examples as disclosed herein.

[0031] FIG. 11 shows a block diagram of a communications manager that supports data burst handling in accordance with one or more examples as disclosed herein.

[0032] FIG. 12 shows a diagram of a system including a device that supports data burst handling in accordance with one or more examples as disclosed herein.

[0033] FIG. 13 shows a flowchart illustrating methods that support data burst handling in accordance with one or more examples as disclosed herein.DETAILED DESCRIPTION

[0034] In wireless communications, signaling may be communicated using packet data units (PDUs) which may be transmitted in bursts, referred to as data bursts. Such data bursts may include one or more PDUs. However, some approaches do not clearly define what a data burst is or how such a data burst is defined (e.g., relying on a description of a set of PDUs transmitted in a short amount of time). Further, in some examples, an indication may be provided in a real time transport protocol (RTP) header extension to indicate the end of the data burst. However, if a PDU carrying such an indication is lost, a receiving device may not be aware of when the data burst is to end. Further, in cases in which two data bursts are in relatively close proximity in time, it may not be clear how the PDUs are to be organized or determined (e.g., into a single data burst or multiple data bursts, or how such multiple data bursts are to be organized or determined).

[0035] Techniques for defining or clarifying data burst structures may be employed. For example, a data burst may be defined to be a set of one or more PDUs that exhibit time domain characteristics that may be expressed through time structure parameters. For example, such parameters could include a time gap parameter that indicates a timeAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO7 gap threshold (e.g., a maximum time gap) between adjacent PDUs, such that a time gap that is less than the threshold indicates that the PDUs belong to the same data burst and a time gap greater than the threshold indicates that the PDUs belong to separate data bursts. Additionally, or alternatively, the time structure parameters could include a duration threshold, such that a data burst is considered to include the PDUs that occur in time within an amount of time that is less than or equal to the duration threshold. Additionally, or alternatively, the time structure parameters could include a range of possible duration thresholds, indicating that a duration of a data burst may fall anywhere within the range and be considered a valid, single data burst.

[0036] The time structure parameters may be communicated via a core network function (e.g., an application function (AF), a network exposure function (NEF), a policy control function (PCF), one or more other core network functions, or any combination thereof. Additionally, or alternatively, the time structure parameters may be communicated via an RTP header extension for data bursts. Such parameters may be negotiated between endpoints, indicated to a traffic source by the network, or determined by the traffic source. Such parameters may be communicated between any device, including a network entity, the traffic source, the traffic recipient, one or more other devices, or any combination thereof. In some examples, a network entity may employ the time structure parameters, a delay jitter (e.g., for PDU delivery from the traffic source to the network entity), or any combination thereof, for scheduling, discontinuous reception (DRX) configuration, delay jitter measurement, or any combination thereof. In at least these ways, communications quality, throughput, resource utilization, flexibility, and reliability may be increased while reducing overhead and latency.

[0037] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are then described with reference to a data burst scheme, a data burst scheme, and a data burst scheme. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to data burst handling.

[0038] FIG. 1 shows an example of a wireless communications system 100 that supports data burst handling in accordance with one or more examples as disclosed herein. The wireless communications system 100 may include one or more devices,Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO8 such as one or more network devices (e.g., network entities 105), one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE- Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0039] The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via communication link(s) 125 (e.g., a radio frequency (RF) access link). For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link(s) 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs).

[0040] The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105), as shown in FIG. 1.

[0041] As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may beAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO9 configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

[0042] In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via backhaul communication link(s) 120 (e.g., in accordance with an SI, N2, N3, or other interface protocol). In some examples, network entities 105 may communicate with one another via backhaul communication link(s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130). In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication link(s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link), among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

[0043] One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB), a 5GNB, a next-generation eNB (ng-eNB), a HomeAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO10NodeB, a Home eNodeB, or other suitable terminology). In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140).

[0044] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105), such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity 105 may include one or more of a central unit (CU), such as a CU 160, a distributed unit (DU), such as a DU 165, a radio unit (RU), such as an RU 170, a RAN Intelligent Controller (RIC), such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0045] The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2))Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO11 functionality and signaling (e.g., Radio Resource Control (RRC), service data adaptation protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs), or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170). In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., Fl, Fl-c, Fl-u), and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.

[0046] In some wireless communications systems (e.g., the wireless communications system 100), infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more of the network entities 105 (e.g., network entities 105 or IAB node(s) 104) may be partially controlled by each other. The IAB node(s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base stationAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO12140 (such as a donor network entity or a donor base station). The one or more donor entities (e.g., IAB donors) may be in communication with one or more additional devices (e.g., IAB node(s) 104) via supported access and backhaul links (e.g., backhaul communication link(s) 120). IAB node(s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node(s) 104 used for access via the DU 165 of the IAB node(s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB node(s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node(s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., the IAB node(s) 104 or components of the IAB node(s) 104) may be configured to operate according to the techniques described herein.

[0047] For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor), IAB node(s) 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node(s) 104 may communicate via an Fl interface according to a protocol that defines signaling messages (e.g., an Fl AP protocol). Additionally, or alternatively, the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g., including a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.

[0048] IAB node(s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities). A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node(s) 104,Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO13 and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node(s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node(s) 104). Additionally, or alternatively, IAB node(s) 104 may also be referred to as parent nodes or child nodes to other IAB node(s) 104, depending on the relay chain or configuration of the AN. The IAB-MT entity of IAB node(s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node(s) 104) to receive signaling from a parent IAB node (e.g., the IAB node(s) 104), and a DU interface (e.g., a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.

[0049] For example, IAB node(s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both. An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link(s) 120) to the core network 130 and may act as a parent node to IAB node(s) 104. For example, the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node(s) 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment via an Fl interface to IAB node(s) 104, and the IAB node(s) 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through one or more DUs (e.g., DUs 165). That is, data may be relayed to and from IAB node(s) 104 via signaling via an NR Uu interface to MT of IAB node(s) 104 (e.g., other IAB node(s)). Communications with IAB node(s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node(s) 104.

[0050] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support data burst handling as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180).

[0051] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some otherAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO14 suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (loT) device, an Internet of Everything (loE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.

[0052] The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

[0053] The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link(s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link(s) 125. For example, a carrier used for the communication link(s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity 105, may refer to any portion of aAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO15 network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105).

[0054] In some examples, such as in a carrier aggregation configuration, a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non- standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT).

[0055] The communication link(s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode).

[0056] A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO16

[0057] Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

[0058] One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (A ) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.

[0059] The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts= l / (A / mflx■ Ay) seconds, for which fmaxmay represent a supported subcarrier spacing, and Ay may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0060] Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may beAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO17 further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Ay) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

[0061] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0062] Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control informationAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO18 to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE).

[0063] A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)). In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.

[0064] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a network entity 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG), the UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.

[0065] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband loT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO19

[0066] In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105). In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105). The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0067] The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities (e.g., different ones of the network entities 105) may be approximately aligned in time. For asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities (e.g., different ones of network entities 105) may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

[0068] Some UEs 115, such as MTC or loT devices, may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather andAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO20 geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0069] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 may include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier.

[0070] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC). The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0071] In some examples, a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170), which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may beAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO21 outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to- many (1 :M) system in which each UE 115 transmits to one or more of the UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.

[0072] In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115). In some examples, vehicles may communicate using vehicle-to- everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to- network (V2N) communications, or with both.

[0073] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet,Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO22Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

[0074] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0075] The wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170), and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

[0076] The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devicesAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO23 such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0077] A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

[0078] The network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receivingAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO24 device, and multiple-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0079] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0080] A network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network entity 105 (e.g., a base station 140, an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity 105 multiple times along different directions. For example, the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.

[0081] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., a network entity 105 or a UE 115) along a single beam direction (e.g., a direction associated with the receivingAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO25 device, such as another network entity 105 or UE 115). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.

[0082] In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115). The UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI- RS)), which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170), a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device).

[0083] A receiving device (e.g., a UE 115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network entity 105), such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weightAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO26 sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to- noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0084] The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP -based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.

[0085] The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link(s) 125, a D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal -to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data receivedAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO27 via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

[0086] A UE may support the use of time structure parameters that may define or clarify data burst structures. For example, a data burst may be defined to be a set of one or more PDUs that exhibit time domain characteristics that may be expressed through these time structure parameters. For example, such parameters could include a maximum time gap between PDUs for the PDUs to be considered as a single data burst, indicates a time gap threshold (e.g., a maximum time gap) between adjacent PDUs, a duration threshold or a range of duration thresholds for defining a data burst, or any combination thereof. The UE may receive the parameters from a network entity, negotiate the parameters with another device, or a traffic source may determine the parameters. In some examples, the network entity may use the time structure parameters or a delay jitter for scheduling, DRX configuration, or delay jitter measurement.

[0087] FIG. 2 shows an example of a data burst scheme 200 that supports data burst handling in accordance with one or more examples as disclosed herein.

[0088] In some examples, traffic (e.g., extended reality (XR) traffic), may be periodic with relatively infrequent updates of the traffic periodicity, e.g., by changing the frame rate from 30 frames per second (FPS) to 60 FPS. The data burst information can be carried along with the XR data, but it may not be efficient or desirable to do so.

[0089] 3GPP TS23.501 defined a data burst as follows: Data Burst: A set of multiple PDUs generated and sent by the application in a short period of time. NOTE 1 : A Data Burst can include one or multiple PDU Sets.

[0090] 3GPP TS26.522 defined the end of data burst marking as part of the RTP header extension for PDU Set Marking. End of Data Burst [D] (1 bit): This field is a flag that shall be set to 1 for the last PDU of a Data Burst. It shall be set to 0 for all other PDUs.

[0091] But the definition of TS23.501 does not say what ‘short’ means. This can cause a problems to network entities that optimize traffic delivery. For example, a base station reconfigures DRX (e.g., puts a UE into the DRX off state) when it detects theAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO28 end of data burst. However, if the PDU with the end of data burst marking is lost, the base station doesn’t know when to stop waiting for the lost PDU.

[0092] The traffic source has may group PDUs into a data burst in a variety of ways. Experimental data: PDU departure time at an XR split rendering server. The gap can be predicted by the traffic source, e.g., when the video traffic and the audio traffic have different periodicities.

[0093] Data burst signaling may include TSCAI (time sensitive communication assistance information) (TS23.501), including flow direction, periodicity, burst arrival time, periodicity range, other information, or any combination thereof. Data burst signaling may involve a RTP header extension (TR26.822), including a TTNB: time to the next data burst and a BSSize: data burst size. The RTP header extension may include a one-byte format for the RTP HE for data burst (6.16.2.3 TR26.822). The RTP header extension may include a two-byte format for the RTP HE for data burst (6.16.2.4 TR26.822).

[0094] The techniques described herein may improve operations related to transmitting the data burst by introducing new time structure parameters (including a maximum time gap and a duration), and may help a network entity better handle the data burst.

[0095] In some examples, a time sensitive communication assistance information (TSCAI) mechanism may convey the burst traffic pattern to the network entity and, if the traffic pattern changes, can convey an update of the burst traffic pattern.

[0096] In some examples, a network entity may enable UE power saving to different degrees. If the network entity does not want to enable a higher level of UE power saving, it is unnecessary for the network entity to know when the first data burst with the new periodicity will arrive. Instead, the network entity can start detecting the arrival of the first data burst after it receives TSCAI message until it detects a change in the periodicity.

[0097] This leads to a first design option. Design option 1 : The TSCAI signals the periodicity to the network entity if the traffic periodicity changes, and the network entity infers the start time of the first data burst by detecting the arrival of the first data burst.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO29

[0098] Alternatively, if the network entity wants to enable maximum UE power saving, it needs to know when the new traffic pattern starts. TSACAI can provide the Burst Arrival time for this purpose. However, the drawback is that this may involve synchronization of the clock at the application and the 5G clock, which may not be feasible for all real-world implementations. Additionally, for XR deployments, it may be the case that the XR traffic source engages in predictions of when the data burst will arrive at a network entity (e.g., a gNB) with high accuracy, which in turn requires the XR traffic source to know the delay to a network entity (e.g., a gNB), which may be difficult to determine in practice.

[0099] In some examples, a TSCAI mechanism with Burst Arrival Time may involve time synchronization between the application and the 5G clock and the knowledge of the delay from the application traffic source to the RAN, and this may not be always feasible.

[0100] In some examples, the PDU Set Sequence Number (PSSN) can synchronize the update of a traffic pattern between the application and the 5G system. This leads to a second design option. Design option 2: The TSCAI signals the periodicity, the PSSN of the first PDU Set in the new traffic pattern and possibly a time offset. The arrival time of the PDU Set, delayed by the time offset, if present, is considered as the start of the new traffic pattern.

[0101] In some examples, the UPF may map a PSSN in an RTP header extension to a different value in a GTP-U packet header if the UPF creates new PDU Sets for lone PDUs. In this case, the PSSN for the first PDU Set of a new periodicity signaled in the control plane may mismatch the PSSN of the GTP-U packet encapsulating the first PDU Set, and this can cause a timing error when RAN respond to the start of the new periodicity. To prevent or discourage this from happening, the UPF may keep the PSSN of an incoming PDU Set unchanged during the RTP-U encapsulation. In some examples, the delay of the proposed TSCAI enhanced with PSSN is the same as that of the current TSCAI. In some examples, the delay comparison between the control-plane approach and the user-plane approach is FFS.

[0102] In some examples, the TSCAI without the Burst Arrival Time can be used to indicate a new traffic pattern. Additionally, or alternatively, the TSCAI can be enhancedAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO30 by incorporating the PDU Set Sequence Number (PSSN) and possibly a time offset to indicate the start time of a traffic pattern.

[0103] FIG. 3 shows an example of a data burst scheme 300 that supports data burst handling in accordance with one or more examples as disclosed herein.

[0104] A data burst is a set of multiple PDUs generated and sent by the application exhibiting a time structure (characteristic), including a maximum time gap parameter. Alternative 1 : The time structure is that the maximum time gap between adjacent PDUs is less than a threshold, i.e., this threshold is satisfied when PDUs are grouped into a data burst. Option 1 : the time structure is for multiple data bursts, and this is suitable for control-plane signaling, e.g., via AF / NEF / PCF. Option 2: the time structure is on a per data burst basis, suitable for user-plane signaling, e.g., by adding the information to the RTP header extension for data burst. Alternative 2: the time structure is the maximum time gap between adjacent PDUs, and this is suitable for user-plane signalling, e.g., by adding the maximum time gap of a data burst to the RTP header extension of at least one of the PDUs that belong to the data burst.

[0105] The time structure parameters (e.g., max time gap threshold, duration threshold, duration range) may be determined by one or more of the following:

[0106] Option 1 : The two endpoints (e.g., a UE and an application server) negotiate(e.g., via SDP Offer and Answer) the threshold and passes the information to the network, e.g., the signaling path is UE- AF- PCF- AMF- base station.

[0107] Option 2: The network indicates a desired value and passes the information to the traffic source (e.g., an application server (AS)), e.g., the signaling path is PCFAF - UE - AS.

[0108] Option 3: the traffic source (e.g., an application server) determines the parameters, and add the information to a packet header (e.g., RTP header extension of at least one of the PDUs that belong to the data burst).

[0109] A network entity may employ the time structure parameters for various purposes. A network entity (e.g., base station) uses the time structure parameters and possibly the delay jitter (for PDU delivery from the traffic source to the network entity) for the following:Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO31

[0110] Scheduling or DRX configuration. The base station decides how long it will wait for the next potential PDU of the data burst before giving up the waiting. For example, the time to wait may be the delay threshold plus a delay jitter, and if no PDUs are received after the wait, the base station can assume that the PDUs are lost and let the UE go to a sleep mode. Additionally, or alternatively, the base station decides the data burst has ended. For example, if the time from when the first PDU is received and to the current time is greater than the duration plus a delay jitter, the base station can let the UE go to a sleep mode.

[0111] Delay jitter measurement (if duration is signaled). The base station measures the duration of a fully received data burst (including the PDU with the end of data burst marking), and compares the measured duration with the indicated duration, and the difference reflects the jitter (from the application server to the base station)

[0112] FIG. 4 shows an example of a data burst scheme 400 that supports data burst handling in accordance with one or more examples as disclosed herein.

[0113] The time structure parameters may include duration information. Alternative 1 : the duration information includes a duration threshold and possibly a range (e.g., a range is 7ms to 11ms, meaning the duration is between 7ms and 11ms) that qualify a group of packets to be a data burst,. Option 1 : the duration information is for multiple data bursts, and this is suitable for control-plane signalling, e.g., via AF / NEF / PCF. Option 2: the duration information is on a per data burst basis, and this is suitable for user-plane signaling e.g., by adding the information to the RTP header extension to one of the PDUs that belong to the data burst. Alternative 2: the duration information is the duration of a data burst, and this is suitable for user-plane signaling, e.g., by adding the max time gap to the RTP header extension to one of the PDUs that belong to the data burst.

[0114] FIG. 5 shows a block diagram 500 of a device 505 that supports data burst handling in accordance with one or more examples as disclosed herein. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, the communications manager 520), may include at least one processor,Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO32 which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0115] The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to data burst handling). Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

[0116] The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to data burst handling). In some examples, the transmitter 515 may be co-located with a receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.

[0117] The communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be examples of means for performing various aspects of data burst handling as described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0118] In some examples, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processorAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO33 and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0119] Additionally, or alternatively, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0120] In some examples, the communications manager 520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0121] Additionally, or alternatively, the communications manager 520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts. The communications manager 520 is capable of, configured to, or operable to support a means for communicating one or more data bursts in accordance with the one or more time structure parameters.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO34

[0122] By including or configuring the communications manager 520 in accordance with examples as described herein, the device 505 (e.g., at least one processor controlling or otherwise coupled with the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) may support techniques for reduced processing, reduced power consumption, more efficient utilization of communication resources, or any combination thereof.

[0123] FIG. 6 shows a block diagram 600 of a device 605 that supports data burst handling in accordance with one or more examples as disclosed herein. The device 605 may be an example of aspects of a device 505 or a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605, or one of more components of the device 605 (e.g., the receiver 610, the transmitter 615, the communications manager 620), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0124] The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to data burst handling). Information may be passed on to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

[0125] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to data burst handling). In some examples, the transmitter 615 may be co-located with a receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.

[0126] The device 605, or various components thereof, may be an example of means for performing various aspects of data burst handling as described herein. For example, the communications manager 620 may include a time structure parameterAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO35 component 625 a data burst communication component 630, or any combination thereof. The communications manager 620 may be an example of aspects of a communications manager 520 as described herein. In some examples, the communications manager 620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0127] The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The time structure parameter component 625 is capable of, configured to, or operable to support a means for communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts. The data burst communication component 630 is capable of, configured to, or operable to support a means for communicating one or more data bursts in accordance with the one or more time structure parameters.

[0128] FIG. 7 shows a block diagram 700 of a communications manager 720 that supports data burst handling in accordance with one or more examples as disclosed herein. The communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620, or both, as described herein. The communications manager 720, or various components thereof, may be an example of means for performing various aspects of data burst handling as described herein. For example, the communications manager 720 may include a time structure parameter component 725, a data burst communication component 730, a data burst quantity component 735, a time structure parameter communication component 740, a time structure parameter negotiation component 745, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO36

[0129] Additionally, or alternatively, the communications manager 720 may support wireless communications in accordance with examples as disclosed herein. The time structure parameter component 725 is capable of, configured to, or operable to support a means for communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts. The data burst communication component 730 is capable of, configured to, or operable to support a means for communicating one or more data bursts in accordance with the one or more time structure parameters.

[0130] In some examples, the one or more time structure parameters include a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

[0131] In some examples, the one or more time structure parameters are associated with a single data burst or with multiple data bursts.

[0132] In some examples, the one or more time structure parameters are communicated via a core network function or, via a real time transport protocol (RTP) header extension, or via negotiation between the device and a communication endpoint.

[0133] In some examples, to support communicating the one or more time structure parameters, the time structure parameter communication component 740 is capable of, configured to, or operable to support a means for receiving an indication of the one or more time structure parameters from a network entity. In some examples, to support communicating the one or more time structure parameters, the time structure parameter negotiation component 745 is capable of, configured to, or operable to support a means for negotiating the one or more time structure parameters with the network entity or a means for negotiating the one or more time structure parameters with a communication endpoint.

[0134] In some examples, the communication manager 720 may be associated with a UE or a communication endpoint.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO37

[0135] FIG. 8 shows a diagram of a system 800 including a device 805 that supports data burst handling in accordance with one or more examples as disclosed herein. The device 805 may be an example of or include components of a device 505, a device 605, or a UE 115 as described herein. The device 805 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof). The device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, an input / output (I / O) controller, such as an I / O controller 810, a transceiver 815, one or more antennas 825, at least one memory 830, code 835, and at least one processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

[0136] The I / O controller 810 may manage input and output signals for the device 805. The I / O controller 810 may also manage peripherals not integrated into the device 805. In some cases, the I / O controller 810 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 810 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally, or alternatively, the I / O controller 810 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as the at least one processor 840. In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0137] In some cases, the device 805 may include a single antenna. However, in some other cases, the device 805 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bi-directionally via the one or more antennas 825 using wired or wireless links as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 815 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 825 for transmission,Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO38 and to demodulate packets received from the one or more antennas 825. The transceiver 815, or the transceiver 815 and one or more antennas 825, may be an example of a transmitter 515, a transmitter 615, a receiver 510, a receiver 610, or any combination thereof or component thereof, as described herein.

[0138] The at least one memory 830 may include random access memory (RAM) and read-only memory (ROM). The at least one memory 830 may store computer- readable, computer-executable, or processor-executable code, such as the code 835. The code 835 may include instructions that, when executed by the at least one processor 840, cause the device 805 to perform various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 835 may not be directly executable by the at least one processor 840 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 830 may include, among other things, a basic I / O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0139] The at least one processor 840 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 840. The at least one processor 840 may be configured to execute computer- readable instructions stored in a memory (e.g., the at least one memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting data burst handling). For example, the device 805 or a component of the device 805 may include at least one processor 840 and at least one memory 830 coupled with or to the at least one processor 840, the at least one processor 840 and the at least one memory 830 configured to perform various functions described herein.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO39

[0140] In some examples, the at least one processor 840 may include multiple processors and the at least one memory 830 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 840 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 840) and memory circuitry (which may include the at least one memory 830)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 840 or a processing system including the at least one processor 840 may be configured to, configurable to, or operable to cause the device 805 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 835 (e.g., processor-executable code) stored in the at least one memory 830 or otherwise, to perform one or more of the functions described herein.

[0141] Additionally, or alternatively, the communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts. The communications manager 820 is capable of, configured to, or operable to support a means for communicating one or more data bursts in accordance with the one or more time structure parameters.

[0142] By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 may support techniques for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communicationAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO40 resources, improved coordination between devices, longer battery life, improved utilization of processing capability, or any combination thereof.

[0143] In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof. Although the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the at least one processor 840, the at least one memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the at least one processor 840 to cause the device 805 to perform various aspects of data burst handling as described herein, or the at least one processor 840 and the at least one memory 830 may be otherwise configured to, individually or collectively, perform or support such operations.

[0144] FIG. 9 shows a block diagram 900 of a device 905 that supports data burst handling in accordance with one or more examples as disclosed herein. The device 905 may be an example of aspects of a network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905, or one or more components of the device 905 (e.g., the receiver 910, the transmitter 915, the communications manager 920), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0145] The receiver 910 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 910 may support obtaining information byAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO41 receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0146] The transmitter 915 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 905. For example, the transmitter 915 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include or be coupled with a modem.

[0147] The communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be examples of means for performing various aspects of data burst handling as described herein. For example, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0148] In some examples, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO42

[0149] Additionally, or alternatively, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0150] In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0151] Additionally, or alternatively, the communications manager 920 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts. The communications manager 920 is capable of, configured to, or operable to support a means for communicating one or more data bursts in accordance with the one or more time structure parameters.

[0152] By including or configuring the communications manager 920 in accordance with examples as described herein, the device 905 (e.g., at least one processor controlling or otherwise coupled with the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof) may support techniques forAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO43 reduced processing, reduced power consumption, more efficient utilization of communication resources, or any combination thereof.

[0153] FIG. 10 shows a block diagram 1000 of a device 1005 that supports data burst handling in accordance with one or more examples as disclosed herein. The device 1005 may be an example of aspects of a device 905 or a network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005, or one of more components of the device 1005 (e.g., the receiver 1010, the transmitter 1015, the communications manager 1020), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0154] The receiver 1010 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0155] The transmitter 1015 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1005. For example, the transmitter 1015 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiverAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO441010 may be co-located in a transceiver, which may include or be coupled with a modem.

[0156] The device 1005, or various components thereof, may be an example of means for performing various aspects of data burst handling as described herein. For example, the communications manager 1020 may include a time structure parameter component 1025 a data burst communication component 1030, or any combination thereof. The communications manager 1020 may be an example of aspects of a communications manager 920 as described herein. In some examples, the communications manager 1020, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0157] The communications manager 1020 may support wireless communications in accordance with examples as disclosed herein. The time structure parameter component 1025 is capable of, configured to, or operable to support a means for communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts. The data burst communication component 1030 is capable of, configured to, or operable to support a means for communicating one or more data bursts in accordance with the one or more time structure parameters.

[0158] FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports data burst handling in accordance with one or more examples as disclosed herein. The communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein. The communications manager 1120, or various components thereof, may be an example of means for performing various aspects of data burst handling as described herein. For example, the communications manager 1120 may include a time structureAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO45 parameter component 1125, a data burst communication component 1130, a data burst quantity component 1135, a time structure parameter communication component 1140, a time structure parameter negotiation component 1145, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses). The communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0159] Additionally, or alternatively, the communications manager 1120 may support wireless communications in accordance with examples as disclosed herein. The time structure parameter component 1125 is capable of, configured to, or operable to support a means for communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts. The data burst communication component 1130 is capable of, configured to, or operable to support a means for communicating one or more data bursts in accordance with the one or more time structure parameters.

[0160] In some examples, the one or more time structure parameters include a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

[0161] In some examples, the one or more time structure parameters are associated with a single data burst or with multiple data bursts.

[0162] In some examples, the one or more time structure parameters are communicated via a core network function, via a real time transport protocol (RTP) header extension, or in association with negotiation between communication endpoints.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO46

[0163] In some examples, to support communicating the one or more time structure parameters, the time structure parameter communication component 1140 is capable of, configured to, or operable to support a means for transmitting an indication of the one or more time structure parameters to a UE. In some examples, to support communicating the one or more time structure parameters, the time structure parameter negotiation component 1145 is capable of, configured to, or operable to support a means for negotiating the one or more time structure parameters with the UE.

[0164] FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports data burst handling in accordance with one or more examples as disclosed herein. The device 1205 may be an example of or include components of a device 905, a device 1005, or a network entity 105 as described herein. The device 1205 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof. The communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support outputting and obtaining communications, such as a communications manager 1220, a transceiver 1210, one or more antennas 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1240).

[0165] The transceiver 1210 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1215, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas 1215, from a wired receiver), and to demodulate signals. InAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO47 some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1215 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1215 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and the one or more antennas 1215, or the transceiver 1210 and the one or more antennas 1215 and one or more processors or one or more memory components (e.g., the at least one processor 1235, the at least one memory 1225, or both), may be included in a chip or chip assembly that is installed in the device 1205. In some examples, the transceiver 1210 may be operable to support communications via one or more communications links (e.g., communication link(s) 125, backhaul communication link(s) 120, a midhaul communication link 162, a fronthaul communication link 168).

[0166] The at least one memory 1225 may include RAM, ROM, or any combination thereof. The at least one memory 1225 may store computer-readable, computerexecutable, or processor-executable code, such as the code 1230. The code 1230 may include instructions that, when executed by one or more of the at least one processor 1235, cause the device 1205 to perform various functions described herein. The code 1230 may be stored in a non -transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1230 may not be directly executable by a processor of the at least one processor 1235 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1225 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1235 may include multiple processors and the at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled with one or more of theAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO48 multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system).

[0167] The at least one processor 1235 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1235. The at least one processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1225) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting data burst handling). For example, the device 1205 or a component of the device 1205 may include at least one processor 1235 and at least one memory 1225 coupled with one or more of the at least one processor 1235, the at least one processor 1235 and the at least one memory 1225 configured to perform various functions described herein. The at least one processor 1235 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1230) to perform the functions of the device 1205. The at least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (such as within one or more of the at least one memory 1225).

[0168] In some examples, the at least one processor 1235 may include multiple processors and the at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1235 may be a component of a processing system, which may refer to a system (such as a series) ofAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO49 machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1235) and memory circuitry (which may include the at least one memory 1225)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1235 or a processing system including the at least one processor 1235 may be configured to, configurable to, or operable to cause the device 1205 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1225 or otherwise, to perform one or more of the functions described herein.

[0169] In some examples, a bus 1240 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device 1205, or between different components of the device 1205 that may be co-located or located in different locations (e.g., where the device 1205 may refer to a system in which one or more of the communications manager 1220, the transceiver 1210, the at least one memory 1225, the code 1230, and the at least one processor 1235 may be located in one of the different components or divided between different components).

[0170] In some examples, the communications manager 1220 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communications manager 1220 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1220 may manage communications with one or more other network entities 105, and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices). In some examples, the communications manager 1220 may support an X2 interface within an LTE / LTE-A wireless communications network technology to provide communication between network entities 105.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO50

[0171] Additionally, or alternatively, the communications manager 1220 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1220 is capable of, configured to, or operable to support a means for communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts. The communications manager 1220 is capable of, configured to, or operable to support a means for communicating one or more data bursts in accordance with the one or more time structure parameters.

[0172] By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 may support techniques for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, improved utilization of processing capability, or any combination thereof.

[0173] In some examples, the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1210, the one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the transceiver 1210, one or more of the at least one processor 1235, one or more of the at least one memory 1225, the code 1230, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1235, the at least one memory 1225, the code 1230, or any combination thereof). For example, the code 1230 may include instructions executable by one or more of the at least one processor 1235 to cause the device 1205 to perform various aspects of data burst handling as described herein, or the at least one processor 1235 and the at least one memory 1225 may be otherwise configured to, individually or collectively, perform or support such operations.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO51

[0174] FIG. 13 shows a flowchart illustrating a method 1300 that supports data burst handling in accordance with one or more examples as disclosed herein. The operations of the method 1300 may be implemented by a UE or its components as described herein. For example, the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0175] At 1305, the method may include communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, where the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts. The operations of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a time structure parameter component 725 as described with reference to FIG. 7.

[0176] At 1310, the method may include communicating one or more data bursts in accordance with the one or more time structure parameters. The operations of 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by a data burst communication component 730 as described with reference to FIG. 7.

[0177] The following provides an overview of aspects of the present disclosure:

[0178] Aspect 1 : A method for wireless communications at a UE, comprising: communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, wherein the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts; and communicating one or more data bursts in accordance with the one or more time structure parameters.

[0179] Aspect 2: The method of aspect 1, wherein the one or more time structure parameters comprise a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst durationAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO52 parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

[0180] Aspect 3: The method of any of aspects 1 through 2, wherein the one or more time structure parameters are associated with a single data burst or with multiple data bursts.

[0181] Aspect 4: The method of any of aspects 1 through 3, wherein the one or more time structure parameters are communicated via a core network function or, via a real time transport protocol (RTP) header extension, or via negotiation between the device and a communication endpoint.

[0182] Aspect 5: The method of any of aspects 1 through 4, wherein communicating the one or more time structure parameters comprises: receiving an indication of the one or more time structure parameters from a network entity, negotiating the one or more time structure parameters with the network entity, or negotiating the one or more time structure parameters with a communication endpoint.

[0183] Aspect 6: A method for wireless communications at a network entity, comprising: communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, wherein the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts; and communicating one or more data bursts in accordance with the one or more time structure parameters.

[0184] Aspect 7: The method of aspect 6, wherein the one or more time structure parameters comprise a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

[0185] Aspect 8: The method of any of aspects 6 through 7, wherein the one or more time structure parameters are associated with a single data burst or with multiple data bursts.

[0186] Aspect 9: The method of any of aspects 6 through 8, wherein the one or more time structure parameters are communicated via a core network function, via aAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO53 real time transport protocol (RTP) header extension, or in association with negotiation between communication endpoints.

[0187] Aspect 10: The method of any of aspects 6 through 9, wherein communicating the one or more time structure parameters comprises: transmitting an indication of the one or more time structure parameters to a UE, or negotiating the one or more time structure parameters with the UE.

[0188] Aspect 11 : A UE for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 5.

[0189] Aspect 12: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 5.

[0190] Aspect 13: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 5.

[0191] Aspect 14: A network entity for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 6 through 10.

[0192] Aspect 15: A network entity for wireless communications, comprising at least one means for performing a method of any of aspects 6 through 10.

[0193] Aspect 16: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 6 through 10.

[0194] It should be noted that the methods described herein describe possible implementations. The operations and the steps may be rearranged or otherwise modified and other implementations are possible. Further, aspects from two or more of the methods may be combined.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO54

[0195] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

[0196] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0197] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU), a neural processing unit (NPU), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

[0198] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examplesAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO55 and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0199] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

[0200] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or BAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO56 or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

[0201] As used herein, including in the claims, the article “a” before a noun is open- ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.”

[0202] The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure), ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO57

[0203] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.

[0204] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0205] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.Attorney Docket No. PY2830IN.WO (114958.5136)

Claims

Qualcomm Ref. No. 2500662WO58CLAIMSWhat is claimed is:

1. A device, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the device to: communicate one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, wherein the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts; and communicate one or more data bursts in accordance with the one or more time structure parameters.

2. The device of claim 1, wherein the one or more time structure parameters comprise a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

3. The device of claim 1, wherein the one or more time structure parameters are associated with a single data burst or with multiple data bursts.

4. The device of claim 1, wherein the one or more time structure parameters are communicated via a core network function, via a real time transport protocol (RTP) header extension, or via negotiation between the device and a communication endpoint.

5. The device of claim 1, wherein, to communicate the one or more time structure parameters, the one or more processors are individually or collectively operable to execute the code to cause the UE to: receive an indication of the one or more time structure parameters from a network entity,Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO59 negotiate the one or more time structure parameters with the network entity, or negotiate the one or more time structure parameters with a communication endpoint.

6. The device of claim 1, wherein the device is a user equipment (UE) or a communication endpoint.

7. A network entity, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to: communicate one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, wherein the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts; and communicate one or more data bursts in accordance with the one or more time structure parameters.

8. The network entity of claim 7, wherein the one or more time structure parameters comprise a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

9. The network entity of claim 7, wherein the one or more time structure parameters are associated with a single data burst or with multiple data bursts.

10. The network entity of claim 7, wherein the one or more time structure parameters are communicated via a core network function, via a real time transport protocol (RTP) header extension, or in association with negotiation between communication endpoints.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO6011. The network entity of claim 7, wherein, to communicate the one or more time structure parameters, the one or more processors are individually or collectively operable to execute the code to cause the network entity to: transmit an indication of the one or more time structure parameters to a user equipment (UE), negotiate the one or more time structure parameters with the UE, or negotiate the one or more time structure parameters with a communication endpoint.

12. A method for wireless communications at device, comprising: communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, wherein the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts; and communicating one or more data bursts in accordance with the one or more time structure parameters.

13. The method of claim 12, wherein the one or more time structure parameters comprise a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

14. The method of claim 12, wherein the one or more time structure parameters are associated with a single data burst or with multiple data bursts.

15. The method of claim 12, wherein the one or more time structure parameters are communicated via a core network function, via a real time transport protocol (RTP) header extension, or via negotiation between the device and a communication endpoint.

16. The method of claim 12, wherein communicating the one or more time structure parameters comprises: receiving an indication of the one or more time structure parameters from a network entity,Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO61 negotiating the one or more time structure parameters with the network entity, or negotiating the one or more time structure parameters with a communication endpoint.

17. The method of claim 12, wherein the device is a user equipment or a communication endpoint.

18. A method for wireless communications at a network entity, comprising: communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, wherein the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts; and communicating one or more data bursts in accordance with the one or more time structure parameters.

19. The method of claim 18, wherein the one or more time structure parameters comprise a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

20. The method of claim 18, wherein the one or more time structure parameters are associated with a single data burst or with multiple data bursts.

21. The method of claim 18, wherein the one or more time structure parameters are communicated via a core network function, via a real time transport protocol (RTP) header extension, or in association with negotiation between communication endpoints.

22. The method of claim 18, wherein communicating the one or more time structure parameters comprises: transmitting an indication of the one or more time structure parameters to a user equipment (UE),Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO62 negotiating the one or more time structure parameters with the UE, or negotiating the one or more time structure parameters with a communication endpoint.

23. A device for wireless communications, comprising: means for communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, wherein the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts; and means for communicating one or more data bursts in accordance with the one or more time structure parameters.

24. The device of claim 23, wherein: the one or more time structure parameters comprise a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

25. The device of claim 23, wherein the one or more time structure parameters are associated with a single data burst or with multiple data bursts.

26. The device of claim 23, wherein the one or more time structure parameters are communicated via a core network function, via a real time transport protocol (RTP) header extension, or via negotiation between the device and a communication endpoint.

27. The device of claim 23, wherein the means for communicating the one or more time structure parameters comprise: means for receiving an indication of the one or more time structure parameters from a network entity, means for negotiating the one or more time structure parameters with the network entity, or means for negotiating the one or more time structure parameters with a communication endpoint.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO6328. The device of claim 23, wherein the device is a user equipment (UE) or a communication endpoint.

29. A network entity for wireless communications, comprising: means for communicating one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, wherein the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts; and means for communicating one or more data bursts in accordance with the one or more time structure parameters.

30. The network entity of claim 29, wherein: the one or more time structure parameters comprise a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

31. The network entity of claim 29, wherein the one or more time structure parameters are associated with a single data burst or with multiple data bursts.

32. The network entity of claim 29, wherein the one or more time structure parameters are communicated via a core network function, via a real time transport protocol (RTP) header extension, or in association with negotiation between communication endpoints.

33. The network entity of claim 29, wherein the means for communicating the one or more time structure parameters comprise: means for transmitting an indication of the one or more time structure parameters to a user equipment (UE), means for negotiating the one or more time structure parameters with the UE, or means for negotiating the one or more time structure parameters with a communication endpoint.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO6434. A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to: communicate one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, wherein the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts; and communicate one or more data bursts in accordance with the one or more time structure parameters.

35. The non-transitory computer-readable medium of claim 34, wherein the one or more time structure parameters comprise a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

36. The non-transitory computer-readable medium of claim 34, wherein the one or more time structure parameters are associated with a single data burst or with multiple data bursts.

37. The non-transitory computer-readable medium of claim 34, wherein the one or more time structure parameters are communicated via a core network function, via a real time transport protocol (RTP) header extension, or via negotiation between communication endpoints.

38. The non-transitory computer-readable medium of claim 34, wherein the instructions to communicate the one or more time structure parameters are executable by the one or more processors to: receive an indication of the one or more time structure parameters from a network entity, negotiate the one or more time structure parameters with the network entity, or negotiate the one or more time structure parameters with a communication endpoint.Attorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO6539. The non-transitory computer-readable medium of claim 34, wherein the one or more processors are associated with a user equipment (UE) or a communication endpoint40. A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to: communicate one or more time structure parameters associated with organization of one or more respective packet data units (PDUs) into one or more respective data bursts, wherein the one or more time structure parameters indicate time domain characteristics of the one or more respective data bursts; and communicate one or more data bursts in accordance with the one or more time structure parameters.

41. The non-transitory computer-readable medium of claim 40, wherein the one or more time structure parameters comprise a time gap parameter that indicates a time gap between adjacent PDUs within a single data burst, a time gap threshold parameter, a data burst duration parameter, a data burst duration threshold parameter, a data burst duration threshold range parameter, or any combination thereof.

42. The non-transitory computer-readable medium of claim 40, wherein the one or more time structure parameters are associated with a single data burst or with multiple data bursts.

43. The non-transitory computer-readable medium of claim 40, wherein the one or more time structure parameters are communicated via a core network function, via a real time transport protocol (RTP) header extension, or in association with negotiation between communication endpoints.

44. The non-transitory computer-readable medium of claim 40, wherein the instructions to communicate the one or more time structure parameters are executable by the one or more processors to: transmit an indication of the one or more time structure parameters to a user equipment (UE), negotiate the one or more time structure parameters with the UE, orAttorney Docket No. PY2830IN.WO (114958.5136)Qualcomm Ref. No. 2500662WO66 negotiate the one or more time structure parameters with a communication endpoint.Atorney Docket No. PY2830IN.WO (114958.5136)

Images