Segmentation-based feedback codebook

Abstract

Methods, systems, and devices for wireless communication are described. The segment-based feedback codebook may result in more efficient and more responsive codebook generation for hybrid automatic repeat / request (HARQ) acknowledgement reporting. A segment-based feedback codebook may support codebook generation, where each bit in an acknowledgement / negative acknowledgement (ACK / NACK) codebook may correspond to a segment of a resource. The network entity may schedule the user equipment with the one or more messages within the one or more segments. The UE may generate one ACK / NACK bit for each segment, and a HARQ codebook transmitted in a physical uplink control channel reporting occasion may include ACK / NACK bits corresponding to messages in those segments. The segment may be a set of time domain resources.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 360,558, filed July 27, 2023, entitled “SEGMENT BASEDFEEDBACK CODEBOOK”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following pertains to wireless communication, including segmented feedback codebooks. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, etc. 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 for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses supporting segmented feedback codebooks. For example, the described techniques provide a segmented HARQ codebook for hybrid automatic repeat / request (HARQ) acknowledgment (HARQ-ACK) reporting.

[0006] Wireless communication systems can support codebook generation, where each bit in the ACK / NACK codebook can correspond to a segment of resources (e.g., a set of resources). For example, a segment can be a set of time-domain resources. Additionally or alternatively, a segment can correspond to a certain number of symbols or time slots, and can be fixed or non-uniform relative to other segments.

[0007] In some cases, network entities can schedule user equipment (UEs) using multiple messages within a single segment (e.g., Physical Downlink Shared Channel (PDSCH) transmission). In these cases, the UE can bundle feedback information for multiple messages into a single ACK / NACK bit. In other cases, a single message can span multiple segments (e.g., including resources from multiple segments). In these cases, the UE can generate a HARQ codebook with a number of ACK / NACK bits corresponding to the number of segments the message spans. In other words, the UE can generate one ACK / NACK bit for each segment, and the HARQ codebook used for Physical Uplink Control Channel (PUCCH) reporting timing can include ACK / NACK bits corresponding to the messages in those segments.

[0008] In some cases, the UE can implement intra-segment bundling checks to reduce at least a portion of ACK-to-NACK errors during bundling. For example, the UE can determine the likelihood that a message was scheduled but not detected by checking the start and length indicator values ​​(SLIV) to identify the number of expected downlink-granted downlink control information (DCI) or any combination thereof. Additionally, the UE can implement segment-based HARQ codebooks in the case of carrier aggregation (CA) operation (e.g., a network entity schedules multiple component carriers (CCs) to the UE on overlapping time resources, and / or the network entity can communicate with the UE via any CC).

[0009] A method for wireless communication by a UE is described. The method may include: receiving control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a hybrid automatic repeat request feedback; generating a feedback codebook associated with a set of multiple segments based on the control signaling; and transmitting the feedback codebook for the set of multiple segments based on the generated feedback codebook, the feedback codebook including the bit of the feedback information associated with the segment according to the feedback codebook.

[0010] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the UE to: receive control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback; generate a feedback codebook associated with a set of multiple segments based on the control signaling; and transmit the feedback codebook for the set of multiple segments based on the generated feedback codebook, the feedback codebook including the bit of the feedback information associated with the segment according to the feedback codebook.

[0011] Another UE for wireless communication is described. The UE may include: means for receiving control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback; means for generating a feedback codebook associated with a set of multiple segments based on the control signaling; and means for transmitting the feedback codebook for the set of multiple segments based on the generated feedback codebook, the feedback codebook including the bit of the feedback information associated with the segment according to the feedback codebook.

[0012] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback; generate a feedback codebook associated with a set of multiple segments based on the control signaling; and transmit the feedback codebook for the set of multiple segments based on the generated feedback codebook, the feedback codebook including the bit of the feedback information associated with the segment according to the feedback codebook.

[0013] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving one or more grants to schedule one or more messages in a segment, wherein generating a feedback codebook may be based on receiving one or more grants.

[0014] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for determining the number of messages for resource scheduling, including segmentation, based on the offset between the time when a number of messages can be received and the uplink timing for sending feedback information associated with the feedback codebook, wherein the generation of the feedback codebook may be based on determining the number of messages.

[0015] In some examples of the methods, devices, and non-transitory computer-readable media described herein, a bit of the feedback information associated with the segmentation includes information about a number of messages.

[0016] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, sending a feedback codebook may include operations, features, components, or instructions for sending a bit of feedback information, including an acknowledgment bit, if each of a number of messages can be successfully decoded.

[0017] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, sending a feedback codebook may include operations, features, components, or instructions for sending a bit of feedback information, including a negative acknowledgment bit, in the event that at least one of a number of messages fails to be successfully decoded.

[0018] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, generating a feedback codebook may include operations, features, components, or instructions for: determining a discontinuity in the value of a downlink assignment index indicator received as part of an authorization; and assigning negative acknowledgments to segments in the feedback codebook based on the determined discontinuity in the value.

[0019] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving permission for a first message to be communicated during segmentation, the permission including a first downlink assignment index indicator associated with the segmentation, wherein the generation of a feedback codebook may be based on the first downlink assignment index indicator.

[0020] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a second grant for a second message to be communicated during a segmentation, the second grant including a second downlink assignment index indicator associated with the segmentation and different from the first downlink assignment index indicator; and receiving a third grant for a third message to be communicated during a segmentation, the third grant including a third downlink assignment index indicator associated with the segmentation and different from the first downlink assignment index indicator and the second downlink assignment index indicator.

[0021] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for determining start parameters and length parameters for a message scheduled to be communicated via a resource including segments, wherein generating a feedback codebook may be based on determining the start parameters and length parameters.

[0022] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for determining whether the number of grants received for a resource including segments meets a threshold, wherein generating a feedback codebook may be based on determining whether the number of granted grants received meets the threshold.

[0023] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for determining whether a message scheduled to be delivered via a segmented resource has not been successfully detected, wherein generating a feedback codebook may be based on determining whether the message has not been successfully detected.

[0024] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second control signaling that includes an indication of a maximum number of messages that can be scheduled to be delivered via resources including segmentation, wherein generating a feedback codebook may be based on receiving the second control signaling.

[0025] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: transmitting signaling to indicate that the UE is capable of supporting a maximum number of messages scheduled in resources including segmentation, wherein receiving a second control signaling may be based on transmitting that signaling.

[0026] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second control signaling that includes an indication of a maximum number of messages that can be scheduled to be communicated via a segmented resource, wherein the generation of a feedback codebook may be based on receiving the second control signaling.

[0027] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, receiving control signaling may include operations, features, components, or instructions for receiving permission for a first message to be communicated during a segmentation period, the permission including a message quantity indicator associated with the number of messages scheduled to be communicated via a resource including the segmentation, wherein generating a feedback codebook may be based on the message quantity indicator.

[0028] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, receiving control signaling may include operations, features, components, or instructions for: receiving permission for a first message to be communicated during a segmentation period, the permission including a segmentation index indicator associated with the segmentation and a message quantity indicator associated with the number of messages scheduled to be communicated via a resource including the segmentation; and receiving a second permission for a second message to be communicated during a segmentation period, the second permission including the segmentation index indicator and the message quantity indicator, wherein generating a feedback codebook may be based on the segmentation index indicator and the message quantity indicator.

[0029] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, resources including segments can be defined on one or more component carriers in a set of time-domain resources and multiple component carriers.

[0030] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving second control signaling to report feedback information for a second segment of a resource; defining a resource including the second segment on a second time-domain resource that at least partially overlaps with a time-domain resource and on at least one component carrier that is different from one or more component carriers; wherein generating a feedback codebook may be based on the second control signaling.

[0031] Some examples of the methods, apparatus, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for generating a dynamically long feedback codebook, wherein generating the feedback codebook may be based on generating a dynamically long feedback codebook.

[0032] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, generating a dynamically long feedback codebook may include operations, features, components, or instructions for: receiving one or more grants that schedule one or more messages in a set of multiple segments, the one or more grants including segment index indicators; determining discontinuities in the values ​​of the segment index indicators received as part of the grants; and assigning negative acknowledgments to at least one segment in the feedback codebook based on the determined discontinuities in the values.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a collection of multiple messages can be received via a resource that includes segments.

[0034] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, segments include one or more time slots, one or more portions of time slots, or combinations thereof.

[0035] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, the first size of the first segment may differ from the second size of the second segment.

[0036] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, segmented resources may be defined by slot indexes, symbol indexes, or any combination thereof.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, resources including segmentation may be defined by the timing of transmission via the physical uplink control channel.

[0038] In some examples of the methods, apparatus, and nontransitory computer-readable media described herein, segmented resources may be associated with the time domain, frequency domain, or any combination thereof.

[0039] A method for wireless communication by a network entity is described. The method may include: transmitting control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback; and receiving, based on the control signaling, a feedback codebook associated with a set of multiple segments, the feedback codebook including the bit of the feedback information associated with the segment according to the feedback codebook.

[0040] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the network entity to: send control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including a mixed acknowledgment bit or a negative acknowledgment bit for automatic repeat request feedback; and, based on the control signaling, receive a feedback codebook associated with a set of multiple segments, the feedback codebook including the bit of the feedback information associated with the segment according to the feedback codebook.

[0041] Another network entity for wireless communication is described. This network entity may include: components for transmitting control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including either an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request for feedback; and components for receiving, based on the control signaling, a feedback codebook associated with a set of multiple segments, the feedback codebook including the bit of the feedback information associated with the segment according to the feedback codebook.

[0042] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: send control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback; and, based on the control signaling, receive a feedback codebook associated with a set of multiple segments, the feedback codebook including the bit of the feedback information associated with the segment according to the feedback codebook. Attached Figure Description

[0043] Figure 1 Examples of wireless communication systems supporting segmented feedback codebooks according to one or more aspects of this disclosure are shown.

[0044] Figure 2 Examples of wireless communication systems supporting segmented feedback codebooks according to one or more aspects of this disclosure are shown.

[0045] Figure 3A and Figure 3B An example of a Physical Downlink Shared Channel (PDSCH) mesh supporting a segmented feedback codebook is shown, according to one or more aspects of this disclosure.

[0046] Figure 4 An example of a grid supporting a segmented feedback codebook is shown, according to one or more aspects of this disclosure.

[0047] Figure 5 An example of a grid supporting a segmented feedback codebook is shown, according to one or more aspects of this disclosure.

[0048] Figure 6A and Figure 6B An example of a grid supporting a segmented feedback codebook is shown, according to one or more aspects of this disclosure.

[0049] Figure 7 An example of a grid supporting a segmented feedback codebook is shown, according to one or more aspects of this disclosure.

[0050] Figure 8 An example of a grid supporting a segmented feedback codebook is shown, according to one or more aspects of this disclosure.

[0051] Figure 9 An example of a process flow supporting a segmented feedback codebook according to one or more aspects of this disclosure is shown.

[0052] Figure 10 and Figure 11 A block diagram of a device supporting a segmented feedback codebook according to one or more aspects of this disclosure is shown.

[0053] Figure 12 A block diagram is shown that supports a communication manager based on a segmented feedback codebook according to one or more aspects of this disclosure.

[0054] Figure 13 A diagram is shown of a system including a device supporting a segmented feedback codebook, according to one or more aspects of this disclosure.

[0055] Figure 14 and Figure 15 A block diagram of a device supporting a segmented feedback codebook according to one or more aspects of this disclosure is shown.

[0056] Figure 16 A block diagram is shown that supports a communication manager based on a segmented feedback codebook according to one or more aspects of this disclosure.

[0057] Figure 17 A diagram is shown of a system including a device supporting a segmented feedback codebook, according to one or more aspects of this disclosure.

[0058] Figures 18 to 20 A flowchart illustrating a method for supporting a segmented feedback codebook according to one or more aspects of this disclosure is shown. Detailed Implementation

[0059] Wireless communication systems typically utilize Hybrid Automatic Repeat / Request Acknowledgement (HARQ-ACK) feedback to confirm that a device (e.g., User Equipment (UE)) has successfully received and decoded a transmission (e.g., a message). The HARQ-ACK feedback report may include a feedback codebook (e.g., a HARQ codebook). The UE can generate a HARQ codebook to include a series of bits based on the transmission configuration. For example, a network entity may schedule a UE using downlink transmissions (e.g., message or Physical Downlink Shared Channel (PDSCH) transmissions). The UE can determine whether the message (e.g., PDSCH) was successfully received and decoded. The UE can then report the acknowledgment / negative acknowledgment (ACK / NACK) bits for the message.

[0060] Multiple HARQ ACK / NACK codebook mechanisms (e.g., Type 1 codebook, Type 2 codebook, Type 3 codebook, etc.) and / or bundling mechanisms may exist. For example, the UE may send the bundled ACK / NACK bits as a single bit (e.g., an ACK bit or a NACK bit). For example, if all feedback bits in the bundled ACK / NACK bits are ACK bits, the UE may send a single ACK bit. Otherwise (e.g., if at least one of the bundled ACK / NACK bits is a NACK bit), the UE may send a single NACK bit. However, according to current technology, the UE can bundle ACK / NACK bits based on scheduling permission, which may not be a flexible and / or efficient process.

[0061] The described technique provides a segmented feedback codebook that can lead to more efficient and responsive codebook generation for HARQ-ACK reporting. For example, a segmented feedback codebook can support codebook generation where each bit in the ACK / NACK codebook corresponds to a segment of a resource (e.g., a set of resources). For example, a segment could be a set of time-domain resources. Additionally or alternatively, a segment can correspond to a number of symbols or time slots (e.g., one or more time slots, one or more sub-time slots, etc.) and can be fixed or non-uniform (e.g., dynamic) relative to other segments.

[0062] In some cases, network entities can schedule UEs using multiple messages within a single segment (e.g., PDSCH transmission). In these cases, the UE can bundle feedback information for multiple messages into a single ACK / NACK bit. In other cases, a single message can span multiple segments (e.g., including resources from multiple segments). In these cases, the UE can generate a HARQ codebook with a number of ACK / NACK bits corresponding to the number of segments the message spans. In other words, the UE can generate one ACK / NACK bit for each segment, and the HARQ codebook used for PUCCH reporting timing can include ACK / NACK bits corresponding to the messages in those segments.

[0063] In some cases, the UE can implement intra-segment bundling checks to reduce at least a portion of ACK-to-NACK errors during bundling. For example, the UE can determine the likelihood that a message was scheduled but not detected by checking the start and length indicator values ​​(SLIV) to identify the number of expected downlink-granted downlink control information (DCI) or any combination thereof. Additionally, the UE can implement segment-based HARQ codebooks in the case of carrier aggregation (CA) operation (e.g., a network entity schedules multiple component carriers (CCs) to the UE on overlapping time resources, and / or the network entity can communicate with the UE via any CC).

[0064] The various aspects of this disclosure are first described in the context of a wireless communication system. Additional aspects of this disclosure are described in the context of mesh and process flow. The various aspects of this disclosure are further illustrated and described by way of apparatus diagrams, system diagrams, and flowcharts relating to segmented feedback codebooks.

[0065] Figure 1 Examples of a wireless communication system 100 supporting a segmented feedback codebook according to one or more aspects of this disclosure are 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 according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0066] Network entity 105 may be distributed across a geographical area to form wireless communication system 100 and may include devices in different forms or with 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, among other names. 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).

[0067] 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 Figure 1 The other UE 115 or network entity 105 shown communicates.

[0068] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, 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. Alternatively, a node may be network entity 105. Alternatively, a first node may be configured to communicate with a second or 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.

[0069] In some examples, network entity 105 may communicate with core network 130 or 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 entity 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 entity 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. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or 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 can communicate with core network 130 via communication link 155.

[0070] 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, evolved Node B (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 evolved 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, self-contained) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0071] 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)).

[0072] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functions 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)) functionality and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 can connect to one or more DU 165s or RU 170s, and the one or more DU 165s or RU 170s can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by the CU 160. Additionally or alternatively, protocol stack functional splitting can be employed between the DU 165 and RU 170, such that the DU 165 can support one or more layers of the protocol stack, and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can (e.g., via one or more RU 170s) support one or more different cells. 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) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165s via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170s 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 that communicate via these communication links.

[0073] In some wireless communication systems (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 165 or one or more Ru 170 may be partially controlled by one or more CU 160 associated with a 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 coupled IAB donor's DU 165. 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 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include DU 165s that support 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.

[0074] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support segmented feedback codebooks as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) can be additionally or alternatively 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).

[0075] 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.

[0076] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that may sometimes act as relays, as well as 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.

[0077] 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 physical layer structure defined 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 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used for both frequency division duplex (FDD) 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 network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0078] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0079] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0080] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0081] 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-order modulation scheme can 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 can increase the data rate or data integrity used for communication with UE 115.

[0082] 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 This can represent the supported subcarrier spacing, while The supported Discrete Fourier Transform (DFT) size can be represented. 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).

[0083] 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.

[0084] 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)).

[0085] Physical channels can be multiplexed using various techniques to enable communication using carriers. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via downlink carriers. The control region of a physical control channel (e.g., a control resource set (CORESET)) can be defined by a set of symbol periods and can extend across the system bandwidth of a carrier or a subset of that bandwidth. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search 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.

[0086] 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.

[0087] 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 commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0088] 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 in a group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support various aspects of such D2D communication configured (e.g., scheduled) by network entity 105. In some examples, one or more UE 115s in such a 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.

[0089] Core network 130 can provide 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 can manage 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 can 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.

[0090] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the region from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) region 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 waves in the High 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).

[0091] Wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency 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 using unlicensed RF spectrum bands, devices (such as network entity 105 and UE 115) may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating using licensed frequency bands (e.g., LAA) in a carrier aggregation-based configuration. Operations using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0092] 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.

[0093] 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 particular 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 by the transmitting or receiving device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0094] 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 correctly receiving data 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). In some examples, the device may support same-slot HARQ feedback, in which case the device may 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 according to a different time interval.

[0095] Wireless communication systems typically utilize HARQ-ACK feedback to confirm that UE 115 has successfully received and decoded a transmission (e.g., a message) from network entity 105. The HARQ-ACK feedback report may include a feedback codebook (e.g., a HARQ codebook). UE 115 may generate a HARQ codebook based on the transmission configuration to include a series of bits. For example, network entity 105 may schedule UE 115 using downlink transmissions (e.g., PDSCH transmissions). UE 115 can determine whether the message was successfully received and decoded. UE 115 can then report the acknowledgment / negative acknowledgment bits for that message.

[0096] Multiple HARQ ACK / NACK codebook mechanisms may exist (e.g., Type 1 codebook, Type 2 codebook, Type 3 codebook, etc.). UE 115 can generate a Type 1 codebook, in which case the feedback message may include an ACK or NACK for each PDSCH timing, resulting in a robust feedback message (e.g., but with significant signaling overhead). UE 115 can generate a Type 2 codebook based on additional bits included in the DCI to avoid lost DCIs. Additional bits may include a counter downlink assignment index (DAI) and / or a total DAI (e.g., corresponding to a common PUSCH or PDSCH). The counter DAI and total DAI can indicate the order of DCIs, allowing UE 115 to detect lost DCIs. However, such additional bits in the DCI can lead to increased signaling overhead. In some examples, UE 115 can generate a Type 3 codebook. In such examples, the DCI can trigger a Type 3 codebook feedback message, in which case the DCI can trigger the transmission or retransmission of the complete set of ACK / NACK bits (e.g., for all HARQ procedures). For example, in the event of a NACK feedback message or a lost feedback message, network entity 105 can trigger a Type 3 codebook feedback message.

[0097] In some cases, UE 115 can implement one or more bonding schemes. In some examples, UE 115 can perform spatial bonding for multi-carrier waveform (MCW) scenarios. In such examples, a single DCI can grant up to two spatial codewords, and two feedback bits can be bonded through configuration. In some examples, UE 115 can perform temporal bonding (e.g., for multi-TTI granting). In such examples, the DCI can schedule multiple PDSCHs on different temporal TTIs. A feedback bit can be generated for each transport block (TB), and feedback bits corresponding to all TBs from a DCI can be bonded to one or more bits through configuration. In some examples, UE 115 can perform multi-carrier granting cross-carrier bonding. In such examples, the DCI can schedule multiple PDSCHs on different carriers. A feedback bit can be generated for each TB, and feedback bits corresponding to all TBs from a DCI can be bonded to one or more bits through configuration.

[0098] UE 115 can bundle ACK / NACK bits (e.g., in a Type 1 codebook). That is, UE 115 can transmit the bundled ACK / NACK bits as a single bit (e.g., an ACK bit or a NACK bit). For example, if all bits in the bundled ACK / NACK bits are ACK bits, UE 115 can transmit a single ACK bit. Otherwise (e.g., if at least one of the bundled ACK / NACK bits is a NACK bit), UE 115 can transmit a single NACK bit. However, according to current technology, UE 115 can bundle ACK / NACK bits based on scheduling permission, which may not be a flexible or efficient process.

[0099] In some cases, UE 115 can generate segmented feedback codebooks, which can lead to more efficient and responsive codebook generation for HARQ-ACK reporting. For example, segmented feedback codebooks can support codebook generation where each bit in the ACK / NACK codebook can correspond to a segment of a resource (e.g., a set of resources). For example, a segment could be a set of time-domain resources. Additionally or alternatively, a segment can correspond to a number of symbols or time slots (e.g., one or more time slots, one or more sub-time slots, etc.) and can be fixed or non-uniform (e.g., dynamic) relative to other segments.

[0100] In some cases, network entity 105 can schedule UE 115 using multiple messages within a single segment. In these cases, UE 115 can bundle feedback information for multiple messages (e.g., PDSCH) into a single ACK / NACK bit. In other cases, a single message can span multiple segments (e.g., including resources from multiple segments). In these cases, UE 115 can generate a HARQ codebook with a number of ACK / NACK bits corresponding to the number of segments the message spans. In other words, UE 115 can generate one ACK / NACK bit for each segment, and the HARQ codebook used for Physical Uplink Control Channel (PUCCH) reporting timing can include ACK / NACK bits corresponding to the messages in those segments.

[0101] In some cases, UE 115 can implement intra-segment bundling checks to reduce at least a portion of ACK-to-NACK errors during bundling. For example, UE 115 can determine the likelihood that a message was scheduled but not detected, check SLIVs, and identify the number of expected downlink DCIs or any combination thereof. Additionally, the UE can implement segment-based HARQ codebooks in the case of CA operation.

[0102] Figure 2 An example of a wireless communication system 200 supporting a segmented feedback codebook according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 may include network entity 105-a and UE 115-a.

[0103] The wireless communication system 200 may support a feedback mechanism to indicate the success or failure of signaling reception. For example, UE 115-a may report feedback information for resource segments to network entity 105-a. More specifically, UE 115-a may generate and transmit a feedback codebook 215 containing feedback information for multiple segments.

[0104] In some cases, network entity 105-a may send one or more grants 205 to UE 115-a. For example, grant 205 may schedule one or more messages (e.g., PDSCH) in a segment of resources. Additionally, network entity 105-a may send control signaling 210 (e.g., DCI) to UE 115-a. For example, UE 115-a may receive control signaling 210 to report feedback information for one or more segments (e.g., segments of time and / or frequency resources). Each segment may be associated with a bit of the feedback information. That is, the ACK bit or NACK bit of the HARQ feedback may correspond to each segment. UE 115-a may generate a feedback codebook (e.g., a HARQ codebook) associated with the segment and may send the feedback codebook to network entity 105-a.

[0105] Segments can include any number or combination of resources. For example, a segment can be a single time slot, multiple time slots (e.g., four time slots), or a portion of a time slot (e.g., a sub-time slot). Additionally, segments can have different sizes and / or uneven lengths when compared to other segments. For example, a first segment can have a different size than a second segment.

[0106] In some cases, the resources including segmentation can be absolute (e.g., defined by slot indices and / or symbol indices). In other cases, the resources including segmentation can be relative to the timing of PUCCH transmission. For example, a segmentation can be a certain number of slots and / or symbols preceding the first PUCCH symbol. Additionally, the resources including segmentation can be associated with both the time and frequency domains. For example, time-domain segmentation can be applied to multiple CCs in the case of CA.

[0107] Figure 3A and Figure 3B Examples of grids 300-a and 300-b supporting segmented feedback codebooks according to one or more aspects of this disclosure are illustrated. Grids 300-a and 300-b may implement aspects of, or be implemented by, wireless communication system 100, wireless communication system 200, or any combination thereof. Although grids 300-a and 300-b are illustrated as including a certain number of segments 305 and PDSCH 310, any number and combination of segments 305 and / or PDSCH 310 is possible.

[0108] In some cases, the UE can report feedback information for a segment of a resource (e.g., segment 305-a). For example, the UE can generate a feedback codebook 315 associated with one or more segments 305, and the UE can send the feedback codebook 315 to a network entity. In the example of mesh 300-a, the network entity can schedule multiple PDSCH 310s within segment 305-a (e.g., PDSCH 310-a, PDSCH 310-b, PDSCH 310-c, etc.). Additionally or alternatively, segment 305-a may include multiple code blocks of PDSCH 310 (e.g., CB). If multiple PDSCH 310s exist within a single segment 305, the UE can bundle multiple feedback bits (e.g., ACK bits or NACK bits corresponding to each PDSCH 310) together and send a single bit (e.g., a bit representing the bundled feedback bits).

[0109] In some cases, network entities may schedule multiple PDSCH 310s within segment 305-a (e.g., the same segment). The UE may bundle all feedback information associated with a PDSCH 310 located within segment 305-a and transmit a single feedback bit for segment 305-a (e.g., in feedback codebook 315-a). If the UE successfully receives and decodes downlink signaling via each of the PDSCH 310s scheduled in segment 305-a (e.g., if each feedback bit corresponding to a PDSCH 310 in segment 305-a is an ACK bit), the UE may transmit a single ACK feedback bit for segment 305-a in feedback codebook 315-a. However, if the UE generates even a single NACK bit for segment 305-a (e.g., if downlink signaling has not been successfully received by at least one of the PDSCH 310 in segment 305-a), the UE can send a single NACK bit for segment 305-a in the feedback codebook 315-a. Feedback bundling can reduce the codebook size used for feedback signaling, resulting in reduced signaling overhead and more efficient use of available system resources.

[0110] In the example of grid 300-b, a network entity can schedule a single PDSCH 310 (e.g., PDSCH 310-d) that can span multiple segments 305 (e.g., segment 305-b, segment 305-c, segment 305-d, segment 305-e, etc.). Additionally or alternatively, multiple segments 305 may include a single CB of PDSCH 310. If the resource corresponding to a single PDSCH 310 spans more than one segment 305, the UE can generate multiple feedback bits for a single PDSCH 310 and send multiple feedback bits (e.g., each bit representing a different segment 305). This situation can occur because each feedback bit in the feedback codebook is associated with a segment (rather than with a message such as a PDSCH).

[0111] For example, a network entity can schedule a single PDSCH 310-d across multiple segments 305 (e.g., segment 305-b, segment 305-c, segment 305-d, segment 305-e). The UE can generate feedback bits for each of the segments 305 and include each feedback bit in the feedback codebook 315-b (e.g., transmit each feedback bit). If the UE successfully receives and decodes downlink signaling via PDSCH 310-d in each of the segments 305 (e.g., if the feedback bit corresponding to PDSCH 310 in segment 305-a is an ACK bit), the UE can transmit four ACK feedback bits in the feedback codebook 315-b. However, if the UE generates a NACK bit for PDSCH 310-d (e.g., if downlink signaling was not successfully received by PDSCH 310-d), the UE can send NACK bits for each of the segments 305 that overlap with PDSCH 310-d in the feedback codebook 315-b. That is, the UE can send four NACK feedback bits representing PDSCH 310-d in the feedback codebook 315-b.

[0112] Figure 4 An example of a grid 400 supporting a segmented feedback codebook according to one or more aspects of this disclosure is shown. The grid 400 may implement aspects of, or be implemented by, wireless communication system 100, wireless communication system 200, grids 300-a and 300-b, or any combination thereof. Although the grid 400 is illustrated as including a certain number of segments 405 and PDSCH 410, any number and combination of segments 405 and / or PDSCH 410 is possible.

[0113] In some cases, the feedback codebook 415 may be a codebook based on semi-static segmentation. Additionally or alternatively, the feedback codebook 415 may be an example of a Type 1 codebook (e.g., an old-style codebook). The UE may generate a single feedback bit for each of the candidate PDSCH 410 locations, regardless of whether PDSCH 410 is successfully received. However, a feedback codebook 415 including feedback bits for each of the scheduled PDSCH 410 locations can consume significant resources (e.g., have a large size), resulting in substantial signaling overhead.

[0114] Conversely, the feedback codebook 415 may include feedback bits for each segment 405. For example, a network entity may send a DCI (e.g., grant) to schedule one or more PDSCH 410s on one or more segments 405. The UE may report feedback information for each segment of the resource (e.g., segment 405-a, segment 405-b, segment 405-c, etc.). For example, the UE may generate a single feedback bit (e.g., ACK bit or NACK bit) for each segment 405. The UE may generate a feedback codebook 415 including feedback bits for each of the segments 405, and the UE may send the feedback codebook 415 to the network entity. That is, the feedback codebook 415 may include a single feedback bit representing each segment (e.g., segment 405-a, segment 405-b, and segment 405-c).

[0115] In some cases, a Type 1 codebook can use K0 and / or K1 values ​​to find (e.g., determine) possible PDSCH 410 scheduling locations (e.g., candidate locations) corresponding to the PUCCH. In some cases, the subcarrier spacing between PDSCH 410 and the Physical Downlink Control Channel (PDCCH) can be different or the same. If the subcarrier spacing of PDSCH 410 and PDCCH is the same, the time delay between the DCI slot and the PDSCH 410 slot can be the K0 value. That is, the K0 value can be the time delay between the DCI slot and the PDSCH 410 slot. The K1 value can indicate the time delay between the PDSCH 410 slot and the Uplink Control Information (UCI) slot. The UCI slot may include a PUCCH carrying feedback information (e.g., ACK or NACK bits) associated with PDSCH 410. In other words, the K1 value can define the time gap between the transmission of PDSCH 410 and the reception of a PUCCH carrying feedback information for PDSCH 410.

[0116] In some cases, the UE can determine a certain number of messages (e.g., PDSCH 410) scheduled within segment 405 (e.g., scheduled for resources associated with segment 405). Furthermore, the UE can use a K1 value (e.g., the time offset between the time PDSCH 410 is received and the PUCCH reporting timing for sending feedback information associated with feedback codebook 415) to determine a certain number of PDSCH 410 scheduled within segment 405. For example, the UE can determine which segments 405 in the segment set (e.g., segment 405-a, segment 405-b, segment 405-c, etc.) may contain one or more PDSCH 410s scheduled to report feedback information at a target PUCCH timing. In some cases, the UE can use multiple K1 configurations.

[0117] In some cases, the UE can generate feedback bits (e.g., ACK or NACK bits) for each segment 405. If multiple PDSCH 410 candidate locations exist within segment 405, the UE can bundle feedback information for all PDSCH 410s within segment 405 into a single feedback bit. The UE can then generate a feedback codebook 415 and transmit the feedback codebook including the single feedback bit.

[0118] In some cases, if each of the PDSCH 410 messages (e.g., a certain number of messages) within segment 405 is successfully received and decoded, the UE may send an ACK bit. For example, the UE may determine that segment 405-a includes three PDSCH 410 scheduling events. The UE may successfully decode PDSCH 410-a, PDSCH 410-b, and PDSCH 410-c. Therefore, the UE may include an ACK bit in the feedback codebook 415 to indicate feedback information associated with segment 405-a.

[0119] In some cases, if the UE fails to successfully decode (e.g., not receive) at least one of the PDSCH 410 messages during segment 405 (e.g., at least one of a certain number of messages), the UE may send a NACK bit. For example, the UE may determine that segment 405-b includes three PDSCH 410 scheduling opportunities. The UE may successfully decode PDSCH 410-e, but may fail to successfully decode PDSCH 410-d and / or PDSCH 410-f. In these cases, the UE may include a NACK bit in the feedback codebook 415 to indicate feedback information associated with segment 405-b. Additionally, the UE may determine that segment 405-c includes two or three PDSCH 410 scheduling opportunities. Alternatively, the UE may not know how many PDSCH 410 scheduling opportunities are within segment 405-c. The UE may fail to successfully decode PDSCH 410-g and / or PDSCH 410-h. Therefore, the UE can include a NACK bit in the feedback codebook 415 to indicate feedback information associated with segment 405-c.

[0120] In some cases, the feedback codebook 415 may include feedback information for multiple segments. For the example of grid 400, the feedback codebook 415 may be a 3-bit codebook (e.g., ACK bit for segment 405-a, NACK bit for segment 405-b, and NACK bit for segment 405-c).

[0121] Figure 5 An example of a grid 500 supporting a segmented feedback codebook according to one or more aspects of this disclosure is shown. The grid 500 may implement aspects of, or be implemented by, wireless communication system 100, wireless communication system 200, grids 300-a, 300-b, and 400, or any combination thereof. Although the grid 500 is illustrated as including a certain number of segments 505 and PDSCH 510, any number and combination of segments 505 and / or PDSCH 510 is possible.

[0122] In some cases, the feedback codebook 515 may be based on a dynamic codebook (e.g., a codebook with a dynamic length). The feedback codebook 515 may include feedback information for multiple segments 505. However, at least one of the segments 505 may not have feedback information (e.g., a corresponding ACK or NACK bit). For example, segment 505-b may be empty (e.g., scheduling events PDSCH 510-d, PDSCH 510-e, and PDSCH 510-f do not have corresponding scheduled messages). In these cases, the UE may not assign feedback bits to segment 505-b (e.g., no corresponding ACK or NACK bit), thereby reducing the size (e.g., number of bits) of the feedback codebook 515.

[0123] In some cases, the UE can determine which segments 505 have relevant feedback information. For example, a DCI (e.g., grant) can indicate which one or more segments 505 have corresponding feedback information. However, the UE may fail to receive the DCI (e.g., due to a DCI loss detection event).

[0124] In some cases, the UE may receive one or more DCI grants for scheduling one or more PDSCH 510s during segment 505. DCI grants may include, and sometimes include, a segment assignment index. In some cases, the segment assignment index may be an example of a DAI. A DAI may be a type of index that associates a scheduled message (e.g., a PDSCH) with a HARQ ACK / NACK transmission associated with the scheduled message. Where a DAI is used as a segment assignment index, the DCI may include a DAI for each PDSCH 510 transmitted in a particular segment. In other cases, where a segment assignment index is associated with a segment, each PDSCH 510 transmitted in a particular segment includes a segment assignment index associated with the segment. In some examples, DAI and segment assignment index are synonymous and may be treated similarly. These segment index indicators may increment sequentially from one PDSCH 510 to the next (e.g., 0, 1, 2, 3, etc.). For example, the UE may receive a first grant for scheduling PDSCH 510-a during segment 505-a. The first grant may also include a first segmentation index indicator (e.g., value 0) associated with segment 505-a. The UE may receive a second grant for scheduling PDSCH 510-b during segment 505-a. The second grant may include a second segmentation index indicator (e.g., value 1) associated with segment 505-a. The UE may receive a third grant for scheduling PDSCH 510-c during segment 505-a. The third grant may include a third segmentation index indicator (e.g., value 2) associated with segment 505-a. In some cases, the UE may successfully decode PDSCH 510-a, PDSCH 510-b, and PDSCH 510-c. Because each PDSCH 510 within segment 505-a is associated with an incrementally increasing (e.g., without skipping any values) segment index indicator (e.g., segment DAI), the UE can generate an ACK bit for segment 505-a.

[0125] In some cases, the UE may determine that at least one or more segment index indicator values ​​have been skipped (e.g., there is a discontinuity in the values ​​of segment DAI indicators received as part of an authorization). Therefore, the UE may generate (e.g., assign) a NACK bit to segment 505 associated with the skipped segment index indicator. For example, authorization may schedule PDSCH 510-g during segment 505-c. This authorization may also include the segment index indicator associated with segment 505-c. If the segment index indicator associated with PDSCH 510-g does not increment from the previous segment index indicator (e.g., by one) (e.g., if the segment index indicator associated with PDSCH 510-g is not 4), the UE may determine that it failed to detect one or more authorizations for scheduling PDSCH 510. Therefore, the UE can generate a NACK bit for segment 505-c in the event of a loss of segment DAI value (e.g., regardless of whether the UE successfully decodes PDSCH 510-g and / or PDSCH 510-h).

[0126] In some cases, the UE may receive one or more DCI grants for scheduling one or more PDSCH 510s during one or more segments 505. A DCI grant may indicate feedback information for a PDSCH 510 to be reported in the same PUCCH timing. Additionally, a DCI grant may include a segment index indicator. For each of the PDSCH 510s reported in the same PUCCH timing, an associated segment index indicator may be added for each subsequent segment 505. For example, each of the PDSCH 510s scheduled in segment 505-a may have segment index one (e.g., value 1). That is, one or more grants for scheduling PDSCH 510-a, PDSCH 510-b, and PDSCH 510-c may include a segment index indicator associated with segment 505-a (e.g., having value 1). Similarly, each of the PDSCH 510s scheduled in segment 505-c may have segment index two (e.g., value 2). In other words, granting permission to schedule PDSCH 510-g may include a segment index indicator (e.g., with a value of 2) associated with segment 505-c.

[0127] Figure 6A and Figure 6BExamples of grids 600-a and 600-b supporting segmented feedback codebooks according to one or more aspects of this disclosure are illustrated. Networks 600-a and 600-b may implement aspects of, or be implemented by, wireless communication system 100, wireless communication system 200, grids 300-a to 500, or any combination thereof. Although grids 600-a and 600-b are illustrated as including a certain number of segments 605 and PDSCH 610, any number and combination of segments 605 and / or PDSCH 610 is possible.

[0128] In some cases, the feedback codebook 615 may include one or more NACK-ACK (e.g., ACK-NACK) bit errors as a result of bundling. For example, a network entity may schedule multiple PDSCH 610s within a single segment 605 (e.g., in Time Division Multiplexing (TDM)). In some cases, the UE may detect a subset (e.g., not all) of the PDSCH 610s scheduled for that particular segment 605. Therefore, the UE may assume that it failed to receive one or more DCI grants (e.g., a lost grant event occurred) and include NACK bits for the lost one or more PDSCH 610s. Thus, the feedback bits associated with a particular segment 605 may be NACK bits. However, the UE may not be able to identify erroneous conditions that lead to the automatic generation of a NACK (e.g., a dummy NACK).

[0129] In some cases, the UE can identify error conditions and reduce ACK-to-NACK errors from bundled errors. The UE can utilize one or more scheduling constraints when identifying error conditions. For example, the UE can implement intra-segment bundle checks.

[0130] In some cases, the UE can determine whether any scheduled but undetected PDSCH 610 exists through intra-segment bundle checks (e.g., DCI loss events). That is, the UE can determine whether a scheduled PDSCH 610 was not successfully detected. In one example, the UE can check the SLIV table. For example, the UE can determine the start parameters and / or length parameters for PDSCH 610. The UE can check multiple (e.g., all) possible SLIV combinations in the Time Domain Resource Allocation (TDRA) table. The UE can then compare the TDRA table with the SLIVs of the detected PDSCH 610. In a second example, the UE can perform DCI-based intra-segment bundle checks. For example, a network entity can configure the UE to expect up to a certain number of downlink grants per segment 605. In other words, if the UE detects that the number of grants for resource reception including a specific segment 605 meets a threshold (e.g., a pre-configured grant threshold), the UE can determine that no other PDSCH 610 is scheduled for that segment (e.g., because a network entity might not send additional DCI grants to schedule other PDSCH 610 in the same segment 605). In some cases, the UE can receive an indication of the maximum number of grants that can be scheduled for PDSCH 610 for segment 605. The maximum number of DCIs (e.g., grants) that can be granted for one or more PDSCH 610 in the segment can be a UE capability (e.g., indicated by the UE) or an RRC configuration.

[0131] In some cases, a network entity may send more than one grant to schedule PDSCH 610 in a particular segment 605. However, if the UE receives a single DCI grant, the UE may be unable to determine whether the network entity sent any additional DCI grants (e.g., a missing grant) or whether only a single DCI grant was sent for that particular segment 605. Therefore, the UE may assume that it failed to detect at least one DCI grant and generate a NACK bit (e.g., a dummy NACK bit). However, if the UE bundles feedback information for segment 605 that includes a dummy NACK bit, the UE may unnecessarily send the NACK bit in the feedback codebook 615. Instead, the UE may use SLIV for the detected grant to determine whether there are any additional potential grants that can schedule PDSCH 610 in segment 605.

[0132] In some cases, network entities can configure the UE (e.g., send control signaling) to have a maximum number of PDSCH 610s (e.g., messages) that can be scheduled (e.g., communicated via a set of resources) for segment 605. The maximum number of PDSCH 610s that can be scheduled within a segment 605 (e.g., the maximum number of PDSCH 610s the UE can support) can be a UE capability (e.g., indicated by the UE) or an RRC configuration. Therefore, the UE can generate fewer dummy NACKs (e.g., not generate any dummy NACKs). In some cases, network entities can indicate that a single PDSCH 610 was scheduled during segment 605 (e.g., the UE expects low-density service). In these cases, the UE may not bundle feedback information.

[0133] exist Figure 6A In the example, the network entity can configure the UE to receive an authorization DCI for each segment 605. For example, the UE can receive authorization to schedule PDSCH 610-a during segment 605-a. Therefore, the UE can determine that PDSCH 610-a is the only PDSCH 610 scheduled during segment 605-a. That is, the UE may not expect authorization to schedule PDSCH 610-b or PDSCH 610-c (e.g., generating a dummy NACK bit). The UE can successfully decode PDSCH 610-a and send an ACK bit (e.g., in feedback codebook 615-a) to indicate feedback information associated with segment 605-a. Similarly, the UE can receive authorization to schedule PDSCH 610-e during segment 605-b. Therefore, the UE can determine that PDSCH 610-e is the only PDSCH 610 scheduled during segment 605-b. In other words, the UE may not expect to be granted permission to schedule PDSCH 610-d or PDSCH 610-f. The UE can successfully decode PDSCH 610-e and send ACK bits (e.g., in feedback codebook 615-a) to indicate feedback information associated with segment 605-b. Feedback codebook 615-a can represent a semi-static codebook. Therefore, if the UE fails to decode PDSCH 610-g and / or PDSCH 610-h during segment 605-c, the UE can generate NACK bits to indicate feedback information associated with segment 605-c. In some cases, feedback codebook 615-a can be a 3-bit codebook (e.g., codebook 615-a includes ACK bits for indicating feedback information from segment 605-a, ACK bits for indicating feedback information from segment 605-b, and NACK bits for indicating feedback information from segment 605-c).

[0134] exist Figure 6BIn the example, the network entity can configure the UE to receive an authorization DCI for each segment 605. For example, the UE can receive authorization to schedule PDSCH 610-k during segment 605-d. Therefore, the UE can determine that PDSCH 610-k is the only PDSCH 610 scheduled during segment 605-d. That is, the UE may not expect authorization to schedule PDSCH 610-i or PDSCH 610-j (e.g., and generate a dummy NACK bit). The UE can successfully decode PDSCH 610-k and send an ACK bit (e.g., in feedback codebook 615-b) to indicate feedback information associated with segment 605-d. Similarly, the UE can receive authorization to schedule PDSCH 610-o during segment 605-f. Therefore, the UE can determine that PDSCH 610-o is the only PDSCH 610 scheduled during segment 605-f. In other words, the UE may not expect to be granted permission to schedule PDSCH 610-p. The UE can successfully decode PDSCH 610-o and send ACK bits (e.g., in feedback codebook 615-b) to indicate feedback information associated with segment 605-f. Feedback codebook 615-b can represent a dynamic codebook. Therefore, segment 605-e can be empty, and if the UE fails to decode PDSCH 610-l, PDSCH 610-m, and / or PDSCH 610-n during segment 605-e, the UE may not generate NACK bits. In some cases, feedback codebook 615-b can be a 2-bit codebook (e.g., codebook 615-b includes ACK bits for indicating feedback information from segment 605-d and ACK bits for indicating feedback information from segment 605-f).

[0135] Figure 7 An example of a grid 700 supporting a segmented feedback codebook according to one or more aspects of this disclosure is shown. The grid 700 may implement aspects of, or be implemented by, wireless communication system 100, wireless communication system 200, grids 300-a to 600-b, or any combination thereof. Although the grid 700 is illustrated as including a certain number of segments 705 and PDSCH 710, any number and combination of segments 705 and / or PDSCH 710 is possible.

[0136] In some cases, a network entity may send more than one grant capable of scheduling PDSCH 710 per segment 705. However, if the UE receives a single DCI grant, the UE may be unable to determine whether the network entity sent any additional DCI grants (e.g., a lost grant) or whether a single DCI grant was sent for that particular segment 705. For example, the UE may determine that the segmentation limit (e.g., the maximum number of grants capable of scheduling PDSCH 710 per segment 705) is two. Furthermore, the UE may detect a single grant. Therefore, the UE may be unable to distinguish whether a second grant was not detected or only one grant was scheduled and sent during the segmentation. In these cases, the UE may assume that it failed to detect at least one DCI grant and generate a NACK bit (e.g., a dummy NACK bit). However, if the UE bundles feedback information for segment 705 including a dummy NACK bit, the UE may unnecessarily send the NACK bit in the feedback codebook 715. Conversely, the UE can perform intra-segment loss detection to determine if there are any undetected potential permissions that could be scheduled for PDSCH 710 in segment 705.

[0137] In some cases, the UE may receive one or more DCI grants during segmentation 705, scheduling one or more PDSCH 710s. DCI grants may include a total segmentation DAI (e.g., a message count indicator). Additionally or alternatively, DCI grants may include a segmentation index indicator, as referenced... Figure 5As described, a message quantity indicator can indicate the number of PDSCH 710s that can be scheduled (e.g., communicated via resources) within segment 705. Each grant for scheduling PDSCH 710s within the same segment 705 may include a message quantity indicator (e.g., total segment DAI value). For example, the UE may receive one or more grants for scheduling PDSCH 710-a, PDSCH 710-b, and PDSCH 710-c within segment 705-a. This one or more grants may indicate that the message quantity indicator associated with segment 705-a is three (e.g., a value of 3). Therefore, if the UE successfully decodes PDSCH 710-a, PDSCH 710-b, and PDSCH 710-c (e.g., the UE decodes a total of three messages in segment 705-a), the UE can generate an ACK bit representing feedback information associated with segment 705-a. Similarly, the UE can receive permission to schedule PDSCH 710-e within segment 705-b. This permission may indicate that the message quantity indicator associated with segment 705-b is one (e.g., a value of 1). In this case, the UE may determine that only one PDSCH 710 is scheduled in segment 705-b and may not expect to receive PDSCH 710-d or PDSCH 710-f. Therefore, if the UE successfully decodes PDSCH 710-e, the UE can generate an ACK bit representing feedback information associated with segment 705-b.

[0138] In some cases, the feedback codebook 715 can represent a semi-static codebook. Therefore, if the UE fails to decode PDSCH 710-g and / or PDSCH 710-h during segment 705-c, the UE can generate a NACK bit to indicate feedback information associated with segment 705-c. In some cases, the feedback codebook 715 can be a 3-bit codebook (e.g., codebook 715 includes an ACK bit for indicating feedback information from segment 705-a, an ACK bit for indicating feedback information from segment 705-b, and a NACK bit for indicating feedback information from segment 705-c). In some other cases, the feedback codebook 715 can represent a dynamic codebook. Therefore, segment 705-c can be empty, and if the UE fails to decode PDSCH 710-g and / or PDSCH 710-h during segment 705-c, the UE may not generate a NACK bit. In some cases, the feedback codebook 715 may be a 2-bit codebook (e.g., the codebook 715 includes ACK bits for representing feedback information from segment 705-a and ACK bits for representing feedback information from segment 705-b).

[0139] Figure 8An example of a grid 800 supporting a segmented feedback codebook according to one or more aspects of this disclosure is shown. The grid 800 may implement aspects of, or be implemented by, wireless communication system 100, wireless communication system 200, grids 300-a to 700, or any combination thereof. Although the grid 800 is illustrated as including a certain number of segments 805, PDSCH 810, and CC 815, any number and combination of segments 805, PDSCH 810, and CC 815 is possible.

[0140] In some cases, the UE can generate a feedback codebook that includes feedback information from PDSCH 810 scheduled for different segments 805 and / or different CC 815s. That is, segments of resources can be defined on time-domain resources and one or more CC 815s. In some cases, one or more segments 805 can be defined in the time domain. That is, the same segmentation boundaries can apply to each of the CC 815s.

[0141] In some cases, network entities can configure the UE using a per-segment limit of 1 (e.g., at most one DCI grant for scheduling one or more PDSCH 810s per segment 805). However, throughput may be relatively low in these cases. Alternatively, network entities can configure the UE to utilize CA mode to improve scheduling flexibility. For example, network entities can serve the UE from any number of CCs (e.g., CC 815-a, CC 815-b, CC 815-c, CC 815-d, etc.). In these cases, even if the per-segment limit is set to 1, multiple CCs 815 can be scheduled to the UE simultaneously (e.g., on overlapping time resources), which may be beneficial for in-band CA (e.g., multiple CCs 815 in frequency range (FR) 2). However, the same segment 805 boundary may not apply to each of the CCs 815 (e.g., for inter-band CA, inter-FR, etc., with different subcarrier spacing).

[0142] In some cases, segment 805 can be defined in both the time and frequency domains (e.g., for CA operations). For example, time-domain segments can be defined on a subset of CC 815 (e.g., the frequency domain). Generally, different time-domain segments can be defined for different subsets of CC 815. In some cases, segment 805 boundaries can be aligned or nested across different CC 815s. Additionally or alternatively, network entities can define different per-segment permission limits for different segments 805 (e.g., across the frequency domain) (e.g., the maximum number of permissions to schedule PDSCH 810 within a segment 805).

[0143] In some cases, network entities can configure the UE to report feedback information for PDSCH 810 across different CC 815s. For example, the UE can receive control signaling to report feedback information for PDSCH 810-a within segment 805-a and across CC 815-a. Additionally, the UE can report feedback for PDSCH 810-b within the same segment 805-a but across CC 815-b (e.g., different frequencies). The UE can bundle feedback information for segment 805-a (e.g., send a feedback bit).

[0144] In some cases, the UE may receive additional control signaling to report feedback information for segment 805-b. The time-domain resources including segment 805-b may at least partially overlap with the time-domain resources including segment 805-a. Simultaneously, segment 805-b may be associated with one or more different CCs (e.g., CC 815-c and CC 815-d). That is, the UE may generate a single feedback bit for PDSCH 810 (e.g., PDSCH 810-c) within segment 805-b. Similarly, the UE may report feedback information for segment 805-c (e.g., including PDSCH 810-d).

[0145] In some cases, the UE can generate a codebook based on semi-static segments. In these cases, when generating the feedback codebook, the UE can determine the number of permissions per segment 805 (e.g., per segment limit), the number of PDSCH 810 per permission, the number of PDSCH 810 per segment 805 (e.g., per segment 805 for missing PDSCH 810 checks), or any combination thereof.

[0146] In some cases, the UE can generate a codebook based on dynamic segmentation (e.g., a feedback codebook with dynamic length). For example, the UE can receive one or more DCI grants for scheduling one or more PDSCH 810s during one or more segments 805 and across one or more CCs 815. A DCI grant can indicate feedback information for PDSCH 810s to be reported in the same PUCCH timing. Additionally, a DCI grant can include a segmentation index indicator (e.g., total DAI). For each of the PDSCH 810s to be reported in the same PUCCH timing, the associated segmentation index indicator can be incremented for each subsequent segment 805. For example, each of the PDSCH 810s scheduled in segment 805-a can have a segmentation index one (e.g., a value of 1). That is, one or more grants for scheduling PDSCH 810-a and PDSCH 810-b can include a segmentation index indicator (e.g., with a value of 1) associated with segment 805-a. Similarly, each of the PDSCH 810s scheduled in segment 805-b may have segment index two (e.g., value 2). That is, permission to schedule PDSCH 810-c may include a segment index indicator (e.g., with value 2) associated with segment 805-b. PDSCH 810s scheduled in segment 805-c (e.g., PDSCH 810-d) may have segment index three (e.g., value 3).

[0147] In some cases, the UE can determine that it failed to detect (e.g., lost) one or more grants by using a segment index indicator. For example, the UE may fail to detect a grant scheduled for PDSCH 810-e within segment 805-d and across CC 815-b. However, the UE can detect a grant scheduled for PDSCH 810-f within segment 805-e and across CC 815-c. A grant scheduled for PDSCH 810-f may include a segment index indicator five (e.g., value 5) associated with segment 805-e. Therefore, the UE can determine that a segment index value is lost (e.g., segment index value 4 is skipped). Due to the discontinuity of the segment index indicator values, the UE can determine that it failed to detect a grant and generate a NACK indicating feedback information for segment 805-d.

[0148] In some cases, the UE may fail to detect permission to schedule PDSCH 810-f within segment 805-e. If future permission is not sent (e.g., subsequent PDSCH 810 is not scheduled within segment 805-f), the UE may fail to determine that permission has been lost, resulting in a mismatch in codebook size (e.g., a mismatch between the number of segments 805 and the number of feedback bits in the codebook).

[0149] Figure 9An example of a process flow 900 supporting a segmented feedback codebook according to one or more aspects of this disclosure is shown. Process flow 900 may implement, or be implemented by, aspects of wireless communication system 100, wireless communication system 200, mesh 300-a to 800, or any combination thereof. For example, process flow 900 may include UE 115-b and network entity 105-b, which may be references... Figure 1 and Figure 2 Examples of the corresponding devices described.

[0150] In the following description of process flow 900, operations between UE 115-b and network entity 105-b may be sent in a different order than the example order shown, or operations performed by UE 115-b and network entity 105-b may be performed in a different order or at different times. Some operations may also be omitted from process flow 900, and other operations may be added to process flow 900.

[0151] At 905, UE 115-b may (e.g., from network entity 105-b) receive one or more grants to schedule one or more PDSCHs (e.g., messages) within a segment of a resource. A segment may be any number and combination of time and / or frequency resources.

[0152] At 910, the UE may (e.g., from network entity 105-b) receive control signaling to report feedback information for resource segmentation, as described herein. The feedback information may include the ACK or NACK bit of the HARQ feedback associated with the segmentation.

[0153] At position 915, the UE can generate a feedback codebook. The feedback codebook can be associated with a PUCCH reporting timing. Additionally, the feedback codebook may include feedback bits corresponding to each segment associated with a PUCCH reporting timing. The UE can bundle feedback information for multiple PDSCHs within a segment into a single feedback bit. In some cases, the feedback codebook can be semi-static or dynamic.

[0154] At 920, the UE may (e.g., send a feedback codebook to network entity 105-b) (e.g., a feedback codebook generated at 915). The feedback codebook may include one or more bits of HARQ feedback, as described herein.

[0155] Figure 10A block diagram 1000 of a device 1005 supporting a segmented feedback codebook according to one or more aspects of this disclosure is shown. Device 1005 may be an example of various aspects of a UE 115 as described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Device 1005 or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020) may include at least one processor, which 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).

[0156] Receiver 1010 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 associated with segmented feedback codebooks). The information may be transmitted to other components of device 1005. Receiver 1010 may utilize a single antenna or a collection of antennas.

[0157] Transmitter 1015 may provide components for transmitting signals generated by other components of device 1005. For example, transmitter 1015 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with segmented feedback codebooks), such as packets, user data, control information, or any combination thereof. In some implementations, transmitter 1015 may be co-located with receiver 1010 in a transceiver module. Transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0158] The communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the segmented feedback codebook as described herein. For example, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0159] In some examples, the communication manager 1020, receiver 1010, transmitter 1015, 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, 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).

[0160] Additionally or alternatively, the communication manager 1020, receiver 1010, transmitter 1015, 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 1020, receiver 1010, transmitter 1015, 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 as or otherwise individually or collectively to support the performance of the functions described in this disclosure).

[0161] In some examples, the communication manager 1020 may be configured to use or otherwise coordinate with the receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or integrate with the receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0162] According to the examples disclosed herein, the communication manager 1020 may support wireless communication. For example, the communication manager 1020 may be capable of, configured to, or operable to support components for receiving control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including either an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback. The communication manager 1020 may be capable of, configured to, or operable to support components for generating a feedback codebook associated with a set of multiple segments based on control signaling. The communication manager 1020 may be capable of, configured to, or operable to support components for transmitting a feedback codebook for a set of multiple segments based on the generated feedback codebook, the feedback codebook including a bit of feedback information associated with the segment according to the feedback codebook.

[0163] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 (e.g., at least one processor that controls or otherwise couples to receiver 1010, transmitter 1015, communication manager 1020, or a combination thereof) can support techniques for more flexible and responsive communication and more efficient use of communication resources.

[0164] Figure 11 A block diagram 1100 of a device 1105 supporting a segmented feedback codebook according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of device 1005 or UE 115 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105 or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, and communication manager 1120) 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).

[0165] Receiver 1110 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 associated with segmented feedback codebooks). The information may be passed to other components of device 1105. Receiver 1110 may utilize a single antenna or a collection of antennas.

[0166] Transmitter 1115 may provide components for transmitting signals generated by other components of device 1105. For example, transmitter 1115 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with segmented feedback codebooks), such as packets, user data, control information, or any combination thereof. In some implementations, transmitter 1115 may be co-located with receiver 1110 in a transceiver module. Transmitter 1115 may utilize a single antenna or a collection of multiple antennas.

[0167] Device 1105 or its various components may be examples of parts for performing various aspects of the segmented feedback codebook as described herein. For example, communication manager 1120 may include feedback information component 1125, codebook generation component 1130, codebook transmission component 1135, or any combination thereof. Communication manager 1120 may be examples of various aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use or otherwise cooperate with receiver 1110, transmitter 1115, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in combination with receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0168] According to the examples disclosed herein, the communication manager 1120 may support wireless communication. The feedback information component 1125 is capable of, configured to, or operable to support components for receiving control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including either an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback. The codebook generation component 1130 is capable of, configured to, or operable to support components for generating a feedback codebook associated with a set of multiple segments based on control signaling. The codebook transmission component 1135 is capable of, configured to, or operable to support components for transmitting a feedback codebook for a set of multiple segments based on the generated feedback codebook, the feedback codebook including a bit of feedback information associated with the segment according to the feedback codebook.

[0169] Figure 12A block diagram 1200 is shown of a communication manager 1220 supporting segmented feedback codebooks according to one or more aspects of this disclosure. The communication manager 1220 may be an example of aspects of the communication manager 1020, communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of parts for performing various aspects of the segmented feedback codebooks as described herein. For example, the communication manager 1220 may include a feedback information component 1225, a codebook generation component 1230, a codebook transmission component 1235, an authorization component 1240, a scheduled message component 1245, a downlink assignment index indicator component 1250, a feedback assignment component 1255, an authorization component 1260, a message parameter component 1265, an authorization threshold component 1270, a second segmentation component 1275, a segmentation index indicator component 1280, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), can communicate with each other directly or indirectly (e.g., via one or more buses).

[0170] According to the examples disclosed herein, the communication manager 1220 may support wireless communication. The feedback information component 1225 is capable of, configured to, or operable to support components for receiving control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including either an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback. The codebook generation component 1230 is capable of, configured to, or operable to support components for generating a feedback codebook associated with a set of multiple segments based on control signaling. The codebook transmission component 1235 is capable of, configured to, or operable to support components for transmitting a feedback codebook for a set of multiple segments based on the generated feedback codebook, the feedback codebook including a bit of feedback information associated with the segment according to the feedback codebook.

[0171] In some examples, grant component 1240 is capable of, configured to, or able to operate to support components for receiving one or more grants for scheduling one or more messages in a segment, wherein the generation of a feedback codebook is based on receiving one or more grants.

[0172] In some examples, the scheduled message component 1245 is capable of, configured to, or operable to support a component for determining, based on the offset between the time when a certain number of messages are received and the uplink timing for sending feedback information associated with the feedback codebook, for resource scheduling including segmentation, wherein the generation of the feedback codebook is based on determining the certain number of messages.

[0173] In some examples, a bit of the feedback information associated with a segment includes information about a certain number of messages.

[0174] In some examples, in order to support the sending of feedback codebooks, the codebook sending component 1235 is capable of being configured or operable to support a component for sending a bit of feedback information, including an acknowledgment bit, in the event that each message in a certain number of messages is successfully decoded.

[0175] In some examples, in order to support the sending of feedback codebooks, the codebook sending component 1235 is capable of being configured or operable to support a component for sending a bit of feedback information, including a negative acknowledgment bit, in the event that at least one message in a number of messages fails to be successfully decoded.

[0176] In some examples, to support the generation of a feedback codebook, the downlink assignment index indicator component 1250 is capable of, configured to, or operable to support components for determining discontinuities in the values ​​of downlink assignment index indicators received as part of an acknowledgment. In some examples, to support the generation of a feedback codebook, the feedback assignment component 1255 is capable of, configured to, or operable to support components for assigning negative acknowledgments to segments in the feedback codebook based on the determined discontinuities in the values.

[0177] In some examples, grant component 1260 is capable of, configured to, or able to operate to support components for receiving grants for a first message to be communicated during segmentation, the grant including a first downlink assignment index indicator associated with the segmentation, wherein the generation of the feedback codebook is based on the first downlink assignment index indicator.

[0178] In some examples, granting component 1260 is capable of, configured to, or operable to support components for receiving a second grant for a second message to be communicated during segmentation, the second grant including a second downlink assignment index indicator associated with the segmentation and different from the first downlink assignment index indicator. In some examples, granting component 1260 is capable of, configured to, or operable to support components for receiving a third grant for a third message to be communicated during segmentation, the third grant including a third downlink assignment index indicator associated with the segmentation and different from the first downlink assignment index indicator and the second downlink assignment index indicator.

[0179] In some examples, message parameter component 1265 is capable of, can be configured to, or can operate to support components for determining start parameters and length parameters for messages scheduled to be delivered via resources including segments, wherein the generation of feedback codebook is based on the determination of start parameters and length parameters.

[0180] In some examples, the permission threshold component 1270 is capable of, configured to, or operable to support components for determining whether the number of permissions received for a resource including segments meets a threshold, wherein the generation of a feedback codebook is based on determining whether the number of received permissions meets the threshold.

[0181] In some examples, the scheduled message component 1245 is capable of, configured to, or able to operate to support components for determining whether a message scheduled to be delivered via a segmented resource has not been successfully detected, wherein a feedback codebook is generated based on the determination that the message has not been successfully detected.

[0182] In some examples, the scheduled message component 1245 is capable of, configured to, or able to operate to support components for receiving a second control signaling that includes an indication of the maximum number of messages that can be scheduled to be delivered via resources including segments, wherein the generation of a feedback codebook is based on receiving the second control signaling.

[0183] In some examples, the scheduled message component 1245 is capable of, configured to, or able to operate to support components for sending signaling to indicate that the UE can support a maximum number of messages scheduled in resources including segments, wherein receiving the second control signaling is based on sending the signaling.

[0184] In some examples, the scheduled message component 1245 is capable of, configured to, or able to operate to support components for receiving a second control signaling that includes an indication of a maximum number of messages that can be scheduled to be delivered via a segmented resource, wherein the generation of a feedback codebook is based on receiving the second control signaling.

[0185] In some examples, in order to support receiving control signaling, grant component 1260 is capable, configured, or able to operate to support components for receiving grants for a first message to be communicated during a segmentation, the grant including a message quantity indicator associated with the number of messages scheduled to be communicated via a resource including the segmentation, wherein the generation of the feedback codebook is based on the message quantity indicator.

[0186] In some examples, to support receive control signaling, the granting component 1260 is capable of, configured to, or able to operate to support components for receiving grants for a first message to be communicated during a segmentation period, the grant including a segmentation index indicator associated with the segmentation and a message quantity indicator associated with the number of messages scheduled to be communicated via a resource including the segmentation. In some examples, to support receive control signaling, the granting component 1260 is capable of, configured to, or able to operate to support components for receiving a second grant for a second message to be communicated during a segmentation period, the second grant including a segmentation index indicator and a message quantity indicator, wherein the generation of the feedback codebook is based on the segmentation index indicator and the message quantity indicator.

[0187] In some examples, segmented resources are defined on one or more component carriers in a set of time-domain resources and multiple component carriers.

[0188] In some examples, the second segmentation component 1275 is capable of, configured to, or operable to support components for receiving second control signaling to report feedback information for the second segmentation of a resource, defining a resource including the second segmentation on a second time-domain resource that at least partially overlaps with the time-domain resource and on at least one component carrier that is different from one or more component carriers, wherein the generation of the feedback codebook is based on the second control signaling.

[0189] In some examples, the codebook generation component 1230 is capable of, can be configured to, or is operable to support components for generating a dynamic-length feedback codebook, wherein the generation of the feedback codebook is based on the generation of a dynamic-length feedback codebook.

[0190] In some examples, to support the generation of a dynamically long feedback codebook, grant component 1260 is capable of, configured to, or operable to support components for receiving one or more grants that schedule one or more messages in a set of multiple segments, the one or more grants including segment index indicators. In some examples, to support the generation of a dynamically long feedback codebook, segment index indicator component 1280 is capable of, configured to, or operable to support components for determining discontinuities in the values ​​of segment index indicators received as part of a grant. In some examples, to support the generation of a dynamically long feedback codebook, feedback assignment component 1255 is capable of, configured to, or operable to support components for assigning negative acknowledgments to at least one segment in the feedback codebook based on the determined discontinuities in values.

[0191] In some examples, a set of multiple messages is received via resources that include segments. In some examples, a segment comprises one or more time slots, one or more portions of time slots, or a combination thereof. In some examples, a first size of a first segment differs from a second size of a second segment. In some examples, resources that include segments are defined by a time slot index, a symbol index, or any combination thereof. In some examples, resources that include segments are defined by the timing of transmission via the physical uplink control channel. In some examples, resources that include segments are associated with the time domain, the frequency domain, or any combination thereof. Figure 13 A diagram of a system 1300 including a device 1305 supporting a segmented feedback codebook, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of device 1005, device 1105, or UE 115 as described herein, or may include components thereof. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1305 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1320, an input / output (I / O) controller 1310, a transceiver 1315, an antenna 1325, at least one memory 1330, code 1335, and at least one processor 1340. These components may communicate electronically via one or more buses (e.g., bus 1345) or be otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically).

[0192] I / O controller 1310 can manage the input and output signals of device 1305. I / O controller 1310 can also manage peripheral devices not integrated into device 1305. In some implementations, I / O controller 1310 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 1310 can utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, it may be another known operating system. Additionally or alternatively, the I / O controller 1310 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some embodiments, the I / O controller 1310 may be implemented as part of a processor or processing system (such as processor 1340). In some embodiments, a user may interact with device 1305 via the I / O controller 1310 or via hardware components controlled by the I / O controller 1310.

[0193] In some embodiments, device 1305 may include a single antenna 1325. However, in other embodiments, device 1305 may have more than one antenna 1325, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1315 may communicate bidirectionally via one or more antennas 1325 as described herein, a wired link, or a wireless link. For example, transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1315 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1325 for transmission; and demodulating packets received from one or more antennas 1325. In some embodiments, transceiver 1315 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1325 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1325 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1315 may include one or more processor or memory components or be configured to couple to such processor 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 1315, or transceiver 1315 and one or more antennas 1325, or transceiver 1315 and one or more antennas 1325 and one or more processor or memory components (e.g., processor 1340 or memory 1330 or both) may be included in a chip or chip assembly mounted in device 1305.

[0194] At least one memory 1330 may include random access memory (RAM), read-only memory (ROM), or any combination thereof. At least one memory 1330 may store computer-readable, computer-executable code 1335, including instructions that, when executed by one or more of at least one processor 1340, cause device 1305 to perform the various functions described herein. Code 1335 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some embodiments, code 1335 may not be directly executable by one of the at least one processor 1340, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some embodiments, at least one memory 1330 may also include a basic I / O system (BIOS) among other things, which controls basic hardware or software operations, such as interaction with peripheral components or devices. In some embodiments, at least one processor 1340 may include multiple processors, and at least one memory 1330 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 (e.g., as part of a processing system).

[0195] At least one processor 1340 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 1340 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 of the at least one processor 1340. At least one processor 1340 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks supporting segmented feedback codebooks). For example, device 1305 or components of device 1305 may include at least one processor 1340 and at least one memory 1330 coupled to one or more of the at least one processor 1340, wherein the at least one processor 1340 and at least one memory 1330 are configured to perform the various functions described herein. At least one processor 1340 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 (e.g., by executing code 1335) host functions for performing the functions of device 1305. At least one processor 1340 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (such as within one or more memories of at least one memory 1330). In some implementations, at least one processor 1340 may be a component of a processing system. A processing system generally refers to a system or a series of machines or components that receive input and process that input to produce a set of outputs (which may be passed to other systems or components of, for example, device 1305). For example, the processing system of device 1305 may refer to a system that includes various other components or sub-components of device 1305 (such as at least one processor 1340, transceiver 1315, communication manager 1320, or other components or combinations of components of device 1305). The processing system of device 1305 can interface with other components of device 1305 and can process information (such as inputs or signals) received from other components or output information to other components. For example, the chip or modem of device 1305 may include a processing system and one or more interfaces for outputting information or for acquiring information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to acquire information, or the same interface configured to both output and acquire information, and other specific implementations.In some embodiments, one or more interfaces may refer to the interface between the processing system of the chip or modem and the transmitter, enabling device 1305 to transmit information output from the chip or modem. Additionally or alternatively, in some embodiments, one or more interfaces may refer to the interface between the processing system of the chip or modem and the receiver, enabling device 1305 to receive information or signal input, and such information can be transmitted to the processing system. Those skilled in the art will readily recognize that a first interface may also receive information or signal input, and a second interface may also output information or signal output.

[0196] According to the examples disclosed herein, the communication manager 1320 may support wireless communication. For example, the communication manager 1320 may be capable of, configured to, or operable to support components for receiving control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including either an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback. The communication manager 1320 may be capable of, configured to, or operable to support components for generating a feedback codebook associated with a set of multiple segments based on control signaling. The communication manager 1320 may be capable of, configured to, or operable to support components for transmitting a feedback codebook for a set of multiple segments based on the generated feedback codebook, the feedback codebook including a bit of feedback information associated with the segment according to the feedback codebook.

[0197] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 can support techniques for improving and reducing processing-related user experience, utilizing communication resources more efficiently, improving coordination between devices, and improving the utilization of processing power.

[0198] In some implementations, the communication manager 1320 may be configured to use or otherwise coordinate with the transceiver 1315, one or more antennas 1325, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1320 is exemplified as a component of the transceiver 1315, in some implementations, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1315, at least one processor 1340, at least one memory 1330, code 1335, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1340, at least one memory 1330, code 1335, or any combination thereof). For example, code 1335 may include instructions that can be executed by one or more of the at least one processor 1340 to cause the device 1305 to perform various aspects of the segmented feedback codebook as described herein, or at least one processor 1340 and at least one memory 1330 may be otherwise configured to perform or support such operations.

[0199] Figure 14 A block diagram 1400 is shown of a device 1405 supporting a segmented feedback codebook according to one or more aspects of this disclosure. Device 1405 may be an example of aspects of network entity 105 as described herein. Device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. Device 1405 or one or more components of device 1405 (e.g., receiver 1410, transmitter 1415, and communication manager 1420) may include at least one processor, which 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).

[0200] Receiver 1410 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 1405. In some examples, receiver 1410 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1410 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0201] Transmitter 1415 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1405. For example, transmitter 1415 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 1415 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1415 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 1415 and receiver 1410 may be co-located in a transceiver, which may include or be coupled to a modem.

[0202] The communication manager 1420, receiver 1410, transmitter 1415, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the segmented feedback codebook as described herein. For example, the communication manager 1420, receiver 1410, transmitter 1415, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0203] In some examples, the communication manager 1420, receiver 1410, transmitter 1415, 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).

[0204] Additionally or alternatively, the communication manager 1420, receiver 1410, transmitter 1415, 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 1420, receiver 1410, transmitter 1415, 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 as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0205] In some examples, the communication manager 1420 may be configured to use or otherwise coordinate with the receiver 1410, transmitter 1415, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1420 may receive information from the receiver 1410, transmit information to the transmitter 1415, or integrate with the receiver 1410, transmitter 1415, or both to acquire information, output information, or perform various other operations as described herein.

[0206] According to the examples disclosed herein, the communication manager 1420 may support wireless communication. For example, the communication manager 1420 may be capable of, configured to, or operable to support components for transmitting control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including either an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request for feedback. The communication manager 1420 may be capable of, configured to, or operable to support components for receiving, based on control signaling, a feedback codebook associated with a set of multiple segments, the feedback codebook including a bit of feedback information associated with the segment according to the feedback codebook.

[0207] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 (e.g., at least one processor that controls or is otherwise coupled to receiver 1410, transmitter 1415, communication manager 1420, or a combination thereof) can support techniques for more flexible and responsive communication and more efficient use of communication resources.

[0208] Figure 15A block diagram 1500 is shown of a device 1505 supporting a segmented feedback codebook according to one or more aspects of this disclosure. Device 1505 may be an example of aspects of device 1405 or network entity 105 as described herein. Device 1505 may include a receiver 1510, a transmitter 1515, and a communication manager 1520. Device 1505 or one or more components of device 1505 (e.g., receiver 1510, transmitter 1515, and communication manager 1520) 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).

[0209] Receiver 1510 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 1505. In some examples, receiver 1510 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1510 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0210] Transmitter 1515 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1505. For example, transmitter 1515 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 1515 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1515 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 1515 and receiver 1510 may be co-located in a transceiver, which may include or be coupled to a modem.

[0211] Device 1505 or its various components may be examples of parts for performing various aspects of the segmented feedback codebook as described herein. For example, communication manager 1520 may include feedback information component 1525, codebook receiving component 1530, or any combination thereof. Communication manager 1520 may be examples of aspects of communication manager 1420 as described herein. In some examples, communication manager 1520 or its various components may be configured to use or otherwise cooperate with receiver 1510, transmitter 1515, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 1520 may receive information from receiver 1510, transmit information to transmitter 1515, or be integrated in combination with receiver 1510, transmitter 1515, or both to acquire information, output information, or perform various other operations as described herein.

[0212] According to the examples disclosed herein, the communication manager 1520 may support wireless communication. The feedback information component 1525 is capable of, configured to, or operable to support components for transmitting control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including either an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback. The codebook receiving component 1530 is capable of, configured to, or operable to support components for receiving, based on control signaling, a feedback codebook associated with a set of multiple segments, the feedback codebook including a bit of feedback information associated with the segment according to the feedback codebook.

[0213] Figure 16 A block diagram 1600 is shown of a communication manager 1620 supporting a segmented feedback codebook according to one or more aspects of this disclosure. The communication manager 1620 may be an example of aspects of the communication manager 1420, communication manager 1520, or both as described herein. The communication manager 1620 or its various components may be examples of parts for performing various aspects of the segmented feedback codebook as described herein. For example, the communication manager 1620 may include a feedback information component 1625, a codebook receiving component 1630, 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.

[0214] According to the examples disclosed herein, the communication manager 1620 may support wireless communication. The feedback information component 1625 is capable of, configured to, or operable to support components for transmitting control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including either an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback. The codebook receiving component 1630 is capable of, configured to, or operable to support components for receiving, based on control signaling, a feedback codebook associated with a set of multiple segments, the feedback codebook including a bit of feedback information associated with a segment according to the feedback codebook.

[0215] Figure 17 A diagram of a system 1700 including a device 1705 supporting a segmented feedback codebook, according to one or more aspects of this disclosure, is shown. Device 1705 may be an example of device 1405, device 1505, or network entity 105 as described herein, or may include components thereof. Device 1705 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 1705 may include components supporting output and enabling communication, such as a communication manager 1720, a transceiver 1710, an antenna 1715, at least one memory 1725, code 1730, and at least one processor 1735. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 1740).

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

[0217] At least one memory 1725 may include RAM, ROM, or any combination thereof. At least one memory 1725 may store computer-readable, computer-executable code 1730 including instructions that, when executed by one or more of at least one processor 1735, cause device 1705 to perform the various functions described herein. Code 1730 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1730 may not be directly executable by one of the at least one processor 1735, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1725 may also include a BIOS, among other things, which can control basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1735 may include multiple processors, and at least one memory 1725 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).

[0218] At least one processor 1735 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 1735 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 of the at least one processor 1735. At least one processor 1735 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1725) to cause device 1705 to perform various functions (e.g., functions or tasks supporting a segmented feedback codebook). For example, device 1705 or components of device 1705 may include at least one processor 1735 and at least one memory 1725 coupled to one or more of the at least one processor 1735, wherein at least one processor 1735 and at least one memory 1725 are configured to perform the various functions described herein. At least one processor 1735 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 (e.g., by executing code 1730) host functions for performing the functions of device 1705. At least one processor 1735 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1705 (such as within one or more memories of at least one memory 1725). In some implementations, at least one processor 1735 may be a component of a processing system. A processing system can generally refer to a system or a series of machines or components that receive input and process that input to produce a set of outputs (which may be passed to other systems or components of, for example, device 1705). For example, the processing system of device 1705 may refer to a system that includes various other components or sub-components of device 1705 (such as at least one processor 1735, transceiver 1710, communication manager 1720, or other components or combinations of components of device 1705). The processing system of device 1705 can interface with other components of device 1705 and can process information (such as inputs or signals) received from other components or output information to other components. For example, the chip or modem of device 1705 may include a processing system and one or more interfaces for outputting information or for acquiring information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to acquire information, or the same interface configured to both output and acquire information, and other specific implementations.In some embodiments, one or more interfaces may refer to the interface between the processing system of the chip or modem and the transmitter, enabling device 1705 to transmit information output from the chip or modem. Additionally or alternatively, in some embodiments, one or more interfaces may refer to the interface between the processing system of the chip or modem and the receiver, enabling device 1705 to receive information or signal input, and such information can be transmitted to the processing system. Those skilled in the art will readily recognize that the first interface may also receive information or signal input, and the second interface may also output information or signal output.

[0219] In some examples, bus 1740 may support communication at protocol layers (e.g., within a protocol layer) in a protocol stack. In some examples, bus 1740 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 1705, or communication performed between different components of device 1705 that are co-addressable or may be located in different locations (e.g., where device 1705 may refer to a system in which one or more of communication manager 1720, transceiver 1710, at least one memory 1725, code 1730 and at least one processor 1735 may be located in one component of different components or partitioned between different components).

[0220] In some examples, the communication manager 1720 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 1720 can manage the transfer of data communication for client devices, such as one or more UEs 115. In some examples, the communication manager 1720 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 1720 may support the X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0221] According to the examples disclosed herein, the communication manager 1720 may support wireless communication. For example, the communication manager 1720 may be capable of, configured to, or operable to support components for transmitting control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including either an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request for feedback. The communication manager 1720 may be capable of, configured to, or operable to support components for receiving, based on control signaling, a feedback codebook associated with a set of multiple segments, the feedback codebook including a bit of feedback information associated with the segment according to the feedback codebook.

[0222] By including or configuring a communication manager 1720 according to an example as described herein, device 1705 can support techniques for improving and reducing processing-related user experience, utilizing communication resources more efficiently, improving coordination between devices, and improving the utilization of processing power.

[0223] In some examples, the communication manager 1720 may be configured to use or otherwise coordinate with the transceiver 1710, one or more antennas 1715 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1720 may be supported or performed by the transceiver 1710, one or more processors in at least one processor 1735, one or more memories in at least one memory 1725, code 1730, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1735, at least one memory 1725, code 1730, or any combination thereof). For example, code 1730 may include instructions that can be executed by one or more processors in at least one processor 1735 to cause the device 1705 to perform various aspects of the segmented feedback codebook as described herein, or at least one processor 1735 and at least one memory 1725 may be otherwise configured to perform or support such operations individually or jointly.

[0224] Figure 18 A flowchart illustrating a method 1800 supporting a segmented feedback codebook according to various aspects of this disclosure is shown. Operation of method 1800 can be implemented by a UE or its components as described herein. For example, operation of method 1800 can be implemented by, as referenced... Figures 1 to 13 The UE 115 described herein performs the following: 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 to perform aspects of the described functions.

[0225] At 1805, the method may include receiving control signaling to report feedback information for a segment of the resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback. Operation of block 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1805 may be provided by reference to [reference needed]. Figure 12 The described feedback information component 1225 is used to execute this.

[0226] At 1810, the method may include generating a feedback codebook associated with a set of multiple segments based on control signaling. The operation of block 1810 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1810 may be derived from references... Figure 12 The described codebook generation component 1230 is used for execution.

[0227] At 1815, the method may include sending a feedback codebook for a set of multiple segments based on a generated feedback codebook, the feedback codebook including a bit of feedback information associated with the segment according to the feedback codebook. The operation of block 1815 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1815 may be provided by reference to [reference needed]. Figure 12 The codebook sending component 1235 described is used to execute this.

[0228] Figure 19 A flowchart illustrating a method 1900 supporting a segmented feedback codebook according to various aspects of this disclosure is shown. Operation of method 1900 can be implemented by a UE or its components as described herein. For example, operation of method 1900 can be implemented by, as referenced... Figures 1 to 13 The UE 115 described herein performs the following: 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 to perform aspects of the described functions.

[0229] At 1905, the method may include receiving one or more grants for scheduling one or more messages in a segment, wherein generating a feedback codebook is based on receiving one or more grants. The operation of block 1905 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1905 may be derived from references... Figure 12 The described permission component 1240 is used to execute.

[0230] At 1910, the method may include receiving control signaling to report feedback information for a segment of the resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback. Operation of block 1910 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1910 may be derived from references... Figure 12 The described feedback information component 1225 is used to execute this.

[0231] At 1915, the method may include generating a feedback codebook associated with a set of multiple segments based on control signaling. The operation of block 1915 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1915 may be derived from references... Figure 12 The described codebook generation component 1230 is used for execution.

[0232] At 1920, the method may include sending a feedback codebook for a set of multiple segments based on a generated feedback codebook, the feedback codebook including a bit of feedback information associated with the segment according to the feedback codebook. The operation of block 1920 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1920 may be derived from references... Figure 12 The codebook sending component 1235 described is used to execute this.

[0233] Figure 20 A flowchart illustrating a method 2000 supporting a segmented feedback codebook according to various aspects of this disclosure is shown. Operation of method 2000 can be implemented by a UE or its components as described herein. For example, operation of method 2000 can be implemented by, as referenced... Figures 1 to 13 The UE 115 described herein performs the following: 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 to perform aspects of the described functions.

[0234] At 2005, the method may include receiving control signaling to report feedback information for a segment of the resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a mixed automatic repeat request feedback. Operation of block 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2005 may be provided by reference to [reference needed]. Figure 12 The described feedback information component 1225 is used to execute this.

[0235] At 2010, the method may include determining, based on the offset between the time a certain number of messages are received and the uplink timing for sending feedback information associated with the feedback codebook, the number of messages to be segmented for resource scheduling, wherein the feedback codebook is generated based on the determination of the number of messages. The operation of block 2010 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2010 may be provided by reference to [reference]. Figure 12 The described message is executed by the scheduled message component 1245.

[0236] At 2015, the method may include generating a feedback codebook associated with a set of multiple segments based on control signaling. The operation of box 2015 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2015 may be derived from references... Figure 12 The described codebook generation component 1230 is used for execution.

[0237] At 2020, the method may include sending a feedback codebook for a set of multiple segments based on a generated feedback codebook, the feedback codebook including a bit of feedback information associated with the segment according to the feedback codebook. The operation of box 2020 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2020 may be provided by reference to [reference needed]. Figure 12 The codebook sending component 1235 described is used to execute this.

[0238] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication by a UE, the method comprising: receiving control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit of a hybrid automatic repeat request for feedback; generating a feedback codebook associated with a plurality of segments based at least in part on the control signaling; and transmitting the feedback codebook for the plurality of segments based at least in part on the generation of the feedback codebook, the feedback codebook including the bit of the feedback information associated with the segment according to the feedback codebook.

[0239] Aspect 2: According to the method of aspect 1, the method further includes: receiving one or more grants for scheduling one or more messages in the segment, wherein the generation of the feedback codebook is based at least in part on receiving the one or more grants.

[0240] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: determining the number of messages for the resource scheduling including the segment based at least in part on the offset between the time when the number of messages is received and the uplink timing for sending the feedback information associated with the feedback codebook, wherein the generation of the feedback codebook is based at least in part on determining the number of messages.

[0241] Aspect 4: According to the method of aspect 3, wherein the bit of the feedback information associated with the segment includes information for the number of messages.

[0242] Aspect 5: The method according to any one of Aspects 3 to 4, wherein sending the feedback codebook further comprises: sending the bit of the feedback information including the acknowledgment bit when each of the plurality of messages is successfully decoded.

[0243] Aspect 6: The method according to any one of Aspects 3 to 5, wherein sending the feedback codebook further comprises: sending the bit of the feedback information including the negative acknowledgment bit if at least one of the certain number of messages fails to be successfully decoded.

[0244] Aspect 7: The method according to any one of Aspects 1 to 6, wherein generating the feedback codebook further comprises: determining a discontinuity in the value of a downlink assignment index indicator received as part of an authorization; and at least in part based on the determination of the discontinuity in the value to provide a negative acknowledgment for the segment assignment in the feedback codebook.

[0245] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: receiving permission for a first message to be communicated during the segmentation, the permission including a first downlink assignment index indicator associated with the segmentation, wherein the generation of the feedback codebook is based at least in part on the first downlink assignment index indicator.

[0246] Aspect 9: The method according to aspect 8, the method further comprising: receiving a second grant for a second message to be communicated during the segmentation, the second grant including a second downlink assignment index indicator associated with the segment and different from the first downlink assignment index indicator; and receiving a third grant for a third message to be communicated during the segmentation, the third grant including a third downlink assignment index indicator associated with the segment and different from the first downlink assignment index indicator and the second downlink assignment index indicator.

[0247] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: determining a start parameter and a length parameter for a message scheduled to be communicated via the resource including the segment, wherein the generation of the feedback codebook is based at least in part on determining the start parameter and the length parameter.

[0248] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: determining whether the number of permissions granted for the resource including the segment meets a threshold, wherein the generation of the feedback codebook is based at least in part on determining whether the number of permissions received meets the threshold.

[0249] Aspect 12: The method according to any one of Aspects 1 to 11, the method further comprising: determining whether a message scheduled to be delivered via the resource including the segment has not been successfully detected, wherein generating the feedback codebook is based at least in part on determining whether the message has not been successfully detected.

[0250] Aspect 13: The method according to any one of Aspects 1 to 12, the method further comprising: receiving a second control signaling, the second control signaling including an indication of a maximum number of messages that can be scheduled to be delivered via the resource including the segment, wherein the generation of the feedback codebook is based at least in part on receiving the second control signaling.

[0251] Aspect 14: The method according to aspect 13, the method further comprising: sending signaling to indicate that the UE is capable of supporting a maximum number of messages scheduled in the resource including the segment, wherein receiving the second control signaling is at least in part based on sending the signaling.

[0252] Aspect 15: The method according to any one of Aspects 1 to 14, the method further comprising: receiving a second control signaling, the second control signaling including an indication of a maximum number of permissions to schedule messages to be communicated via the resource including the segment, wherein the generation of the feedback codebook is based at least in part on receiving the second control signaling.

[0253] Aspect 16: The method according to any one of Aspects 1 to 15, wherein receiving the control signaling further comprises: receiving permission for a first message to be transmitted during the segmentation, the permission including a message quantity indicator associated with the number of messages scheduled to be transmitted via the resource including the segment, wherein the feedback codebook is generated at least in part based on the message quantity indicator.

[0254] Aspect 17: The method according to aspect 16, wherein receiving the control signaling further comprises: receiving permission for a first message to be communicated during the segmentation, the permission including a segmentation index indicator associated with the segment and a message quantity indicator associated with the number of messages scheduled to be communicated via the resource including the segment; and receiving a second permission for a second message to be communicated during the segmentation, the second permission including the segmentation index indicator and the message quantity indicator, wherein the feedback codebook is generated at least in part based on the segmentation index indicator and the message quantity indicator.

[0255] Aspect 18: The method according to any one of aspects 1 to 17, wherein the resource including the segment is defined on a time-domain resource and one or more component carriers of a plurality of component carriers.

[0256] Aspect 19: The method according to aspect 18, the method further comprising: receiving second control signaling to report the feedback information for a second segment of a resource, defining the resource including the second segment on a second time-domain resource that at least partially overlaps with the time-domain resource and on at least one component carrier that is different from the one or more component carriers, wherein the generation of the feedback codebook is at least partially based on the second control signaling.

[0257] Aspect 20: The method according to any one of aspects 18 to 19, the method further comprising: generating a feedback codebook of dynamic length, wherein the generation of the feedback codebook is at least partially based on the generation of the feedback codebook of dynamic length.

[0258] Aspect 21: According to the method of aspect 20, generating the feedback codebook of the dynamic length further includes: receiving one or more grants for scheduling one or more messages in the plurality of segments, the one or more grants including a segment index indicator; determining a discontinuity in the value of the segment index indicator received as part of the grant; and assigning a negative acknowledgment to at least one segment in the feedback codebook based at least in part on the determination of the discontinuity in the value.

[0259] Aspect 22: The method according to any one of aspects 1 to 21, wherein a plurality of messages are received via the resource including the segment.

[0260] Aspect 23: The method according to any one of Aspects 1 to 22, wherein the segmentation comprises one or more time slots, one or more portions of time slots, or combinations thereof.

[0261] Aspect 24: The method according to any one of aspects 1 to 23, wherein the first size of the first segment is different from the second size of the second segment.

[0262] Aspect 25: The method according to any one of Aspects 1 to 24, wherein the resources of the segment are defined by a slot index, a symbol index, or any combination thereof.

[0263] Aspect 26: The method according to any one of Aspects 1 to 25, wherein the resources of the segment are defined by the timing of transmission of the physical uplink control channel.

[0264] Aspect 27: The method according to any one of Aspects 1 to 26, wherein the resources of the segment are associated with the time domain, the frequency domain, or any combination thereof.

[0265] Aspect 28: A method for wireless communication at a network entity, the method comprising: transmitting control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit of a hybrid automatic repeat request for feedback; and receiving, at least in part, a feedback codebook associated with a plurality of segments based on the control signaling, the feedback codebook including the bit of the feedback information associated with the segment according to the feedback codebook.

[0266] Aspect 29: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 1 to 27.

[0267] Aspect 30: A UE for wireless communication, the UE including at least one component for performing the method according to any one of aspects 1 to 27.

[0268] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the method according to any one of aspects 1 to 27.

[0269] Aspect 32: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors 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 the method according to aspect 28.

[0270] Aspect 33: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to aspect 28.

[0271] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to aspect 28.

[0272] 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 methods can be combined.

[0273] 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.

[0274] 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.

[0275] 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.

[0276] 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.

[0277] Computer-readable media includes both non-transitory computer storage media and communication media, with the latter including 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.

[0278] As used herein (including in the claims), the word "or" used in an enumeration of items (e.g., an enumeration of items accompanied by phrases such as "at least one of" or "one or more of") indicates an inclusive enumeration, such that an enumeration 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). Additionally, 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".

[0279] 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 those 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".

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

[0281] 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.

[0282] 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 cases, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0283] The description provided herein is intended 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; 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 UE: Receive control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a hybrid automatic repeat request feedback; The feedback codebook associated with multiple segments is generated, at least in part, based on the control signaling. as well as The feedback codebook for the plurality of segments is sent at least in part based on the generation of the feedback codebook, the feedback codebook including the bit of the feedback information associated with the segment according to the feedback codebook.

2. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive one or more grants for scheduling one or more messages in the segment, wherein the generation of the feedback codebook is based at least in part on receiving the one or more grants.

3. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The number of messages for the resource scheduling including the segment is determined at least in part based on the offset between the time when a certain number of messages are received and the uplink timing for sending the feedback information associated with the feedback codebook, wherein the generation of the feedback codebook is at least in part based on determining the number of messages.

4. The UE of claim 3, wherein the bit of the feedback information associated with the segment includes information for the number of messages.

5. The UE according to claim 3, wherein, In order to send the feedback codebook, the one or more processors can further operate individually or jointly to execute the code to enable the UE to: If each of the specified number of messages is successfully decoded, the first bit of the feedback information, including the acknowledgment bit, is sent.

6. The UE according to claim 3, wherein, In order to send the feedback codebook, the one or more processors can further operate individually or jointly to execute the code to enable the UE to: If at least one of the certain number of messages fails to be successfully decoded, the bit of the feedback information including the negative acknowledgment bit is sent.

7. The UE according to claim 1, wherein, In order to generate the feedback codebook, the one or more processors can further operate individually or jointly to execute the code to enable the UE to: Determine the discontinuity of the values ​​of the downlink assignment index indicator received as part of the grant; and Negative acknowledgments are assigned to the segments in the feedback codebook based at least in part on the determination of the discontinuity of the value.

8. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive permission for a first message to be communicated during the segmentation, the permission including a first downlink assignment index indicator associated with the segmentation, wherein the feedback codebook is generated at least in part based on the first downlink assignment index indicator.

9. The UE of claim 8, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive a second grant for a second message to be communicated during the segmentation, the second grant including a second downlink assignment index indicator associated with the segment and different from the first downlink assignment index indicator; and Receive a third grant for a third message to be communicated during the segmentation, the third grant including a third downlink assignment index indicator associated with the segment and different from the first downlink assignment index indicator and the second downlink assignment index indicator.

10. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Determine the start parameter and length parameter for a message scheduled to be delivered via the resource including the segment, wherein the generation of the feedback codebook is based at least in part on determining the start parameter and the length parameter.

11. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Determine whether the number of grants received for the resource including the segment meets a threshold, wherein the generation of the feedback codebook is based at least in part on determining whether the number of granted grants received meets the threshold.

12. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Determining whether a message scheduled to be delivered via the resource including the segment was not successfully detected, wherein the generation of the feedback codebook is based at least in part on determining whether the message was not successfully detected.

13. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive a second control signaling, the second control signaling including an indication of the maximum number of messages that can be scheduled to be delivered via the resource including the segment, wherein the generation of the feedback codebook is based at least in part on receiving the second control signaling.

14. The UE of claim 13, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Sending signaling to indicate that the UE can support a maximum number of messages scheduled in the resources including the segment, wherein receiving the second control signaling is at least in part based on sending the signaling.

15. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive a second control signaling, the second control signaling including an indication of a maximum number of messages that can be scheduled to be communicated via the resource including the segment, wherein the generation of the feedback codebook is based at least in part on receiving the second control signaling.

16. The UE according to claim 1, wherein, In order to receive the control signaling, the one or more processors can further operate individually or jointly to execute the code to enable the UE to: Receive permission for a first message to be communicated during the segmentation, the permission including a message quantity indicator associated with the number of messages scheduled to be communicated via the resource including the segment, wherein the feedback codebook is generated at least in part based on the message quantity indicator.

17. The UE according to claim 16, wherein, In order to receive the control signaling, the one or more processors can further operate individually or jointly to execute the code to enable the UE to: Receive the permission for the first message to be communicated during the segmentation, the permission including a segmentation index indicator associated with the segment and a message quantity indicator associated with the number of messages scheduled to be communicated via the resource including the segment; as well as Receive a second permission for a second message to be communicated during the segmentation period, the second permission including the segmentation index indicator and the message quantity indicator, wherein the feedback codebook is generated at least in part based on the segmentation index indicator and the message quantity indicator.

18. The UE of claim 1, wherein the resource including the segment is defined on one or more component carriers of a plurality of component carriers in the time domain.

19. The UE of claim 18, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive second control signaling to report the feedback information for a second segment of the resource, define the resource including the second segment on a second time-domain resource that at least partially overlaps with the time-domain resource and on at least one component carrier that is different from the one or more component carriers, wherein the generation of the feedback codebook is at least partially based on the second control signaling.

20. The UE of claim 18, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Generate a feedback codebook of dynamic length, wherein the generation of the feedback codebook is at least in part based on the generation of the feedback codebook of dynamic length.

21. The UE according to claim 20, wherein, In order to generate the dynamic-length feedback codebook, the one or more processors can further operate individually or jointly to execute the code to enable the UE to: Receive one or more grants for scheduling one or more messages in the plurality of segments, the one or more grants including a segment index indicator; Determine the discontinuity of the value of the segment index indicator received as part of the grant; as well as Negative acknowledgments are assigned to at least one segment of the feedback codebook based at least in part on the discontinuity in determining the value.

22. The UE of claim 1, wherein multiple messages are received via the resource including the segment.

23. The UE of claim 1, wherein the segmentation comprises one or more time slots, one or more portions of time slots, or a combination thereof.

24. The UE of claim 1, wherein the first size of the first segment is different from the second size of the second segment.

25. The UE of claim 1, wherein the resources of the segment are defined by a slot index, a symbol index, or any combination thereof.

26. The UE of claim 1, wherein the resources of the segment are defined by the timing of transmission of the physical uplink control channel.

27. The UE of claim 1, wherein the resources of the segment are associated with the time domain, frequency domain, or any combination thereof.

28. 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 control signaling to report feedback information for a segment of the resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a hybrid automatic repeat request feedback; and The feedback codebook associated with a plurality of segments is received at least in part based on the control signaling, the feedback codebook including the bit of the feedback information associated with the segments according to the feedback codebook.

29. A method for wireless communication by a user equipment (UE), the method comprising: Receive control signaling to report feedback information for a segment of a resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a hybrid automatic repeat request feedback; The feedback codebook associated with multiple segments is generated, at least in part, based on the control signaling. as well as The feedback codebook for the plurality of segments is sent at least in part based on the generation of the feedback codebook, the feedback codebook including the bit of the feedback information associated with the segment according to the feedback codebook.

30. A method for conducting wireless communication at a network entity, the method comprising: Send control signaling to report feedback information for a segment of the resource, the segment being associated with a bit of the feedback information, the bit including an acknowledgment bit or a negative acknowledgment bit for a hybrid automatic repeat request feedback; and The feedback codebook associated with a plurality of segments is received at least in part based on the control signaling, the feedback codebook including the bit of the feedback information associated with the segments according to the feedback codebook.

Images