Soft buffer status reporting

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may perform a decoding operation on a downlink message of the UE. The UE may store decoding information associated with the decoding operation on the downlink message in a buffer of the UE based at least in part on the decoding operation on the downlink message being at least partially unsuccessful. In some examples, a UE may send a report to a network entity indicating buffer usage information for a buffer of the UE, where the buffer usage information indicates one or more parameters associated with decoding information stored in the buffer of the UE. In some cases, the buffer usage information may indicate one or more transport blocks for which entries are present in the buffer of the UE.

Description

Cross-references

[0001] This patent application claims the benefit of U.S. Patent Application No. 18 / 481,144, entitled “SOFT BUFFER STATUSREPORTING”, filed October 4, 2023, by SUN et al., which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following content relates to wireless communication, including soft buffer status reporting. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing 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-A 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 Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses supporting soft buffer status reporting. For example, the described technology enables a UE to perform a decoding operation on its downlink messages. If the decoding operation is at least partially unsuccessful, the UE can store decoding information associated with the decoding operation on the downlink message in its buffer. In some examples, the UE can send a report indicating buffer usage information of the UE's buffer. The buffer usage information can indicate parameters of the decoding information stored in the UE's buffer. For example, the buffer usage information can indicate the presence of one or more transport blocks with entries in the UE's buffer.

[0005] A method performed by a UE is described. The method may include: performing a decoding operation on a downlink message of the UE; storing decoding information associated with the decoding operation on the downlink message in a buffer of the UE based on the decoding operation being at least partially unsuccessful; and sending a report to a network entity indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters associated with the decoding information stored in the buffer of the UE.

[0006] A UE is described. The UE may include: one or more memories storing processor-executable code; a transceiver; and one or more processors of the UE coupled to the transceiver and the one or more memories. The one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: perform a decoding operation on a downlink message of the UE; based on the decoding operation on the downlink message being at least partially unsuccessful, store decoding information associated with the decoding operation on the downlink message in a buffer of the UE; and send a report to a network entity indicating buffer usage information of the buffer of the UE, wherein the buffer usage information indicates one or more parameters associated with the decoding information stored in the buffer of the UE.

[0007] Another type of UE is described. This UE may include: components for performing a decoding operation on a downlink message of the UE; components for storing decoding information associated with the decoding operation on the downlink message in a buffer of the UE based on the decoding operation being at least partially unsuccessful; and components for sending a report to a network entity indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters associated with the decoding information stored in the buffer of the UE.

[0008] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to: perform a decoding operation on a downlink message of the UE; based on the at least partial failure of the decoding operation on the downlink message, store decoding information associated with the decoding operation on the downlink message in a buffer of the UE; and send a report to a network entity indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters associated with the decoding information stored in the buffer of the UE.

[0009] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the methods, apparatus, and nontransitory computer-readable media may include further operations, features, components, or instructions for performing the following actions: receiving a retransmission of the downlink message based on the report; and performing a second decoding operation on the retransmission based on one or more log-likelihood ratios (LLRs).

[0010] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for performing the following actions: receiving from the network entity a message indicating a periodic set of time resources for sending the report according to periodicity.

[0011] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, sending the report may include operations, features, components, or instructions for performing the following actions: sending the report via one or more time resources in the periodic set of time resources, according to the periodicity.

[0012] The methods described herein, some examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for performing actions such as avoiding the transmission of a second report via one or more time resources in the periodic set of time resources, based on the fact that the buffer usage information is the same as the buffer usage information included in a previous report, that the buffer utilization is below a threshold, that the buffer is empty, or a combination thereof.

[0013] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing the following actions: receiving from the network entity a message including one or more downlink control information bits, wherein the one or more downlink control information bits trigger the UE to send the report.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the one or more downlink control information bits indicate one or more priority values, one or more component carriers, or combinations thereof, associated with buffer usage information to be included in the report.

[0015] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for detecting an event at the UE, wherein the report may be sent based on the UE's detection of the event.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, detecting the event may include operations, features, components, or instructions for detecting the absence of downlink control information transmission from the network entity.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, sending the report may include operations, features, components, or instructions for performing the following actions: sending the report based on buffer usage meeting a threshold, wherein the event includes: the buffer usage meeting the threshold.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the one or more parameters indicate the transport block associated with the decoded information stored in the buffer.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the one or more parameters include indications of: carrier identification values, hybrid automatic repeat request identification values, new data indications associated with the downlink message, or combinations thereof.

[0020] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for performing the following actions: storing in the buffer of the UE additional decoding information associated with a set of multiple decoding operations for a corresponding set of multiple downlink messages, each of the multiple decoding operations in the set of multiple decoding operations being at least partially unsuccessful.

[0021] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for performing the following actions: sending a report indicating buffer usage information, wherein the buffer usage information indicates one or more parameters of the decoding information associated with the set of multiple decoding operations.

[0022] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the buffer uses information including a corresponding bitmap of each component carrier in a set of component carriers associated with the set of multiple downlink messages, wherein each corresponding bit of the first bit map of the first component carrier in the set of component carriers indicates whether decoding information associated with a corresponding transport block of a corresponding downlink message in the set of multiple downlink messages can be stored in the buffer.

[0023] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the buffer uses information indicating a time instance that indicates that decoding information associated with a downlink message sent after the time instance can be stored in the buffer, and that decoding information associated with at least one downlink message sent before the time instance can be cleared from the buffer.

[0024] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the report may be sent via an uplink control information message. In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the report may be sent via a Media Access Control (MAC) Control Element (MAC-CE) message.

[0025] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing the following actions: sending a first uplink control information message indicating the size of the report; and sending a second uplink control information message including the report.

[0026] A method performed by a network entity is described. The method may include: sending a downlink message to a UE; receiving from the UE a report indicating buffer usage information of the UE's buffers, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of the downlink message at the UE; and retransmitting the downlink message based on receiving the report.

[0027] A network entity is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors of the network entity coupled to the one or more memories. The one or more processors are capable of operating individually or jointly to execute the code to cause the network entity to: send a downlink message to a UE; receive from the UE a report indicating buffer usage information of the UE's buffers, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of the downlink message at the UE; and retransmit the downlink message based on the receipt of the report.

[0028] Another network entity is described. This network entity may include: components for sending downlink messages to a UE; components for receiving from the UE a report indicating buffer usage information of the UE's buffers, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of the downlink message at the UE; and components for retransmitting the downlink message based on the received report.

[0029] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to: send a downlink message to a UE; receive from the UE a report indicating buffer usage information of the UE's buffers, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of the downlink message at the UE; and retransmit the downlink message based on the receipt of the report. In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the decoding information includes one or more LLRs of the transport block associated with the downlink message.

[0030] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a message indicating a periodic set of time resources for the UE to send the report periodically, wherein the report may be received periodically via one or more resources in the periodic set of time resources.

[0031] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a message including one or more downlink control information bits, wherein the one or more downlink control information bits trigger the UE to send the report.

[0032] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more downlink control information bits indicate one or more priority values, one or more component carriers, or combinations thereof, associated with buffer usage information to be included in the report.

[0033] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more parameters indicate the transport block associated with the decoded information stored in the buffer.

[0034] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more parameters include indications of: carrier identification values, hybrid automatic repeat request identification values, new data indications associated with the downlink message, or combinations thereof.

[0035] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the report may include operations, features, components, or instructions for performing the following actions: receiving the report indicating buffer usage information, wherein the buffer usage information indicates one or more parameters of additional decoding information associated with a set of multiple decoding operations corresponding to a set of multiple downlink messages, each of the multiple decoding operations in the set of multiple decoding operations being at least partially unsuccessful.

[0036] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the buffer uses information including a corresponding bitmap of each component carrier in a set of component carriers associated with the set of multiple downlink messages, wherein each corresponding bit of the first bit map of the first component carrier in the set of component carriers indicates whether decoding information associated with a corresponding transport block of a corresponding downlink message in the set of multiple downlink messages can be stored in the buffer.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the buffer uses information indicating a time instance that indicates that decoding information associated with a downlink message sent after that time instance can be stored in the buffer, and that decoding information associated with at least one downlink message sent before that time instance can be cleared from the buffer.

[0038] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the report may be received via an uplink control information message. In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the report may be sent via a MAC-CE message.

[0039] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving a first uplink control information message indicating the size of the report; and receiving a second uplink control information message including the report. Attached Figure Description

[0040] Figure 1 An example of a wireless communication system supporting soft buffer status reporting is shown, according to one or more aspects of this disclosure.

[0041] Figure 2 An example of a wireless communication system supporting soft buffer status reporting is shown, according to one or more aspects of this disclosure.

[0042] Figure 3 An example of a process flow supporting soft buffer status reporting is shown, according to one or more aspects of this disclosure.

[0043] Figure 4 and Figure 5 A block diagram of a device supporting soft buffer status reporting according to one or more aspects of this disclosure is shown.

[0044] Figure 6 A block diagram of a communication manager supporting soft buffer status reporting according to one or more aspects of this disclosure is shown.

[0045] Figure 7 A diagram of a system including a device supporting soft buffer status reporting, according to one or more aspects of this disclosure, is shown.

[0046] Figure 8 and Figure 9 A block diagram of a device supporting soft buffer status reporting according to one or more aspects of this disclosure is shown.

[0047] Figure 10 A block diagram of a communication manager supporting soft buffer status reporting according to one or more aspects of this disclosure is shown.

[0048] Figure 11 A diagram of a system including a device supporting soft buffer status reporting, according to one or more aspects of this disclosure, is shown.

[0049] Figures 12 to 15 A flowchart illustrating a method for supporting soft buffer status reporting according to one or more aspects of this disclosure is shown. Detailed Implementation

[0050] The UE can decode downlink messages from network entities by determining the LLR of the transport block carried by the downlink message. However, in some cases, the decoding operation may (e.g., at least partially) fail. In these cases, the UE may store decoding information (e.g., LLR) associated with the decoding operation in the UE's buffer (e.g., a soft buffer). The UE can use the decoding information in decoding operations for retransmission of downlink messages (e.g., for performing soft combining), thereby reducing computation and power consumption at the UE and improving network efficiency and resource utilization. Network entities can typically track the decoding information stored by the UE in the buffer. For example, the network entity may receive a negative acknowledgment (NACK) from the UE corresponding to an unsuccessful decoding operation for a downlink message, and the network entity may determine that the UE has stored decoding information associated with the downlink message that was not successfully decoded. However, in some cases, there may be a mismatch between the decoding information stored in the UE's buffer and the decoding information that the network entity tracks as stored in the UE's buffer. For example, because the buffer capacity may be limited, the UE may clear (e.g., delete, remove) older entries in the buffer, but the network entity may estimate that there are still cleared entries in the buffer. Therefore, techniques for aligning the UE and network entities in the current state of use of the buffer may be beneficial.

[0051] According to the examples described herein, a UE may send a report to a network entity indicating buffer usage information for the UE. In some examples, the UE may, for example, send an indication of transport blocks whose entries are stored in the buffer by sending one or more bitmaps. For example, each corresponding bit of the bitmap may indicate whether the corresponding transport block is associated with an entry stored in the buffer, whether the corresponding transport block is associated with a New Data Indicator (NDI), or both. In some other examples, the UE may report a list of one or more entries stored in the buffer, and this list may include one or more carrier identifiers (IDs), HARQ IDs, NDIs, or combinations thereof to indicate one or more transport blocks associated with the corresponding entries stored in the buffer. In some other examples, the UE may report an indication of a time instance associated with the most recent clearing operation. For example, the report may indicate that transport blocks sent before the time instance are not associated with entries in the buffer (e.g., the entries have been cleared), while transport blocks sent after the time instance are associated with entries in the buffer. Therefore, the network entity can retransmit downlink messages based on the updated buffer usage information reported by the UE. This enables more efficient communication between the network entity and the UE and helps prevent failed retransmissions due to misalignment of information contained in the UE's buffer between the network entity and the UE.

[0052] The various aspects of this disclosure are first described in the context of a wireless communication system. The various aspects of this disclosure are further illustrated and described with reference to process flow. The various aspects of this disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to soft buffer status reporting, and are further described with reference to these apparatus diagrams, system diagrams, and flowcharts.

[0053] Figure 1 An example of a wireless communication system 100 supporting soft buffer state reporting according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0054] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0055] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0056] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or 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, apparatus, device, 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 UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0057] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0058] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0059] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an integrated access 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, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0060] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, MAC layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0061] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0062] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support soft buffer state reporting as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0063] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0064] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0065] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0066] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0067] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0068] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0069] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0070] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0071] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0072] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private 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 prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0073] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in this group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0074] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0075] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is 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 these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0076] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0077] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation 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, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0078] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0079] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correct data reception via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). HARQ feedback may involve UE 115 sending an acknowledgment (ACK) to network entity 105 to indicate successful reception and decoding of downlink messages, or sending a NACK to indicate unsuccessful reception or decoding of downlink messages. In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or based on some other time interval.

[0080] In some examples, to decode a downlink message from network entity 105 (e.g., using soft decoding techniques), UE 115 may calculate one or more LLRs (e.g., soft values) that indicate the probability that one or more bits associated with the downlink message have a value (e.g., a value one or a value zero). However, in some cases, the decoding operation performed by UE 115 may be at least partially unsuccessful. In these cases, UE 115 may store the calculated LLR for the downlink transport block associated with the downlink message in a buffer (e.g., a soft buffer) of UE 115, allowing UE 115 to use soft combining in decoding operations for retransmission of the downlink message. The buffer of UE 115 (which may be memory, or may include memory) may have a limited storage capacity. In some examples, the memory may be powered off to save power, which may remove the contents stored in the buffer. In some cases, the number of soft buffer entries (e.g., pages) may be less than the number of HARQ procedures that network entity 105 and UE 115 can use. Network entity 105 can typically track decoding information stored in a buffer by UE 115. For example, network entity 105 can receive a NACK from UE 115 corresponding to an unsuccessful decoding operation for a downlink message, and network entity 105 can determine that UE 115 has stored decoding information associated with the downlink message.

[0081] However, in some cases, there may be a mismatch between the decoded information stored in the buffer of UE 115 and the decoded information that the network entity estimates should be stored in the buffer of UE 115. For example, because the buffer capacity may be limited, UE 115 may clear (e.g., erase, discard) older entries in the buffer, or UE 115 may delete entries in the buffer if the memory is powered off (e.g., to save power, or when UE 115 is powered off). Additionally or alternatively, if the number of soft buffer entries is less than the number of HARQ procedures used between UE 115 and network entity 105, the buffer of UE 115 may not have the capacity to store decoded information for all HARQ procedures. Furthermore, in some cases, UE 115 may report a single ACK or NACK corresponding to a transport block, but UE 115 may store decoded information in the buffer at the code block level. Therefore, UE 115 may not have decoded information stored for each code block of the transport block, but network entity 105 may not know which code blocks have corresponding decoded information stored in the buffer. Additionally or alternatively, some events (e.g., error events, such as decoding failure, reception failure) and UE 115 reporting of error events may be associated with latency.

[0082] Therefore, due to one or more of these reasons, network entity 105 may have outdated or incorrect information about entries in UE 115's buffer, which could lead to errors when retransmitting downlink messages. For example, network entity 105 may rely on the LLR stored in the buffer by UE 115 to enable UE 115 to successfully decode messages (e.g., by changing the puncturing scheme), but if the LLR is not stored, this could cause UE 115 to fail to decode. Therefore, techniques for aligning UE 115 and network entity 105 on the current usage state of the buffer may be beneficial.

[0083] According to the examples described herein, UE 115 may report buffer usage information (e.g., the buffer status of UE 115's buffers, parameters associated with UE 115's buffers) to network entity 105. In some examples, UE 115 may, for example, send an indication of transport blocks having entries stored in the buffer by sending one or more bitmaps. For example, UE 115 may report whether each transport block is associated with an entry stored in the buffer, whether each transport block is associated with an NDI, or both. In some other examples, UE 115 may report a list of one or more entries stored in the buffer, and this list may include one or more carrier IDs, HARQ IDs, NDIs, or combinations thereof to indicate one or more transport blocks associated with the corresponding entry stored in the buffer. In some other examples, UE 115 may report an indication of a time instance associated with the latest clearing operation, which may indicate that transport blocks sent before that time instance are not associated with entries in the buffer (e.g., indicating that the corresponding entry has been cleared), while transport blocks sent after that time instance are associated with entries in the buffer. Therefore, the buffer usage information estimated by network entity 105 can be aligned (e.g., synchronized) based on the report from UE 115, and network entity 105 can perform downlink message retransmission based on the updated buffer usage information reported by UE 115.

[0084] Figure 2 An example of a wireless communication system 200 supporting soft buffer state reporting according to one or more aspects of this disclosure is shown. The wireless communication system 200 may include a UE 115-a and a network entity 105-a, which may be as referenced herein. Figure 1 Examples of the corresponding devices described herein. UE 115-a and network entity 105-a can communicate via one or more communication links 230, which may be, for example, referenced herein. Figure 1 An example of the described communication link 125.

[0085] In some examples, UE 115-a may perform a decoding operation to decode downlink message 215 received from network entity 105-a. For example, UE 115-a may calculate one or more LLRs (e.g., soft values) that indicate the probability that one or more bits associated with the downlink message have a value (e.g., a value "1" or a value "0"). However, in some cases, the decoding operation performed by UE 115-a may be at least partially unsuccessful. In these cases, UE 115-a may store the decoded information in entry 210 of UE 115-a's buffer 205 (e.g., memory). For example, UE 115-a may store decoding information in entry 210-d due to unsuccessful decoding of downlink message 215, and the decoding information may include the calculated LLR of the downlink transport block associated with the downlink message, an indication of the transport block, whether the transport block is associated with NDI (e.g., whether the transport block includes new data), HARQ ID or Redundancy Version (RV), carrier ID, or other parameters associated with downlink message 215. UE 115-a may receive retransmissions of downlink message 215, and UE 115-a may use soft combining to decode the retransmissions, which reduces the operations performed by UE 115-a (e.g., calculations) and reduces power consumption.

[0086] Network entity 105-a can estimate which transport blocks are associated with entries 210 stored in buffer 205. For example, UE 115-a can report a NACK to network entity 105-a in response to a decoding operation (e.g., at least partially) failing for a transport block of downlink message 215, and network entity 105-a can update its estimate of which transport blocks are associated with entries 210 in buffer 205. Therefore, network entity 105-a can perform a retransmission based on the estimated entries 210 to be stored in buffer 205. In some examples, if network entity 105-a determines (e.g., estimates) that buffer 205 does not contain decoding information associated with a transport block of downlink message 215, network entity 105-a can perform a retransmission for the downlink message using an RV identifier (RVID) with a value of zero, which indicates the system cardinality (e.g., the cardinality for low-density parity-check (LDPC) codes) used for decoding by UE 115-a. Additionally or alternatively, network entity 105-a may use different formats to form new transport blocks for retransmission. These different formats may include different information, different parameters, or a different number of bits than the original transport block. Alternatively, for example, if network entity 105-a determines that buffer 205 does indeed contain decoded information associated with the transport block of downlink message 215, network entity 105-a may use the same transport block to send the retransmission, network entity 105-a may apply a different puncturing pattern, or both.

[0087] However, in some cases, the estimation of network entity 105-a may be incorrect or outdated. For example, UE 115-a's buffer may have a limited storage capacity (e.g., the number of entries 210), and UE 115-a may perform a purge operation if buffer 205 is at or above a threshold capacity or if buffer 205 is full (e.g., full capacity). For example, UE 115-a may remove one or more entries 210 from the buffer, and UE 115-a may first delete the oldest entry (e.g., entry 210-a). Additionally or alternatively, UE 115-a may choose not to maintain entries 210 of buffer 205 after closing buffer 205 or after UE 115-a, and network entity 105-a may not be aware that entry 210 has been deleted. In some cases, there may be a delay between an unsuccessful decoding operation and network entity 105-a receiving a report of an error event (e.g., via NACK), which may cause network entity 105-a's estimation of buffer usage to become outdated. Furthermore, UE 115-a can maintain entry 210 at the code block level, which can be a smaller (e.g., more precise) unit relative to the transport block (e.g., multiple code blocks may be in one transport block), but UE 115-a can report ACK / NACK feedback at the transport block level. Therefore, even if network entity 105-a receives a NACK for a transport block from UE 115-a, network entity 105-a may not know which code blocks are associated with entries in buffer 205. Therefore, techniques for aligning UE 115-a and network entity 105-a on the current usage state of the buffer can reduce differences in buffer usage between UE 115-a and network entity 105-a.

[0088] According to the example described herein, UE 115-a may send a report 225 to network entity 105-a indicating buffer usage information (e.g., buffer status). The buffer usage information may indicate to network entity 105-a which transport blocks are associated with entries 210 stored in buffer 205. Additionally or alternatively, such as when UE 115-a stores decoding information on a block or block group basis, UE 115-a may indicate which blocks or block groups are associated with entries 210 stored in buffer 205. Therefore, network entity 105-a may maintain updated information about which transport blocks, blocks, or block groups are associated with entries 210 in buffer 205, and network entity 105-a may schedule retransmissions (e.g., select transport blocks and RVIDs) based on the updated information.

[0089] In some examples, UE 115-a may send report 225 via uplink control information. For example, UE 115-a may send report 225 in a fixed size, and UE 115-a may multiplex the uplink control information with other uplink control information to be sent to network entity 105-a. In some cases, such as if report 225 has a variable size, UE 115-a may send a two-part message (e.g., two parts of uplink control information), where the first message may indicate the size of report 225, and the second message may include report 225. In some other examples, UE 115-a may send report 225 via a MAC-CE message or via a Physical Uplink Shared Channel (PUSCH) message (such as configuring PUSCH permission).

[0090] In some examples, there may be a time delay between the time when UE 115-a sends report 225 and the time when network entity 105-a decodes and parses the information contained in report 225 (e.g., the message containing report 225). Therefore, some information in report 225 may become outdated after the time delay when UE 115-a generates the report. To reduce the possibility of outdated information, UE 115-a may consider the time delay when generating report 225. For example, if UE 115-a determines that a purge operation can be performed soon (e.g., if the buffer is at or above a threshold capacity), UE 115-a may exclude one or more entries 210 from report 225 (e.g., starting with the oldest entry 210) because these entries can be purged when network entity 105-a decodes and parses report 225. In some cases, network entity 105-a may indicate the time delay to UE 115-a, which can increase the accuracy of report 225.

[0091] In some examples, UE 115-a may receive report configuration 220 from network entity 150-a. In some cases, report configuration 220 may be indicated via RRC or may be semi-statically configured to UE 115-a by network entity 105-a. Report configuration 220 may indicate a set of one or more periodic resources (e.g., time resources, frequency resources), for example, by indicating periodicity, offset (e.g., time offset, frequency offset), frequency position, or a combination thereof. Therefore, UE 115-a may periodically send report 225 during each periodic resource period according to report configuration 220 (e.g., according to configured periodicity and offset).

[0092] In some cases, UE 115-a may skip one or more periodic resources from a set of periodic resources (e.g., avoid sending report 225 during this period). For example, UE 115-a may be subject to one or more rules for skipping periodic resources (e.g., such rules are configured). In some examples, if there is no other information to send (e.g., to be reused) for UCI or configuration-granted PUSCH, UE 115-a may skip sending report 225, thereby reducing interference with other transmissions (e.g., other transmissions performed by other UE 115). Additionally or alternatively, UE 115-a may skip sending report 225 if buffer 205 is empty (e.g., does not have entry 210) or if buffer usage information has not changed since the last report 225. In some cases, if buffer 205 is relatively empty (e.g., if the number of entries 210 in buffer 205 is at or below a threshold), the buffer usage information estimated by network entity 105-a may be more accurate (e.g., because UE 115-a may not have performed a clearing operation). Therefore, if buffer 205 is relatively empty, UE 115-a can avoid (e.g., during configured periodic timings) sending report 225.

[0093] In some examples, network entity 105-a may trigger UE 115-a to send report 225 (e.g., instead of configuring periodic resources). For example, network entity 105-a may include one or more bits in downlink control information that may trigger UE 115-a to send report 225. UE 115-a may include report 225 in uplink transmissions in response to the trigger (e.g., in a standalone UCI or multiplexed with other UCIs). In some examples, one or more bits may indicate the type of report 225 to be sent by UE 115-a. For example, one or more types of reports may be defined, which may include different information such as report 225 including buffer usage information associated with a specific priority of downlink messages (e.g., high priority transmission, low priority transmission, all transmissions), report 225 associated with one or more component carriers associated with (e.g., assigned to) UE 115-a, the number of entries to be included in report 225, information to be included for each entry in report 225, or other types of report 225.

[0094] In some examples, UE 115-a may be triggered to send report 225 (e.g., non-periodicly) based on one or more conditions. For example, UE 115-a may be triggered to send report 225 based on the occurrence of an event that could cause network entity 105-a to be misaligned with information stored in buffer 205. For example, UE 115-a may identify an erroneous event, such as the absence of downlink control information transmission or code block transmission expected to be sent by network entity 105-a, which may trigger UE 115-a to send report 225. Additionally or alternatively, UE 115-a may be triggered to send report 225 if buffer 205 is full (e.g., full) or meets a threshold capacity (e.g., capacity is at or above a threshold, number of entries 210 is at or above a threshold), because the probability of misalignment with the estimate of network entity 105-a may be greater when buffer 205 is close to full capacity. In some examples, UE 115-a may send the non-periodic report 225 via MAC-CE because network entity 105-a may not know that UE 115-a will send report 225. In some other examples, UE 115-a may send the non-periodic report 225 by indicating in the first UCI transmission (e.g., using one or more bits multiplexed with the UCI transmission) that report 225 should be sent in the second upcoming UCI transmission.

[0095] In some examples, report 225 may include one or more bitmaps indicating whether a transport block has a corresponding entry 210 in buffer 205. Each corresponding bit in the bitmap may indicate whether a corresponding transport block corresponding to a HARQ procedure ID has a corresponding entry 210 in buffer 205. For example, a value of one may indicate that the transport block has a corresponding entry 210, while a value of zero may indicate that the transport block does not have a corresponding entry 210 in buffer 205. In some cases, report 225 may include a bitmap (e.g., a long bitmap) for each component carrier associated with UE 115-a. In some examples, UE 115-a may (e.g., by network entity 105-a) be configured with a subset of component carriers (e.g., the total set of component carriers), a subset of HARQ procedure IDs (e.g., the total set of component carriers), or both, for which bitmaps may be included in report 225. In some examples, report 225 may also indicate, for example, via a bit of a bitmap, whether a transport block is associated with an NDI (e.g., by including a second bitmap, or a second bit of each transport block in the first bitmap).

[0096] In some other examples, report 225 may be a list of entries 210 included in buffer 205 (e.g., entries 210-a, 210-b, 210-c, and 210-d), or it may include a list of entries included in that buffer. This list may include information for identifying each transport block associated with each entry 210 in buffer 205. For example, the list may include indications of carrier ID, HARQ ID, NDI, or combinations thereof, which may be used by network entity 105-a to identify the transport block. Therefore, UE 115-a may indicate transport blocks with associated entries 210 and may exclude any transport blocks without associated entries 210, which could reduce the report size. However, this could result in a variable size for report 225.

[0097] In some examples, a two-part message (such as a two-part UCI) may be used to send a variable-size report 225. Alternatively, the size of report 225 may be fixed. For example, the size of report 225 may be configured to be proportional to (e.g., equal to a multiple of) the capacity of buffer 205 (e.g., the number of entries or pages supported by buffer 205). If buffer 205 is not at full capacity, report 225 may include one or more special values ​​reserved for unused entries (e.g., zero padding may be used to fill report 225). Alternatively, UE 115-a may be configured (e.g., by network entity 105-a via an RRC message) with the number of entries to be indicated in report 225. If buffer 205 contains more entries than the configured number, UE 115-a may send a second report 225. In some cases, report 225 may include flags indicating whether report 225 is a continuation of a previous report 225 (e.g., in the case where UE 115-a sends two reports 225). If buffer 205 contains fewer entries 210 than the configured number, report 225 can similarly be filled with reserved values ​​(e.g., zero bits).

[0098] In some examples, UE 115-a may report ACK / NACK feedback for a block group. For example, each transport block may include multiple blocks, which may be grouped into one or more block groups. If decoding of a block within a block group is unsuccessful, UE 115-a may report a NACK corresponding to that block group. In these examples, the bitmap or list included in report 225 may also indicate a block group or an individual block (e.g., rather than a transport block). That is, each bit of the bitmap may indicate whether entry 210 corresponding to a block group or block is in buffer 205. Similarly, if report 225 includes an indication of a list of entries 210, the list may indicate the block group or individual block associated with entry 210 stored in buffer 205.

[0099] In some additional examples, report 225 may indicate a time instance associated with a purge operation (e.g., latest purge operation). For example, a time instance may indicate to network entity 105-a that entry 210 corresponding to a transport block (e.g., a code block, or a group of code blocks) sent before the time instance has been purged from buffer 205, while entry 210 corresponding to a transport block sent after the time instance remains in buffer 205. Alternatively, a time instance may indicate to network entity 105-a that entry 210 corresponding to a NACK sent before the time instance has been purged from buffer 205, while entry 210 corresponding to a NACK sent after the time instance remains in buffer 205. In some examples, a time instance may be indicated as an index included in report 225, which may correspond to a time instance in a configuration table. In some cases, a time instance may be, for example, a time offset relative to the time associated with the transmission of report 225, and the index included in report 225 may indicate a time offset from a time offset table.

[0100] Therefore, UE 115-a can send report 225 to network entity 105-a to indicate buffer usage information, and network entity 105-a can update the estimate of buffer usage information maintained by network entity 105-a. This improves the reliability of retransmissions between UE 115-a and network entity 105-a.

[0101] Figure 3 An example of a process flow 300 supporting soft buffer status reporting according to one or more aspects of this disclosure is shown. Process flow 300 illustrates UE 115-b and network entity 105-b (which may be as referenced herein). Figure 1 and Figure 2 Communication between the corresponding devices described (examples of which are described). In some examples, the steps illustrated in process flow 300 may be performed in a different order. Additionally, some steps may be added to process flow 300, and some steps shown may be omitted.

[0102] At 305, network entity 105-b may send a report configuration to UE 115-b. In some examples, the report configuration may indicate a periodic set of time resources for UE 115-b to send buffer usage information reports. For example, the report configuration may indicate a period (e.g., periodicity), an offset (e.g., time offset), or both, which may indicate a periodic set of time resources to UE 115-b. In some other examples, the report configuration may trigger UE 115-b to send buffer usage information reports (e.g., in the next UCI transmission). Additionally or alternatively, the report configuration may indicate one or more conditions that may trigger UE 115-b to send buffer usage information reports.

[0103] At 310, network entity 105-b may send downlink messages. For example, network entity 105-b may send downlink messages to UE 115-b via a transport block. In some examples, downlink messages may be associated with the timing of feedback for sending feedback messages (e.g., HARQ feedback) (such as ACK or NACK messages).

[0104] At 315, UE 115-b may perform a decoding operation for downlink messages. The decoding operation may fail at least partially, and UE 115-b may be unable to decode the downlink messages. At 320, UE 115-b may update its buffer based on the failure of the decoding operation. For example, UE 115-b may store decoding information (e.g., one or more LLRs) associated with the decoding operation in the buffer, which can be used for soft combining during the decoding operation for retransmission of downlink messages.

[0105] At point 325, UE 115-b may send a NACK during the feedback period associated with the downlink message, based on the fact that the decoding operation for the downlink message was at least partially unsuccessful. Network entity 105-b may update its estimate of the information contained in UE 115-b's buffer based on the NACK. For example, network entity 105-b may estimate that the decoded information associated with the downlink message is stored in UE 115-b's buffer.

[0106] At 330, UE 115-b may send a buffer usage information report to network entity 105-b. In some examples, the buffer usage information report may indicate, for example, by sending one or more bitmaps to indicate the transport blocks in which entries are stored in the buffer. For example, one or more bitmaps may indicate whether each transport block is associated with an entry stored in the buffer, whether each transport block is associated with an NDI, or both. In some other examples, the buffer usage information report may include a list of one or more entries stored in the buffer, and this list may include one or more carrier IDs, HARQ IDs, NDIs, or combinations thereof to indicate one or more transport blocks associated with each corresponding entry. In some other examples, UE 115 may report an indication of a time instance associated with a latest purge operation, which may indicate that transport blocks sent before that time instance are not associated with entries in the buffer, while transport blocks sent after that time instance are associated with entries in the buffer. In some examples, the latest purge operation may be sent via a UCI (e.g., a single UCI or two-part UCI) and may be multiplexed with another UCI transmission. Alternatively, the latest purge operation may be sent via MAC-CE or another message.

[0107] At 335, network entity 105-b may retransmit downlink messages based on a buffer usage information report. For example, the buffer usage information report may indicate that decoding information associated with the downlink message is not included in the buffer. Therefore, network entity 105-b may use an RVID of zero to perform a retransmission of the downlink message, which may indicate the system cardinality (e.g., the cardinality for LDPC codes) used for decoding by UE 115-b. Additionally or alternatively, network entity 105-b may use a different format to form a new transport block for retransmission, which may include different information, different parameters, or a different number of bits than the original transport block. Alternatively, for example, if the buffer usage information report indicates that the buffer does indeed contain decoding information associated with the downlink message, network entity 105-b may use the same transport block to send the retransmission, and network entity 105-b may apply a different puncturing pattern.

[0108] Therefore, by sending buffer usage information reports, UE 115-b allows network entity 105-b to update its estimate of buffer usage information maintained by network entity 105-b. This improves the reliability of retransmissions between UE 115-b and network entity 105-b.

[0109] Figure 4A block diagram 400 of a device 405 supporting soft buffer state reporting according to one or more aspects of this disclosure is shown. Device 405 may be an example of aspects of UE 115 as described herein. Device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. Device 405, or one or more components of device 405 (e.g., receiver 410, transmitter 415, and communication manager 420), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0110] Receiver 410 may provide components 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 soft buffer status reporting). The information may be passed to other components of device 405. Receiver 410 may utilize a single antenna or a collection of antennas.

[0111] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to soft buffer status reporting), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.

[0112] The communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of soft buffer status reporting as described herein. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0113] In some examples, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0114] Additionally or alternatively, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0115] In some examples, the communication manager 420 may be configured to use a receiver 410, a transmitter 415, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or integrate with the receiver 410, the transmitter 415, or both to acquire information, output information, or perform various other operations as described herein.

[0116] For example, the communication manager 420 can, is configured, or is operable to support components for performing decoding operations on downlink messages of the UE. The communication manager 420 can, is configured, or is operable to support components for storing decoding information associated with the decoding operation on the downlink message in the UE's buffer based on the decoding operation being at least partially unsuccessful. The communication manager 420 can, is configured, or is operable to support components for sending a report to a network entity indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters associated with the decoding information stored in the UE's buffer.

[0117] By including or configuring a communication manager 420 according to an example as described herein, device 405 (e.g., controlling receiver 410, transmitter 415, communication manager 420 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for soft buffer status reporting to increase communication reliability and reduce processing associated with retransmissions.

[0118] Figure 5 A block diagram 500 of a device 505 supporting soft buffer state reporting according to one or more aspects of this disclosure is shown. Device 505 may be an example of aspects of device 405 or UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0119] Receiver 510 may provide components 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 soft buffer status reporting). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

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

[0121] Device 505 or its various components may be examples of parts used to perform various aspects of soft buffer status reporting as described herein. For example, communication manager 520 may include decoding component 525, buffer component 530, reporting component 535, or any combination thereof. Communication manager 520 may be examples of aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use receiver 510, transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in combination with receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0122] Decoding component 525 is capable of, configured to, or operable to support components for performing decoding operations on downlink messages of the UE. Buffer component 530 is capable of, configured to, or operable to support components for storing decoding information associated with the decoding operation on the downlink message in the UE's buffer based on the at least partial failure of the decoding operation on the downlink message. Reporting component 535 is capable of, configured to, or operable to support components for sending a report to a network entity indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters associated with the decoding information stored in the UE's buffer.

[0123] Figure 6 A block diagram 600 is shown of a communication manager 620 supporting soft buffer status reporting according to one or more aspects of this disclosure. Communication manager 620 may be an example of aspects of communication manager 420, communication manager 520, or both as described herein. Communication manager 620 or its various components may be examples of parts for performing various aspects of soft buffer status reporting as described herein. For example, communication manager 620 may include decoding component 625, buffer component 630, reporting component 635, resource manager 640, triggering component 645, event component 650, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0124] Decoding component 625 is capable of, configured to, or operable to support components for performing decoding operations on downlink messages of the UE. Buffer component 630 is capable of, configured to, or operable to support components for storing decoding information associated with the decoding operation on the downlink message in the UE's buffer based on the at least partial failure of the decoding operation on the downlink message. Reporting component 635 is capable of, configured to, or operable to support components for sending a report to a network entity indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters associated with the decoding information stored in the UE's buffer.

[0125] In some examples, decoding component 625 is capable of, configured to, or operable to support components for receiving retransmissions of downlink messages based on reports. In some examples, decoding information includes one or more LLRs of transport blocks associated with downlink messages, and decoding component 625 is capable of, configured to, or operable to support components for performing a second decoding operation on retransmissions based on one or more LLRs.

[0126] In some examples, the resource manager 640 is capable of, configured to, or able to operate to support components for receiving messages from network entities indicating a periodic set of time resources for sending reports according to periodicity.

[0127] In some examples, to support report sending, the resource manager 640 is able to, is configured to, or is operable to support components for sending reports based on a periodic set of time resources.

[0128] In some examples, the resource manager 640 is capable of, configured to, or able to operate to support components that avoid sending a second report via one or more time resources in a periodic set of time resources, based on buffer usage information being the same as buffer usage information included in a previous report, buffer utilization being below a threshold, buffers being empty, or a combination thereof.

[0129] In some examples, triggering component 645 is capable of, configured to, or operable to support components for receiving messages from network entities including one or more downlink control information bits, wherein the one or more downlink control information bits trigger the UE to send a report. In some examples, the one or more downlink control information bits indicate one or more priority values, one or more component carriers, or combinations thereof, associated with buffer usage information to be included in the report.

[0130] In some examples, event component 650 is capable of, configured to, or operable to support components for detecting events at the UE, wherein reports are sent based on the UE's detection of the event. In some examples, to support event detection, event component 650 is capable of, configured to, or operable to support components for detecting missing downlink control information transmissions from network entities.

[0131] In some examples, to support report sending, event component 650 is capable, configured, or operable to support components for sending reports based on buffer usage meeting a threshold, wherein the event includes: buffer usage meeting the threshold. In some examples, one or more parameters indicate a transport block associated with decoded information stored in the buffer. In some examples, one or more parameters include indications of: carrier identification values, mixed automatic repeat request identification values, new data indications associated with downlink messages, or combinations thereof.

[0132] In some examples, buffer component 630 is capable of, configured to, or operable to support components for storing in the UE's buffer additional decoding information associated with a set of multiple decoding operations for a corresponding set of multiple downlink messages, each of the multiple decoding operations in that set being at least partially unsuccessful.

[0133] In some examples, the reporting component 635 is capable of, configured to, or able to operate to support components for sending reports indicating buffer usage information, wherein the buffer usage information indicates one or more parameters of decoding information associated with a set of multiple decoding operations.

[0134] In some examples, the buffer usage information includes a corresponding bitmap of each component carrier in a set of component carriers associated with a set of multiple downlink messages, and each corresponding bit of the first bit map of the first component carrier in the set of component carriers indicates whether the decoding information associated with the corresponding transport block of the corresponding downlink message in the set of multiple downlink messages is stored in the buffer.

[0135] In some examples, the buffer uses information indicating a time instance that indicates that decoded information associated with a downlink message sent after that time instance is stored in the buffer, and decoded information associated with at least one downlink message sent before that time instance is cleared from the buffer. In some examples, the report is sent via uplink control information messages.

[0136] In some examples, the reporting component 635 is capable of, configured to, or operable to support components for sending a first uplink control information message indicating the size of the report. In some examples, the reporting component 635 is capable of, configured to, or operable to support components for sending a second uplink control information message including the report. In one example, the report is sent via a Media Access Control - Control Element message.

[0137] Figure 7 A diagram of a system 700 including a device 705 supporting soft buffer state reporting, according to one or more aspects of this disclosure, is shown. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or a component including such devices. Device 705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, at least one memory 730, code 735, and at least one processor 740. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 745).

[0138] I / O controller 710 manages the input and output signals of device 705. I / O controller 710 can also manage peripheral devices not integrated into device 705. In some cases, I / O controller 710 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 710 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.

[0139] In some cases, device 705 may include a single antenna 725. However, in other cases, device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 715 may communicate bidirectionally via one or more antennas 725, a wired link, or a wireless link as described herein. For example, transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. Transceiver 715, or transceiver 715 and one or more antennas 725, may be an example of transmitter 415, transmitter 515, receiver 410, receiver 510, or any combination thereof or components thereof as described herein.

[0140] At least one memory 730 may include random access memory (RAM) and read-only memory (ROM). At least one memory 730 may store computer-readable, computer-executable (e.g., processor-executable) code 735, including instructions that, when executed by at least one processor 740, cause device 705 to perform the various functions described herein. Code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 735 may not be directly executable by at least one processor 740, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 730 may contain a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0141] At least one processor 740 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 740 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 740. At least one processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., functions or tasks supporting soft buffer status reporting). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, wherein at least one processor 740 and at least one memory 730 are configured to perform the various functions described herein. In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 740 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 740) and memory circuitry (which may include at least one memory 730)) or components that receive or receive input and process the input 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. Thus, at least one processor 740 or a processing system including at least one processor 740 may be configured, capable of being configured, or operable to cause device 705 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 730 or otherwise.

[0142] For example, the communication manager 720 can, is configured, or is operable to support components for performing decoding operations on downlink messages of the UE. The communication manager 720 can, is configured, or is operable to support components for storing decoding information associated with the decoding operation on the downlink message in the UE's buffer based on the decoding operation being at least partially unsuccessful. The communication manager 720 can, is configured, or is operable to support components for sending a report to a network entity indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters associated with the decoding information stored in the UE's buffer.

[0143] By including or configuring a communication manager 720 according to an example as described herein, device 705 can support techniques for soft buffer status reporting to increase communication reliability, improve coordination between devices, and reduce processing associated with retransmissions.

[0144] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 715, one or more antennas 725, or any combination thereof, or otherwise cooperating with them. For example, the communication manager 720 may be configured to receive or transmit messages or other signaling as described herein via the transceiver 715. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or performed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions that can be executed by at least one processor 740 to cause the device 705 to perform various aspects of soft buffer status reporting as described herein, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.

[0145] Figure 8 A block diagram 800 of a device 805 supporting soft buffer state reporting according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of network entity 105 as described herein. Device 805 may include receiver 810, transmitter 815, and communication manager 820. Device 805 or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0146] Receiver 810 may provide components for acquiring (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). The information may be passed to other components of device 805. In some examples, receiver 810 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 810 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0147] Transmitter 815 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 805. For example, transmitter 815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 815 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 815 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, transmitter 815 and receiver 810 may be co-located in a transceiver, which may include or be coupled to a modem.

[0148] The communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of soft buffer status reporting as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0149] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0150] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0151] In some examples, the communication manager 820 may be configured to use a receiver 810, a transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0152] For example, the communication manager 820 can, is configured, or is operable to support components for transmitting downlink messages to the UE. The communication manager 820 can, is configured, or is operable to support components for receiving reports from the UE indicating buffer usage information of the UE's buffers, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of a downlink message at the UE. The communication manager 820 can, is configured, or is operable to support components for retransmitting downlink messages based on received reports.

[0153] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for soft buffer status reporting to increase communication reliability and reduce processing associated with retransmissions.

[0154] Figure 9 A block diagram 900 of a device 905 supporting soft buffer status reporting according to one or more aspects of this disclosure is shown. Device 905 may be an example of aspects of device 805 or network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0155] Receiver 910 may provide components for acquiring (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). The information may be passed to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0156] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, 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, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0157] Device 905 or its various components may be examples of parts used to perform various aspects of soft buffer status reporting as described herein. For example, communication manager 920 may include downlink messaging component 925, report manager 930, retransmission component 935, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use receiver 910, transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0158] Downlink message component 925 is capable of, configured to, or operable to support components for transmitting downlink messages to the UE. Report manager 930 is capable of, configured to, or operable to support components for receiving reports from the UE indicating buffer usage information of the UE's buffers, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of the downlink message at the UE. Retransmission component 935 is capable of, configured to, or operable to support components for retransmitting downlink messages based on received reports.

[0159] Figure 10 A block diagram 1000 of a communication manager 1020 supporting soft buffer status reporting according to one or more aspects of this disclosure is shown. Communication manager 1020 may be an example of aspects of communication manager 820, communication manager 920, or both as described herein. Communication manager 1020 or its various components may be examples of components for performing various aspects of soft buffer status reporting as described herein. For example, communication manager 1020 may include downlink messaging component 1025, reporting manager 1030, retransmission component 1035, resource component 1040, trigger manager 1045, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0160] Downlink message component 1025 is capable of, configured to, or operable to support components for transmitting downlink messages to the UE. Report manager 1030 is capable of, configured to, or operable to support components for receiving reports from the UE indicative of buffer usage information for the UE's buffers, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of the downlink message at the UE. Retransmission component 1035 is capable of, configured to, or operable to support components for retransmitting downlink messages based on received reports. In some examples, the decoding information includes one or more log-likelihood ratios of transport blocks associated with the downlink message.

[0161] In some examples, resource component 1040 is capable of, configured to, or able to operate to support a component for sending a message indicating a periodic set of time resources for which a report is sent by the UE according to a periodicity, wherein the report is received according to a periodicity via one or more resources in the periodic set of time resources.

[0162] In some examples, the trigger manager 1045 is capable of, configured to, or able to operate to support components for sending messages including one or more downlink control information bits, wherein one or more downlink control information bits trigger the UE to send a report.

[0163] In some examples, one or more downlink control information bits indicate one or more priority values, one or more component carriers, or combinations thereof, associated with buffer usage information to be included in the report. In some examples, one or more parameters indicate transport blocks associated with decoded information stored in the buffer. In some examples, one or more parameters include indications of carrier identification values, hybrid automatic repeat request identification values, new data indications associated with downlink messages, or combinations thereof.

[0164] In some examples, to support receiving reports, the report manager 1030 is capable of, configured to, or operable to support components for receiving reports indicating buffer usage information, wherein the buffer usage information indicates one or more parameters of additional decoding information associated with a set of multiple decoding operations corresponding to a set of multiple downlink messages, each of the multiple decoding operations in the set being at least partially unsuccessful.

[0165] In some examples, the buffer usage information includes a corresponding bitmap of each component carrier in a set of component carriers associated with a set of multiple downlink messages, and each corresponding bit of the first bit map of the first component carrier in the set of component carriers indicates whether the decoding information associated with the corresponding transport block of the corresponding downlink message in the set of multiple downlink messages is stored in the buffer.

[0166] In some examples, the buffer uses information indicating a time instance that indicates that decoded information associated with a downlink message sent after that time instance is stored in the buffer, and decoded information associated with at least one downlink message sent before that time instance is cleared from the buffer. In some examples, the report is received via uplink control information messages.

[0167] In some examples, the report manager 1030 is capable of, configured to, or operable to support components for receiving a first uplink control information message indicating the size of the report. In some examples, the report manager 1030 is capable of, configured to, or operable to support components for receiving a second uplink control information message including the report. In one example, the report is sent via a Media Access Control - Control Element message.

[0168] Figure 11 A diagram of a system 1100 including a device 1105 supporting soft buffer state reporting, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, or network entity 105 as described herein, or may include components thereof. Device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1105 may include components supporting output and acquisition of communication, such as a communication manager 1120, a transceiver 1110, an antenna 1115, at least one memory 1125, code 1130, and at least one processor 1135. These components may communicate electronically or otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1140).

[0169] Transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, device 1105 may include one or more antennas 1115 that may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1110 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1115, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1115, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1115 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1115 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1110 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1110, or transceiver 1110 and one or more antennas 1115, or transceiver 1110 and one or more antennas 1115 and one or more processors or one or more memory components (e.g., at least one processor 1135, at least one memory 1125, or both) may be included in a chip or chip assembly mounted in device 1105. In some examples, transceiver 1110 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0170] At least one memory 1125 may include RAM, ROM, or any combination thereof. At least one memory 1125 may store computer-readable, computer-executable (e.g., processor-executable) code 1130 including instructions that, when executed by one or more of the at least one processor 1135, cause the device 1105 to perform the various functions described herein. Code 1130 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1130 may not be directly executable by one of the at least one processor 1135, but may enable the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1125 may contain a BIOS, etc., that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0171] At least one processor 1135 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1135. At least one processor 1135 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1125) to cause device 1105 to perform various functions (e.g., functions or tasks supporting soft buffer status reporting). For example, device 1105 or components of device 1105 may include at least one processor 1135 and at least one memory 1125 coupled to one or more processors in at least one processor 1135, wherein at least one processor 1135 and at least one memory 1125 are configured to perform the various functions described herein. At least one processor 1135 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions (e.g., by executing code 1130) to perform the functions of device 1105. At least one processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1105 (such as within one or more memories of at least one memory 1125). In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1135 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1135) and memory circuitry (which may include at least one memory 1125)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1135 or a processing system including at least one processor 1135 may be configured, configured to, or operated to cause the device 1105 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1125 or otherwise.

[0172] In some examples, bus 1140 may support communication at protocol layers (e.g., within a protocol layer) in a protocol stack. In some examples, bus 1140 may support communication associated with logical channels of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1105, or communication performed between different components of device 1105 that are co-addressable or may be located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, at least one memory 1125, code 1130 and at least one processor 1135 may be located in one component of different components or partitioned between different components).

[0173] In some examples, the communication manager 1120 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1120 can manage the transfer of data communication between client devices such as one or more UEs 115. In some examples, the communication manager 1120 can manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1120 may support the X2 interface in LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0174] For example, the communication manager 1120 is capable of, configured to, or operable to support components for transmitting downlink messages to the UE. The communication manager 1120 is capable of, configured to, or operable to support components for receiving reports from the UE indicating buffer usage information of the UE's buffers, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of a downlink message at the UE. The communication manager 1120 is capable of, configured to, or operable to support components for retransmitting downlink messages based on received reports.

[0175] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support techniques for soft buffer status reporting to increase communication reliability, improve coordination between devices, and reduce processing associated with retransmissions.

[0176] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using a transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof, or otherwise cooperating with them. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the transceiver 1110, one or more processors in at least one processor 1135, one or more memories in at least one memory 1125, code 1130, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1135, at least one memory 1125, code 1130, or any combination thereof). For example, code 1130 may include instructions that can be executed by one or more processors in at least one processor 1135 to cause the device 1105 to perform various aspects of soft buffer status reporting as described herein, or at least one processor 1135 and at least one memory 1125 may be otherwise configured to perform or support such operations individually or jointly.

[0177] Figure 12 A flowchart illustrating a method 1200 for supporting soft buffer state reporting according to an example as described herein is shown. The operation of method 1200 can be implemented by a UE or its components as described herein. For example, the operation of method 1200 can be implemented by, as referenced... Figures 1 to 7 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0178] At 1205, the method may include performing a decoding operation on the downlink message of the UE. The operation of block 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1205 may be derived from references... Figure 6 The described decoding component 625 is used to perform this.

[0179] At 1210, the method may include: storing decoding information associated with the decoding operation on the downlink message in a buffer of the UE, based on the fact that the decoding operation on the downlink message was at least partially unsuccessful. The operation of block 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1210 may be derived from references... Figure 6 The described buffer component 630 is used for execution.

[0180] At 1215, the method may include: sending a report to a network entity indicating buffer usage information of a UE's buffer, wherein the buffer usage information indicates one or more parameters associated with decoded information stored in the UE's buffer. The operation of block 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1215 may be provided by reference to [reference needed]. Figure 6 The report component 635 described is used to perform this.

[0181] Figure 13 A flowchart illustrating a method 1300 for supporting soft buffer state reporting, as exemplified by an example described herein, is shown. The operation of method 1300 can be implemented by a UE or its components as described herein. For example, the operation of method 1300 can be implemented by, as referenced... Figures 1 to 7 The UE 115 described herein performs the functions. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware as described herein, such as, but not limited to, a communication manager 720, an I / O controller 710, a transceiver 715, an antenna 725, at least one memory 730, code 735, and at least one processor 740, to perform aspects of the described functions.

[0182] At 1305, the method may include performing a decoding operation on the downlink message of the UE. The operation at block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1305 may be derived from references... Figure 6 The described decoding component 625 is used to perform this.

[0183] At 1310, the method may include: storing decoding information associated with the decoding operation on the downlink message in a buffer of the UE, based on the fact that the decoding operation on the downlink message was at least partially unsuccessful. The operation of block 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be derived from references... Figure 6 The described buffer component 630 is used for execution.

[0184] At 1315, the method may include: sending a report to a network entity indicating buffer usage information of a UE's buffer, wherein the buffer usage information indicates one or more parameters associated with decoded information stored in the UE's buffer. The operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be provided by reference to [reference needed]. Figure 6 The report component 635 described is used to perform this.

[0185] At 1320, the method may include: receiving retransmissions of downlink messages based on reports. The operation of block 1320 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1320 may be derived from references... Figure 6 The described decoding component 625 is used to perform this.

[0186] At 1325, the method may include performing a second decoding operation on the retransmission based on one or more log-likelihood ratios. The operation at block 1325 may be performed according to examples disclosed herein. In some examples, aspects of the operation at 1325 may be derived from references... Figure 6 The described decoding component 625 is used to perform this.

[0187] Figure 14 A flowchart illustrating a method 1400 for supporting soft buffer state reporting, as exemplified by an example described herein, is shown. The operation of method 1400 can be implemented by a network entity or its components as described herein. For example, the operation of method 1400 can be implemented by, as referenced... Figures 1 to 3 as well as Figures 8 to 11 The network entity described herein performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware such as receiver 810, transmitter 815, and communication manager 820 as described herein to perform aspects of the described functions.

[0188] At 1405, the method may include: sending a downlink message to the UE. The operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be derived from references... Figure 10 The downlink message component 1025 described herein is used to execute this.

[0189] At 1410, the method may include: receiving from the UE a report indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of a downlink message at the UE. Operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1410 may be derived from references... Figure 10 The report manager 1030 described is used to execute this.

[0190] At 1415, the method may include: retransmitting downlink messages based on a received report. The operation of block 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be derived from references... Figure 10 The described retransmission component 1035 is used for execution.

[0191] Figure 15 A flowchart illustrating a method 1500 for supporting soft buffer state reporting, as exemplified by an example described herein, is shown. The operation of method 1500 can be implemented by a network entity or its components as described herein. For example, the operation of method 1500 can be implemented by, as referenced... Figures 1 to 3 as well as Figures 8 to 11 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0192] At 1505, the method may include: sending a downlink message to the UE. The operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be derived from references... Figure 10 The downlink message component 1025 described herein is used to execute this.

[0193] At 1510, the method may include: sending a message indicating a periodic set of time resources for which the UE will send reports periodically. The operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to... Figure 10 The resource component 1040 described is used for execution.

[0194] At 1515, the method may include: receiving from the UE a report indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of a downlink message at the UE, and wherein the report is received periodically via one or more resources of a periodic set of time resources. The operation of block 1515 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1515 may be derived from references... Figure 10 The report manager 1030 described is used to execute this.

[0195] At 1520, the method may include: retransmitting downlink messages based on a received report. The operation of block 1520 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1520 may be derived from references... Figure 10 The described retransmission component 1035 is used for execution.

[0196] The following provides an overview of the various aspects of this disclosure.

[0197] Aspect 1: A method for wireless communication by a UE, the method comprising: performing a decoding operation on a downlink message of the UE; storing decoding information associated with the decoding operation on the downlink message in a buffer of the UE, based at least in part on the decoding operation on the downlink message being at least partially unsuccessful; and sending a report to a network entity indicating buffer usage information of the buffer of the UE, wherein the buffer usage information indicates one or more parameters associated with the decoding information stored in the buffer of the UE.

[0198] Aspect 2: The method according to aspect 1, wherein the decoding information includes one or more log-likelihood ratios of transport blocks associated with the downlink message, the method further comprising: receiving a retransmission of the downlink message at least in part based on the report; and performing a second decoding operation on the retransmission at least in part based on the one or more log-likelihood ratios.

[0199] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: receiving from the network entity a message indicating a periodic set of time resources for sending the report according to periodicity.

[0200] Aspect 4: According to the method of aspect 3, sending the report includes: sending the report via one or more time resources in the periodic set of time resources according to the periodicity.

[0201] Aspect 5: The method according to any one of Aspects 3 to 4, the method further comprising: at least in part based on the fact that the buffer usage information is the same as the buffer usage information included in the previous report, that the utilization rate of the buffer is below a threshold, that the buffer is empty, or a combination thereof, avoiding sending a second report via one or more time resources in the periodic set of time resources.

[0202] Aspect 6: The method according to any one of Aspects 1 to 2, the method further comprising: receiving from the network entity a message including one or more downlink control information bits, wherein the one or more downlink control information bits trigger the UE to send the report.

[0203] Aspect 7: According to the method of aspect 6, wherein the one or more downlink control information bits indicate one or more priority values, one or more component carriers, or a combination thereof, associated with buffer usage information to be included in the report.

[0204] Aspect 8: The method according to any one of Aspects 1 to 2, the method further comprising: detecting an event at the UE, wherein the report is sent at least in part based on the UE's detection of the event.

[0205] Aspect 9: According to the method of aspect 8, detecting the event includes: detecting the absence of downlink control information transmission from the network entity.

[0206] Aspect 10: The method according to any one of Aspects 8 to 9, wherein sending the report comprises: sending the report at least in part based on buffer usage satisfying a threshold, wherein the event includes: the buffer usage satisfying the threshold.

[0207] Aspect 11: The method according to any one of Aspects 1 to 10, wherein one or more parameters indicate a transport block associated with the decoded information stored in the buffer.

[0208] Aspect 12: According to the method of aspect 11, the one or more parameters include indications of: carrier identification value, hybrid automatic repeat request identification value, new data indication associated with the downlink message, or a combination thereof.

[0209] Aspect 13: The method according to any one of Aspects 1 to 12, the method further comprising: storing in the buffer of the UE additional decoding information associated with a plurality of decoding operations for corresponding plurality of downlink messages, each of the plurality of decoding operations being at least partially unsuccessful.

[0210] Aspect 14: The method according to aspect 13, the method further comprising: sending a report indicating buffer usage information, wherein the buffer usage information indicates one or more parameters of the decoding information associated with the plurality of decoding operations.

[0211] Aspect 15: The method according to any one of Aspects 13 to 14, wherein the buffer usage information includes a corresponding bitmap of each component carrier in a set of component carriers associated with the plurality of downlink messages, and each corresponding bit of the first bit map of the first component carrier in the set of component carriers indicates whether decoding information associated with a corresponding transport block of a corresponding downlink message in the plurality of downlink messages is stored in the buffer.

[0212] Aspect 16: The method according to any one of Aspects 1 to 12, wherein the buffer uses information to indicate a time instance, the time instance indicating that decoding information associated with a downlink message sent after the time instance is stored in the buffer, and decoding information associated with at least one downlink message sent before the time instance is cleared from the buffer.

[0213] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the report is sent via an uplink control information message.

[0214] Aspect 18: The method according to aspect 17, the method further comprising: sending a first uplink control information message indicating the size of the report; and sending a second uplink control information message including the report.

[0215] Aspect 19: The method according to any one of Aspects 1 to 16, wherein the report is sent via a media access control-control element message.

[0216] Aspect 20: A method for wireless communication by a network entity, the method comprising: sending a downlink message to a UE; receiving from the UE a report indicating buffer usage information of a buffer of the UE, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of the downlink message at the UE; and retransmitting the downlink message at least in part based on receiving the report.

[0217] Aspect 21: The method according to aspect 20, wherein the decoding information includes one or more log-likelihood ratios of transport blocks associated with the downlink message.

[0218] Aspect 22: The method according to any one of Aspects 20 to 21, the method further comprising: sending a message indicating a periodic set of time resources for the UE to send the report according to periodicity, wherein the report is received according to periodicity via one or more resources in the periodic set of time resources.

[0219] Aspect 23: The method according to any one of Aspects 20 to 22, the method further comprising: sending a message including one or more downlink control information bits, wherein the one or more downlink control information bits trigger the UE to send the report.

[0220] Aspect 24: According to the method of aspect 23, wherein the one or more downlink control information bits indicate one or more priority values, one or more component carriers, or a combination thereof, associated with buffer usage information to be included in the report.

[0221] Aspect 25: The method according to any one of Aspects 20 to 21, wherein one or more parameters indicate a transport block associated with the decoded information stored in the buffer.

[0222] Aspect 26: According to the method of aspect 25, the one or more parameters include indications of: carrier identification value, hybrid automatic repeat request identification value, new data indication associated with the downlink message, or a combination thereof.

[0223] Aspect 27: The method according to any one of Aspects 20 to 26, wherein receiving the report further comprises: receiving the report indicating buffer usage information, wherein the buffer usage information indicates one or more parameters of additional decoding information associated with a plurality of decoding operations corresponding to a plurality of downlink messages, each of the plurality of decoding operations being at least partially unsuccessful.

[0224] Aspect 28: According to the method of aspect 27, wherein the buffer usage information includes a corresponding bitmap of each component carrier in a set of component carriers associated with the plurality of downlink messages, and each corresponding bit of the first bit map of the first component carrier in the set of component carriers indicates whether decoding information associated with a corresponding transport block of a corresponding downlink message in the plurality of downlink messages is stored in the buffer.

[0225] Aspect 29: The method according to any one of Aspects 20 to 26, wherein the buffer uses information to indicate a time instance, the time instance indicating that decoding information associated with a downlink message sent after the time instance is stored in the buffer, and decoding information associated with at least one downlink message sent before the time instance is cleared from the buffer.

[0226] Aspect 30: The method according to any one of aspects 20 to 29, wherein the report is received via an uplink control information message.

[0227] Aspect 31: According to the method of aspect 30, the method further includes: receiving a first uplink control information message indicating the size of the report; and receiving a second uplink control information message including the report.

[0228] Aspect 32: The method according to any one of Aspects 20 to 29, wherein the report is sent via a media access control-control element message.

[0229] Aspect 33: A UE comprising: one or more memories storing processor-executable code; a transceiver; and one or more processors of the UE, the one or more processors being coupled to the one or more memories and the transceiver and being operable individually or jointly to execute the code to enable the UE to perform a method according to any one of aspects 1 to 19.

[0230] Aspect 34: A UE comprising at least one component for performing the method according to any one of aspects 1 to 19.

[0231] Aspect 35: A non-transitory computer-readable medium storing code, said code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 19.

[0232] Aspect 36: A network entity comprising: one or more memories storing processor-executable code; and one or more processors of the network entity coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of Aspects 20 to 32.

[0233] Aspect 37: A network entity comprising at least one component for performing the method according to any one of aspects 20 to 32.

[0234] Aspect 38: A non-transitory computer-readable medium storing code, said code comprising instructions executable by a processor to perform the method according to any one of aspects 20 to 32.

[0235] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0236] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0237] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0238] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a 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 combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0239] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0240] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible 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, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0241] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0242] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing 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 “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0243] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0244] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0245] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0246] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; transceiver; and One or more processors, coupled to the one or more memories and the transceiver, and capable of operating individually or jointly to execute the code to enable the UE: Perform decoding operations on the downlink messages of the UE; At least in part, based on the fact that the decoding operation on the downlink message was at least partially unsuccessful, the UE stores decoding information associated with the decoding operation on the downlink message in its buffer; as well as The transceiver sends a report to the network entity indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters associated with the decoded information stored in the UE's buffer.

2. The UE of claim 1, wherein the decoding information includes one or more log-likelihood ratios of transport blocks associated with the downlink message, and wherein the one or more processors are individually or jointly capable of operating to execute the code to cause the UE to: Based at least in part on the report, the transceiver receives retransmissions of the downlink messages; and The second decoding operation is performed on the retransmission at least in part based on the one or more log-likelihood ratios.

3. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The transceiver receives a message from the network entity indicating a periodic set of time resources for sending the report according to a periodicity.

4. The UE of claim 3, wherein, in order to send the report, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: According to the periodicity, the report is transmitted via the transceiver through one or more time resources from the periodic set of time resources.

5. The UE of claim 3, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The second report is avoided from being sent via one or more time resources in the periodic set of time resources, at least in part based on the fact that the buffer usage information is the same as the buffer usage information included in the previous report, that the buffer utilization is below a threshold, that the buffer is empty, or a combination thereof.

6. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The UE receives a message from the network entity via the transceiver, including one or more downlink control information bits, wherein the one or more downlink control information bits trigger the UE to send the report.

7. The UE of claim 6, wherein the one or more downlink control information bits indicate one or more priority values, one or more component carriers, or a combination thereof, associated with buffer usage information to be included in the report.

8. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Detecting events at the UE, wherein the report is sent at least in part based on the UE's detection of the event.

9. The UE of claim 8, wherein, in order to detect the event, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The system detects the absence of downlink control information transmissions from the network entity.

10. The UE of claim 8, wherein, in order to send the report, the one or more processors are capable of operating individually or jointly to execute the code to cause the UE to: The report is transmitted via the transceiver, at least in part based on buffer usage meeting a threshold, wherein the events include: The buffer is used to satisfy the threshold.

11. The UE of claim 1, wherein one or more parameters indicate a transport block associated with the decoded information stored in the buffer.

12. The UE of claim 11, wherein one or more parameters include indications of: a carrier identification value, a hybrid automatic repeat request identification value, a new data indication associated with the downlink message, or a combination thereof.

13. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The buffer of the UE stores additional decoding information associated with multiple decoding operations for corresponding multiple downlink messages, each of the multiple decoding operations being at least partially unsuccessful.

14. The UE of claim 13, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Send the report indicating the buffer usage information, wherein the buffer usage information indicates one or more parameters of the decoding information associated with the plurality of decoding operations.

15. The UE of claim 13, wherein the buffer usage information includes a corresponding bitmap of each component carrier in a set of component carriers associated with the plurality of downlink messages, and each corresponding bit of the first bit map of the first component carrier in the set of component carriers indicates whether decoding information associated with a corresponding transport block of a corresponding downlink message in the plurality of downlink messages is stored in the buffer.

16. The UE of claim 1, wherein the buffer uses information to indicate a time instance, the time instance indicating that decoding information associated with a downlink message sent after the time instance is stored in the buffer, and decoding information associated with at least one downlink message sent before the time instance is cleared from the buffer.

17. The UE of claim 1, wherein the report is sent via an uplink control information message.

18. The UE of claim 17, wherein the one or more processors are individually or jointly further operable to execute the code to cause the UE to: A first uplink control information message indicating the size of the report is sent via the transceiver; and A second uplink control information message, including the report, is sent via the transceiver.

19. The UE of claim 1, wherein the report is sent via a Media Access Control - Control Element message.

20. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: Send downlink messages to user equipment (UE); The UE receives a report indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of the downlink message at the UE; as well as The retransmission of the downlink message is based at least in part on the receipt of the report.

21. The network entity of claim 20, wherein the decoding information includes one or more log-likelihood ratios of transport blocks associated with the downlink message.

22. The network entity of claim 20, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Send a message indicating a periodic set of time resources for the UE to send the report according to a periodicity, wherein the report is received according to the periodicity via one or more resources in the periodic set of time resources.

23. The network entity of claim 20, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Send a message including one or more downlink control information bits, wherein the one or more downlink control information bits trigger the UE to send the report.

24. The network entity of claim 23, wherein the one or more downlink control information bits indicate one or more priority values, one or more component carriers, or a combination thereof, associated with buffer usage information to be included in the report.

25. The network entity of claim 20, wherein one or more parameters indicate a transport block associated with the decoded information stored in the buffer.

26. The network entity of claim 25, wherein one or more parameters include indications of: a carrier identification value, a hybrid automatic repeat request identification value, a new data indication associated with the downlink message, or a combination thereof.

27. The network entity of claim 20, wherein, in order to receive the report, the one or more processors are individually or jointly capable of further operating to execute the code to cause the network entity to: Receive the report indicating buffer usage information, wherein the buffer usage information indicates one or more parameters of additional decoding information associated with multiple decoding operations corresponding to multiple downlink messages, each of the multiple decoding operations being at least partially unsuccessful.

28. The network entity of claim 27, wherein the buffer usage information includes a corresponding bitmap of each component carrier in a set of component carriers associated with the plurality of downlink messages, and each corresponding bit of the first bit map of the first component carrier in the set of component carriers indicates whether decoding information associated with a corresponding transport block of a corresponding downlink message in the plurality of downlink messages is stored in the buffer.

29. A method for wireless communication by a user equipment (UE), the method comprising: Perform decoding operations on the downlink messages of the UE; At least in part, based on the fact that the decoding operation on the downlink message was at least partially unsuccessful, the UE stores decoding information associated with the decoding operation on the downlink message in its buffer; as well as A report is sent to a network entity indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters associated with the decoding information stored in the UE's buffer.

30. A method for wireless communication by a network entity, the method comprising: Send downlink messages to user equipment (UE); The UE receives a report indicating buffer usage information of the UE's buffer, wherein the buffer usage information indicates one or more parameters of decoding information associated with at least a partially unsuccessful decoding operation of the downlink message at the UE; as well as The retransmission of the downlink message is based at least in part on the receipt of the report.

Images