Multiple transport block uplink shared channel transmission feedback mechanism
By introducing multi-TB-associated feedback process ID and UCI formats in the wireless communication system, the problem of communication uncertainty in the multi-TB uplink shared channel feedback mechanism is solved, and higher communication reliability and efficiency are achieved.
Patent Information
- Application Number
- CN202380034220.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-28
- Filing Date
- 2023-04-27
- Publication Date
- 2024-11-22
AI Technical Summary
In existing wireless communication systems, the feedback mechanism of the multi-transport block (TB) uplink shared channel is difficult to accurately determine whether the network entity successfully decodes multiple TB of data, resulting in communication uncertainty and ambiguity between the UE and the network entity. , affects communication reliability and efficiency.
Introduce multi-TB-associated feedback process ID and uplink control information (UCI) formats. Through the design of DFI and UCI, multi-TB feedback mechanism is supported, including multiple bit maps and fields to clarify the feedback of each TB. Information to ensure mutual understanding and accurate decoding between UE and network entities.
Improves communication reliability and efficiency between UE and network entities, reduces signaling overhead and delay, enhances data rate and spectrum efficiency, and supports higher system capacity.
Smart Images

Figure CN119013930A_ABST
Abstract
Description
[0001] Cross-references
[0002] This patent application claims the benefit of U.S. patent application No. 17 / 732,341, entitled “MULTI-TRANSPORT BLOCKUPLINK SHARED CHANNELTRANSMISSION FEEDBACK MECHANISMS,” filed by Khoshnevisan et al. on April 28, 2022, which is assigned to the assignee of this application. Background Art
[0003] The following relates to wireless communications, including a multi-transport block (TB) uplink shared channel transmission feedback mechanism.
[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to 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, advanced LTE (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 use techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of a communication device, which may be referred to as a user equipment (UE). Summary of the invention
[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting a feedback mechanism for uplink shared channel transmission of multiple transport blocks (TBs). For example, the described technology provides a signaling design and feedback mechanism for the transmission of a data message using or including multiple TBs, such as a physical uplink shared channel (PUSCH) transmission. For example, a user equipment (UE), which may be referred to as a network node in this document, may transmit a data message using or including multiple TBs, and may include a feedback process identifier (ID) associated with the multiple TBs in the data message. A network entity, which may also be referred to as a network node in this document, may receive a data message including multiple TBs, and may send feedback associated with the data message to the UE via downlink feedback information (DFI). In some aspects, the UE and the network entity may support a mutually understood DFI format or DFI interpretation rules associated with multiple TBs, so that the UE can detect whether the network entity successfully decodes one or more TBs of the multiple TBs included in the data message. Additionally, in some aspects, the UE may multiplex uplink control information (UCI) with the data message, and the UE and network entities may support a UCI format associated with multiple TBs, which includes a new data indicator (NDI) field and a redundant version (RV) field for the data message or each TB in the multiple TBs included in the data message.
[0006] A method for wireless communication at a first network node is described. The method may include: receiving information from a second network node indicating that the first network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB; sending the data message using the set of multiple TBs to the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs; and receiving a DFI corresponding to the feedback process ID from the second network node.
[0007] An apparatus for wireless communication at a first network node is described. The apparatus may include at least one processor, a memory coupled to the at least one processor, and instructions stored in the memory. The instructions may be executable by the at least one processor to cause the apparatus to: receive information from a second network node indicating that the first network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB; send the data message using the set of multiple TBs to the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs; and receive a DFI corresponding to the feedback process ID from the second network node.
[0008] Another apparatus for wireless communication at a first network node is described. The apparatus may include: a means for receiving information from a second network node indicating that the first network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB; a means for sending the data message using the set of multiple TBs to the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs; and a means for receiving a DFI corresponding to the feedback process ID from the second network node.
[0009] A non-transitory computer-readable medium storing code for wireless communication at a first network node is described. The code may include instructions that can be executed by at least one processor to: receive information from a second network node indicating that the first network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB; send the data message using the set of multiple TBs to the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs; and receive a DFI corresponding to the feedback process ID from the second network node.
[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the DFI may include operations, features, components, or instructions for performing the following operations: receiving downlink control information (DCI) including the DFI, wherein the DFI includes a first bit corresponding to the feedback process ID, and wherein the first bit indicates a first feedback that corresponds exclusively to the first TB.
[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DFI may be a 16-bit bitmap that includes the first bit and excludes any feedback corresponding to the second TB.
[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the DFI may include operations, features, components, or instructions for performing the following operations: receiving a DCI including the DFI, wherein the DFI includes a first bit corresponding to the feedback process ID, and wherein the first bit indicates a first feedback corresponding to the first TB and a second feedback corresponding to the second TB.
[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first bit may be a first value or a second value, the first value indicating that the first feedback and the second feedback may each be a corresponding acknowledgment (ACK), and the second value indicating that at least one of the first feedback or the second feedback may be a negative acknowledgment (NACK).
[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DFI includes a set of multiple bits, the set of multiple bits including the first bit, each corresponding bit in the set of multiple bits corresponds to a corresponding feedback process ID in a set of multiple feedback process IDs, the set of multiple feedback process IDs includes the feedback process ID associated with the set of multiple TBs, and the set of multiple feedback process IDs may all be different.
[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first bit corresponds to a logical AND operation between the first feedback and the second feedback.
[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first bit corresponds to a logical “OR” operation between the first feedback and the second feedback.
[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the DFI may include operations, features, components, or instructions for performing the following operations: receiving a DCI including the DFI, wherein the DFI includes a set of multiple bits corresponding to the feedback process ID, wherein each corresponding bit in the set of multiple bits indicates corresponding feedback corresponding to each corresponding TB in the set of multiple TBs.
[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first bit in the set of multiple bits indicates first feedback corresponding to the first TB, and a second bit in the set of multiple bits indicates second feedback corresponding to the second TB.
[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DFI may be a 32-bit bitmap including the set of the plurality of bits, and the 32-bit bitmap includes the first bit and the second bit.
[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple bits includes multiple bit sets, each corresponding bit set in the multiple bit sets corresponds to a corresponding feedback process ID in a set of multiple feedback process IDs, the set of multiple feedback process IDs includes the feedback process ID associated with the set of multiple TBs, and the set of multiple feedback process IDs may all be different.
[0021] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the second bit may be a null value or a default value; or the first network node ignores the second bit.
[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DCI format associated with both the DCI including the DFI and the scheduling DCI may have a fixed size, the DCI including the DFI including a first number of bits, the scheduling DCI including a second number of bits, and the fixed size may be equal to or greater than the larger of the first number of bits and the second number of bits.
[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple bits includes the multiple sets of bits if the scheduling DCI includes a number of bits equal to or greater than a total number of bits of the DCI that includes the multiple sets of bits.
[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for: receiving configuration information from the second network node via radio resource control (RRC) signaling; and processing the DFI based on the configuration information.
[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: sending a UCI associated with the data message, wherein the UCI includes a set of multiple NDI fields and a set of multiple RV fields, wherein corresponding NDI fields in the set of multiple NDI fields and corresponding RV fields in the set of multiple RV fields correspond to corresponding TBs in the set of multiple TBs.
[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: encoding the UCI to obtain a single UCI message including the set of the multiple NDI fields and the set of the multiple RV fields, wherein sending the UCI includes sending the single UCI message.
[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: multiplexing the single UCI message on one or more layers associated with a TB in the set of multiple TBs, wherein sending the UCI includes sending the single UCI message on the one or more layers.
[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: multiplexing the single UCI message on a first set of one or more layers associated with the first TB in the set of multiple TBs and on a second set of one or more layers associated with the second TB in the set of multiple TBs, wherein sending the UCI includes sending the single UCI message on the first set of one or more layers and on the second set of one or more layers.
[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: encoding the UCI to obtain a set of multiple UCI messages, wherein the set of multiple UCI messages includes a first UCI message and a second UCI message, wherein the first UCI message includes a first NDI field from the set of multiple NDI fields and a second RV field from the set of multiple RV fields, and wherein the second UCI message includes a second NDI field from the set of multiple NDI fields and a second RV field from the set of multiple RV fields; and multiplexing the first UCI message on a first set of one or more layers associated with the first TB and multiplexing the second UCI message on a second set of one or more layers associated with the second TB, wherein sending the UCI includes sending the first UCI message on the first set of one or more layers and sending the second UCI message on the second set of one or more layers.
[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first UCI message associated with the first TB in the set of multiple UCI messages includes the first RV field, the first NDI field, the first feedback process ID field, and the first channel occupancy time sharing information field; and the second UCI message associated with the second TB in the set of multiple UCI messages includes the second RV field, the second NDI field, the second feedback process ID field, and the second channel occupancy time sharing information field, wherein the second feedback process ID field and the second channel occupancy time sharing information field respectively include the same information as the first feedback process ID field and the first channel occupancy time sharing information field.
[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first UCI message associated with the first TB in the set of multiple UCI messages includes the first RV field, the first NDI field, the first feedback process ID field, and the first channel occupancy time sharing information field; and the second UCI message associated with the second TB in the set of multiple UCI messages exclusively includes the second RV field and the second NDI field.
[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the data message may be a configured grant physical uplink shared channel (CG-PUSCH) transmission or a dynamic grant physical uplink shared channel (DG-PUSCH) transmission.
[0033] A method for wireless communication at a first network node is described. The method may include: sending information to a second network node indicating that the second network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB; receiving the data message including the set of multiple TBs from the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs; and sending a DFI corresponding to the feedback process ID to the second network node.
[0034] An apparatus for wireless communication at a first network node is described. The apparatus may include at least one processor, a memory coupled to the at least one processor, and instructions stored in the memory. The instructions may be executable by the at least one processor to cause the apparatus to: send information to a second network node indicating that the second network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB; receive the data message including the set of multiple TBs from the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs; and send a DFI corresponding to the feedback process ID to the second network node.
[0035] Another apparatus for wireless communication at a first network node is described. The apparatus may include: means for sending information to a second network node indicating that the second network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB; means for receiving the data message including the set of multiple TBs from the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs; and means for sending a DFI corresponding to the feedback process ID to the second network node.
[0036] A non-transitory computer-readable medium storing code for wireless communication at a first network node is described. The code may include instructions executable by at least one processor to: send information to a second network node indicating that the second network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB; receive the data message including the set of multiple TBs from the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs; and send a DFI corresponding to the feedback process ID to the second network node.
[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the DFI may include operations, features, components, or instructions for performing the following operations: sending a DCI including the DFI, wherein the DFI includes a first bit corresponding to the feedback process ID, and wherein the first bit indicates a first feedback that corresponds exclusively to the first TB.
[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DFI may be a 16-bit bitmap that includes the first bit and excludes any feedback corresponding to the second TB.
[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the DFI may include operations, features, components, or instructions for performing the following operations: sending a DCI including the DFI, wherein the DFI includes a first bit corresponding to the feedback process ID, and wherein the first bit indicates a first feedback corresponding to the first TB and a second feedback corresponding to the second TB.
[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first bit may be a first value or a second value, the first value indicating that the first feedback and the second feedback may each be a corresponding ACK, and the second value indicating that at least one of the first feedback or the second feedback may be a NACK.
[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DFI includes a set of multiple bits, the set of multiple bits including the first bit, each corresponding bit in the set of multiple bits corresponds to a corresponding feedback process ID in a set of multiple feedback process IDs, the set of multiple feedback process IDs includes the feedback process ID associated with the set of multiple TBs, and the set of multiple feedback process IDs may all be different.
[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first bit corresponds to a logical AND operation between the first feedback and the second feedback.
[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first bit corresponds to a logical “OR” operation between the first feedback and the second feedback.
[0044] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the DFI may include operations, features, components, or instructions for performing the following operations: sending a DCI including the DFI, wherein the DFI includes a set of multiple bits corresponding to the feedback process ID, wherein each corresponding bit in the set of multiple bits indicates corresponding feedback corresponding to each corresponding TB in the set of multiple TBs.
[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first bit in the set of multiple bits indicates first feedback corresponding to the first TB, and a second bit in the set of multiple bits indicates second feedback corresponding to the second TB.
[0046] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DFI may be a 32-bit bitmap including the set of the plurality of bits, and the 32-bit bitmap includes the first bit and the second bit.
[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple bits includes multiple bit sets, each corresponding bit set in the multiple bit sets corresponds to a corresponding feedback process ID in a set of multiple feedback process IDs, the set of multiple feedback process IDs includes the feedback process ID associated with the set of multiple TBs, and the set of multiple feedback process IDs may all be different.
[0048] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second bit may be a null value or a default value; or the second network node may ignore the second bit.
[0049] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DCI format associated with both the DCI including the DFI and the scheduling DCI may have a fixed size, the DCI including the DFI including a first number of bits, the scheduling DCI including a second number of bits, and the fixed size may be equal to or greater than the larger of the first number of bits and the second number of bits.
[0050] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple bits includes the multiple sets of bits if the scheduling DCI includes a number of bits equal to or greater than a total number of bits of the DCI that includes the multiple sets of bits.
[0051] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending configuration information from the second network node via RRC signaling, wherein the configuration information may be associated with the DFI.
[0052] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: receiving UCI associated with the data message, wherein the UCI includes a set of multiple NDI fields and a set of multiple RV fields, wherein corresponding NDI fields in the set of multiple NDI fields and corresponding RV fields in the set of multiple RV fields correspond to corresponding TBs in the set of multiple TBs.
[0053] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the UCI may be a single UCI message, and the methods, apparatus, and non-transitory computer-readable media may include additional operations, features, components, or instructions for performing the following operations: decoding the UCI to obtain the single UCI message including the set of multiple NDI fields and the set of multiple RV fields.
[0054] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: demultiplexing the single UCI message from one or more layers associated with a TB in the set of the plurality of TBs, wherein receiving the UCI includes receiving the single UCI message on the one or more layers.
[0055] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: demultiplexing the single UCI message from a first set of one or more layers associated with a first TB in the set of multiple TBs and from a second set of one or more layers associated with a second TB in the set of multiple TBs, wherein receiving the UCI includes receiving the single UCI message on the first set of one or more layers and on the second set of one or more layers.
[0056] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the UCI may be a set of multiple UCI messages, and the methods, apparatuses, and non-transitory computer-readable media may also include operations, features, components, or instructions for performing the following operations: decoding the UCI to obtain the set of multiple UCI messages, wherein the set of multiple UCI messages includes a first UCI message and a second UCI message, wherein the first UCI message includes a first NDI field in the set of multiple NDI fields and a second RV field in the set of multiple RV fields, and wherein the second UCI message includes a second NDI field in the set of multiple NDI fields and a second RV field in the set of multiple RV fields; and demultiplexing the first UCI message on a first set of one or more layers associated with the first TB and multiplexing the second UCI message on a second set of one or more layers associated with the second TB, wherein receiving includes receiving the first UCI message on the first set of the one or more layers and sending the second UCI message on the second set of the one or more layers.
[0057] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first UCI message associated with the first TB in the set of multiple UCI messages includes the first RV field, the first NDI field, the first feedback process ID field, and the first channel occupancy time sharing information field; and the second UCI message associated with the second TB in the set of multiple UCI messages includes the second RV field, the second NDI field, the second feedback process ID field, and the second channel occupancy time sharing information field, wherein the second feedback process ID field and the second channel occupancy time sharing information field respectively include the same information as the first feedback process ID field and the first channel occupancy time sharing information field.
[0058] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first UCI message associated with the first TB in the set of multiple UCI messages includes the first RV field, the first NDI field, the first feedback process ID field, and the first channel occupancy time sharing information field; and the second UCI message associated with the second TB in the set of multiple UCI messages exclusively includes the second RV field and the second NDI field.
[0059] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the data message may be a CG-PUSCH transmission or a DG-PUSCH transmission. BRIEF DESCRIPTION OF THE DRAWINGS
[0060] Figure 1 and Figure 2An example of a wireless communication system supporting a multi-transport block (TB) uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown.
[0061] Figure 3 and Figure 4 An example of an uplink control information (UCI) signaling design supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown.
[0062] Figure 5 An example of a communication timeline supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown.
[0063] Figure 6 An example of a process flow for supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown.
[0064] Figure 7 and Figure 8 A block diagram of a device supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown.
[0065] Fig. 9 A block diagram of a communication manager supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown.
[0066] Fig.10 A diagram of a system including a device supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown.
[0067] Fig.11 and Fig.12 A block diagram of a device supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown.
[0068] Fig.13 A block diagram of a communication manager supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown.
[0069] Fig.14 A diagram of a system including a device supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown.
[0070] Fig.15 and Fig.16 A flow chart illustrating a method for supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION
[0071] In some wireless communication systems, a user equipment (UE) (which may be an example of a network node) may perform uplink data transmission to a network entity (which may be another example of a network node) via a physical uplink shared channel (PUSCH). The network entity may dynamically or non-dynamically schedule PUSCH transmissions, wherein a dynamically scheduled PUSCH may be scheduled via a dynamic grant (DG) and is referred to as a DG-PUSCH, and a non-dynamically scheduled PUSCH may be scheduled at least in part via radio resource control (RRC) signaling and is referred to as a configured grant (CG) PUSCH. For either or both of the DG-PUSCH transmission and the CG-PUSCH transmission, the network entity may attempt to decode the data and may send feedback to the UE indicating whether the data was successfully decoded or unsuccessfully decoded by the network entity. In order to convey feedback for the DG-PUSCH or CG-PUSCH transmission, the network entity may include a single bit in the downlink feedback information (DFI) field of the downlink control information (DCI) message corresponding to the DG-PUSCH or CG-PUSCH. In addition, to support feedback sent for CG-PUSCH, the UE may multiplex uplink control information (UCI) with the CG-PUSCH, and the UCI may indicate a hybrid automatic repeat request (HARQ) process ID and other information associated with the CG-PUSCH that the network entity may use when providing feedback for the CG-PUSCH.
[0072] This feedback mechanism for DG-PUSCH and CG-PUSCH transmissions may be designed to indicate feedback for DG-PUSCH and CG-PUSCH transmissions associated with a single codeword or a single transport block (TB). For example, some DCI formats may provide enough bits for the DFI field to indicate feedback for one codeword or TB per PUSCH transmission, and some UCI formats may provide enough bits to indicate information about one (but no more than one) codeword or TB of the associated PUSCH. However, in some systems, the UE may use multiple codewords and multiple TBs for DG-PUSCH or CG-PUSCH transmissions. Therefore, a feedback mechanism designed for a single codeword or a single TB may result in ambiguity or uncertainty between the UE and the network entity as to whether a given DG-PUSCH or CG-PUSCH transmission is successfully decoded at the network entity or how many are successfully decoded.
[0073] In some specific implementations of the present disclosure, the UE and the network entity may support a signaling design that enables a feedback mechanism associated with a DG-PUSCH or CG-PUSCH transmission that includes or uses multiple codewords or TBs. For example, the UE may receive one or both of RRC signaling and DCI that schedules or activates a data message to be sent from the UE to the network entity, and the RRC signaling or DCI may indicate that the UE will use at least a first TB and a second TB to send the data message, wherein the HARQ process ID of the data message is associated with the two TBs. In a specific implementation in which the data message is a DG-PUSCH transmission or a CG-PUSCH transmission, the UE may send the data message and may receive a DFI corresponding to the HARQ process ID of the data message (e.g., a HARQ process ID associated with two TBs). In some aspects, the DFI may include a single bit corresponding to the HARQ process ID, and the UE and the network entity may support mutually understood rules for interpreting feedback indicated by the single bit. In some other aspects, the DFI may include multiple bits (e.g., two bits) corresponding to the HARQ process ID, and the UE and the network entity may support mutually understood rules according to which the first bit provides first feedback for the first TB and the second bit provides second feedback for the second TB.
[0074] In addition, in a specific implementation in which the data message is sent by CG-PUSCH, the UE may multiplex UCI (e.g., CG-UCI) with the CG-PUSCH, and the UE and the network entity may support the UCI format based on the data message including or using multiple TBs. In some aspects, for example, the UCI may include a corresponding new data indicator (NDI) field and a corresponding redundancy version (RV) field for each of the first TB and the second TB. For example, the UE may include a first NDI field and a first RV field corresponding to the first TB in the UCI, and may include a second NDI field and a second RV field corresponding to the second TB in the UCI. The UE may encode the UCI to indicate multiple NDI and RV fields via a single UCI message or to distribute multiple NDI and RV fields across multiple UCI messages.
[0075] Specific implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. For example, as a result of supporting mutually understood rules for interpreting DFIs associated with multiple TBs or supporting a DFI design that carries multiple bits for a HARQ process ID (so that the DFI indicates separate feedback for each TB associated with a given PUSCH transmission), the UE may more accurately determine whether a network entity is able to successfully decode a multi-TB PUSCH transmission or how many multi-TB PUSCH transmissions are able to successfully decode. Thus, the UE may more accurately determine whether to perform a retransmission (partial or full) of a PUSCH transmission, which may result in greater reliability and higher likelihood of successful communication between the UE and the network entity as well as less signaling overhead and lower latency. In addition, in an implementation in which the UE multiplexes UCI with CG-PUSCH transmissions associated with multiple TBs, the described UCI formatting techniques may provide the network entity with more feedback-associated information for each of the multiple TBs associated with the CG-PUSCH transmission, which may enable the network entity to provide more relevant and accurate feedback for the CG-PUSCH transmission. As a result, UEs and network entities can achieve higher data rates, greater spectral efficiency, and increased system capacity, among other benefits.
[0076] First, various aspects of the present disclosure are described in the context of a wireless communication system. Various aspects of the present disclosure are additionally illustrated and described with reference to UCI signaling design, communication timeline, and process flow. Various aspects of the present disclosure are further illustrated and described with reference to device diagrams, system diagrams, and flow charts related to a multi-TB uplink shared channel transmission feedback mechanism.
[0077] Figure 1 An example of a wireless communication system 100 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).
[0078] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).
[0079] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices such as Figure 1 Other UEs 115 or network entities 105 are shown communicating.
[0080] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote unit (RU), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. As another example, the network node may be a base station or a network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first set of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.
[0081] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). The disclosure of one communication term includes the disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node. In addition, the network node (one or both of the first network node and the second network node) may include multiple components or otherwise be associated with multiple components (e.g., as part of an open RAN (O-RAN) or a decomposed RAN (D-RAN) deployment). In such aspects where the network node includes or is otherwise associated with multiple components, and if the network node is configured to send or receive information, such information sending may include providing, transmitting, outputting, or indicating information from a first component of the network node to one or more other components, and such information receiving may include obtaining, decoding, ascertaining, sensing, determining, or identifying information at the first component of the network node from one or more other components. Such information sending or receiving may include wireless sending or receiving or wired sending or receiving.
[0082] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the 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, the network entities 105 may communicate with each other directly (e.g., directly between each network entity 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .
[0083] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).
[0084] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an O-RAN (e.g., a network configuration advocated by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the 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 (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0085] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may 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 may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (eg, channel) between layers of a protocol stack supported by the respective network entities 105 communicating over those communication links.
[0086] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may 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 nodes 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 DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a 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 nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The 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 an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.
[0087] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support a multi-TB uplink shared channel transmission feedback mechanism as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may be additionally or alternatively performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).
[0088] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.
[0089] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which 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 shown.
[0090] The UE 115 and the network entity 105 may communicate with each other wirelessly via one or more communication links 125 (e.g., access links) via one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates 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 for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).
[0091] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates 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 located according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.
[0092] The signal waveform transmitted through the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, in which case the symbol period and the 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 coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may improve the data rate or data integrity of communications with UE 115.
[0093] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.
[0094] The time interval of the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N fThe maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).
[0095] 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, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain 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 certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple micro time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.
[0096] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).
[0097] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may 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 sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .
[0098] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., via a carrier), and may be associated with an identifier used to distinguish adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) within which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.
[0099] A macro cell typically covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) compared to macro cells, and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.
[0100] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.
[0101] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for 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 provide coverage for various coverage areas 110 using the same or different radio access technologies.
[0102] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.
[0103] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering a power saving deep sleep mode when not engaged in active communications, operating with limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.
[0104] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
[0105] In some examples, a UE 115 may be able to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), and the one or more UEs may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in the group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .
[0106] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an 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), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.
[0107] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about 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 may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.
[0108] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, there may be even greater atmospheric attenuation and a shorter range for the propagation of EHF transmissions than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.
[0109] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration in conjunction with a component carrier (e.g., LAA) operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.
[0110] The 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 technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located in different geographic locations. The network entity 105 may have an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.
[0111] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.
[0112] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).
[0113] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as network entity 105, or by a receiving device, such as UE 115) beam directions for later transmission or reception by the network entity 105.
[0114] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.
[0115] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured beam set across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or unprecoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-faceted codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).
[0116] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105), the receiving device (e.g., UE 115) may perform receiving operations (e.g., directional listening) according to multiple receiving configurations. For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).
[0117] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate through logical channels. The MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between a UE 115 and a network entity 105 or a core network 130. At the PHY layer, transport channels may be mapped to physical channels.
[0118] UE 115 and network entity 105 may support retransmission of data to increase the possibility of successfully receiving data. HARQ feedback is a technique for increasing the possibility of correctly receiving data through a communication link (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 the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.
[0119] In some wireless communication systems, UE 115 (which may be an example of a network node) may perform uplink data transmission to network entity 105 (which may be another example of a network node) via PUSCH. Network entity 105 may dynamically or non-dynamically schedule PUSCH transmission, wherein dynamically scheduled PUSCH may be scheduled via DG and is referred to as DG-PUSCH, and non-dynamically scheduled PUSCH may be scheduled at least in part via RRC signaling and is referred to as CG PUSCH. For either or both of DG-PUSCH transmission and CG-PUSCH transmission, network entity 105 may attempt to decode the data and may send feedback to UE 115 indicating whether the data was successfully decoded or unsuccessfully decoded by network entity 105. In order to convey feedback for DG-PUSCH or CG-PUSCH transmission, network entity 105 may include a single bit in the DFI field of the DCI message corresponding to the DG-PUSCH or CG-PUSCH. In addition, to support feedback sent for the CG-PUSCH, the UE 115 may multiplex the UCI with the CG-PUSCH, and the UCI may indicate the HARQ process ID and other information about the CG-PUSCH that the network entity 105 may use when providing feedback for the CG-PUSCH.
[0120] This feedback mechanism for DG-PUSCH and CG-PUSCH transmissions may be designed to indicate feedback for DG-PUSCH and CG-PUSCH transmissions associated with a single codeword or a single TB. For example, some DCI formats may provide enough bits for the DFI field to indicate feedback for one codeword or TB per PUSCH transmission, and some UCI formats may provide enough bits to indicate information about one (but no more than one) codeword or TB of the associated PUSCH. However, in some systems, the UE 115 may use multiple codewords and multiple TBs for DG-PUSCH or CG-PUSCH transmissions. Therefore, the feedback mechanism designed for a single codeword or a single TB may result in ambiguity or uncertainty between the UE 115 and the network entity 105 as to whether a given DG-PUSCH or CG-PUSCH transmission is successfully decoded at the network entity 105 or how many are successfully decoded.
[0121] In some specific implementations of the present disclosure, the UE 115 and the network entity 105 may support signaling designs and feedback mechanisms associated with DG-PUSCH or CG-PUSCH transmissions that include or use multiple codewords or TBs. For example, the UE 115 may receive one or both of RRC signaling and DCI that schedules or activates a data message to be sent from the UE 115 to the network entity 105, and the RRC signaling or DCI may indicate that the UE 115 will use at least a first TB and a second TB to send the data message, wherein the HARQ process ID of the data message is associated with the two TBs. In a specific implementation in which the data message is a DG-PUSCH transmission or a CG-PUSCH transmission, the UE 115 may send the data message and may receive a DFI corresponding to the HARQ process ID of the data message (e.g., a HARQ process ID associated with two TBs). In some aspects, the DFI may include a single bit corresponding to the HARQ process ID, and the UE 115 and the network entity 105 may support mutually understood rules for interpreting feedback indicated by the single bit. In some other aspects, the DFI may include multiple bits (e.g., two bits) corresponding to the HARQ process ID, and the UE 115 and the network entity 105 may support a mutually understood rule according to which the first bit indicates first feedback for the first TB and the second bit indicates second feedback for the second TB.
[0122] In addition, in a specific implementation in which the data message is a CG-PUSCH transmission, the UE 115 may multiplex the UCI (e.g., CG-UCI) with the CG-PUSCH, and the UE 115 and the network entity 105 may support a UCI format associated with a data message including or using multiple TBs. In some aspects, for example, the UCI may include a corresponding NDI field and a corresponding RV field for each of the first TB and the second TB. For example, the UE 115 may include a first NDI field and a first RV field corresponding to the first TB in the UCI, and may include a second NDI field and a second RV field corresponding to the second TB in the UCI. The UE 115 may encode the UCI to indicate multiple NDI and RV fields via a single UCI message or to distribute multiple NDI and RV fields across multiple UCI messages.
[0123] As described herein, a codeword may represent information formatted for transmission before. In addition, a codeword may be defined as an information block to which a CRC may be attached. Each codeword may be encoded and decoded separately. In some aspects, a codeword may correspond to a TB. For example, UE 115 and network entity 105 may support a one-to-one mapping between codewords and TBs. Therefore, a multi-codeword data message may be equivalently understood or referred to as a multi-TB data message, wherein each codeword and TB in a plurality of codewords and TBs may be encoded and decoded separately.
[0124] Figure 2 An example of a wireless communication system 200 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a network entity 105-a and a UE 115-a, which may be Figure 1 Examples of corresponding devices illustrated and described with reference to the figure. The UE 115-a and the network entity 105-a may communicate via a communication link 205, which may generally refer to one or both of an uplink 205-a and a downlink 205-b, and the UE 115-a may send one or more data messages 210 to the network entity 105-b via one or more DG-PUSCH or CG-PUSCH transmissions. In some aspects, the UE 115-a and the network entity 105-a may support signaling designs and feedback mechanisms that support scenarios in which the UE 115-a uses multiple TBs and multiple codewords to send the data message 210.
[0125] For example, UE 115-a may send data message 210 to network entity 105-a via DG-PUSCH transmission or CG-PUSCH transmission. CG-PUSCH may be referred to as type 1 CG or may be an example of type 1 CG and may be exclusively RRC configured, and DG-PUSCH may be referred to as type 2 CG or may be an example of type 2 CG and may be DCI activated (e.g., for type 2 CG-PUSCH, some information may be RRC configured and some other information may be indicated via activation of DCI). Figure 5 Additional details related to DG-PUSCH and CG-PUSCH are illustrated and described with reference to this figure.
[0126] In aspects where UE 115-a transmits data message 210 via DG-PUSCH or CG-PUSCH, network entity 105-a may receive and attempt to decode data message 210. Network entity 105-a may transmit feedback associated with data message 210 to UE 115-a via DFI 215 (which may sometimes be equivalently referred to as CG-DFI). For example, DFI 215 may indicate a HARQ-ACK for each HARQ ID of a previous set of one or more PUSCH transmissions from UE 115-a to network entity 105-a. As described herein, feedback and HARQ-ACK may refer to information indicating whether a receiving device (e.g., network entity 105-a) successfully decoded a transmission. In scenarios where network entity 105-a successfully decodes a transmission, network entity 105-a may indicate an acknowledgment (ACK) via feedback or HARQ-ACK information. In a scenario where the network entity 105-a is unable to successfully decode a transmission, the network entity 105-a may indicate a negative ACK (NACK) via feedback or HARQ-ACK information. Thus, the feedback or HARQ-ACK information may indicate an ACK or NACK for a given transmission, and the UE 115-a may identify or determine which transmission the ACK or NACK corresponds to based on a HARQ ID (e.g., a HARQ process ID) associated with the ACK or NACK (where such association may be defined by a mapping rule and a bitmap).
[0127] For example, the network entity 105-a may send the DFI 215 in a DCI (e.g., a DCI format 0_1 with CRC bits scrambled by a configured scheduling radio network temporary identifier (CS-RNTI), and if a DFI flag in the DCI is set to a value (e.g., if the DFI flag is 1), the DFI is present in the DCI and conveyed via a 16-bit bitmap indicating a HARQ-ACK for each HARQ ID of a previous set of one or more PUSCH transmissions. In other words, each corresponding bit in the 16-bit bitmap may indicate an ACK or NACK for a corresponding HARQ ID, where a mapping rule may define a correspondence between a bit in the bitmap and a corresponding HARQ ID. If the DFI flag is set to a zero value (e.g., if the DFI flag is 0), the DCI may not include the DFI 215. In such a case where the DFI flag is set to a zero value, the DCI may be an uplink-associated DCI that may, for example, activate a CG-PUSCH. Therefore, DCI format 0_1 including DFI 215 may have a CRC scrambled with CS-RNTI, and in this case may exclusively indicate DFI 215 and set the DFI flag to 1.
[0128] As an example, if the UE 115-a is configured to monitor DCI format 0_1 with a CRC scrambled by CS-RNTI, and for operation in a cell with shared spectrum channel access, the network entity 105-a may set the DFI flag to 1 bit. For DCI format 0_1 with a CRC scrambled by CS-RNTI, a bit value of 0 may indicate activation of type 2 CG transmission, and a bit value of 1 may indicate CG-DFI. For DCI format 0_1 with a CRC scrambled by C-RNTI, a semi-persistent channel state information radio network temporary identifier (SP-CSI-RNTI), or a modulation and coding scheme cell radio network temporary identifier (MCS-C-RNTI), and for operation in a cell with shared spectrum channel access, this bit (e.g., a bit otherwise used for the DFI flag) is reserved. Otherwise, the DFI flag bit may be set to a value of zero.
[0129] In addition, if DCI format 0_1 is used to indicate CG-DFI (so that DFI 215 is present in the DCI), the remaining fields of the DCI may be set to include a HARQ-ACK bitmap and a transmit power control (TPC) command field, and all remaining bits in DCI format 0_1 may be set to zero. The HARQ-ACK bitmap may include 16 bits, and the order of the bitmap to HARQ process index mapping is such that the HARQ process index may be mapped in ascending order from the most significant bit (MSB) to the least significant bit (LSB) of the bitmap. For each bit of the bitmap, a value of 1 may indicate ACK, and a value of 0 may indicate NACK. The TPC command field may be used for the scheduled PUSCH and may include two bits.
[0130] In addition, in some aspects, the UE 115-a may use one or more CG resources for one or more retransmissions. In such aspects where the UE 115-a uses CG resources for retransmissions, the UE 115-a may autonomously decide or select a HARQ ID, an NDI value (wherein if the NDI is switched, it indicates a new transmission; otherwise, it indicates a retransmission), and a RV for each CG opportunity. Based on this autonomous selection by the UE 115-a, the UE 115-a may include an indication of the selected HARQ ID, NDI, and RV in the UCI 220, as well as channel occupancy time (COT) sharing information (which may be related to unlicensed operations such as new radio unlicensed (NRU) operations), and the UCI 220 may be multiplexed on each CG-PUSCH. The UE 115-a may encode UCI 220 (which may be referred to as CG-UCI) separately for separate or different CG-PUSCH transmissions, and may multiplex the UCI 220 on the CG-PUSCH to which the information in the UCI 220 corresponds. Thus, the network entity 105-a may decode the associated CG-PUSCH using the UCI 220 including the HARQ ID, NDI, RV, and COT shared information. In other words, the network entity 105-a may decode the UCI 220 and may subsequently decode uplink data on the CG-PUSCH to which the UCI 220 corresponds (e.g., for which the UCI 220 provides information).
[0131] The mapping order of the UCI 220 (e.g., CG-UCI) field is illustrated by Table 1 shown below. As shown in Table 1, the UCI 220 may include a HARQ process number (or HARQ process ID) field with a bit width of 4, an RV field with a bit width of 2, an NDI field with a bit width of 1, and a COT sharing information field with a variable bit width. For example, if a higher layer parameter ul-toDL-COT-SharingED-Threshold and a higher layer parameter cg-COT-SharingList are configured, the COT sharing information field may include a COT sharing information field based on The COT sharing information field may have a bit width of 1 if the higher layer parameter ul-toDL-COT-SharingED-Threshold is not configured and the higher layer parameter cg-COT-SharingOffset is configured. In another example, otherwise the COT sharing information field may have a bit width of 0. In addition, if UE 115-a indicates COT sharing other than "not shared" in the CG-PUSCH within the initiated COT of UE 115-a, UE 115-a may be configured to provide consistent COT sharing information in a set (e.g., all) of subsequent CG-PUSCHs (if any) occurring within the same initiated COT of UE 115-a, so that the same downlink starting point and duration can be maintained.
[0132] Fields Bit width HARQ process number 4 Redundancy Version (RV) 2 New Data Indicator (NDI) 1 COT Shared Information variable
[0133] Table 1: Mapping order of CG-UCI fields
[0134] In some aspects, the UE 115-a and the network entity 105-a may support multiple (e.g., two) codewords and multiple (e.g., two) TBs for PUSCH transmissions. For example, the UE 115-a and the network entity 105-a may introduce or otherwise support multiple codewords and TBs as part of more than four layers (with eight transmit ports) transmissions, or as part of simultaneous multi-panel transmissions, or both. Thus, the UE 115-a and the network entity 105-a may support one or more uplink demodulation reference signal (DMRS), sounding reference signal (SRS), SRS resource indicator (SRI), or transmit precoding matrix indicator (TPMI) (including codebook) enhancements to enable eight-transmit port uplink operation, thereby supporting four or more layers per UE in the uplink (e.g., for customer premises equipment (CPE), fixed wireless access (FWA), vehicles, or industrial equipment). The UE 115-a and the network entity 105-a may support updates, rules, or constraints associated with coherence assumptions or full / non-full power modes as part of such DMRS, SRS, SRI, or TPMI enhancements. In addition, the UE 115-a and the network entity 105-a may facilitate simultaneous multi-panel uplink transmissions based on uplink precoding indications for PUSCH to obtain higher uplink throughput or reliability (e.g., for FR2 or multi-TRP operation, assuming a maximum of two TRPs and a maximum of two panels, and for example for CPE, FWA, vehicles, or industrial equipment, if applicable) without introducing new codebooks for simultaneous transmission of multiple panels. In such aspects, considering multi-TRP operation based on a single DCI or multiple DCI, the total number of layers across a group (e.g., all) of panels may be up to four, and the total number of codewords across a group (e.g., all) of panels may be up to two.
[0135] Thus, a multi-codeword or multi-TB PUSCH transmission may include two (or potentially more) TBs. In addition, the UE 115-a and the network entity 105-a may define various use cases associated with PUSCH transmissions that include or use multiple TBs. For example, the UE 115-a and the network entity 105-a may define a first use case in which, for DG-PUSCH, PUSCH with two or more TBs is supported, but not for CG-PUSCH. Additionally or alternatively, the UE 115-a and the network entity 105-a may define a second use case in which, for both DG-PUSCH and CG-PUSCH, PUSCH with two or more TBs is supported. Thus, in the context of the wireless communication system 200, UE 115-a may send a data message 210 using or including a first codeword (e.g., CW0) and a corresponding first TB (e.g., TB0) and using or including a second codeword (e.g., CW1) and a corresponding second TB (e.g., TB1) as part of a DG-PUSCH transmission according to a first use case, or as part of a DG-PUSCH or CG-PUSCH transmission according to a second use case.
[0136] However, in some systems, the UE 115-a and the network entity 105-a may lack mutually understood rules for interpreting or formatting the DFI 215 or UCI 220 to support PUSCH transmissions using or including multiple codewords and TBs. For example, in some systems, the DFI 215 may include sufficient bits to indicate feedback for one codeword or one TB per PUSCH transmission, and similarly, the UCI 220 may include sufficient bits to indicate feedback-related information for a single (but no more than one) codeword and TB for the corresponding CG-PUSCH. In addition, although the UE 115-a may not use the UCI 220 for the data message 210 in the first use case (because the UE 115-a may avoid using multiple TBs for CG-PUSCH transmissions), updating the DFI 215 may improve communication between the UE 115-a and the network entity 105-a because the network entity 105-a may still provide feedback associated with the multi-TB DG-PUSCH via the DFI 215. For example, in some systems, the DFI 215 may include a 16-bit HARQ-ACK bitmap, which may be insufficient when two or more TBs are utilized to schedule at least some of the HARQ IDs in a previous set of HARQ IDs corresponding to one or more DG-PUSCH transmissions (because each TB or codeword may be associated with a different decoding operation and, therefore, different feedback).
[0137] In some implementations, the UE 115-a and the network entity 105-a may support signaling designs and feedback mechanisms associated with a data message 210 sent by the UE 115-a that includes or uses two or more TBs. For example, if the UE 115-a is configured (e.g., configured by RRC) with multiple codewords or TBs for the data message 210 (e.g., configured by RRC with a maximum number of codewords or TBs for the PUSCH = 2, at least for a PUSCH scheduled by DCI, such as a DG-PUSCH), then if for a given HARQ process ID, the PUSCH includes multiple TBs and the DFI flag is set to 1 in DCI format 0_1 (so that the HARQ-ACK bitmap field is indicated by the DCI), then the UE 115-a and the network entity 105-a may operate according to mutually understood rules or support a DFI format adapted to multiple TBs to maintain synchronization between the UE 115-a and the network entity 105-a. In some aspects, for example, the DFI 215 may include a single bit corresponding to the HARQ process ID associated with the data message 210, and the UE 115-a and the network entity 105-a may operate according to mutually understood rules to interpret the feedback indicated by the single bit. In some other aspects, the DFI 215 may include multiple bits corresponding to the HARQ process ID associated with the data message 210, such that corresponding bits of the multiple bits indicate corresponding feedback for corresponding TBs of multiple TBs used or included in the data message 210.
[0138] In some aspects where there is a single bit corresponding to the HARQ process ID associated with the data message 210, the UE 115-a and the network entity 105-a may determine or expect that the single bit corresponds exclusively to the first TB (e.g., TB0 and CW0) of the data message (e.g., PUSCH). In such aspects, the network entity 105-a may suppress HARQ-ACK information for other TBs (e.g., TB1 and CW1) of the data message indicated via the DFI 215 (or the DCI carrying the DFI 215), and the bitmap size of the DFI 215 may be 16 bits. In some other aspects where there is a single bit corresponding to the HARQ process ID associated with the data message 210, the UE 115-a and the network entity 105-a may determine or expect that the single bit corresponds to a logical operation between feedback associated with different TBs of the data message 210. For example, UE 115-a and network entity 105-a may determine or expect that the single bit corresponds to a logical "AND" operation or a logical "OR" operation between a first HARQ-ACK feedback for a first TB (e.g., TB0 and CW0) and a second HARQ-ACK feedback for a second TB (e.g., TB1 and CW1).
[0139] In such aspects where a logical "AND" operation is used, the network entity 105-a may set a single bit corresponding to the HARQ process ID associated with the data message 210 to a 1 value to indicate an ACK for both the first TB and the second TB, or to a 0 value to indicate a NACK for at least one of the first TB and the second TB. In such aspects where a logical "OR" operation is used, the network entity 105-a may set a single bit to a 1 value to indicate an ACK for at least one of the first TB and the second TB, or to a 0 value to indicate a NACK for both the first TB and the second TB. Thus, the network entity 105-a may effectively bundle two (or more) HARQ-ACKs together to indicate feedback for data messages 210 associated with multiple TBs, and the bitmap size of the DFI 215 may be 16 bits.
[0140] In aspects where there are multiple bits (e.g., two bits) corresponding to the HARQ process ID associated with the data message 210 (and thus associated with the first and second TBs of the PUSCH), the bitmap size of the DFI 215 may be increased, and the DFI 215 may include a corresponding bit for each TB associated with the data message 210. For example, the DFI 215 may include a first bit indicating a first HARQ-ACK feedback for a first TB (e.g., TB0 and CW0) and a second bit indicating a second HARQ-ACK feedback for a second TB (e.g., TB1 and CW1). In such examples where the data message 210 uses or includes two TBs (or where a maximum of two TBs for PUSCH transmissions are supported), the bitmap size of the DFI 215 may be 32 bits.
[0141] In some aspects, the DFI 215 may be extended to include multiple bits for each of the several PUSCH transmissions, and in some scenarios, a portion of the several PUSCH transmissions may use multiple TBs. For example, if a TB is included for different PUSCHs corresponding to different HARQ process IDs, the second bit in the DFI 215 corresponding to the different HARQ process IDs may be ignored or may be set to a fixed value or default value (e.g., set to a 0 value, such as to indicate a NACK). In other words, the UE 115-a may be configured to ignore any additional bits in the DFI 215 for any PUSCH transmission transmitted that includes a TB in a scenario where the bitmap size of the DFI 215 is extended to support multiple TBs for the several PUSCH transmissions.
[0142] Furthermore, in some aspects, the UE 115-a and the network entity 105-a may maintain a fixed size for DCI format 0_1 (e.g., a DCI format associated with carrying DFI 215) regardless of whether the DCI has a CRC scrambled with a CS-RNTI (which may indicate that DFI 215 is potentially included) or a CRC scrambled with a cell radio network temporary identifier (C-RNTI). For example, in aspects where DFI 215 is extended to include 32 bits, the number of bits (e.g., information conveying bits) in a DCI having a CRC scrambled with a CS-RNTI and a DFI flag set to 1 may be greater than the number of bits (e.g., information conveying bits) in a DCI having a CRC scrambled with a C-RNTI or a DFI not set to 1. In other words, some designs of DCI format 0_1, which is more generally used for scheduling or activating a PUSCH, may sometimes not have enough bits to accommodate 32 bits in a DFI 215.
[0143] Thus, in some implementations, the UE 115-a and the network entity 105-a may set or anticipate the size of the DCI format 0_1 based on the maximum number of bits between the scheduling DCI (e.g., DCI format 0_1 scrambled by the C-RNTI) and the DCI indicating the DFI 215 (e.g., DCI format 0_1 scrambled by the CS-RNTI). In such implementations, the UE 115-a and the network entity 105-a may zero-pad the DCI with a smaller number of bits until the size of the scheduling DCI and the size of the DCI indicating the DFI 215 become the same. For example, if the DCI indicating the DFI 215 includes 10 more information-carrying bits than the scheduling DCI, the UE 115-a and the network entity 105-a may add 10 zero bits (or anticipate adding 10 zero bits) to the scheduling DCI so that the DCI associated with the DCI format 0_1 is always the same. In some other embodiments, the UE 115-a and the network entity 105-a may expect that expansion of the size of the DFI 215 occurs exclusively (e.g., is supported only) when the scheduling DCI (e.g., DCI format 0_1 scrambled by C-RNTI) and the DCI indicating the DFI 215 (e.g., DCI format 0_1 scrambled by CS-RNTI) are the same size, or when the scheduling DCI already has enough bits to accommodate the extended DFI 215 (e.g., a 32-bit DFI 215) in addition to other fields associated with the DFI 215 (e.g., the DCI identifier field, the carrier indicator field (CIF), and the TPC field).
[0144] In some aspects, the UE 115-a and the network entity 105-a may support one or more options associated with whether the DFI 215 includes a single bit or multiple bits to indicate feedback for the data message 210, and one or more selections between the one or more options may be configurable by the network entity 105-a (e.g., by the network), such as via RRC signaling. In some aspects, the network entity 105-a may configure multiple options at the UE 115-a associated with whether the DFI 215 includes a single bit or multiple bits, and the UE 115-a and the network entity 105-a may use additional signaling or mutually understood rules to select one of the multiple options. Additionally or alternatively, the network entity 105-a may configure one or more options at the UE 115-a, and may send an implicit indication of one option via additional signaling. For example, if UE 115-a is configured with a first option associated with interpreting a single bit in DFI 215 as exclusively indicating feedback for one TB among multiple TBs, a second option associated with interpreting a single bit in DFI 215 as indicating bundled feedback for a first TB and a second TB, and a third option associated with supporting multiple (e.g., two) bits in DFI 215 corresponding to a multi-TB data message 210, then if bundling of HARQ-ACK feedback for two uplink TBs of PUSCH is configured by RRC, UE 115-a and network entity 105-a may select the second option; otherwise, UE 115-a and network entity 105-a may select the first option or the third option. For another example, if UE 115-a is configured with 32 bits for the size of the HARQ-ACK bitmap field by RRC, UE 115-a and network entity 105-a may select the third option; otherwise, UE 115-a and network entity 105-a may select the first option or the second option.
[0145] In addition, in some aspects, the selection between various options configured or available at the UE 115-a and the network entity 105-a may be adjusted based on the cg-RetransmissionTimer parameter to be configured by RRC. For example, indicating the DFI 215 in DCI format 0_1 may be adjusted based on the cg-RetransmissionTimer parameter to be configured. In other words, the transmission behavior, format, or content of the DFI 215 (or UCI 220, or both) may depend on whether the cg-RetransmissionTimer parameter is configured. For example, if the cg-RetransmissionTimer parameter is configured, the UE 115-a and the network entity 105-a may support a first set of one or more options for the DFI 215, and if the cg-RetransmissionTimer parameter is not configured, a second set of one or more options for the DFI 215 may be supported. For example, if the cg-RetransmissionTimer parameter is not configured, the UE 115-a and the network entity 105-a may exclusively support the first option for the DFI 215.
[0146] Additionally or alternatively, the UE 115-a and the network entity 105-a may multiplex the UCI 220 (e.g., CG-UCI) with the data message 210 and may support a UCI design associated with a CG-PUSCH transmission that provides sufficient information for a CG-PUSCH transmission using or including multiple TBs. For example, the UE 115-a and the network entity 105-a may support a UCI format according to which the UE 115-a is able to indicate multiple NDI fields and multiple RV fields via the UCI 220 associated with the data message 210. Therefore, the corresponding NDI field and the corresponding RV field may indicate feedback-related information for a corresponding TB of the multiple TBs used or included in the data message 210. In a second use case in which the CG-PUSCH is available for multi-TB transmission and in addition to supporting the DFI 215 (e.g., the DFI 215 associated with multiple TBs), the UE 115-a and the network entity 105-a also support this UCI format. In some aspects, in a second use case where UE 115-a and network entity 105-a also support a UCI format associated with multiple TBs, UE 115-a and network entity 105-a may relatively more frequently select the second option (wherein DFI 215 indicates bundled feedback for multiple TBs) or the third option (wherein DFI 215 includes multiple bits for a given HARQ process ID). Figure 3 and Figure 4Additional details related to UCI 220 are illustrated and described with reference to these figures.
[0147] Figure 3 An example of a UCI signaling design 300 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The UCI signaling design 300 may be implemented or implemented to implement aspects of the wireless communication system 100 or the wireless communication system 200. For example, the UE 115 and the network entity 105 (which may be, for example, Figure 1 and Figure 2 The examples of corresponding devices illustrated and described with reference to these figures) may support the UCI signaling design 300 to construct a single UCI message 305 (e.g., a CG-UCI message) and transmit it together with a data message (such as the data message 210) associated with multiple TBs 310. For example, the UE 115 may be scheduled or activated to transmit the data message 210 using a first TB 310-a (e.g., TB0 associated with CW0) and a second TB 310-b (e.g., TB1 associated with CW1), and in a scenario in which the data message 210 is a CG-PUSCH transmission, the UE 115 may multiplex the single UCI message 305 with the data message 210, and feedback-related information associated with the multiple TBs 310 may be provided via the single UCI message 305.
[0148] In some implementations, for example, the UE 115 and the network entity 105 may support a UCI format such that a single UCI message 305 multiplexed on the CG-PUSCH indicates multiple (e.g., two) NDI fields and multiple (e.g., two) RV fields corresponding to multiple (e.g., two) TBs 310. In some aspects, the UE 115 may jointly encode the UCI to obtain a single UCI message 305, and may multiplex the single UCI message 305 on the PUSCH. For example, and as illustrated by the UCI signaling design 300, the single UCI message 305 may have: two RV fields (e.g., 4 bits total) including a first RV field and a second RV field, two NDI fields (e.g., 2 bits total) including a first NDI field and a second NDI field, one HARQ process ID field, and one COT shared information field.
[0149] In some aspects, and as illustrated by option 315, the UE 115 may multiplex jointly coded UCI (e.g., a single UCI message 305) on one or more layers of one of the TBs 310. For example, the UE 115 may multiplex the UCI message 305 on one or more layers associated with the first TB 310-a. The first TB 310-a may be the first TB, a TB associated with a relatively larger MCS, or a TB corresponding to a relatively larger TB size (TBS), etc. In some other aspects, and as illustrated by option 320, the UE 115 may multiplex jointly coded UCI (e.g., a single UCI message 305) on one or more layers associated with multiple TBs. For example, the UE 115 may multiplex a single UCI message 305 on a first set of one or more layers associated with the first TB 310-a and on a second set of one or more layers associated with the second TB 310-b. Thus, the UE 115 may multiplex jointly coded UCI on layers of two TBs 310.
[0150] The network entity 105 may demultiplex and decode UCI in a manner similar to how the UE 115 encodes and multiplexes UCI. For example, if the UE 115 jointly encodes UCI such that a single UCI message 305 includes a first RV field, a first NDI field, a second RV field, and a second NDI field, and multiplexes the single UCI message 305 over one or more layers associated with the first TB 310-a (e.g., if the UE 115 complies with option 315), the network entity 105 may demultiplex the single UCI message 305 from the one or more layers associated with the first TB 310-a and attempt to decode the demultiplexed single UCI message 305. If the UE 115 multiplexes a single message on both the first TB 310-a and the second TB 310-b (e.g., if the UE 115 follows option 320), the network entity 105 may alternatively demultiplex the single UCI message 305 from one or more layers of both the first TB 310 and the second TB 310-b and attempt to decode the demultiplexed single UCI message 305.
[0151] Figure 4 An example of a UCI signaling design 400 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The UCI signaling design 400 may be implemented or implemented to implement aspects of the wireless communication system 100 or the wireless communication system 200. For example, the UE 115 and the network entity 105 (which may be, for example, Figure 1 and Figure 2The example of the corresponding device illustrated and described with reference to these figures) may support the UCI signaling design 400 to construct multiple UCI messages 405 (e.g., multiple CG-UCI messages) and send them together with data messages (such as data message 210) associated with multiple TBs 410. For example, the UE 115 may be scheduled or activated to send the data message 210 using the first TB 410-a (e.g., TB0 associated with CW0) and the second TB 410-b (e.g., TB1 associated with CW1), and in a scenario in which the data message 210 is a CG-PUSCH transmission, the UE 115 may multiplex the multiple UCI messages 405 with the data message 210, and may provide feedback-related information associated with the multiple TBs 310 via the multiple UCI messages 405.
[0152] In some specific implementations, for example, the UE 115 may separately encode the UCI (e.g., CG-UCI) corresponding to each TB 410 to obtain a plurality of UCI messages 405, and may multiplex the corresponding UCI messages 405 in the plurality of UCI messages 405 on the corresponding TB 410. For example, the UE 115 may encode the UCI to obtain a UCI message 405-a indicating feedback-related information for a first TB 410-a and a UCI message 405-b indicating feedback-related information for a second TB 410-b. Thus, the UE 115 may multiplex a single UCI message 405-a on a first set of one or more layers associated with the first TB 410-a, and multiplex a UCI message 405-b on a second set of one or more layers associated with the second TB 410-b. For one TB among the TBs 410 (e.g., the first TB 410-a), the corresponding UCI message 405 (e.g., the UCI message 405-a) may include a first RV field, a first NDI field, a HARQ process ID field, and a COT shared information field. For the remaining number of TBs 410 (e.g., for other TBs 410, such as the second TB 410-b), the corresponding one or more UCI messages 405 (e.g., the UCI message 405-b) may include a second RV field, a second NDI field, a HARQ process ID field, and a COT shared information field, or include the second RV field and the second NDI field and exclude the HARQ process ID field and the COT shared information field.
[0153] For example, in option 415, the UE 115 may include a second RV field and a second NDI field, and exclude the HARQ process ID field and the COT shared information field. In such option 415, the UE 115 and the network entity 105 may achieve lower signaling overhead and greater spectral efficiency because the UCI message 405-b may include fewer (and less redundant) fields. In option 420, the UE 115 may additionally include the HARQ process ID field and the COT shared information field in the UCI message 405-b (along with the second RV field and the second NDI field), and the HARQ process ID field and the COT shared information field of both the UCI message 405-a and the UCI message 405-b may include the same content or information. In this option 420, the UE 115 and the network entity 105 can achieve greater reliability because even if the network entity 105 fails to decode the UCI message 405-a but successfully decodes the UCI message 405-b, the network entity 105 can still attempt to decode the second TB 410-b using information in the successfully decoded UCI message 405-b.
[0154] The network entity 105 may demultiplex and decode UCI in a manner similar to how UCI is encoded and multiplexed by the UE 115. For example, the network entity may demultiplex a UCI message 405-a from a first TB 410- and may demultiplex a UCI message 405-b from a second TB 410-b, and may decode the demultiplexed UCI message 405-a and the demultiplexed UCI message 405-b, respectively.
[0155] Figure 5 An example of a communication timeline 500 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The communication timeline 500 may implement or be implemented to implement aspects of the wireless communication system 100, the wireless communication system 200, the UCI signaling design 300, or the UCI signaling design 400. For example, the UE 115 and the network entity 105 (which may be, for example, Figure 1 and Figure 2 Examples of corresponding devices illustrated and described with reference to these figures) may communicate according to the communication timeline 500 according to the CG configuration for various CG opportunities 505. In some specific implementations, the UE 115 and the network entity 105 may support feedback-related signaling designs that support feedback mechanisms for CG-PUSCH or DG-PUSCH transmissions using or including multiple TBs.
[0156] The CG configuration may be associated with a Type 1CG or a Type 2CG. In a Type 1CG, the network entity 105 may configure (e.g., RRC configure) all relevant parameters and scheduling information. In a Type 2CG, the network entity 105 may configure (e.g., RRC configure) a first portion of the parameters or information, and may indicate a second portion of the parameters or information in a DCI that activates the CG-PUSCH. This first portion of the parameters or information may include a periodicity 510 and an offset. In some aspects, the DCI activates the CG, and the UE 115 may send a PUSCH according to the periodicity 510 and the offset until another DCI releases the CG. In other words, the periodicity 510 and the offset, as well as other parameters, may indicate or otherwise enable the UE 115 to identify various CG opportunities 505 during which the UE 115 may perform CG-PUSCH transmissions. For example, based on the periodicity 510 and the offset, the UE 115 may identify the CG timing 505-a, the CG timing 505-b, the CG timing 505-c, the CG timing 505-d, the CG timing 505-e, and the CG timing 505-f.
[0157] For both activation and release DCI, the CRC of the DCI may be scrambled with the CS-RNTI. For confirmation of activation or release indicated by the DCI, the DCI may include an NDI field = 0, an Rv field = 0, and a HARQ Id field = 0. In addition, for both Type 1 CG and Type 2 CG, in each CG opportunity 505, the RV may be equal to 0, and the UE 115 and the network entity 105 may calculate, calculate, or otherwise determine the HARQ ID from the timing by performing a modulo operation on the nrofHARQ-Processes configured for the CG opportunity 505 (for each CG opportunity 505). For example, the UE 115 and the network entity 105 may calculate, calculate, or determine the HARQ process ID according to Equation 1 shown below.
[0158]
[0159] As shown in Equation 1, CURRENT_symbol = (SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+number of slots in frame×numberOfSymbolsPerSlot+number of symbols in slot), and numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the number of consecutive slots per frame and the number of consecutive symbols per slot, respectively. In some aspects, CURRENT_symbol may refer to the symbol index of the first or initial transmission opportunity of a repeated beam that occurs. As shown in the communication timeline 500, CG opportunity 505-a and CG opportunity 505-e may be associated with HARQ ID=0, CG opportunity 505-b and CG opportunity 505-f may be associated with HARQ ID=1, CG opportunity 505-c may be associated with HARQ ID=2, and CG opportunity 505-d may be associated with HARQ ID=3.
[0160] Figure 6 An example of a process flow 600 for supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The process flow 600 may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the UCI signaling design 300, the UCI signaling design 400, or the communication timeline 500. For example, the process flow 600 illustrates communication between a UE 115-b and a network entity 105-b, which may be, for example, Figure 1 and Figure 2 Examples of corresponding devices illustrated and described with reference to these figures. In some specific implementations, the UE 115-b and the network entity 105-b may support feedback-related signaling designs that support feedback mechanisms for CG-PUSCH or DG-PUSCH transmissions using or including multiple TBs.
[0161] In the following description of process flow 600, operations may be performed (e.g., reported or provided) in a different order than shown, or operations performed by the example device may be performed in a different order or at a different time. For example, specific operations may also be excluded from process flow 600, or other operations may be added to process flow 600. In addition, although some operations or signaling are shown as occurring at different times for discussion purposes, these operations may actually occur simultaneously.
[0162] At 605, UE 115-b may receive scheduling or configuration information from network entity 105-b indicating that UE 115-b will send a data message using multiple TBs, the multiple TBs including at least a first TB and a second TB. Additionally or alternatively, UE 115-b may receive configuration information associated with a DFI that network entity 105-b may provide to UE 115-a in response to the data message, and UE 115-b may anticipate processing the DFI based on the configuration information. In some aspects, such configuration information for the DFI may indicate options for formatting or interpreting the DFI based on the data message using multiple TBs, as described in reference to FIG. Figure 2 Described in more detail. For example, the configuration information may indicate how the UE 115-b is to interpret one or more bits in the DFI as HARQ-ACK feedback for one or both of the first TB and the second TB, or whether the UE 115-b is to ignore any bits in the DFI, etc. In some aspects, the UE 115-b may receive scheduling or configuration information from the network entity 105-b via one or more of RRC signaling, DCI, or MAC control element (MAC-CE).
[0163] At 610, in some implementations, the UE 115-b may encode the UCI to obtain one or more UCI messages associated with the data message. For example, in an implementation in which the UE 115-b sends a data message via the CG-PUSCH, the UE 115-b may multiplex the UCI with the data message, and the UCI may include multiple NDI fields and multiple RV fields, wherein corresponding NDI fields in the multiple NDI fields and corresponding RV fields in the multiple RV fields correspond to corresponding TBs in the multiple TBs.
[0164] In some aspects, the UE 115-b may encode the UCI to obtain a single UCI message including multiple NDI fields and multiple RV fields. Additional details related to such joint encoding to obtain a single UCI message having multiple NDI fields and multiple RV fields are provided by Figure 3 1 and 2. In some other aspects, UE 115-b may encode UCI to obtain multiple UCI messages. The multiple UCI messages may include a first UCI message and a second UCI message, wherein the first UCI message includes a first NDI field and a first RV field corresponding to the first TB, and the second UCI message includes a second NDI field and a second RV field corresponding to the second TB.
[0165] At 615, in some implementations, UE 115-b may multiplex one or more UCI messages with a data message. For example, in an implementation in which UE 115-b sends UCI with a data message via CG-PUSCH, UE 115-b may multiplex UCI with the data message on CG-PUSCH. In aspects in which UE 115-b jointly encodes UCI to obtain a single UCI message, UE 115-b may multiplex the single UCI message on one or more layers associated with one of the first TB or the second TB, or may multiplex the single UCI message on both a first set of one or more layers associated with the first TB and a second set of one or more layers associated with the second TB. In aspects in which UE 115-b encodes UCI to obtain multiple UCI messages including a first UCI message and a second UCI message, UE 115-b may multiplex the first UCI message on a first set of one or more layers associated with the first TB, and may multiplex the second UCI message on a second set of one or more layers associated with the second TB.
[0166] At 620, UE 115-b may send a data message using or including multiple TBs to network entity 105-b based on the scheduling or configuration information. The data message may include a feedback process ID (e.g., a HARQ process ID) associated with the multiple TBs of the data message or may be associated with the feedback process ID in other ways. For example, the data message may indicate the feedback process ID via UCI (e.g., for CG-PUSCH), or the data message may be associated with a feedback process ID indicated in a scheduling or activation DCI (e.g., for DG-PUSCH).
[0167] At 625, in some implementations, the network entity 105-b may demultiplex UCI from the data message. Depending on whether the UE 115-b encodes the UCI to obtain a single UCI message or multiple UCI messages, the network entity 105-b may demultiplex a single UCI message from one or both of the first set of layers associated with the first TB and the second set of layers associated with the second TB, or demultiplex a different UCI message from each of the first set of layers associated with the first TB and the second set of layers associated with the second TB. In some aspects, receiving the data message by the network entity 105-b is associated with demultiplexing the UCI from the data message.
[0168] At 630, in some implementations, the network entity 105-b may decode the UCI to obtain one or more UCI messages. In some aspects, the network entity 105-b may decode the UCI demultiplexed from the data message to obtain a single UCI message including multiple NDI fields and multiple RV fields. In some other aspects, the network entity 105-b may decode the UCI demultiplexed from the data message to obtain multiple UCI messages. The multiple UCI messages may include a first UCI message and a second UCI message, and the first UCI message may include a first NDI field and a first RV field corresponding to a first TB of the data message, and the second UCI message may include a second NDI field and a second RV field corresponding to a second TB of the data message.
[0169] At 635, UE 115-b may receive a DFI corresponding to a feedback process ID (e.g., a feedback process ID associated with a data message and, likewise, multiple TBs included in the data message) from network entity 105-b. In some aspects, the DFI may include a single bit corresponding to the feedback process ID, and the single bit may exclusively indicate feedback for a first TB (e.g., one of the TBs included in the data message). In some other aspects, the DFI may include a single bit corresponding to the feedback process ID, and the single bit may indicate first feedback corresponding to the first TB and second feedback corresponding to the second TB. For example, the single bit may indicate bundled feedback for the first TB and the second TB via a logical "AND" operation or a logical "OR" operation between the first feedback and the second feedback.
[0170] In some other aspects, the DFI may include a plurality of bits corresponding to the feedback process ID, and each respective bit of the plurality of bits indicates a respective feedback corresponding to each respective TB of the plurality of TBs. For example, the DFI may include two bits corresponding to the feedback process ID, the two bits including a first bit indicating a first feedback associated with the first TB and a second bit indicating a second feedback associated with the second TB. In such examples, the DFI may include a 32-bit bitmap, and the 32-bit bitmap may include a plurality of bit sets, wherein each respective bit set corresponds to a respective feedback process ID of the plurality of (unique) feedback process IDs. For example, a first set of a plurality of (e.g., two) bits may correspond to a feedback process ID associated with a data message, a second set of a plurality of (e.g., two) bits may correspond to a second feedback process ID associated with a second data message, a third set of a plurality of (e.g., two) bits may correspond to a third feedback process ID associated with a third data message, and so on.
[0171] In some of such examples where the DFI includes multiple sets of bits, each set of bits corresponding to a different feedback process ID, the UE 115-b and the network entity 105-b may support mutually understood rules (which may be preconfigured or signaled, such as signaled via configuration information) according to which the UE 115-b and the network entity 105-b handle scenarios in which a feedback process ID in a plurality of different feedback process IDs is associated with a single TB. For example, if a second set of multiple bits corresponding to a second feedback process ID associated with a second data message is also associated with a single TB, the UE 115-b and the network entity 105-b may expect a first bit in the second set of multiple bits to indicate feedback for a single TB, and may handle a second bit in the second set of multiple bits according to one or more of the various options. In some aspects, the UE 115-b and the network entity 105-b may expect the second bit to be set to a null or default value. Additionally or alternatively, UE 115-b may be configured (via signaling or by at least one processor of UE 115-b, or both) to ignore the second bit.
[0172] At 640, the UE 115-b may handle the DFI based on the configuration information provided by the network entity 105-b and based on one or more selected or preconfigured rules associated with how the UE 115-b is to interpret the DFI associated with the multi-TB PUSCH transmission.
[0173] In some aspects, UE 115-b may communicate with network entity 105-b based on sending a data message and based on the DFI. For example, if the DFI indicates that network entity 105-b successfully decoded the data message (e.g., successfully decoded all TBs in a plurality of TBs associated with the data message), UE 115-b and network entity 105-b may subsequently communicate new data. Alternatively, if the DFI indicates that network entity 105-b did not successfully decode at least one TB of the data message, UE 115-b may perform one or more partial or full retransmissions of the data message to increase the likelihood that network entity 105-b is able to successfully decode each TB in a plurality of TBs associated with the data message. If network entity 105-b successfully decodes a first TB and fails to successfully decode a second TB, UE 115-b may exclusively retransmit the second TB (and refrain from retransmitting the first TB), or may retransmit both the first TB and the second TB.
[0174] Figure 7A block diagram 700 of a device 705 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0175] The receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to a multi-TB uplink shared channel transmission feedback mechanism). The information may be passed to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.
[0176] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to a multi-TB uplink shared channel transmission feedback mechanism), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.
[0177] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the multi-TB uplink shared channel transmission feedback mechanism as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.
[0178] In some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include at least one processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured to or otherwise support components for performing the functions described in the present disclosure. In some examples, at least one processor and a memory coupled to the at least one processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the at least one processor).
[0179] Additionally or alternatively, in some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.
[0180] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.
[0181] The communication manager 720 may support wireless communication at the first network node according to the examples disclosed herein. For example, the communication manager 720 may be configured to or otherwise support a component for receiving information from a second network node indicating that the first network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB. The communication manager 720 may be configured to or otherwise support a component for sending a data message using the set of multiple TBs to the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs. The communication manager 720 may be configured to or otherwise support a component for receiving a DFI corresponding to the feedback process ID from the second network node.
[0182] By including or configuring a communications manager 720 according to examples as described herein, a device 705 (e.g., a processor controlling or otherwise coupled to a receiver 710, a transmitter 715, a communications manager 720, or a combination thereof) may support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communications resources.
[0183] Figure 8A block diagram 800 of a device 805 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the device 705 or UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0184] The receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to a multi-TB uplink shared channel transmission feedback mechanism). The information may be communicated to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.
[0185] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to a multi-TB uplink shared channel transmission feedback mechanism), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.
[0186] Device 805 or its various components may be examples of components for performing various aspects of the multi-TB uplink shared channel transmission feedback mechanism as described herein. For example, the communication manager 820 may include a CG component 825, a PUSCH transmission component 830, a feedback component 835, or any combination thereof. The communication manager 820 may be an example of various aspects of the communication manager 720 as described herein. In some examples, the communication manager 820 or its various components may be configured to use or otherwise cooperate with the receiver 810, the transmitter 815, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or integrate with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.
[0187] The communication manager 820 may support wireless communication at the first network node according to the examples disclosed herein. The CG component 825 may be configured to or otherwise support a component for receiving information from the second network node indicating that the first network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB. The PUSCH transmission component 830 may be configured to or otherwise support a component for sending a data message using the set of multiple TBs to the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs. The feedback component 835 may be configured to or otherwise support a component for receiving a DFI corresponding to the feedback process ID from the second network node.
[0188] Fig. 9 A block diagram 900 of a communication manager 920 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The communication manager 920 may be an example of aspects of the communication manager 720, the communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of components for performing various aspects of the multi-TB uplink shared channel transmission feedback mechanism as described herein. For example, the communication manager 920 may include a CG component 925, a PUSCH transmission component 930, a feedback component 935, an RRC component 940, a UCI component 945, a coding component 950, a multiplexing component 955, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).
[0189] The communication manager 920 may support wireless communication at the first network node according to the examples disclosed herein. The CG component 925 may be configured to or otherwise support a component for receiving information from the second network node indicating that the first network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB. The PUSCH transmission component 930 may be configured to or otherwise support a component for sending a data message using the set of multiple TBs to the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs. The feedback component 935 may be configured to or otherwise support a component for receiving a DFI corresponding to the feedback process ID from the second network node.
[0190] In some examples, to support receiving a DFI, feedback component 935 may be configured or otherwise support means for receiving a DCI including a DFI, wherein the DFI includes a first bit corresponding to a feedback process ID, and wherein the first bit indicates a first feedback corresponding exclusively to a first TB.
[0191] In some examples, the DFI is a 16-bit bitmap. In some examples, the 16-bit bitmap includes a first bit. In some examples, the 16-bit bitmap excludes any feedback corresponding to the second TB.
[0192] In some examples, to support receiving a DFI, feedback component 935 may be configured to or otherwise support means for receiving a DCI including a DFI, wherein the DFI includes a first bit corresponding to a feedback process ID, and wherein the first bit indicates first feedback corresponding to a first TB and second feedback corresponding to a second TB.
[0193] In some examples, the first bit is a first value or a second value. In some examples, the first value indicates that the first feedback and the second feedback are each a corresponding ACK. In some examples, the second value indicates that at least one of the first feedback or the second feedback is a NACK.
[0194] In some examples, the DFI includes a set of multiple bits. In some examples, the set of multiple bits includes a first bit. In some examples, each corresponding bit in the set of multiple bits corresponds to a corresponding feedback process ID in a set of multiple feedback process IDs. In some examples, the set of multiple feedback process IDs includes a feedback process ID associated with a set of multiple TBs. In some examples, the sets of multiple feedback process IDs are all different.
[0195] In some examples, the first bit corresponds to a logical AND operation between the first feedback and the second feedback.
[0196] In some examples, the first bit corresponds to a logical OR operation between the first feedback and the second feedback.
[0197] In some examples, to support receiving a DFI, feedback component 935 may be configured to or otherwise support components for receiving a DCI that includes a DFI, wherein the DFI includes a set of multiple bits corresponding to a feedback process ID, wherein each respective bit in the set of multiple bits indicates respective feedback corresponding to each respective TB in a set of multiple TBs.
[0198] In some examples, a first bit in the set of multiple bits indicates first feedback corresponding to a first TB, and a second bit in the set of multiple bits indicates second feedback corresponding to a second TB.
[0199] In some examples, the DFI is a 32-bit bitmap including a set of a plurality of bits. In some examples, the 32-bit bitmap includes a first bit and a second bit.
[0200] In some examples, the set of multiple bits includes multiple bit sets. In some examples, each corresponding bit set in the multiple bit sets corresponds to a corresponding feedback process ID in the set of multiple feedback process IDs. In some examples, the set of multiple feedback process IDs includes feedback process IDs associated with a set of multiple TBs. In some examples, the sets of multiple feedback process IDs are all different.
[0201] In some examples, the second bit is a null or default value; or the first network node ignores the second bit.
[0202] In some examples, the DCI format associated with both the DCI including the DFI and the scheduling DCI has a fixed size. In some examples, the DCI including the DFI includes a first number of bits. In some examples, the scheduling DCI includes a second number of bits. In some examples, the fixed size is equal to the larger of the first number of bits and the second number of bits.
[0203] In some examples, if the scheduling DCI includes a number of bits that is equal to or greater than the total number of bits of the DCI including the multiple sets of bits, then the set of multiple bits includes the multiple sets of bits.
[0204] In some examples, RRC component 940 may be configured or otherwise support means for receiving configuration information from the second network node via RRC signaling.In some examples, feedback component 935 may be configured or otherwise support means for processing DFI based on the configuration information.
[0205] In some examples, the UCI component 945 may be configured to or otherwise support components for sending UCI associated with a data message, wherein the UCI includes a set of multiple NDI fields and a set of multiple RV fields, wherein corresponding NDI fields in the set of multiple NDI fields and corresponding RV fields in the set of multiple RV fields correspond to corresponding TBs in the set of multiple TBs.
[0206] In some examples, encoding component 950 may be configured or otherwise support means for encoding UCI to obtain a single UCI message including a set of multiple NDI fields and a set of multiple RV fields, wherein sending the UCI includes sending the single UCI message.
[0207] In some examples, multiplexing component 955 may be configured or otherwise support means for multiplexing a single UCI message on one or more layers associated with a TB in a set of multiple TBs, wherein sending UCI includes sending the single UCI message on the one or more layers.
[0208] In some examples, the multiplexing component 955 may be configured as or otherwise support components for multiplexing a single UCI message on a first set of one or more layers associated with a first TB in a set of multiple TBs and on a second set of one or more layers associated with a second TB in the set of multiple TBs, wherein sending the UCI includes sending the single UCI message on the first set of one or more layers and on the second set of one or more layers.
[0209] In some examples, encoding component 950 may be configured to or otherwise support means for encoding UCI to obtain a set of multiple UCI messages, wherein the set of multiple UCI messages includes a first UCI message and a second UCI message, wherein the first UCI message includes a first NDI field in a set of multiple NDI fields and a first RV field in a set of multiple RV fields, and wherein the second UCI message includes a second NDI field in a set of multiple NDI fields and a second RV field in a set of multiple RV fields. In some examples, multiplexing component 955 may be configured to or otherwise support means for multiplexing the first UCI message on a first set of one or more layers associated with a first TB and multiplexing the second UCI message on a second set of one or more layers associated with a second TB, wherein sending UCI includes sending the first UCI message on the first set of one or more layers and sending the second UCI message on the second set of one or more layers.
[0210] In some examples, a first UCI message associated with a first TB in a set of multiple UCI messages includes a first RV field, a first NDI field, a first feedback process ID field, and a first channel occupancy time sharing information field; and a second UCI message associated with a second TB in a set of multiple UCI messages includes a second RV field, a second NDI field, a second feedback process ID field, and a second channel occupancy time sharing information field, wherein the second feedback process ID field and the second channel occupancy time sharing information field respectively include the same information as the first feedback process ID field and the first channel occupancy time sharing information field.
[0211] In some examples, a first UCI message associated with a first TB in a set of multiple UCI messages includes a first RV field, a first NDI field, a first feedback process ID field, and a first channel occupancy time sharing information field; and a second UCI message associated with a second TB in a set of multiple UCI messages exclusively includes a second RV field and a second NDI field.
[0212] In some examples, the data message is a CG-PUSCH transmission or a DG-PUSCH transmission.
[0213] Fig.10 A diagram of a system 1000 including a device 1005 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a UE 115 as described herein, or include components thereof. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).
[0214] I / O controller 1010 can manage input and output signals for device 1005. I / O controller 1010 can also manage peripheral devices that are not integrated into device 1005. In some cases, I / O controller 1010 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1010 may be implemented as part of at least one processor such as processor 1040. In some cases, a user may interact with device 1005 via I / O controller 1010 or via hardware components controlled by I / O controller 1010.
[0215] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1015 may communicate bidirectionally via one or more antennas 1025, a wired or wireless link, as described herein. For example, the transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1015 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1025 for transmission; and demodulating packets received from one or more antennas 1025. The transceiver 1015 or the transceiver 1015 and one or more antennas 1025 may be examples of transmitters 715, transmitters 815, receivers 710, receivers 810, or any combination thereof or components thereof as described herein.
[0216] The memory 1030 may include random access memory (RAM) and read-only memory (ROM). The memory 1030 may store computer-readable, computer-executable code 1035 including instructions that, when executed by the processor 1040, cause the device 1005 to perform various functions described herein. The code 1035 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1035 may not be directly executable by the processor 1040, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1030 may also contain, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0217] Processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks that support a multi-TB uplink shared channel transmission feedback mechanism). For example, device 1005 or a component of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040, and processor 1040 and memory 1030 are configured to perform the various functions described herein.
[0218] The communication manager 1020 may support wireless communication at the first network node according to the examples disclosed herein. For example, the communication manager 1020 may be configured to or otherwise support a component for receiving information from a second network node indicating that the first network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB. The communication manager 1020 may be configured to or otherwise support a component for sending a data message using the set of multiple TBs to the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs. The communication manager 1020 may be configured to or otherwise support a component for receiving a DFI corresponding to the feedback process ID from the second network node.
[0219] By including or configuring a communications manager 1020 according to the examples described herein, the device 1005 may support techniques for improving communications reliability, reducing latency, improving user experience associated with reduced processing, reducing power consumption, more efficiently utilizing communications resources, improving coordination between devices, extending battery life, and improving utilization of processing power.
[0220] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions that may be executed by the processor 1040 to cause the device 1005 to perform various aspects of the multi-TB uplink shared channel transmission feedback mechanism as described herein, or the processor 1040 and the memory 1030 may be otherwise configured to perform or support such operations.
[0221] Fig.11 A block diagram 1100 of a device 1105 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0222] Receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) 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). The information may be communicated to other components of device 1105. In some examples, receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.
[0223] The transmitter 1115 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 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, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.
[0224] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the multi-TB uplink shared channel transmission feedback mechanism as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.
[0225] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include at least one processor, DSP, CPU, ASIC, FPGA or other programmable logic device, microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured to or otherwise support means for performing the functions described in the present disclosure. In some examples, at least one processor and a memory coupled to at least one processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by at least one processor).
[0226] Additionally or alternatively, in some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functions of the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.
[0227] In some examples, communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in conjunction with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.
[0228] The communication manager 1120 may support wireless communication at the first network node according to the examples disclosed herein. For example, the communication manager 1120 may be configured to or otherwise support a component for sending information indicating that the second network node will send a data message using a set of multiple TBs to the second network node, wherein the set of multiple TBs includes a first TB and a second TB. The communication manager 1120 may be configured to or otherwise support a component for receiving a data message including the set of multiple TBs from the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs. The communication manager 1120 may be configured to or otherwise support a component for sending a DFI corresponding to the feedback process ID to the second network node.
[0229] By including or configuring a communications manager 1120 according to the examples described herein, a device 1105 (e.g., a processor controlling or otherwise coupled to a receiver 1110, a transmitter 1115, a communications manager 1120, or a combination thereof) may support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communications resources.
[0230] Fig.12 A block diagram 1200 of a device 1205 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the device 1105 or network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0231] The receiver 1210 may provide means for obtaining (e.g., receiving, determining, identifying) 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). The information may be passed to other components of the device 1205. In some examples, the receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.
[0232] The transmitter 1215 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1205. For example, the transmitter 1215 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, the transmitter 1215 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1215 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include a modem or be coupled to a modem.
[0233] Device 1205 or its various components may be examples of components for performing various aspects of a multi-TB uplink shared channel transmission feedback mechanism as described herein. For example, communication manager 1220 may include CG component 1225, PUSCH receiving component 1230, feedback component 1235, or any combination thereof. Communication manager 1220 may be an example of various aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1210, transmitter 1215, or both. For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated with receiver 1210, transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.
[0234] The communication manager 1220 may support wireless communication at the first network node according to the examples disclosed herein. The CG component 1225 may be configured to or otherwise support a component for sending information indicating that the second network node will send a data message using a set of multiple TBs to the second network node, wherein the set of multiple TBs includes a first TB and a second TB. The PUSCH reception component 1230 may be configured to or otherwise support a component for receiving a data message including the set of multiple TBs from the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs. The feedback component 1235 may be configured to or otherwise support a component for sending a DFI corresponding to the feedback process ID to the second network node.
[0235] Fig.13A block diagram 1300 of a communication manager 1320 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The communication manager 1320 can be an example of aspects of the communication manager 1120, the communication manager 1220, or both as described herein. The communication manager 1320 or its various components can be examples of components for performing various aspects of the multi-TB uplink shared channel transmission feedback mechanism as described herein. For example, the communication manager 1320 may include a CG component 1325, a PUSCH reception component 1330, a feedback component 1335, an RRC component 1340, a UCI component 1345, a decoding component 1350, a demultiplexing component 1355, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.
[0236] The communication manager 1320 may support wireless communication at the first network node according to the examples disclosed herein. The CG component 1325 may be configured to or otherwise support a component for sending information indicating that the second network node will send a data message using a set of multiple TBs to the second network node, wherein the set of multiple TBs includes a first TB and a second TB. The PUSCH reception component 1330 may be configured to or otherwise support a component for receiving a data message including the set of multiple TBs from the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs. The feedback component 1335 may be configured to or otherwise support a component for sending a DFI corresponding to the feedback process ID to the second network node.
[0237] In some examples, to support sending a DFI, feedback component 1335 may be configured to or otherwise support means for sending a DCI including a DFI, wherein the DFI includes a first bit corresponding to a feedback process ID, and wherein the first bit indicates a first feedback corresponding exclusively to a first TB.
[0238] In some examples, the DFI is a 16-bit bitmap. In some examples, the 16-bit bitmap includes a first bit. In some examples, the 16-bit bitmap excludes any feedback corresponding to the second TB.
[0239] In some examples, to support sending a DFI, feedback component 1335 may be configured to or otherwise support components for sending a DCI including a DFI, wherein the DFI includes a first bit corresponding to a feedback process ID, and wherein the first bit indicates first feedback corresponding to a first TB and second feedback corresponding to a second TB.
[0240] In some examples, the first bit is a first value or a second value. In some examples, the first value indicates that the first feedback and the second feedback are each a corresponding ACK. In some examples, the second value indicates that at least one of the first feedback or the second feedback is a NACK.
[0241] In some examples, the DFI includes a set of multiple bits. In some examples, the set of multiple bits includes a first bit. In some examples, each corresponding bit in the set of multiple bits corresponds to a corresponding feedback process ID in a set of multiple feedback process IDs. In some examples, the set of multiple feedback process IDs includes a feedback process ID associated with a set of multiple TBs. In some examples, the sets of multiple feedback process IDs are all different.
[0242] In some examples, the first bit corresponds to a logical AND operation between the first feedback and the second feedback.
[0243] In some examples, the first bit corresponds to a logical OR operation between the first feedback and the second feedback.
[0244] In some examples, to support sending a DFI, feedback component 1335 may be configured to or otherwise support components for sending a DCI including a DFI, wherein the DFI includes a set of multiple bits corresponding to a feedback process ID, wherein each respective bit in the set of multiple bits indicates respective feedback corresponding to each respective TB in a set of multiple TBs.
[0245] In some examples, a first bit in the set of multiple bits indicates first feedback corresponding to a first TB, and a second bit in the set of multiple bits indicates second feedback corresponding to a second TB.
[0246] In some examples, the DFI is a 32-bit bitmap including a set of a plurality of bits. In some examples, the 32-bit bitmap includes a first bit and a second bit.
[0247] In some examples, the set of multiple bits includes multiple bit sets. In some examples, each corresponding bit set in the multiple bit sets corresponds to a corresponding feedback process ID in the set of multiple feedback process IDs. In some examples, the set of multiple feedback process IDs includes feedback process IDs associated with a set of multiple TBs. In some examples, the sets of multiple feedback process IDs are all different.
[0248] In some examples, the second bit is a null or default value; or the second network node will ignore the second bit.
[0249] In some examples, the DCI format associated with both the DCI including the DFI and the scheduling DCI has a fixed size. In some examples, the DCI including the DFI includes a first number of bits. In some examples, the scheduling DCI includes a second number of bits. In some examples, the fixed size is equal to the larger of the first number of bits and the second number of bits.
[0250] In some examples, if the scheduling DCI includes a number of bits that is equal to or greater than the total number of bits of the DCI including the multiple sets of bits, then the set of multiple bits includes the multiple sets of bits.
[0251] In some examples, RRC component 1340 may be configured or otherwise support means for sending configuration information from the second network node via RRC signaling, wherein the configuration information is associated with the DFI.
[0252] In some examples, UCI component 1345 may be configured to or otherwise support components for receiving UCI associated with a data message, wherein the UCI includes a set of multiple NDI fields and a set of multiple RV fields, wherein corresponding NDI fields in the set of multiple NDI fields and corresponding RV fields in the set of multiple RV fields correspond to corresponding TBs in the set of multiple TBs.
[0253] In some examples, the UCI is a single UCI message, and the decoding component 1350 can be configured or otherwise support means for decoding the UCI to obtain a single UCI message including a set of multiple NDI fields and a set of multiple RV fields.
[0254] In some examples, demultiplexing component 1355 may be configured or otherwise support means for demultiplexing a single UCI message from one or more layers associated with a TB in a set of multiple TBs, wherein receiving UCI includes receiving a single UCI message on the one or more layers.
[0255] In some examples, demultiplexing component 1355 may be configured as or otherwise support components for demultiplexing a single UCI message from a first set of one or more layers associated with a first TB in a set of multiple TBs and from a second set of one or more layers associated with a second TB in the set of multiple TBs, wherein receiving UCI includes receiving a single UCI message on the first set of one or more layers and on the second set of one or more layers.
[0256] In some examples, the UCI is a set of multiple UCI messages, and the decoding component 1350 may be configured to or otherwise support means for decoding the UCI to obtain the set of multiple UCI messages, wherein the set of multiple UCI messages includes a first UCI message and a second UCI message, wherein the first UCI message includes a first NDI field in a set of multiple NDI fields and a first RV field in a set of multiple RV fields, and wherein the second UCI message includes a second NDI field in a set of multiple NDI fields and a second RV field in a set of multiple RV fields. In some examples, the UCI is a set of multiple UCI messages, and the demultiplexing component 1355 may be configured to or otherwise support means for demultiplexing the first UCI message on a first set of one or more layers associated with the first TB and demultiplexing the second UCI message on a second set of one or more layers associated with the second TB, wherein receiving the UCI includes receiving the first UCI message on the first set of one or more layers and receiving the second UCI message on the second set of one or more layers.
[0257] In some examples, a first UCI message associated with a first TB in a set of multiple UCI messages includes a first RV field, a first NDI field, a first feedback process ID field, and a first COT shared information field; and a second UCI message associated with a second TB in a set of multiple UCI messages includes a second RV field, a second NDI field, a second feedback process ID field, and a second channel occupancy time sharing information field, wherein the second feedback process ID field and the second channel occupancy time sharing information field respectively include the same information as the first feedback process ID field and the first COT shared information field.
[0258] In some examples, a first UCI message associated with a first TB in a set of multiple UCI messages includes a first RV field, a first NDI field, a first feedback process ID field, and a first channel occupancy time sharing information field; and a second UCI message associated with a second TB in a set of multiple UCI messages exclusively includes a second RV field and a second NDI field.
[0259] In some examples, the data message is a CG-PUSCH transmission or a DG-PUSCH transmission.
[0260] Fig.14A diagram of a system 1400 including a device 1405 supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of a device 1105, a device 1205, or a network entity 105 as described herein, or include components thereof. The device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1405 may include components that support output and acquisition of communications, such as a communication manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, a code 1430, and a processor 1435. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1440).
[0261] The transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1410 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1410 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1405 may include one or more antennas 1415 that may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1410 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1415, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1415, from a wired receiver); and demodulating the signal. The transceiver 1410 or the transceiver 1410 and one or more antennas 1415 or a wired interface (where applicable) may be an example of a transmitter 1115, a transmitter 1215, a receiver 1110, a receiver 1210, or any combination thereof or any component thereof as described herein. In some examples, the transceiver 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, fronthaul communication link 168).
[0262] Memory 1425 may include RAM and ROM. Memory 1425 may store computer-readable, computer-executable code 1430 including instructions that, when executed by processor 1435, cause device 1405 to perform various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by processor 1435, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1425 may also contain, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0263] Processor 1435 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1435. Processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1425) to cause device 1405 to perform various functions (e.g., functions or tasks that support a multi-TB uplink shared channel transmission feedback mechanism). For example, device 1405 or a component of device 1405 may include processor 1435 and memory 1425 coupled to processor 1435, and processor 1435 and memory 1425 are configured to perform the various functions described herein. Processor 1435 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality for performing functions of device 1405 (e.g., by executing code 1430).
[0264] In some examples, bus 1440 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1440 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1405, or communications performed between different components of device 1405 that may be co-located or located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, memory 1425, code 1430, and processor 1435 may be located in one of these different components or divided between different components).
[0265] In some examples, communication manager 1420 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1420 may manage delivery of data communications for client devices such as one or more UEs 115. In some examples, communication manager 1420 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in coordination with other network entities 105. In some examples, communication manager 1420 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.
[0266] The communication manager 1420 may support wireless communication at the first network node according to the examples disclosed herein. For example, the communication manager 1420 may be configured to or otherwise support a component for sending information indicating that the second network node will send a data message using a set of multiple TBs to the second network node, wherein the set of multiple TBs includes a first TB and a second TB. The communication manager 1420 may be configured to or otherwise support a component for receiving a data message including the set of multiple TBs from the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of multiple TBs. The communication manager 1420 may be configured to or otherwise support a component for sending a DFI corresponding to the feedback process ID to the second network node.
[0267] By including or configuring a communications manager 1420 according to the examples described herein, the device 1405 may support techniques for improving communications reliability, reducing latency, improving user experience associated with reduced processing, reducing power consumption, more efficiently utilizing communications resources, improving coordination between devices, extending battery life, and improving utilization of processing power.
[0268] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof. Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the processor 1435, the memory 1425, the code 1430, the transceiver 1410, or any combination thereof. For example, the code 1430 may include instructions that may be executed by the processor 1435 to cause the device 1405 to perform various aspects of the multi-TB uplink shared channel transmission feedback mechanism as described herein, or the processor 1435 and the memory 1425 may be otherwise configured to perform or support such operations.
[0269] Fig.15 A flow chart illustrating a method 1500 for supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The UE 115 described herein may be executed. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0270] At 1505, the method may include: receiving information from a second network node indicating that the first network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig. 9 The CG component 925 is used to execute.
[0271] At 1510, the method may include: sending a data message using the set of the plurality of TBs to a second network node based on the information, wherein the data message includes a feedback process ID associated with the set of the plurality of TBs. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig. 9 The PUSCH sending component 930 is used to perform.
[0272] At 1515, the method may include: receiving a DFI corresponding to the feedback process ID from the second network node. The operations of 1515 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig. 9 The feedback component 935 is used to perform.
[0273] Fig.16 A flow chart illustrating a method 1600 for supporting a multi-TB uplink shared channel transmission feedback mechanism according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 6 as well as Figures 11 to 14 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.
[0274] At 1605, the method may include: sending information to the second network node indicating that the second network node will send a data message using a set of multiple TBs, wherein the set of multiple TBs includes a first TB and a second TB. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.13 The CG component 1325 is used to execute.
[0275] At 1610, the method may include: receiving a data message including the set of the plurality of TBs from the second network node based on the information, wherein the data message includes a feedback process ID associated with the set of the plurality of TBs. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig.13 The PUSCH receiving component 1330 is used to perform.
[0276] At 1615, the method may include: sending a DFI corresponding to the feedback process ID to the second network node. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.13 The feedback component 1335 is used to perform.
[0277] The following provides an overview of various aspects of the disclosure:
[0278] Aspect 1: A method for wireless communication at a first network node, comprising: receiving information from a second network node indicating that the first network node will send a data message using several TBs, wherein the several TBs include a first TB and a second TB; sending the data message using the several TBs to the second network node based on the information, wherein the data message includes a feedback process ID associated with the several TBs; and receiving a DFI corresponding to the feedback process ID from the second network node.
[0279] Aspect 2: The method according to aspect 1, wherein receiving the DFI further comprises: receiving a DCI including the DFI, wherein the DFI comprises a first bit corresponding to the feedback process ID, and wherein the first bit indicates a first feedback corresponding exclusively to the first TB.
[0280] Aspect 3: The method according to aspect 2, wherein the DFI is a 16-bit bitmap, the 16-bit bitmap includes the first bit, and the 16-bit bitmap excludes any feedback corresponding to the second TB.
[0281] Aspect 4: A method according to any one of Aspects 1 to 3, wherein receiving the DFI further comprises: receiving a DCI including the DFI, wherein the DFI includes a first bit corresponding to the feedback process ID, and wherein the first bit indicates a first feedback corresponding to the first TB and a second feedback corresponding to the second TB.
[0282] Aspect 5: The method according to aspect 4, wherein the first bit is a first value or a second value, the first value indicates that the first feedback and the second feedback are each a corresponding ACK, and the second value indicates that at least one of the first feedback or the second feedback is a NACK.
[0283] Aspect 6: A method according to any one of Aspects 4 to 5, wherein the DFI includes a number of bits, the number of bits including the first bit, each corresponding bit of the number of bits corresponds to a corresponding feedback process ID of a number of feedback process IDs, the number of feedback process IDs include the feedback process IDs associated with the number of TBs, and the number of feedback process IDs are all different.
[0284] Aspect 7: The method according to any one of aspects 4 to 6, wherein the first bit corresponds to a logical “AND” operation between the first feedback and the second feedback.
[0285] Aspect 8: The method according to any one of aspects 4 to 7, wherein the first bit corresponds to a logical “or” operation between the first feedback and the second feedback.
[0286] Aspect 9: A method according to any one of Aspects 1 to 8, wherein receiving the DFI further comprises: receiving a DCI including the DFI, wherein the DFI includes a number of bits corresponding to the feedback process ID, wherein each corresponding bit of the number of bits indicates corresponding feedback corresponding to each corresponding TB of the number of TBs.
[0287] Aspect 10: The method according to aspect 9, wherein a first bit of the plurality of bits indicates a first feedback corresponding to the first TB, and a second bit of the plurality of bits indicates a second feedback corresponding to the second TB.
[0288] Aspect 11: The method according to aspect 10, wherein the DFI is a 32-bit bitmap including the number of bits, the 32-bit bitmap including the first bit and the second bit.
[0289] Aspect 12: A method according to any one of Aspects 9 to 11, wherein the number of bits includes multiple bit sets, each corresponding bit set in the multiple bit sets corresponds to a corresponding feedback process ID in a number of feedback process IDs, the number of feedback process IDs include the feedback process IDs associated with the number of TBs, and the number of feedback process IDs are all different.
[0290] Aspect 13: A method according to Aspect 12, wherein the multiple bit sets include a first bit set and a second bit set, wherein the first bit set corresponds to the feedback process ID associated with the number of TBs, and wherein the second bit set corresponds to a second feedback process ID, wherein the second feedback process ID is associated with a single TB, wherein the second bit set includes a first bit and a second bit, wherein the first bit indicates feedback corresponding to the single TB associated with the second feedback process ID, and wherein the second bit is a null value or a default value; or the first network node ignores the second bit.
[0291] Aspect 14: A method according to any one of Aspects 12 to 13, wherein the DCI format associated with both the DCI including the DFI and the scheduling DCI has a fixed size, the DCI including the DFI includes a first number of bits, the scheduling DCI includes a second number of bits, and the fixed size is equal to the larger of the first number of bits and the second number of bits.
[0292] Aspect 15: A method according to any one of aspects 12 to 14, wherein if the scheduling DCI includes a number of bits equal to or greater than the total number of bits of the DCI including the multiple bit sets, then the number of bits includes the multiple bit sets.
[0293] Aspect 16: The method according to any one of aspects 1 to 15 further includes: receiving configuration information from the second network node via RRC signaling; and processing the DFI based on the configuration information.
[0294] Aspect 17: The method according to any one of Aspects 1 to 16 further includes: sending UCI associated with the data message, wherein the UCI includes several NDI fields and several RV fields, wherein corresponding NDI fields among the several NDI fields and corresponding RV fields among the several RV fields correspond to corresponding TBs among the several TBs.
[0295] Aspect 18: The method according to aspect 17, further comprising: encoding the UCI to obtain a single UCI message including the plurality of NDI fields and the plurality of RV fields, wherein sending the UCI comprises sending the single UCI message.
[0296] Aspect 19: The method according to aspect 18 further includes: multiplexing the single UCI message on one or more layers associated with a TB among the plurality of TBs, wherein sending the UCI includes sending the single UCI message on the one or more layers.
[0297] Aspect 20: The method according to any one of Aspects 18 to 19 further includes: multiplexing the single UCI message on a first set of one or more layers associated with a first TB among the several TBs and on a second set of one or more layers associated with a second TB among the several TBs, wherein sending the UCI includes sending the single UCI message on the first set of one or more layers and on the second set of one or more layers.
[0298] Aspect 21: The method according to any one of Aspects 17 to 20 further includes: encoding the UCI to obtain several UCI messages, wherein the several UCI messages include a first UCI message and a second UCI message, wherein the first UCI message includes a first NDI field among the several NDI fields and a first RV field among the several RV fields, and wherein the second UCI message includes a second NDI field among the several NDI fields and a second RV field among the several RV fields; and multiplexing the first UCI message on a first set of one or more layers associated with the first TB and multiplexing the second UCI message on a second set of one or more layers associated with the second TB, wherein sending the UCI includes sending the first UCI message on the first set of one or more layers and sending the second UCI message on the second set of one or more layers.
[0299] Aspect 22: A method according to Aspect 21, wherein the first UCI message associated with the first TB among the several UCI messages includes the first RV field, the first NDI field, the first feedback process ID field and the first channel occupancy time sharing information field; and the second UCI message associated with the second TB among the several UCI messages includes the second RV field, the second NDI field, the second feedback process ID field and the second channel occupancy time sharing information field, wherein the second feedback process ID field and the second channel occupancy time sharing information field respectively include the same information as the first feedback process ID field and the first channel occupancy time sharing information field.
[0300] Aspect 23: A method according to any one of Aspects 21 to 22, wherein the first UCI message associated with the first TB among the several UCI messages includes the first RV field, the first NDI field, the first feedback process ID field and the first channel occupancy time sharing information field; and the second UCI message associated with the second TB among the several UCI messages exclusively includes the second RV field and the second NDI field.
[0301] Aspect 24: A method according to any one of Aspects 1 to 23, wherein the data message is a CG-PUSCH transmission or a DG-PUSCH transmission.
[0302] Aspect 25: A method for performing wireless communication at a first network node, comprising: sending information to a second network node indicating that the second network node will send a data message using several TBs, wherein the several TBs include a first TB and a second TB; receiving the data message including the several TBs from the second network node based on the information, wherein the data message includes a feedback process ID associated with the several TBs; and sending a DFI corresponding to the feedback process ID to the second network node.
[0303] Aspect 26: The method according to Aspect 25, wherein sending the DFI further comprises: sending a DCI including the DFI, wherein the DFI includes a first bit corresponding to the feedback process ID, and wherein the first bit indicates a first feedback corresponding exclusively to the first TB.
[0304] Aspect 27: The method according to aspect 26, wherein the DFI is a 16-bit bitmap, the 16-bit bitmap includes the first bit, and the 16-bit bitmap excludes any feedback corresponding to the second TB.
[0305] Aspect 28: A method according to any one of Aspects 25 to 27, wherein sending the DFI further comprises: sending a DCI including the DFI, wherein the DFI includes a first bit corresponding to the feedback process ID, and wherein the first bit indicates a first feedback corresponding to the first TB and a second feedback corresponding to the second TB.
[0306] Aspect 29: The method according to aspect 28, wherein the first bit is a first value or a second value, the first value indicates that the first feedback and the second feedback are each a corresponding ACK, and the second value indicates that at least one of the first feedback or the second feedback is a NACK.
[0307] Aspect 30: A method according to any one of Aspects 28 to 29, wherein the DFI includes a number of bits, the number of bits including the first bit, each corresponding bit of the number of bits corresponds to a corresponding feedback process ID of a number of feedback process IDs, the number of feedback process IDs include the feedback process IDs associated with the number of TBs, and the number of feedback process IDs are all different.
[0308] Aspect 31: The method according to any one of aspects 28 to 30, wherein the first bit corresponds to a logical AND operation between the first feedback and the second feedback.
[0309] Aspect 32: The method according to any one of aspects 28 to 31, wherein the first bit corresponds to a logical OR operation between the first feedback and the second feedback.
[0310] Aspect 33: A method according to any one of Aspects 25 to 32, wherein sending the DFI further comprises: sending a DCI including the DFI, wherein the DFI includes a number of bits corresponding to the feedback process ID, wherein each corresponding bit of the number of bits indicates corresponding feedback corresponding to each corresponding TB of the number of TBs.
[0311] Aspect 34: The method according to aspect 33, wherein a first bit of the number of bits indicates a first feedback corresponding to the first TB, and a second bit of the number of bits indicates a second feedback corresponding to the second TB.
[0312] Aspect 35: The method according to aspect 34, wherein the DFI is a 32-bit bitmap including the number of bits, the 32-bit bitmap including the first bit and the second bit.
[0313] Aspect 36: A method according to any one of Aspects 33 to 35, wherein the number of bits includes multiple bit sets, each corresponding bit set in the multiple bit sets corresponds to a corresponding feedback process ID in a number of feedback process IDs, the number of feedback process IDs include the feedback process IDs associated with the number of TBs, and the number of feedback process IDs are all different.
[0314] Aspect 37: A method according to Aspect 36, wherein the multiple bit sets include a first bit set and a second bit set, wherein the first bit set corresponds to the feedback process ID associated with the number of TBs, and wherein the second bit set corresponds to a second feedback process ID, wherein the second feedback process ID is associated with a single TB, wherein the second bit set includes a first bit and a second bit, wherein the first bit indicates feedback corresponding to the single TB associated with the second feedback process ID, and wherein the second bit is a null value or a default value; or the second network node will ignore the second bit.
[0315] Aspect 38: A method according to any one of Aspects 36 to 37, wherein the DCI format associated with both the DCI including the DFI and the scheduling DCI has a fixed size, the DCI including the DFI includes a first number of bits, the scheduling DCI includes a second number of bits, and the fixed size is equal to the larger of the first number of bits and the second number of bits.
[0316] Aspect 39: A method according to any one of Aspects 36 to 38, wherein if the scheduling DCI includes a number of bits equal to or greater than the total number of bits of the DCI including the multiple bit sets, then the number of bits includes the multiple bit sets.
[0317] Aspect 40: The method according to any one of aspects 25 to 39 further comprises: sending configuration information from the second network node via RRC signaling, wherein the configuration information is associated with the DFI.
[0318] Aspect 41: The method according to any one of Aspects 25 to 40 further includes: receiving UCI associated with the data message, wherein the UCI includes several NDI fields and several RV fields, wherein corresponding NDI fields among the several NDI fields and corresponding RV fields among the several RV fields correspond to corresponding TBs among the several TBs.
[0319] Aspect 42: The method according to aspect 41, wherein the UCI is a single UCI message, the method further comprising: decoding the UCI to obtain the single UCI message including the plurality of NDI fields and the plurality of RV fields.
[0320] Aspect 43: The method according to aspect 42 further comprises: demultiplexing the single UCI message from one or more layers associated with a TB in the plurality of TBs, wherein receiving the UCI comprises receiving the single UCI message on the one or more layers.
[0321] Aspect 44: The method according to any one of Aspects 42 to 43 further includes: demultiplexing the single UCI message from a first set of one or more layers associated with a first TB among the several TBs and from a second set of one or more layers associated with a second TB among the several TBs, wherein receiving the UCI includes receiving the single UCI message on the first set of one or more layers and on the second set of one or more layers.
[0322] Aspect 45: A method according to any one of Aspects 41 to 44, wherein the UCI is several UCI messages, and the method further includes: decoding the UCI to obtain the several UCI messages, wherein the several UCI messages include a first UCI message and a second UCI message, wherein the first UCI message includes a first NDI field among the several NDI fields and a first RV field among the several RV fields, and wherein the second UCI message includes a second NDI field among the several NDI fields and a second RV field among the several RV fields; and demultiplexing the first UCI message on a first set of one or more layers associated with the first TB and demultiplexing the second UCI message on a second set of one or more layers associated with the second TB, wherein receiving the UCI includes receiving the first UCI message on the first set of one or more layers and receiving the second UCI message on the second set of one or more layers.
[0323] Aspect 46: A method according to Aspect 45, wherein the first UCI message associated with the first TB among the several UCI messages includes the first RV field, the first NDI field, the first feedback process ID field and the first channel occupancy time sharing information field; and the second UCI message associated with the second TB among the several UCI messages includes the second RV field, the second NDI field, the second feedback process ID field and the second channel occupancy time sharing information field, wherein the second feedback process ID field and the second channel occupancy time sharing information field respectively include the same information as the first feedback process ID field and the first channel occupancy time sharing information field.
[0324] Aspect 47: A method according to any one of Aspects 45 to 46, wherein the first UCI message associated with the first TB among the several UCI messages includes a first RV field, a first NDI field, a first feedback process ID field and a first channel occupancy time sharing information field; and the second UCI message associated with the second TB among the several UCI messages exclusively includes the second RV field and the second NDI field.
[0325] Aspect 48: A method according to any one of aspects 25 to 47, wherein the data message is a CG-PUSCH transmission or a DG-PUSCH transmission.
[0326] Aspect 49: An apparatus for performing wireless communications at a first network node, comprising: at least one processor; a memory coupled to the at least one processor; and instructions stored in the memory and executable by the at least one processor to cause the apparatus to perform a method according to any one of Aspects 1 to 24.
[0327] Aspect 50: An apparatus for wireless communication at a first network node, comprising: at least one means for performing a method according to any one of aspects 1 to 24.
[0328] Aspect 51: A non-transitory computer-readable medium storing code for wireless communication at a first network node, the code comprising instructions executable by at least one processor to perform the method according to any one of aspects 1 to 24.
[0329] Aspect 52: A first network node for wireless communication, comprising: a memory; and at least one processor, the at least one processor coupled to the memory, wherein the at least one processor is configured to perform the method according to any one of aspects 1 to 24.
[0330] Aspect 53: An apparatus for performing wireless communications at a first network node, comprising: at least one processor; a memory coupled to the at least one processor; and instructions stored in the memory and executable by the at least one processor to cause the apparatus to perform a method according to any one of Aspects 25 to 48.
[0331] Aspect 54: An apparatus for wireless communication at a first network node, comprising: at least one means for performing a method according to any one of aspects 25 to 48.
[0332] Aspect 55: A non-transitory computer-readable medium storing code for wireless communication at a first network node, the code comprising instructions executable by at least one processor to perform the method according to any one of aspects 25 to 48.
[0333] Aspect 56: A first network node for wireless communication, comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to perform the method according to any one of aspects 25 to 48.
[0334] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.
[0335] Although aspects of LTE, LTE-A, LTE-APro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-APro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-APro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.
[0336] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.
[0337] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0338] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of the present disclosure and claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.
[0339] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes to transfer computer program from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
[0340] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items preceded by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of 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). In addition, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based on at least A" unless specifically stated differently.
[0341] The term "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), etc. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
[0342] In the drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number to distinguish between the similar components. If only the first reference number is used in the specification, the description may apply to any of the similar components having the same first reference number, regardless of the second or other subsequent reference numbers.
[0343] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The terms "aspect" or "example" used herein mean "used as an aspect, example, instance, or illustration," rather than "preferred" or "having advantages over other aspects." The specific embodiments include specific details for providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.
[0344] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present 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 first network node for wireless communication, include: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving information from a second network node indicating that the first network node will send a data message using a number of transport blocks (TBs), wherein the number of TBs includes a first TB and a second TB; sending the data message using the number of TBs to the second network node based on the information, wherein the data message includes a feedback process identifier (ID) associated with the number of TBs; and Downlink feedback information (DFI) corresponding to the feedback process ID is received from the second network node.
2. The first network node according to claim 1, wherein in order to receive the DFI, the at least one processor is configured to: Downlink control information (DCI) including the DFI is received, wherein the DFI includes a first bit corresponding to the feedback process ID, and wherein the first bit indicates a first feedback corresponding exclusively to the first TB. 3 . The first network node of claim 2 , wherein the DFI is a 16-bit bitmap, wherein the 16-bit bitmap includes the first bit, and wherein the 16-bit bitmap excludes any feedback corresponding to the second TB.
4. The first network node of claim 1 , wherein to receive the DFI, the at least one processor is configured to: Downlink control information (DCI) including the DFI is received, wherein the DFI includes a first bit corresponding to the feedback process ID, and wherein the first bit indicates a first feedback corresponding to the first TB and a second feedback corresponding to the second TB.
5. The first network node according to claim 4, wherein the first bit is a first value or a second value, wherein the first value indicates that the first feedback and the second feedback are each a respective acknowledgment (ACK), and wherein the second value indicates that at least one of the first feedback or the second feedback is a negative acknowledgment (NACK).
6. The first network node of claim 4, wherein the DFI comprises a plurality of bits, wherein the plurality of bits comprises the first bit, wherein each respective bit of the plurality of bits corresponds to a respective feedback process ID of a plurality of feedback process IDs, wherein the plurality of feedback process IDs comprises the feedback process IDs associated with the plurality of TBs, and wherein the plurality of feedback process IDs are all different.
7. The first network node according to claim 4, wherein the first bit corresponds to a logical AND operation between the first feedback and the second feedback.
8. The first network node according to claim 4, wherein the first bit corresponds to a logical OR operation between the first feedback and the second feedback.
9. The first network node of claim 1 , wherein to receive the DFI, the at least one processor is configured to: Downlink control information (DCI) including the DFI is received, wherein the DFI includes a number of bits corresponding to the feedback process ID, wherein each respective bit of the number of bits indicates respective feedback corresponding to each respective TB of the number of TBs. 10 . The first network node of claim 9 , wherein a first bit of the plurality of bits indicates a first feedback corresponding to the first TB, and a second bit of the plurality of bits indicates a second feedback corresponding to the second TB.
11. The first network node of claim 10, wherein the DFI is a 32-bit bitmap comprising the number of bits, wherein the 32-bit bitmap comprises the first bit and the second bit.
12. The first network node of claim 9, wherein the number of bits comprises a plurality of bit sets, wherein each respective bit set in the plurality of bit sets corresponds to a respective feedback process ID in a plurality of feedback process IDs, wherein the plurality of feedback process IDs comprises the feedback process ID associated with the plurality of TBs, and wherein the plurality of feedback process IDs are all different.
13. The first network node according to claim 12, wherein the plurality of bit sets include a first bit set and a second bit set, wherein the first bit set corresponds to the feedback process ID associated with the plurality of TBs, and wherein the second bit set corresponds to a second feedback process ID, wherein the second feedback process ID is associated with a single TB, wherein the second bit set includes a first bit and a second bit, wherein the first bit indicates feedback corresponding to the single TB associated with the second feedback process ID, and in: The second bit is a null or default value; or The at least one processor is configured to ignore the second bit.
14. The first network node of claim 12, wherein a DCI format associated with both the DCI including the DFI and a scheduling DCI has a fixed size, wherein the DCI including the DFI includes a first number of bits, wherein the scheduling DCI includes a second number of bits, and wherein the fixed size is equal to the larger of the first number of bits and the second number of bits.
15. The first network node of claim 12, wherein the number of bits comprises the multiple sets of bits if the scheduling DCI comprises a number of bits that is equal to or greater than a total number of bits of the DCI comprising the multiple sets of bits.
16. The first network node of claim 1, wherein the at least one processor is configured to: receiving configuration information from the second network node via radio resource control (RRC) signaling; and The DFI is processed based on the configuration information.
17. The first network node of claim 1, wherein the at least one processor is configured to: Uplink control information (UCI) associated with the data message is sent, wherein the UCI includes several new data indicator (NDI) fields and several redundancy version (RV) fields, wherein corresponding NDI fields in the several NDI fields and corresponding RV fields in the several RV fields correspond to corresponding TBs in the several TBs.
18. The first network node of claim 17, wherein the at least one processor is configured to: The UCI is encoded to obtain a single UCI message including the plurality of NDI fields and the plurality of RV fields, wherein to transmit the UCI, the at least one processor is configured to transmit the single UCI message.
19. The first network node according to claim 18, wherein the at least one processor is configured to: The single UCI message is multiplexed on one or more layers associated with a TB among the plurality of TBs, wherein to send the UCI, the at least one processor is further configured to send the single UCI message on the one or more layers.
20. The first network node of claim 18, wherein the at least one processor is configured to: The single UCI message is multiplexed on a first set of one or more layers associated with the first TB among the plurality of TBs and on a second set of one or more layers associated with the second TB among the plurality of TBs, wherein in order to send the UCI, the at least one processor is further configured to send the single UCI message on the first set of one or more layers and on the second set of one or more layers.
21. The first network node of claim 17, wherein the at least one processor is configured to: encoding the UCI to obtain a plurality of UCI messages, wherein the plurality of UCI messages include a first UCI message and a second UCI message, wherein the first UCI message includes a first NDI field among the plurality of NDI fields and a first RV field among the plurality of RV fields, and wherein the second UCI message includes a second NDI field among the plurality of NDI fields and a second RV field among the plurality of RV fields; and The first UCI message is multiplexed on a first set of one or more layers associated with the first TB and the second UCI message is multiplexed on a second set of one or more layers associated with the second TB, wherein, to send UCI, the at least one processor is configured to send the first UCI message on the first set of one or more layers and send the second UCI message on the second set of one or more layers.
22. The first network node according to claim 21, in: The first UCI message associated with the first TB among the plurality of UCI messages includes the first RV field, the first NDI field, a first feedback process ID field, and a first channel occupancy time sharing information field; and The second UCI message associated with the second TB among the several UCI messages includes the second RV field, the second NDI field, the second feedback process ID field, and the second channel occupancy time sharing information field, wherein the second feedback process ID field and the second channel occupancy time sharing information field respectively include the same information as the first feedback process ID field and the first channel occupancy time sharing information field.
23. The first network node according to claim 21, in: The first UCI message associated with the first TB among the plurality of UCI messages includes the first RV field, the first NDI field, a first feedback process ID field, and a first channel occupancy time sharing information field; and The second UCI message associated with the second TB among the plurality of UCI messages exclusively includes the second RV field and the second NDI field.
24. The first network node of claim 1, wherein the data message is a Configured Grant Physical Uplink Shared Channel (CG-PUSCH) transmission or a Dynamic Grant Physical Uplink Shared Channel (DG-PUSCH) transmission.
25. A first network node for wireless communication, include: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: sending information to a second network node indicating that the second network node will send a data message using a number of transport blocks (TBs), wherein the number of TBs includes a first TB and a second TB; receiving the data message including the number of TBs from the second network node based on the information, wherein the data message includes a feedback process identifier (ID) associated with the number of TBs; and Downlink Feedback Information (DFI) corresponding to the feedback process ID is sent to the second network node.
26. The first network node of claim 25, wherein to send the DFI, the at least one processor is configured to: Downlink control information (DCI) including the DFI is transmitted, wherein the DFI includes a first bit corresponding to the feedback process ID, and wherein the first bit indicates a first feedback corresponding exclusively to the first TB.
27. The first network node of claim 26, wherein the DFI is a 16-bit bitmap, wherein the 16-bit bitmap includes the first bit, and wherein the 16-bit bitmap excludes any feedback corresponding to the second TB.
28. The first network node of claim 25, wherein to send the DFI, the at least one processor is configured to: A DCI including the DFI is transmitted, wherein the DFI includes a first bit corresponding to the feedback process ID, and wherein the first bit indicates a first feedback corresponding to the first TB and a second feedback corresponding to the second TB.
29. The first network node according to claim 28, wherein the first bit is a first value or a second value, wherein the first value indicates that the first feedback and the second feedback are each a respective acknowledgment (ACK), and wherein the second value indicates that at least one of the first feedback or the second feedback is a negative acknowledgment (NACK).
30. The first network node of claim 28, wherein the DFI comprises a number of bits, wherein the number of bits comprises the first bit, wherein each respective bit of the number of bits corresponds to a respective feedback process ID of a number of feedback process IDs, wherein the number of feedback process IDs comprises the feedback process IDs associated with the number of TBs, and wherein the number of feedback process IDs are all different.
31. The first network node of claim 28, wherein the first bit corresponds to a logical AND operation between the first feedback and the second feedback.
32. The first network node of claim 28, wherein the first bit corresponds to a logical OR operation between the first feedback and the second feedback.
33. The first network node of claim 25, wherein to send the DFI, the at least one processor is configured to: A DCI including the DFI is transmitted, wherein the DFI includes a number of bits corresponding to the feedback process ID, wherein each respective bit of the number of bits indicates respective feedback corresponding to each respective TB of the number of TBs.
34. The first network node of claim 33, wherein a first bit of the number of bits indicates a first feedback corresponding to the first TB, and a second bit of the number of bits indicates a second feedback corresponding to the second TB.
35. The first network node of claim 34, wherein the DFI is a 32-bit bitmap comprising the number of bits, wherein the 32-bit bitmap comprises the first bit and the second bit.
36. The first network node of claim 33, wherein the number of bits comprises a plurality of bit sets, wherein each respective bit set in the plurality of bit sets corresponds to a respective feedback process ID in a number of feedback process IDs, wherein the number of feedback process IDs comprises the feedback process ID associated with the number of TBs, and wherein the number of feedback process IDs are all different.
37. The first network node of claim 36, wherein the plurality of bit sets include a first bit set and a second bit set, wherein the first bit set corresponds to the feedback process ID associated with the plurality of TBs, and wherein the second bit set corresponds to a second feedback process ID, wherein the second feedback process ID is associated with a single TB, wherein the second bit set includes a first bit and a second bit, wherein the first bit indicates feedback corresponding to the single TB associated with the second feedback process ID, and in: The second bit is a null or default value; or The at least one processor is configured to cause the second network node to ignore the second bit.
38. A first network node according to claim 36, wherein the DCI format associated with both the DCI including the DFI and the scheduling DCI has a fixed size, wherein the DCI including the DFI includes a first number of bits, wherein the scheduling DCI includes a second number of bits, and wherein the fixed size is equal to the larger of the first number of bits and the second number of bits.
39. The first network node of claim 36, wherein the number of bits comprises the multiple sets of bits if the scheduling DCI comprises a number of bits that is equal to or greater than a total number of bits of the DCI comprising the multiple sets of bits.
40. The first network node of claim 25, wherein the at least one processor is configured to: Configuration information is sent from the second network node via radio resource control (RRC) signaling, wherein the configuration information is associated with the DFI.
41. The first network node of claim 25, wherein the at least one processor is configured to: Uplink control information (UCI) associated with the data message is received, wherein the UCI includes a plurality of new data indicator (NDI) fields and a plurality of redundancy version (RV) fields, wherein corresponding NDI fields in the plurality of NDI fields and corresponding RV fields in the plurality of RV fields correspond to corresponding TBs in the plurality of TBs.
42. The first network node of claim 41 , wherein the UCI is a single UCI message, and wherein the at least one processor is configured to: The UCI is decoded to obtain the single UCI message including the NDI fields and the RV fields.
43. The first network node of claim 42, wherein the at least one processor is configured to: The single UCI message is demultiplexed from one or more layers associated with a TB among the plurality of TBs, wherein to receive the UCI, the at least one processor is further configured to receive the single UCI message on the one or more layers.
44. The first network node of claim 42, wherein the at least one processor is configured to: The single UCI message is demultiplexed from a first set of one or more layers associated with the first TB among the plurality of TBs and from a second set of one or more layers associated with the second TB among the plurality of TBs, wherein in order to receive the UCI, the at least one processor is further configured to receive the single UCI message on the first set of one or more layers and on the second set of one or more layers.
45. The first network node of claim 41 , wherein the UCI is a plurality of UCI messages, and wherein the at least one processor is configured to: decoding the UCI to obtain the plurality of UCI messages, wherein the plurality of UCI messages include a first UCI message and a second UCI message, wherein the first UCI message includes a first NDI field among the plurality of NDI fields and a first RV field among the plurality of RV fields, and wherein the second UCI message includes a second NDI field among the plurality of NDI fields and a second RV field among the plurality of RV fields; and The first UCI message is demultiplexed on a first set of one or more layers associated with the first TB and the second UCI message is demultiplexed on a second set of one or more layers associated with the second TB, wherein, in order to receive UCI, the at least one processor is configured to receive the first UCI message on the first set of one or more layers and receive the second UCI message on the second set of one or more layers.
46. The first network node according to claim 45, in: The first UCI message associated with the first TB among the plurality of UCI messages includes the first RV field, the first NDI field, a first feedback process ID field, and a first channel occupancy time sharing information field; and The second UCI message associated with the second TB among the several UCI messages includes the second RV field, the second NDI field, the second feedback process ID field, and the second channel occupancy time sharing information field, wherein the second feedback process ID field and the second channel occupancy time sharing information field respectively include the same information as the first feedback process ID field and the first channel occupancy time sharing information field.
47. The first network node according to claim 45, in: The first UCI message associated with the first TB among the plurality of UCI messages includes the first RV field, the first NDI field, a first feedback process ID field, and a first channel occupancy time sharing information field; and The second UCI message associated with the second TB among the plurality of UCI messages exclusively includes the second RV field and the second NDI field.
48. The first network node of claim 25, wherein the data message is a Configured Grant Physical Uplink Shared Channel (CG-PUSCH) transmission or a Dynamic Grant Physical Uplink Shared Channel (DG-PUSCH) transmission.
Citation Information
Cited By
(RE) transmission mechanisms for physical uplink shared channel transmissions in wireless communication networks
WO2026137572A1
