RELIABILITY IMPROVEMENT SIGNALING SOLUTION FOR UPLINK TRANSMISSION.
Patent Information
- Authority / Receiving Office
- MX · MX
- Patent Type
- Patents
- Current Assignee / Owner
- ZTE CORP
- Filing Date
- 2022-07-21
- Publication Date
- 2026-06-12
Smart Images

Figure MX434873B0
Abstract
Description
RELIABILITY IMPROVEMENT SIGNALING SOLUTION FOR UPLINK TRANSMISSION FIELD OF INVENTION The disclosure generally refers to wireless communications, which include but are not limited to systems and methods for improving the reliability of uplink transmissions. BACKGROUND OF THE INVENTION The Third Generation Partnership Project (3GPP) standards organization is currently in the process of specifying a new radio interface called 5G New Radio (5G NR), as well as a Next Generation Packet Core Network (NG-CN or NGC). In a wireless communication system (e.g., a 5G NR wireless communication system), blocking can prevent, disrupt, and / or impact the transmission and / or exchange of signals, messages, data, and / or information. Therefore, blocking can affect and / or impact the reliability of uplink / downlink transmissions. BRIEF DESCRIPTION OF THE INVENTION The example embodiments disclosed herein relate to solving problems related to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent with reference to the following detailed description when considered in conjunction with the accompanying figures. According to various embodiments, examples of computer systems, methods, devices, and software products are disclosed herein. However, it is understood that these embodiments are presented by way of example and are not exhaustive, and it will be evident to those skilled in the art who read this disclosure that various modifications may be made to the embodiments disclosed as long as they remain within the scope of this disclosure. At least one aspect refers to a computer-readable system, method, apparatus, or medium. A wireless communication device can receive a scheduling lease for an uplink channel from a wireless communication node. The wireless communication device can transmit the uplink channel to the wireless communication node. The wireless communication device can transmit a transmission block indication to the wireless communication node. The transmission block indication can be used to determine a transmission block size (TBS) for the uplink channel. In some modes, the scheduling lease may include downlink control information (DCI) or a higher-layer configuration for scheduling the uplink channel. In some modes, the transmission block indication may show whether the uplink channel's time-based signal (TBS) is determined according to the scheduling lease information. In some modes, the transmission block indication may show whether the uplink channel's TBS is determined according to information in a lease associated with the scheduling lease. In some modes, the wireless communication device may use the scheduling lease and the lease associated with it to schedule repetitive uplink channel transmissions or to schedule repetitive transmissions of the same data block. In some modes, the scheduling grant and the grant associated with it can be configured, activated, or indicated by Transmit Independent Configuration Indicator (TCI) states. In some modes, the scheduling grant and the grant associated with it can be from different Control Resource Sets (CORESETs) or can be associated with different coresetPoollndex-r16 parameter values. In some modes, the scheduling grant and the grant associated with it can indicate the same Hybrid Auto Repeat Request (HARQ) processing number or identifier, or the same New Number Indicator (NDI). In some modes, the wireless communication device can receive a higher-layer configuration.In some modes, the wireless communication device can transmit the transmission block indication on the uplink channel to the wireless communication node, according to the upper-layer configuration. In some modes, the upper-layer configuration can be configured by CORESET, by search space (SS), or by CORESET grouping. In some modes, the wireless communication device can transmit the transmit block indication to the wireless communication node indication if an uplink shared channel indicator (UL-SCH) has a value of 1. In some modes, the wireless communication device can transmit the transmit block indication on the uplink channel using at least one of the uplink control information (UCI) procedures on a physical uplink shared channel (PUSCH). The UCI procedures on a PUSCH may include code block segmentation, cyclic redundancy check (CRC) junction, channel coding, rate matching, code block concatenation, or bit multiplexing. The UCI may include at least one hybrid auto-repeat request acknowledgment (HARQ-ACK) information. ML / t / ZUZZ / U / 3100 of channel status (CSI) part 1 or CSI part 2. In some modes, the offset values defined for the wireless communication device to determine a number of resources for multiplexing the uplink centroid information (UCI) on the uplink channel can be used to determine a number of resources for multiplexing the transmit block indication on the uplink channel. In some modes, the offset values defined for the wireless communication device to determine a number of resources for multiplexing the transmit block indication information on the uplink channel can be configured through the upper-layer configuration or specified by scheduling. In some modes, one or more bits of the transmit block indication can be arranged adjacent to a sequence of uplink control information (UCI) bits.In some modes, one or more coded bits for transmission block indication may be arranged adjacent to the coded bits for uplink control information (UCI). In some modes, a frequency hop of the uplink channel, modulated resource elements (RE) for the transmission block indication, can be mapped after a first symbol carrying a demodulation reference signal (DMRS). In some modes, a frequency hop of the uplink channel, modulated resource elements (RE) for the transmission block indication, can be mapped starting from a first symbol of the uplink channel that does not carry a DMRS. At least one aspect refers to a computer-readable system, method, apparatus, or medium. A wireless communication node can transmit a scheduling lease for an uplink channel to a wireless communication device. The wireless communication node can receive the uplink channel from the wireless communication device. The wireless communication node can receive a transmit block indication to determine a transmit block size (TBS) for the uplink channel from the wireless communication device. In some modes, the scheduling grant may include downlink control information (DCI) or a higher-layer configuration for scheduling the uplink channel. In some modes, the transmission block indication may indicate whether the uplink channel's TBS is determined according to the scheduling grant information. In some modes, the transmission block indication may indicate whether the uplink channel's TBS is determined according to information from a grant associated with the scheduling grant. In some modes, the scheduling of repetitive uplink channel transmissions or the ML / t / ZUZZ / U / 3103 Programming repetitive transmissions of the same block of data may include using the programming grant and the grant associated with the programming grant. In some modes, the scheduling lease and the lease associated with it can be configured, activated, or indicated by Transmit Independent Configuration Indicator (TCI) states. In some modes, the scheduling lease and the lease associated with it can be from different Control Resource Sets (CORESETs) or can be associated with different coresetPoollndex-r16 parameter values. In some modes, the scheduling lease and the lease associated with it can indicate the same Hybrid Auto Repeat Request (HARQ) processing number or identifier, or the same New Number Indicator (NDI). In some modes, the wireless communication node can transmit a higher-layer configuration.In some modes, the wireless communication node can receive the transmission block indication on the uplink channel from the wireless communication device, according to the upper-layer configuration. In some modes, the upper-layer configuration can be configured either by CORESET, by search space (SS), or by CORESET grouping. In some modes, the wireless communication node can receive the transmit block indication from the wireless communication device if an uplink shared channel indicator (UL-SCH) has a value of 1. In some modes, the wireless communication node can receive the receive block indication on the uplink channel using at least one of the uplink control information (UCI) procedures on a physical uplink shared channel (PUSCH). The UCI procedures on a PUSCH may include code block segmentation, cyclic redundancy check (CRC) junction, channel coding, rate matching, code block concatenation, or bit multiplexing. The UCI may include at least one hybrid automatic repeat request acknowledgment (HARQ-ACK), channel status information (CSI) Part 1, or CSI Part 2. In some modes, the offset values defined for the wireless communication device to determine a number of resources for multiplexing uplink control information (UCI) on the uplink channel can be used to determine a number of resources for multiplexing the transmit block indication on the uplink channel. In some modes, the offset values defined for the wireless communication device to determine a number of resources for multiplexing the transmit block indication information can also be used to determine a number of resources for multiplexing the transmit block indication information. MA / t / ZUZZ / U / 3100 uplink channel transmission can be configured through the upper layer configuration or indicated by scheduling. In some modes, one or more bits of the transmission block indication can be placed adjacent to a sequence of uplink control information (UCI) bits. In some modes, one or more bits encoded for the transmission block indication can be placed adjacent to the bits encoded for the uplink control information (UCI). In some modes, a frequency hop of the uplink channel, modulated resource elements (RE) for the transmission block indication, can be mapped after a first symbol carrying a demodulation reference signal (DMRS). In some modes, a frequency hop of the uplink channel, modulated resource elements (RE) for the transmission block indication, can be mapped starting from a first symbol of the uplink channel that does not carry a DMRS. BRIEF DESCRIPTION OF THE FIGURES Several example embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and simply represent example embodiments of the present solution to aid the reader's understanding. Therefore, the drawings should not be considered as limiting the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale. Figure 1 illustrates an example cellular communication network in which techniques disclosed herein can be implemented, according to one modality of this disclosure; Figure 2 illustrates a block diagram of an example base station and user equipment device, in accordance with some modalities of this disclosure; Figures 3-5 illustrate various approaches to transmitting downlink data using multiple transmit-receive points (MTRP) and one or more scheduling leases, in accordance with some modalities of this disclosure; Figure 6 illustrates example approaches for transmitting uplink data using MTRP and two or more scheduling grants, in accordance with some modalities of this disclosure; and Figure 7 illustrates a flowchart of an example method for improving the reliability of uplink transmissions using a signaling solution, in accordance with one modality of this disclosure. ML / t / ZUZZ / U í 0103 DETAILED DESCRIPTION OF THE INVENTION Several example embodiments of the present solution are described below with reference to the accompanying figures to enable a person skilled in the art to implement and use the present solution. As would be evident to those skilled in the art after reading this disclosure, various changes or modifications can be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the example embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein are merely illustrative approaches. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged as long as they remain within the scope of the present solution.Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present solution is not limited to the specific order or hierarchy presented unless expressly stated otherwise. ML / t / ZUZZ / U í 0103 The following acronyms are used throughout this disclosure: Acronym Full Name 3GPP Third Generation Partnership Project 5G 5th Generation Mobile Networks 5G-AN 5G Access Network 5G gNB Next Generation NodeB 5G-GUTI 5G- Globally Unique Temporary UE Identity AF Application Function AMF Access and Mobility Management Function AN Access Network ARP Assignment and Retention Priority CA Handset Aggregation CM Connected Mode CMR Channel Measurement Resource CSI Channel Status Information CQI Channel Quality Indicator CSI-RS Channel Status Information Reference Signal CRI CSI-RS Resource Indicator CSS Common Search Space DAI Downlink Allocation Index DCI Downlink Control Information DL Downlink DN Data Network DNN Data Network Name ETSI European Telecommunication Standardization Institute FR Frequency Range GBR Guaranteed Bit Rate GFBR Guaranteed Flow Bit Rate HARQ Hybrid Auto Repeat Request MAC-CE Media Access Control (MAC) Control Element (CE) MCS Modulation and Coding Scheme MBR Maximum Bit Rate MFBR Maximum Flow Bit Rate NAS Non-Access Stratum NF Network Function NG-RAN Next Generation Node Radio Access Node NR New Radio NZP Non-Zero Power OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access PCF Policy Control Function PDCCH Downlink Control Physical Channel PDSCH Downlink Shared Physical Channel PDU Packet Data Unit PUCCH Uplink Control Physical Channel PMIPrecoding Matrix Indicator PPCH Broadcast Physical Channel PRI Resource Indicator PUCCH QoS Quality of Service RAN Radio Access Network CP Radio Access Network Control Plane RATA Radio Access Technology RBG Resource Block Group RRC Radio Resource Control ML / IZ / ZUZZ / U ï DI OO RV Redundant version SM NAS Session management accessless layer SMF Session management function SRS Polling reference signal SS Synchronization signal SSB SS / PBCH block TB Transport block TC Transmit configuration TCI Transmit configuration indicator TRP Transmit / receive point UCI Uplink control information UDM Unified data management UDR Unified data repository UE User equipment UL Uplink UPF User plane function USS UE-specific search space Mobile communication environment and technology Figure 1 illustrates an example wireless communication network, and / or system, 100 in which techniques disclosed herein may be implemented according to one embodiment of this disclosure. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as “network 100”. This example network 100 includes a base station 102 (hereafter referred to as “BS 102”; also called a wireless communication node) and a user equipment device 104 (hereafter referred to as “UE 104”; also called a wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) and a cell grouping 126, 130, 132, 134, 136, 138 and 140 that overlap a geographical area 101.In Figure 1, BS 102 and UE 104 are contained within a respective geographical boundary of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users. For example, BS 102 can operate on an allocated channel transmission bandwidth to provide adequate coverage for UE 104. BS 102 and UE 104 can communicate via a downlink radio frame 118 and an uplink radio frame 124, respectively. Each 118 / 124 radio frame can be further divided into 120 / 127 subframes, which can include 122 / 128 data symbols. In this disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes" in general, which can implement the methods disclosed herein. These communication nodes can be capable of wireless and / or wired communication, according to various modalities of this solution. Figure 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some embodiments of the present solution. System 200 may include components and elements configured to support known or conventional operating characteristics that need not be described in detail herein. In one illustrative embodiment, System 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 in Figure 1, as described above. The 200 system generally includes a base station 202 (hereinafter referred to as “BS 202”) and a user equipment device 204 (hereinafter referred to as “UE 204”). The BS 202 includes a BS transceiver module (base station) 210, an antenna BS 212, a processor module BS 214, a memory module BS 216, and a network communication module 218, each module coupled and interconnected as required via a data communication bus 220. The UE 204 includes a UE transceiver module (user equipment) 230, an antenna UE 232, a memory module UE 234, and a processor module UE 236, each module coupled and interconnected as required via a data communication bus 240. The BS 202 communicates with the UE 204 at through a 250 communication channel, which may be any wireless channel or other suitable means for data transmission as described herein. As would be understood by persons skilled in the art, the 200 system may also include any number of modules other than those shown in Figure 2. Persons skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether this functionality is implemented as hardware, firmware, or software may depend on the ML / t / ZUZZ / U ZOIOO particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement this functionality in a manner appropriate for their particular application, but such implementation decisions should not be interpreted as limiting the scope of this disclosure. According to some embodiments, the UE 230 transceiver may be referred to herein as an uplink transceiver 230 comprising a radio frequency (RF) transmitter and an RF receiver, each comprising circuitry that couples to the antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in temporary duplex mode. Similarly, according to some embodiments, the BS 210 transceiver may be referred to herein as a downlink transceiver 210 comprising an RF transmitter and an RF receiver, each comprising circuitry that couples to the antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in temporary duplex mode.The operations of the two transceiver modules 210 and 230 can be time-coordinated so that the uplink receiver circuitry couples to the uplink antenna 232 for receiving transmissions over the wireless transmission link 250 at the same time that the downlink transmitter couples to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 can be time-coordinated so that the downlink receiver couples to the downlink antenna 212 for receiving transmissions over the wireless transmission link 250 at the same time that the uplink transmitter couples to the uplink antenna 232. In some modes, there is time-closure synchronization with a minimal guard time between duplex direction changes. The UE 230 transceiver and the 210 base station transceiver are configured to communicate over the 250 wireless data communication link and cooperate with a suitably configured 212 / 232 RF antenna arrangement that can support a particular wireless communication protocol and modulation scheme. In some illustrative configurations, the UE 210 transceiver and the 210 base station transceiver are configured to support industry standards such as Long-Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that this disclosure is not necessarily limited in application to a particular standard and associated protocols. Instead, the UE 230 transceiver and the 210 base station transceiver can be configured to support alternative wireless data communication protocols or Additional ML / t / ZUZZ / U / 3103, which include future standards or variations thereof. Depending on the configuration, the BS 202 can be an evolved node B (eNB), a service eNB, a target eNB, a femtostation, or a picostation, for example. In some configurations, the UE 204 can be represented in various types of user devices such as a mobile phone, a smartphone, a personal digital assistant (PDA), a tablet, a laptop, a portable computing device, etc. The processor modules 214 and 236 can be implemented or realized using a general-purpose processor, content-addressable memory, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein.Thus, a processor can be realized as a microprocessor, a controller, a microcontroller, a state machine, or similar. A processor can also be implemented as a combination of computing devices, for example, a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors together with a digital signal processor core, or any other such configuration. Furthermore, the steps of a method or algorithm described in relation to the modalities disclosed herein may be incorporated directly into hardware, firmware, a software module executed by processor modules 214 and 236, respectively, or any practical combination thereof. Memory modules 216 and 234 may be implemented as RAM, flash memory, ROM, EPROM, EEPROM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to processor modules 210 and 230, respectively, such that processor modules 210 and 230 may read information from, and write information to, memory modules 216 and 234, respectively. Memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230.In some configurations, memory modules 216 and 234 may each include a cache to store temporary variables or other immediate information during the execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory to store instructions to be executed by processor modules 210 and 230, respectively. The network communication module 218 generally represents the hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable ML / t / ZUZZ / U / 3100 bidirectional communication between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communication module 218 can be configured to support Internet or WiMAX traffic. In a typical implementation, without limitation, the network communication module 218 provides an 802.3 Ethernet interface so that the base station transceiver 210 can communicate with a conventional Ethernet-based computer network. In this way, the network communication module 218 can include a physical interface for connection to the computer network (e.g., a mobile switching center (MSC)). The terms “configured by,” “configured for,” and combinations thereof, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., which is physically constructed, programmed, formatted and / or arranged to perform the specified operation or function. The Open Systems Interconnection (OSI) model (referred to herein as the “Open Systems Interconnection Model”) is a conceptual and logical design that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems. The model is divided into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below. The OSI model also defines a logical network and effectively describes computer packet transfer using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some configurations, the first layer may be a physical layer. In some configurations, the second layer may be a media access control (MAC) layer.In some configurations, a third layer may be a radio link control (RLC) layer. In some configurations, a fourth layer may be a packet data convergence protocol (PDCP) layer. In some configurations, a fifth layer may be a radio resource control (RRC) layer. In some configurations, a sixth layer may be a non-accessible layer (NAS) or an Internet protocol (IP) layer, and the seventh layer is the other layer. Systems and methods for improving the reliability of uplink transmissions In a wireless communication system, two or more uplink channel programming leases (e.g., downlink control information (DCI), upper-layer configurations, and / or other information) can activate, trigger, and / or indicate transmission on two or more uplink channels (e.g., shared physical uplink channel (PUSCH) and / or other uplink channels). For example, two DCIs can trigger the transmission of two respective PUSCHs. The two or more uplink channels can carry and / or include the same data block and / or separate data blocks. If two or more scheduling leases trigger the transmission of the same data block, the uplink channels can carry the same data block using the same data block size. A wireless communication node (e.g., a ground terminal, base station, gNB, eNB, transmit-receive point (TRP), or service node) can receive and / or obtain the same data block to perform a smooth merge (or any other method that combines or integrates data from multiple transmissions to minimize incomplete information and / or errors).If two or more scheduling concessions cause the transmission / scheduling of separate / distinct data blocks, the uplink channels can carry / include the separate / distinct data blocks using separate / distinct data block sizes. In some modes, a wireless communication device (e.g., a UE, a terminal, or a served node) may receive at least one (but less than the full amount) of two or more scheduling leases sent / transmitted by the wireless communication node. For example, a block (e.g., blockage by a physical entity, signal interference, and / or other blocking sources) may cause the wireless communication device to receive only one of two DCIs transmitted by the wireless communication node. In some modes, the wireless communication node may receive at least one (but less than the full amount) of two or more uplink channels sent / transmitted by the wireless communication device. For example, a blockage may cause the wireless communication node to receive only one of two PUSCHs transmitted by the wireless communication device. The wireless communication node and the wireless communication device can extract, obtain, determine, and / or share data block sizes. The wireless communication device can send, transmit, provide, and / or broadcast an uplink channel transmission block indication to the wireless communication node. The uplink channel transmission block indication can report and / or provide data block size information. For example, the wireless communication device can inform the wireless communication node via the transmission block indication whether the uplink channel data block size (e.g., PUSCH) is determined / specified / indicated by scheduling lease information (e.g., the scheduling DCI). The scheduling lease can be used to schedule the uplink channel.In another example, the wireless communication device can inform the node of. ML / t / ZUZZ / U / 3100 Wireless communication via transmit block indication if the uplink channel data block size (e.g., PUSCH) is determined / specified / indicated by information from (not the scheduling grant itself, but) a grant associated with the scheduling grant. If the data block size is determined / specified / indicated by the scheduling grant, a first uplink channel (e.g., a first PUSCH carrying a data block) can be different / independent of a second uplink channel (e.g., a second PUSCH carrying a separate data block). The first and / or second uplink channels can use separate / different data block sizes to carry the data blocks. If the data block size is determined / specified / indicated by the grant associated with the scheduling grant, the first uplink channel (e.g., the first PUSCH carrying a data block) can carry and / or include the same data blocks as the second uplink channel (e.g., the second PUSCH carrying the same data block).The grant associated with the scheduling grant can be used to schedule the second uplink channel. The first and / or second uplink channel can use corresponding / equal data block sizes to include / carry the data blocks. With reference to Figure 3, a representation of a downlink transmission example using multiple transmit-receive points (MTRP) and a single scheduling lease (e.g., DCI) is illustrated. Certain systems can support transmissions using a single DCI and MTRP. In single DCI-based MTRP transmissions, wireless communication nodes can schedule one or more downlink channel transmissions (e.g., downlink physical shared channel (PDSCH) transmissions and / or other downlink channel transmissions) using a scheduling lease (e.g., DCI, radio resource centroid (RRC) signaling, and / or other indicators). For example, a TRP0 PDSCH transmission and / or a TRP1 PDSCH transmission can be scheduled using DCI0.Any one or more Transmit-Receive Points (TRPs) can send / transmit / broadcast the programming lease (e.g., DCI, RRC signaling, and / or other leases). For example, TRP1 or TRP0 can send / transmit DCI0 to a wireless communication device. In some configurations, two or more TRPs can send / transmit across one or more layers to the wireless communication device (e.g., UE 302) at any given time. For example, TRP0 and TRP1 can send / transmit across Layer 0 and Layer 1, respectively, to a UE 302. In the case of an ideal backhaul network between two or more TRPs (e.g., TRP0 and TRP1), a single programming lease (e.g., DCI0 or another) is used. The ML / t / ZUZZ / U / 3100 indicator can provide and / or indicate information for scheduling a downlink channel transmission (e.g., a PDSCH through one or more layers of two TRPs). Downlink channel transmissions from the TRPs can utilize at least two layers (e.g., Layer 0, Layer 1, and / or other layers). These at least two layers can be spatially multiplexed into the same physical time and / or frequency resources (e.g., the at least two layers can utilize a space-division multiplexing (SDM) scheme). With reference to Figure 4, a representation of a downlink transmission example using MTRP and a single scheduling lease (e.g., DCI) is illustrated. In some modes, one or more TRPs can send / transmit / broadcast one or more downlink channels (e.g., PDSCH or other downlink channels) to a wireless communication device (e.g., a UE 302) using a time-division multiplexing (TDM) scheme. For example, TRP0 and / or TRP1 can transmit / send one or more PDSCHs (e.g., PDSCH0, PDSCH1, PDSCH2, PDSCH3, and / or other PDSCHs) to a UE 302 using TDM. In some modes, one or more downlink channels can carry / carry (e.g., transport, communicate, transmit) the same block of data and / or information. For example, PDSCH0 and PDSCH1 may include / carry the same block of data and / or information.In another example, PDSCH2 and PDSCH3 can carry the same block of data and / or information. Downlink channels (e.g., PDSCH) that carry the same block of data can be called repeat occasions or replay transmissions. The scheduling grant (e.g., DCI0) can provide information to schedule downlink transmissions (e.g., PDSCH0, PDSCH1, PDSCH2, and / or PDSCH3) from one or more TRPs (e.g., TRP0 and / or TRP1). Any one or more TRPs can generate, transmit, or provide the scheduling grant (e.g., DCI, RRC signaling, and / or other indicators). For example, TRP0 or TRP1 can generate, send, or transmit DCI0. Wireless communication nodes can save / reduce DCI-related overhead (e.g., transmission, processing) and / or improve / increase transmission reliability for PDSCH transmissions by using an individual DCI. The carrier frequencies of frequency range 2 (FR2) may exceed the carrier frequencies of other frequency ranges. For example, the carrier frequencies of FR2 may exceed the carrier frequencies of frequency range 1 (FR1) or other frequency ranges. In some modes, blocking may occur in FR2 (or other frequency ranges). If blocking occurs, it may affect / impact / prevent the transmission of one or more TRPs. For example, blocking may MTRP affects / impacts / impacts the transmissions of PDSCHs (e.g., PDSCHO, PDSCH1, PDSCH2, and / or PDSCH3) from TRPO and / or TRP1. If blocking affects / disrupts / impacts the transmissions of one TRP, the wireless communication device may still receive / obtain / detect the complete transmissions of another TRP (e.g., a TRP not affected by blocking). For example, if blocking affects TRPO transmissions, the wireless communication device may receive the complete transmissions of TRP1 (e.g., the transmissions are repeat instances). Therefore, the use of MTRP can increase / improve the robustness of downlink channel transmissions (e.g., PDSCH transmissions) on FR2 (or other frequency ranges). In some modes, blocking can disrupt or affect the transmission of the single programming lease (e.g., DCI) from the wireless communication node (e.g., TRP). If the programming lease transmission is blocked, the wireless communication device may be unable to receive or decode the downlink channel transmission. For example, if the TRPO's DCI transmission is blocked, the UE 302 may be unable to receive or decode the PDSCHO and / or PDSCH1 transmissions. The DCI (or other programming lease) may include or provide programming information for the PDSCH, such as time / frequency resource location, modulation and coding scheme (MCS), and / or other information. The wireless communication device / node may use the information provided by the DCI for the downlink channel transmission (e.g., PDSCH). With reference to Figure 5, a representation of a downlink transmission example using MTRP and two or more scheduling leases (e.g., two or more DCIs) is illustrated. Multiple DCI-based MTRP transmissions can be used to address scheduling lease transmission blocks. In some modes, two or more wireless communication nodes (e.g., TRPs) can each transmit at least one scheduling lease. For example, TRPO and TRP1 can each transmit one DCI (e.g., DCIO and DCI1, respectively). The scheduling leases (e.g., DCIO and / or DCI1) can provide information for scheduling downlink channel transmissions. For example, DCIO and DCI1 can provide information for scheduling PDSCHO and PDSCHI, respectively.The scheduling concession transmissions of the two or more TRPs can provide / specify information for scheduling separate / distinct downlink channel transmissions (e.g., PDSCH). For example, DCIO can provide / specify information for scheduling PDSCHO, which can be separate from / distinct from PDSCH1. One or more values of the RRC parameter coresetPoollndex-r16 (e.g., corresponding to a CORESET pooling index or other parameters) can be specified. ML / t / ZUZZ / U / 3103 is used to configure / determine programming concessions (e.g., DCI). In some modes, one or more coresefPoo / / nc / ex-r / 6 values may indicate / correspond to a particular TRP. The use of MTRP and multiple scheduling concessions can increase / improve the reliability of downlink channel transmissions (e.g., PDSCH transmissions) on FR2 (or other frequency bands). However, certain systems may not provide similar increases / improvements for uplink channel transmissions (e.g., PUSCH or other uplink channels). The transmission power of uplink channel transmissions may be lower than the transmission power of downlink channel transmissions. Therefore, ensuring uplink coverage and / or reliability can be challenging. The systems and methods presented herein include a novel approach to improving and / or increasing the reliability of uplink channel transmissions through redundancy / duplication, by at least 25% (e.g., 35%, 45%, or another percentage), as an example. In some modes, transmissions using MTRP and a single scheduling lease (e.g., DCI) can improve the reliability of uplink data transmissions. For example, wireless communication devices can transmit two or more PUSCH repeats using TDM and a single DCI (or other scheduling lease). In FR2, the use of analog beams can achieve beamforming gain and / or compensate for the large path loss. The narrow bandwidth of analog beams can make them highly vulnerable to blocking by an object (e.g., human bodies). If the beam bandwidth is narrow, using a single DCI and MTRP may be an ineffective approach. However, the wireless communication device can send / transmit / broadcast one or more uplink channels (e.g., PUSCH) to one or more wireless communication nodes (e.g., TRP).For example, the wireless communication device may use one or more analog beams to transmit one or more PUSCHs across one or more beam directions. In some modes, the wireless communication node may send / transmit a single programming lease (e.g., DCI) using a single beam. If the single beam is blocked, the wireless communication device may be unable to receive / obtain the programming lease. As a result, the wireless communication device may be unable to transmit the intended replays (e.g., PUSCH replays). With reference now to Figure 6, a representation of an example uplink transmission using MTRP and two or more scheduling leases (e.g., two or more DCIs) is illustrated. Two or more uplink channel transmissions (by For example, PUSCH transmissions can carry / include the same data block to improve and / or increase the reliability of uplink channel transmissions through redundancy / replication. For example, PUSCHO and PUSCH1 can carry / include the same data block to improve reliability through redundancy / repetition. The wireless communication node can receive uplink channel transmissions and perform a smooth combination of the received transmissions. Therefore, two or more uplink channel transmissions (e.g., PUSCHO and PUSCH1) can carry the same data block with the same Transmission Block Size (TBS). For example, PUSCHO and PUSCH1 can carry a data block with the same TBS. The wireless communication node can receive the transmissions and perform a smooth combination of PUSCHO and PUSCH1. The scheduling grant (e.g., the scheduling DCI and / or the upper-layer configuration) can specify scheduling information (e.g., the amount of time resources, the amount of frequency resources, the MCS, and / or other information). In some modes, the scheduling information can be used to determine the TBS.The wireless communication node can determine / identify / configure the Time Base Scheduling (TBS) of an uplink channel transmission using the scheduling information provided by the relevant scheduling lease (e.g., the corresponding upper-layer configuration and / or DCI). For example, the wireless communication node can determine the TBS of PUSCHO using the scheduling information provided by the DCI. In another example, the wireless communication node can determine the TBS of PUSCH1 using the scheduling information provided by the DCI. Two or more programming grants (e.g., DCI) may include / indicate / provide distinct and / or different programming information. For example, DCIO may include / indicate programming information that differs from the programming information provided by DCI1. If the programming information for the programming grants is distinct / separate, the TBS for uplink channel transmissions may also be distinct / different. For example, DCIO and DCI1 may specify / indicate separate programming information. Therefore, the TBS for PUSCHO and the TBS for PUSCH1 may be distinct / different as specified by the corresponding programming grant (e.g., DCIO and DCI1, respectively).In order to ensure equal / corresponding TBS between two or more uplink channel transmissions, the programming lease corresponding to a first uplink transmission can be used to transmit / send a second (or other) uplink transmission. For example, the wireless communication device can use the lease of. ML / t / ZUZZ / U í OΊ 03 programming corresponding to PUSCHO (e.g., DCIO) to determine / configure the TBS of PUSCH1. In another example, the wireless communication device can use DCI1 to determine / configure the TBS of PUSCHO. In this example, the wireless communication device can use the corresponding programming lease of the uplink transmission (e.g., PUSCHO) to determine other types of programming information (e.g., frequency resource allocation, antenna port indication, and / or other types of information). For example, the wireless communication device can use DCI1 to determine the TBS of PUSCHO and DCIO to determine the antenna port indication. In some modes, the wireless communication device may receive at least one (but less than the full amount) of two or more programming leases sent by the wireless communication node (for example, due to blocking). The wireless communication node may configure / activate / indicate programming leases using separate analog beams. A single analog beam may correspond to a transmit configuration indicator (TCI) state, a quasi-colocation configuration (QCL) set, spatial relationship information, and / or a probe reference signal (SRS) indicator (SRI). In some modes, the wireless communication node may receive at least one (but less than the full amount) of two or more uplink transmissions from the wireless communication device (for example, due to blocking).The wireless communication node and / or the wireless communication device may be unable to predict / anticipate blocking (e.g., blocking occurs randomly). In some modes, the wireless communication node may send / transmit at least one (but less than the full amount) of two or more programming leases (e.g., DCI and / or upper-layer configuration) to improve flexibility and / or capacity. In some modes, one or more uplink channel transmissions may carry / include separate data blocks with separate transmission block sizes. For example, PUSCH1 and PUSCHO may carry / include distinct data blocks with separate transmission block sizes (e.g., PUSCH transmissions may represent / correspond to separate / distinct transmissions). In some modes, one or more uplink channel transmissions may contain / carry the same data block (for example, the transmissions may have a corresponding / equal TBS). Two or more scheduling leases can be associated if they are used to schedule two or more uplink transmissions that contain / carry the same data block. For example, DCIO and DCI1 can be associated if they are used to schedule two PUSCHs that contain / carry the same data block. The communication node ML / t / ZUZZ / U í 0103 Wireless can inform / indicate / specify to the wireless communication device that two or more programming leases (e.g., DCI and / or upper-layer configuration) are associated / linked. For example, TRPO and / or TRP1 can provide information to UE 302 indicating that DCI0 and DCI1 are associated. The wireless communication node can provide / specify association information through an indicator, a programming grant, a message, a transmission, and / or other methods. For example, the wireless communication node can send / transmit two or more DCIs (e.g., DCI0 and DCI1) that carry / include the same / associated Hybrid Auto Repeat Request (HARQ) processing number (or other indicator / number). Higher-layer signaling (or other signaling types) can configure and / or predetermine whether two or more HARQ processing numbers are associated. The wireless communication device can receive / obtain the two or more DCIs (or other programming grants) and can determine whether the corresponding HARQ numbers (or other indicators / numbers) are the same / associated. For example, the UE 302 can receive DCI0 and DCI1, each of which includes / carries a HARQ processing number.The UE 302 can determine if the HARQ number of DCI0 and the HARQ number of DCI1 are the same / associated. If the HARQ numbers are the same / associated, the wireless communication device can determine that the two or more uplink transmissions (e.g., PUSCH0 and PUSCH1) programmed with the DCIs are repetitive transmissions. Therefore, the wireless communication device can determine that the DCIs (e.g., DCI0 and DCI1) are associated. If the HARQ numbers are different / unequal, the wireless communication device can determine that the two or more uplink transmissions (e.g., PUSCH0 and PUSCH1) are different / independent (e.g., the DCIs are not associated). In some configurations, scheduling grants can be associated with separate control resource sets (CORESETs) and / or coresetPoollndex-r16 (or other upper-layer signaling parameters). The coresetPoollndex-r16 can specify the CORESET pool index. Two or more scheduling grants associated with separate CORESETs and / or coresetPoollndex-r16 can include the same HARQ processing number (for example, the two or more scheduling grants can be linked). For example, DCI1 and DCI0 can carry the same HARQ processing number, and each is associated with a separate CORESET. Therefore, DCI1 and DCI0 can be linked (for example, the DCIs carry the same HARQ number). In some modalities, a new number indicator (NDI) may provide information that indicates / specifies whether two or more programming grants are associated.For example, two DCIs (or other concessions) can be associated. MA / t / ZUZZ / U / 3100 of programming) that carry / include / specify the same NDL In some modes, misalignment / lack of communication can occur between the wireless communication node and the wireless communication device. The modes analyzed here are non-limiting examples that describe cases of alignment and / or misalignment. Case 1: The wireless communication node can transmit / send two or more scheduling leases to schedule two or more repetitive uplink transmissions (e.g., repeat occasions). The wireless communication device can receive / obtain the two or more scheduling leases. The wireless communication device can transmit two or more uplink transmissions using the same TBS. The wireless communication device can use one of two or more scheduling leases to determine / configure the TBS. For example, the wireless communication device can transmit PUSCHO and PUSCH1 using the same TBS. The wireless communication device can use DCIO (or DC11) to determine the TBS. The wireless communication node can receive / obtain / detect uplink transmissions. The wireless communication node can determine that the TBS is configured based on information provided by one or more programming leases. Case 2: The wireless communication node can transmit / send a single scheduling lease to schedule a single uplink transmission. In some modes, the wireless communication node can transmit / send two or more scheduling leases to schedule independent / distinct / separate uplink transmissions. The wireless communication device can transmit one or more uplink transmissions using the corresponding scheduling lease. The wireless communication device can determine the Time-Based Service (TBS) of a particular uplink channel transmission based on the corresponding scheduling lease of that particular uplink channel transmission. The wireless communication node can receive / obtain / detect one or more uplink transmissions. The corresponding scheduling lease can indicate / specify the TBS of one or more uplink transmissions. Case 3: The wireless communication node can send / transmit two or more scheduling leases to schedule two or more repeating transmissions (e.g., repeat occasions). The wireless communication device can receive / obtain at least one (but less than the full amount) of the two or more leases. ML / t / ZUZZ / U / 3100 programming due to a lock. In some modes, the wireless communication device may receive / obtain one of two or more programming grants. The wireless communication device can receive at least one (but less than the full amount) of the two or more scheduling leases. Therefore, the wireless communication device can determine that Case 2 is occurring. The wireless communication device can transmit at least one (but less than the full amount) uplink transmission. The wireless communication device can determine the TBS of at least one uplink transmission using the corresponding scheduling lease. For example, the wireless communication device can transmit PUSCH1 using the TBS indicated by DCI1. In some modes, the wireless communication node may determine / assume that Case 1 is occurring. Therefore, the wireless communication node may receive / obtain at least one uplink transmission under the assumption that the TBS was determined using a lease associated with the corresponding scheduling lease. For example, the wireless communication node may receive PUSCH1 under the assumption that the TBS was determined using DCIO. The wireless communication node may not receive PUSCHO, thus determining that PUSCHO was blocked. Misalignment may occur between the wireless communication node and the wireless communication device. In some modes, the wireless communication device can send / transmit a transmission block (TB) indication to the wireless communication node to determine the information (e.g., TBS) of a scheduled uplink data transmission. The wireless communication device can report / indicate whether the uplink transmission's TBS is determined using the corresponding scheduling lease. In some modes, the wireless communication device can report / indicate whether the uplink transmission's TBS is determined using a lease associated with the scheduling lease (e.g., a lease associated with the scheduling lease). For example, the UE 302 can report / indicate whether the PUSCHO TBS is determined using the scheduling information of the corresponding scheduling DCI (e.g., DCI).In another example, UE 302 can report / indicate whether PUSCHO's TBS is determined by using concession scheduling information associated with the scheduling concession (e.g., DCI1). In some modes, the wireless communication device can transmit a TB indication. The TB indication can specify whether the uplink channel transmission's Time-Based Service (TBS) is determined using scheduling information from the scheduling lease (e.g., DCI, upper-layer configuration, or other leases). The TB indication can also specify whether the uplink channel transmission's TBS is determined using scheduling information from a lease associated with the scheduling lease. The association between the scheduling lease and the leases associated with it can indicate that the leases can schedule repetitive transmissions of the same data block.Uplink transmissions that are scheduled using associated leases can be repetitive transmissions (e.g., repeat occasions). The scheduling grant and the grant associated with the scheduling grant can be from different CORESETs and / or be associated with different coreset values (or CORESET pooling). A beam (for example, corresponding to a TCI state and / or spatial relationship information) can be configured according to CORESET. Therefore, the scheduling grant and the grant associated with the scheduling grant can be from different CORESETs (or be associated with different coreset values) to achieve beam diversity gain. In some modes, the scheduling grant and the grant associated with the scheduling grant can be from separate TRPs. In some modes, the TB indication can specify whether the TBS of an uplink transmission is determined using the scheduling grant or the grant associated with the scheduling grant. For example, the TB indication can specify that the TBS is determined using the scheduling information of the scheduling grant. In another example, the TB indication can specify that the TBS is determined using the scheduling information of the grant associated with the scheduling grant. If the TBS is determined using the scheduling grant (for example, the scheduling DCI), the uplink channel transmission can be independent of other uplink transmissions. For example, PUSCHO can be independent of PUSCH1 if PUSCHO's TBS is determined using DCI.In this example, the wireless communication device can program PUSCH1 by using the programming information from DCI1. If the Time Base Scheme (TBS) is determined using the lease associated with the scheduling lease (for example, an associated DCI), the uplink channel transmission can be a repeat transmission (for example, a repeat occasion) of another uplink channel transmission. For example, PUSCHO and PUSCH1 can be repeat transmissions if the TBS of both PUSCH transmissions is determined / configured using DCI1. The wireless communication device can determine the TBS of the repeat transmission. ML / t / ZUZZ / U í 0103 when using a lease associated with the scheduling lease. The TBS of the repetitive transmissions may be the same. If the uplink transmissions are repetitive transmissions, the scheduling lease and the lease associated with the scheduling lease may be linked. The associated leases of the repetitive transmissions may include / carry / specify the same / corresponding / associated HARQ processing number / identification (or other indicator). The associated leases may be of separate / different CORESETs and / or associated with separate / different coresetPoollndex-r16 values. In some modes, the associated leases may include / carry / specify the same / corresponding / associated NDI. In some modes, the associated leases may include / carry / specify the same / corresponding / associated carrier indicator and / or bandwidth share indicator. In some modes, the uplink channel transmission may carry, include, provide, and / or specify the TB indication. A higher-layer configuration (e.g., RRC signaling, Media Access Control Element (MACCE) signaling, or other configurations / signaling) may determine / indicate whether the uplink transmission (e.g., PUSCH) includes the TB indication. The higher-layer configuration may be configured by CORESET, Search Space (SS), and / or CORESET grouping (e.g., by coresetPoollndex-r16 and / or TRP). The wireless communication node may schedule the uplink transmission using a scheduling lease (e.g., DCI) associated with the CORESET, SS, or TRP. The uplink channel transmission may carry / include the TB indicator to inform / specify / indicate whether the uplink channel transmission is a repetitive transmission.For example, if a PUSCH is programmed by a DCI associated with a CORESET, SS, or TRP that is configured with a TB indication, the PUSCH may carry / include the TB indication. The PUSCH may carry the TB indication to indicate / specify that the PUSCH's TBS is based on the programming DCI or the DCI associated with the programming DCI. If a PUSCH is programmed by a DCI associated with a CORESET, SS, or TRP that is not configured with the TB indication, the indicator may be excluded from the PUSCH. The PUSCH's TBS may be based on the programming DCI, rather than another DCI. In some modes, the upper layer signaling may comprise RRC signaling or MACCE signaling. The wireless communication node and / or device can use the TB indicator to determine / specify the TBS. Therefore, the wireless communication device can transmit / send the TB indicator only if the Uplink Shared Channel (UL-SCH) indicator of the scheduling lease (e.g., DCI) has a value of one. The TB indicator can be used to determine the data block size. Therefore, the TB indicator can only exist if the UL-SCH indicator (Uplink Shared Channel) is set to one. The UL-SCH (ML / t / ZUZZ / U / 3100 and / or UL data) in the DCI has a value of one. The UL-SCH can comprise one or more bits. If the UL-SCH has a value of one, the uplink channel transmission can include / indicate / specify the UL-SCH. If the UL-SCH has a value of zero, the uplink channel transmission can exclude the UL-SCH. The DCI can be used to schedule an uplink channel transmission (e.g., PUSCH). In some modes, an RRC configuration (or RRC signal) can determine, indicate, and / or specify the scheduling of semi-persistent uplink channel transmissions (e.g., semi-persistent PUSCH instances). Therefore, the systems and methods disclosed herein can be used for PUSCH transmissions that are scheduled using an RRC configuration. In some modes, the RRC configuration can replace the DCL. Independent beams can configure, activate, and / or indicate PUSCH transmissions that are scheduled using at least two leases (e.g., DCI and / or RRC configurations). Mapping the TB indicator to the uplink channel transmission The wireless communication node can receive the TB indication from the wireless communication device. The wireless communication node can decode the received TB indication to determine the uplink channel's TBS. The wireless communication device can use the information provided by the decoded TB indication to decode the uplink channel. In some modes, the uplink channel may carry the TB indication. The wireless communication device can send the uplink channel's TB indication with UL-SCH using at least one of the uplink control information (UCI) transmission procedures. The UCI may comprise at least one HARQ Acknowledgement Channel Status Information (CSI) Part 1 and / or CSI Part 2.In some modes, the wireless communication device can transmit the TB indication using at least one of the following: code block segmentation, cyclic redundancy check (CRC) junction, channel coding, rate matching, code block concatenation, and / or UCI bit multiplexing encoded in the PUSCH. The modes discussed herein are non-limiting examples that describe options or implementations for mapping the TB indication to the uplink channel (e.g., PUSCH). Option 1: The wireless communication device can use the uplink channel to send / transmit the TB indication using HARQ-ACK multiplexing on the uplink channel with UL-SCH. The channel coding and / or resource element (RE) mapping can follow / mimic / adopt certain HARQ-ACK procedures. Option 1-1: If the uplink channel (e.g., PUSCH) includes a HARQ ML / t / ZUZZ / U / 3100 In ACK, the HARQ-ACK bits may include or correspond to the TB indication. In some modes, the offset values ( / ?^ / ^) may include or correspond to the TB indication. The wireless communication device may configure the offset values to determine a certain amount of resources for multiplexing HARQ-ACK information on an uplink channel. For example, in a bit sequence 00, 0^02, 0.3,... the bit a0 may include or correspond to the TB indication. In this example, the bits aAΆαA <pueden incluir o corresponderá los bits HARQ-ACK. En otro ejemplo, el bit aA_rpuede incluir o corresponder a la indicación TB en tanto que los bits restantes corresponden a los bits HARQ-ACK. Uno o más bits de la secuencia de bits pueden incluir o corresponder a la indicación TB. Otros bits en la secuencia de bits (por ejemplo, aA,a2, y / u otros bits) pueden incluir o corresponder a la indicación TB. If the uplink channel with UL-SCH excludes HARQ-ACK, the TB indicator may include or correspond to the HARQ-ACK bits. Offset values can be used for transmitting the TB indication over the uplink channel with ULSCH. Offset values {PoA^tACK} can be defined so that a wireless communication device determines a number of resources for multiplexing HARQ-ACK information in a PUSCH. Offset values {PgA^ACK} can be used for the TB indication. Option 1-2: If the uplink channel (e.g., PUSCH) includes a HARQACK, the TB indication can be mapped / placed / configured before or after (e.g., adjacent to) the ACK / NACK bits. The wireless communication device can configure offset values to determine the amount of resources for multiplexing the TB indication information on the uplink channel. Higher-layer configurations (e.g., RRC signaling, MAC CE signaling, and / or other signaling types) can determine / configure / define the offset values. The TB indication and the HARQ-ACK can be encoded separately. For example, in a bit sequence encoded g0g1,...,gG-29g-i^, the bits g0gr can include or correspond to bits encoded with the TB indication. In this example, the remaining bits correspond to the HARQ-ACK encoded bits.In another example, the bits gG_29c-i may include or correspond to the bits encoded with indication TB, and the remaining bits correspond to the bits encoded HARQACK. One or more bits in the encoded bit sequence may include or correspond to the bits encoded with indication TB. If the uplink channel with UL-SCH excludes HARQ-ACK, the RE mapping rules can follow / mimick the HARQ-ACK RE mapping rules. Upper-layer signaling (e.g., RRC, MACCE, and / or other signaling) can MA / t / ZUZZ / U / 3103 configure / define / determine the offset values. In some modes, the programming grant (e.g., DCI) may indicate / specify the offset values. The modulated resource elements (REs) of the TB indication can be mapped / placed after a first symbol that carries / specifies a demodulation reference signal (DMRS). If the intra-slot PUSCH hop is enabled, on an uplink channel frequency hop, the modulated resource elements (REs) for the transmit block indication can be mapped after a first symbol that carries a DMRS. In some modes, HARQ-ACK can be replaced by CSI Part 1 and / or CSI Part 2 in the above solutions. Option 2: The wireless communication device can use the uplink channel to send / transmit the TB indication using CSI Part 1 transmission procedures on the uplink channel with UL-SCH. The channel coding and / or RE mapping can follow / mimick the CSI Part 1 procedures. Option 2-1: If the uplink channel (e.g., PUSCH) includes CSI Part 1, the CSI Part 1 bits may include or correspond to the TB indication. The TB indication may be mapped / linked before or after the CSI Part 1 bits. The wireless communication device may configure offset values (Poffset) to determine a quantity of resources for multiplexing CSI Part 1 information on an uplink channel. The offset values may include or correspond to the TB indication. Option 2-2: If the uplink channel (e.g., PUSCH) includes CSI Part 1, the TB indication can be mapped / placed / configured before or after the CSI Part 1 bits. Upper-layer configurations (e.g., RRC signaling, MAC CE signaling, and / or other signaling types) can determine / configure / define the offset values. In some modes, the programming grant (e.g., DCI) can indicate / specify the offset values. Option 3: The wireless communication device can use the uplink channel to send / transmit the TB indication using CSI Part 2 transmission procedures on the uplink channel with UL-SCH. The channel coding and / or RE mapping can follow / imitate / adopt certain CSI Part 2 procedures. Option 3-1: If the uplink channel (e.g., PUSCH) includes CSI Part 2, the CSI Part 2 bits may include or correspond to the TB indication. The TB indication may be mapped / linked before or after the CSI Part 2 bits. The wireless communication device may configure the offset values (β^εύ). ML / t / ZUZZ / U 70100 Determine a quantity of resources for CSI information multiplexing part 2 on an uplink channel. Offset values may include or correspond to indication TB. Option 3-2: If the uplink channel (e.g., PUSCH) includes CSI Part 2, the TB indication can be mapped / placed / configured before or after the CSI Part 2 bits. Upper-layer configurations (e.g., RRC signaling, MAC CE signaling, and / or other signaling types) can determine / configure / define the offset values. In some modes, the scheduling grant (e.g., DCI) can indicate / specify the offset values. In some modes, the modulated resource elements (REs) for the TB indication can be mapped / placed starting from a first symbol on the uplink channel that does not carry a DMRS. If intra-slot PUSCH hopping is enabled, on an uplink channel frequency hop, the modulated resource elements (REs) for the transmit block indication can be mapped starting from a first symbol on the uplink channel that excludes / omits a DMRS. Methods to improve the reliability of uplink transmissions Figure 750 illustrates a flowchart of a Method 750 for improving the reliability of uplink transmissions. Method 750 can be implemented using any of the components and devices detailed herein, along with Figures 1–6. In summary, Method 750 may include receiving a scheduling grant (752). Method 750 may include transmitting an uplink channel (754). Method 750 may include determining whether the UL-SCH indicator has a value of one (756). Method 750 may include transmitting the transmission block indication (758). Method 750 may include omitting a transmission block indication (760). With reference to operation (752) and in some modes, a wireless communication device (e.g., a terminal node or a UE) can receive and / or obtain a programming lease from a wireless communication node (e.g., a base station or a gNB). The wireless communication node can generate / send / transmit / broadcast the programming lease to the wireless communication device. For example, UE 302 can receive / obtain one or more programming leases from one or more TRPs (e.g., TRP0 and / or TRP1). The wireless communication node can send / transmit the programming lease using a downlink channel (e.g., PDCCH) and / or other channel types. The programming lease can comprise downlink control information (DCI), a higher-layer configuration, and / or other indicators / configurations for programming the uplink channel.The top layer configuration may include RRC signaling. ML / t / ZUZZ / U / 3103 MAC CE signaling and / or other types of signaling. The programming lease may support the transmission of uplink / downlink channels (e.g., DL-SCH, UL-SCH and / or other channels). Programming leases may include / provide resource allocation information, modulation and coding schemes, power transmission information, HARQ number / indicator information, precoding information and / or other types of information. With reference to operation (754), and in some modes, the wireless communication device can transmit and / or send an uplink channel to the wireless communication node. The uplink channel can comprise a shared physical uplink channel (PUSCH) or other types of uplink channels. The wireless communication node can receive / obtain the uplink channel from the wireless communication device. For example, a TRP can receive / obtain a PUSCH from the UE 302. In some modes, the wireless communication device can use scheduling leases to configure the uplink channel transmission. For example, the UE 302 can use information provided by DCI0 to configure the PUSCH0 transmission.The wireless communication device can use the TBS information indicated / provided by the programming grant to configure the uplink channel transmission. In some modes, the wireless communication device can send / transmit the uplink channel in response to receiving the programming grant. With reference to operation (756), and in some modes, the wireless communication device can determine if the UL-SCH indicator has a value of 1. The programming grant may include the UL-SCH indicator and / or other indicators. Before transmitting the TB indication, the wireless communication device can determine if the UL-SCH indicator (or other indicators) has a value of 1. For example, the wireless communication device may receive the programming grant (e.g., DCI0) from the wireless communication node. In response to receiving the programming grant, the wireless communication device can determine if the UL-SCH indicator included in the programming grant has a value of 1.If the UL-SCH indicator has a value of 1 (for example, indicating that data is available for transmission), the wireless communication device can transmit the UL-SCH and / or TB indication using the uplink channel (for example, PUSCH0). Conversely, if the UL-SCH indicator has a value of 0, the wireless communication device can exclude the UL-SCH and / or TB indication from the uplink transmission. Values other than 0 or 1 can be used to indicate the inclusion or exclusion of the UL-SCH and / or TB indication from the uplink transmission. The TB indication can specify... MA / t / ZUZZ / U / 3103 TBS information of the uplink channel transmission. With reference to operation (758), and in some modes, the wireless communication device can transmit / configure / generate the Transmission Block (TB) indication. The wireless communication device can transmit the TB indication in response to a determination that the UL-SCH indicator has a value of 1. For example, the wireless communication device may determine that the UL-SCH indicator included in the programming lease has a value of 1. In response to this determination, the wireless communication device can transmit the TB indication to the wireless communication node. Therefore, the wireless communication node can receive / obtain the TB indication from the wireless communication device. A programming lease value of 1 can indicate that the link data is available for transmission.The wireless communication device can transmit the TB indication and the uplink channel separately. For example, the wireless communication device can send the TB indication (e.g., via a message, transmission, or signal) without using the PUSCH transmission. With reference to operation (760), and in some modes, the wireless communication device may omit / skip the transmission / configuration / generation of the TB indication. The wireless communication device may omit / avoid / skip the TB indication in response to a determination that the UL-SCH indicator has a value other than 1. For example, the wireless communication device may determine that the UL-SCH indicator included in the programming lease has a value of 0. In response to this determination, the wireless communication device may omit / exclude (for example, not incorporate) the TB indication from the uplink transmission to the wireless communication node. The wireless communication node may receive the uplink transmission without the TB indication. A programming lease value of 0 may indicate that the uplink data is not available for transmission. The TB indication may specify whether the uplink channel's TBS is determined according to the scheduling grant information and / or the information in a grant associated with the scheduling grant. For example, the TB indication may specify whether the PUSCH0 TBS is determined according to DCI0 or DCI1. Grant information may include a time resource amount, a frequency resource amount, a modulation and coding scheme, and / or other information. The wireless communication device may use the scheduling grant and / or the grant associated with the scheduling grant to schedule repetitive uplink channel transmissions. ML / t / ZUZZ / U / 3100 is a scheduling lease for scheduling repetitive transmissions of the same data block. For example, the wireless communication device can use DCI1 or DCI1 to schedule repetitive transmissions of a PUSCH. The association between leases can indicate / specify that two or more uplink transmissions are repetitive transmissions (for example, the uplink transmission has the same TBS). For example, if DCI1 and DCI1 are associated with each other, the association can indicate that PUSCHO and PUSCH1 are repetitive transmissions. In some modes, the wireless communication device can receive a higher-layer configuration (e.g., RRC signaling, MAC CE signaling, and / or other signaling) to transmit the TB indication on the uplink channel. In some modes, the wireless communication device can use the higher-layer configuration to determine whether the TB indication is included on the uplink channel. The wireless communication node can send the higher-layer configuration to the wireless communication device. Therefore, the wireless communication node can configure whether the TB indication is included on the uplink channel. The wireless communication device can then transmit the TB indication according to the higher-layer configuration.For example, RRC signaling can specify that the TB indication is included in the uplink channel. Therefore, the wireless communication device can transmit the TB indication using the uplink channel. The wireless communication node can receive the TB indication according to the upper-layer configuration. For example, the wireless communication node can transmit an upper-layer configuration to the wireless communication device specifying the exclusion of the TB indication. Therefore, the wireless communication node can receive the uplink channel transmission without the TB indication. The upper-layer configuration can be configured by CORESET, by SS, and / or by CORESET grouping. The wireless communication device can transmit / send the TB indication on the uplink channel using (for example, adopting, adapting) at least one of the UCI procedures in PUSCH. These procedures may include code block segmentation, CRC joining, channel coding, rate matching, code block concatenation, multiplexing of UCI bits encoded in PUSCH, and / or other procedures. The UCI may include / comprising at least one of HARQ-ACK, CSI Part 1, or CSI Part 2. In some modes, the wireless communication node can receive / obtain the TB indication on the uplink channel using at least one of the UCI procedures in PUSCH. For example, block segmentation mechanisms. UCI code bits, CRC binding, channel coding, rate matching, code block concatenation, and / or multiplexing of encoded UCI bits can be reused or adapted for the TB indication. In some modes, one or more bits of the TB indication can be arranged / placed / mapped adjacent to a sequence of UCI bits. For example, the TB indication can be placed before or after the UCI bit sequence. In some modes, one or more encoded bits of the TB indication can be arranged / placed / mapped adjacent to a sequence of UCI bits. For example, the encoded bits of the TB indication can be placed before and / or after the UCI bit sequence. The encoded bits of the TB indication may appear distinct, but they can be placed adjacent to the UCI bit sequence. In some modes, the wireless communication node can configure / activate / indicate the programming lease and / or the lease associated with the programming lease with independent / separate / distinct TCI states. Therefore, the programming lease and / or the lease associated with the programming lease can be associated / linked to an independent TCI state. For example, a TRP can configure / activate / indicate DCIO and / or DCI1 with independent TCI states. In some modes, a single analog beam can correspond to a single TCI state. The programming lease and / or the lease associated with the programming lease can be from different CORESETs. For example, DCIO and DCI1 (associated with DCIO) can be from different CORESETs. The programming lease and / or the lease associated with the programming lease can be associated with different values of the coresetPoolIndexr16 parameter.For example, two associated grants (e.g., DCIO and DCI1) may be from different CORESETs and / or be associated with different values of the coresetPoollndex-r16 parameter (or other parameters). In some modes, the scheduling grant and / or the grant associated with the scheduling grant may indicate / specify / include the same HARQ processing number / identifier or other numbers / identifiers. The scheduling grant and / or the grant associated with the scheduling grant may indicate / specify / include the same NDI and / or other indicators. For example, if two DCIs are associated, the DCIs may indicate / specify the same HARQ processing number and / or NDI (or other numbers / indicators). In some modes, two or more separate / distinct CORESET programming grants (or those associated with different coresetPoollndex-r16 values) may indicate / specify / include the same HARQ processing number, NDI and / or other numbers / indicators. In some modes, offset values can be defined for the wireless communication device. These offset values can be used to determine the number of resources for multiplexing the TB indication on the link channel. ML / t / ZUZZ / U / 3103 Upstream. Offset values can be used to determine a number of resources for multiplexing UCI and / or TB indication information on the uplink channel. Offset values can be configured / determined by upper-layer configuration (e.g., RRC signaling, MAC CE signaling, and / or other signaling types). In some modes, offset values can be indicated / specified by programming grant (e.g., DCI). An uplink channel (e.g., PUSCH) can comprise / include two or more frequency hops. Each frequency hop can be programmed through one or more frequency resources. An uplink channel frequency hop can comprise / include modulated resource (RE) elements for TB indication.In some modes, modulated REs can be mapped / associated after a first symbol carrying a DMRS. In some modes, modulated REs can be mapped / associated starting from a first symbol of the uplink channel that does not carry a DMRS. While several modalities of the present solution have been described above, it should be understood that they have been presented solely as examples, not as limitations. Similarly, the various diagrams may represent an example architecture or configuration, provided to enable those skilled in the art to understand the example features and functions of the present solution. These individuals would understand, however, that the solution is not limited to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Furthermore, as would be understood by those skilled in the art, one or more features of one modality can be combined with one or more features of another modality described herein.Therefore, the breadth and scope of this disclosure should not be limited by any of the illustrative methods described above. It is also understood that any reference to an element herein using a designation such as first, second, etc., generally does not limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Therefore, a reference to the first and second elements does not mean that only two elements may be employed, or that the first element must precede the second element in any way. Furthermore, a technical expert will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, and symbols referred to in the description above can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any other means. ML / t / ZUZZ / U / 3103 combination of the same. A person skilled in the art would also appreciate that any of the various illustrative logic blocks, modules, processors, media, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented by means of electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of both), firmware, various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as software or a software module), or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above in general terms of their functionality.Whether this functionality is implemented as hardware, firmware, or software, or a combination of these techniques, depends on the specific application and design constraints imposed on the overall system. Experts may implement the described functionality in various ways for each specific application, but these implementation decisions do not result in a departure from the scope of this disclosure. Furthermore, a person skilled in the art would understand that the various logic blocks, modules, devices, components, and illustrative circuits described herein can be implemented or realized within an integrated circuit (IC) that may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or another programmable logic device, or any combination thereof. The logic blocks, units, and circuits may also include antennas and / or transceivers for communicating with various components within the network or within the device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine.A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors together with a DSP core, or any other configuration suitable for performing the functions described herein. If implemented in software, functions can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include both computer storage media and communication media, which includes any medium that can be activated to transfer a program or code. ML / t / ZUZZ / U / 3100 computer from one place to another. A storage medium can be any available medium that can be accessed by a computer. By way of example and without limitation, these computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures, and which can be accessed by a computer. In this document, the term "module," as used herein, refers to software, firmware, hardware, and any combination thereof to perform the associated functions described herein. Furthermore, for the purpose of analysis, the various modules are described as discrete modules; however, as would be evident to one skilled in the art, two or more modules may be combined to form a single module that performs the associated functions according to the modalities of this solution. Additionally, memory or other storage, as well as communication components, may be used in various versions of this solution. It will be noted that, for the sake of clarity, the preceding description has described versions of this solution with references to different functional units and processors. However, it will be evident that any suitable distribution of functionality among different functional units, processing logic elements, or domains may be used without detracting from the value of this solution. For example, the illustrated functionality to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Therefore, references to specific functional units are merely references to a suitable means of providing the described functionality, rather than indicating a strict logical or physical structure or organization. Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is intended to have the broadest scope consistent with the novel features and principles disclosed herein, as mentioned in the claims below.
Claims
NOVELTY OF THE INVENTION Having described the present invention, the following claims are considered novel and are therefore claimed as property. CLAIMS 1. A method, characterized in that it comprises: receiving, by means of a wireless communication device from a wireless communication node, a programming lease of an uplink channel; transmitting, by means of the wireless communication device to the wireless communication node, the uplink channel; and transmitting, by means of the wireless communication device to the wireless communication node, a transmission block indication to determine a transmission block size (TBS) of the uplink channel.
2. The method according to claim 1, characterized in that the scheduling grant comprises downlink control information (DCI) or a higher layer configuration for scheduling the uplink channel.
3. The method according to claim 1, characterized in that the transmission block indication is indicative of whether the uplink channel TBS is determined according to the programming grant information, or according to the information of a grant associated with the programming grant.
4. The method according to claim 3, characterized in that it comprises using the scheduling grant and the grant associated with the scheduling grant, to schedule repetitive transmissions of the uplink channel or to schedule repetitive transmissions of the same block of data.
5. The method according to claim 3, characterized in that the programming grant and the grant associated with the programming grant are configured, activated, or indicated by transmit-independent configuration indicator (TCI) states.
6. The method according to claim 3, characterized in that the programming grant and the grant associated with the programming grant are from different control resource sets (CORESET), or are associated with different values of the coresetPoollndex-r16 parameter.
7. The method according to claim 3, characterized in that the scheduling grant and the grant associated with the scheduling grant indicate the same Hybrid Automatic Repeat Request Processing (HARQ) number or identifier or the same New Number Indicator (NDI).
8. The method according to claim 1, characterized in that it comprises: receiving, by the wireless communication device, a higher layer configuration ML / t / ZUZZ / U / 3103; and transmitting, by means of the wireless communication device to the wireless communication node, the transmission block indication on the uplink channel, in accordance with the higher layer configuration, wherein the higher layer configuration is configured in a manner by control resource set (CORESET), in a manner by search space (SS) or in a manner by CORESET grouping.
9. The method according to claim 1, characterized in that it comprises transmitting, by means of the wireless communication device to the wireless communication node, the transmission block indication if an uplink shared channel indicator (UL-SCH) has a value of 1.
10. The method according to claim 1, characterized in that it comprises transmitting the transmission block indication on the uplink channel using at least one of the following uplink control information (UCI) procedures on a shared physical uplink channel (PUSCH): code block segmentation, cyclic redundancy check (CRC) junction, channel coding, rate matching, code block concatenation, or UCI bit multiplexing encoded on the PUSCH, wherein the UCI includes at least one hybrid automatic repeat request acknowledgment (HARQ-ACK), channel status information (CSI) part 1, or CSI part 2.
11. The method according to claim 1, characterized in that the offset values defined for the wireless communication device to determine a number of resources for multiplexing the uplink centroid information (UCI) in the uplink channel are used to determine a number of resources for multiplexing the transmit block indication in the uplink channel.
12. The method according to claim 1, characterized in that the offset values defined for the wireless communication device to determine a number of resources for multiplexing the transmission block indication information on the uplink channel are configured through the upper layer configuration or indicated by the scheduling grant.
13. The method according to claim 1, characterized in that one or more bits of the transmission block indication are arranged adjacent to a sequence of uplink control information (UCI) bits.
14. The method according to claim 1, characterized in that one or more encoded bits for transmission block indication are arranged adjacent to the encoded bits for uplink control information (UCI).
15. The method according to claim 1, characterized in that in an uplink channel frequency hop ML / t / ZUZZ / U / 3103, the modulated resource elements (RE) for transmit block indication are mapped after a first symbol carrying a demodulation reference signal (DMRS), or are mapped from a first uplink channel symbol not carrying a DMRS.
16. A method, characterized in that it comprises: transmitting, by means of a wireless communication node to a wireless communication device, a scheduling lease of an uplink channel; receiving, by the wireless communication node of the wireless communication device, the uplink channel; and receiving, by means of the wireless communication node of the wireless communication device, a transmission block indication to determine a transmission block size (TBS) of the uplink channel.
17. The method according to claim 16, characterized in that the programming grant comprises downlink control information (DCI) or a higher layer configuration for programming the uplink channel.
18. The method according to claim 16, characterized in that the transmission block indication is indicative of whether the uplink channel TBS is determined according to the programming grant information, or according to the information of a grant associated with the programming grant.
19. The method according to claim 18, characterized in that the scheduling of repetitive uplink channel transmissions or the scheduling of repetitive transmissions of the same data block comprises using the scheduling grant and the grant associated with the scheduling grant.
20. The method according to claim 18, characterized in that the programming grant and the grant associated with the programming grant are configured, activated, or indicated by transmit-independent configuration indicator (TCI) states.
21. The method according to claim 18, characterized in that the programming grant and the grant associated with the programming grant are from different control resource sets (CORESET), or are associated with different values of the coresetPoollndex-r16 parameter.
22. The method according to claim 18, characterized in that the scheduling grant and the grant associated with the scheduling grant indicate the same hybrid automatic repeat request processing (HARQ) number or identifier or the same new number indicator (NDI).
23. The method according to claim 16, characterized in that it comprises: transmitting, by the wireless communication node, a top-layer configuration; and receiving, by means of the wireless communication node of the wireless communication device, the transmission block indication on the uplink channel, in accordance with the top-layer configuration, wherein the top-layer configuration is configured in a manner by control resource set (CORESET), in a manner by search space (SS) or in a manner by CORESET grouping.
24. The method according to claim 16, characterized in that it comprises receiving, by means of the wireless communication node from the wireless communication device, the transmission block indication if an uplink shared channel indicator (UL-SCH) has a value of 1.
25. The method according to claim 16, characterized in that it comprises receiving the transmission block indication on the uplink channel using at least one of the following uplink control information (UCI) procedures on a shared physical uplink channel (PUSCH): code block segmentation, cyclic redundancy check (CRC) junction, channel coding, rate matching, code block concatenation, or bit multiplexing of UCIs encoded on the PUSCH, wherein the UCI includes at least one hybrid automatic repeat request acknowledgment (HARQ-ACK), channel status information (CSI) part 1 or CSI part 2.
26. The method according to claim 16, characterized in that the offset values defined for the wireless communication device to determine a number of resources for multiplexing the uplink centroid information (UCI) in the uplink channel are used to determine a number of resources for multiplexing the transmit block indication in the uplink channel.
27. The method according to claim 16, characterized in that the offset values defined for the wireless communication device to determine a number of resources for multiplexing the transmission block indication information on the uplink channel are configured through the upper layer configuration or indicated by the scheduling grant.
28. The method according to claim 16, characterized in that one or more bits of the transmission block indication are arranged adjacent to a sequence of uplink control information (UCI) bits.
29. The method according to claim 16, characterized in that one or more encoded bits for transmission block indication are arranged adjacent to the encoded bits for uplink control information (UCI).
30. The method according to claim 16, characterized in that in a frequency hop ML / t / ZUZZ / U í 0103 of the uplink channel, the modulated resource elements (RE) for transmission block indication are mapped after a first symbol carrying a demodulation reference signal (DMRS), or are mapped from a first symbol of the uplink channel that does not carry a DMRS.
31. A non-transient, computer-readable medium that stores instructions, characterized in that when executed by at least one processor, they cause the at least one processor to perform the method according to any one of claims 1-30.
32. A wireless communication device, characterized in that it comprises: at least one processor configured to: receive, through a transceiver of a wireless communication node, a scheduling lease of an uplink channel; transmit, through the transceiver to the wireless communication node, the uplink channel; and transmit, through the transceiver to the wireless communication node, a transmission block indication to determine a transmission block size (TBS) of the uplink channel.
33. A wireless communication device, characterized in that it comprises: at least one processor configured to perform the method in accordance with claims 2-15.
34. A wireless communication node, characterized in that it comprises: at least one processor configured to: transmit, through a transceiver to a wireless communication device, a scheduling lease of an uplink channel; receive, through the transceiver of the wireless communication device, the uplink channel; and receive, through the transceiver of the wireless communication device, a transmit block indication to determine a transmit block size (TBS) of the uplink channel.
35. A wireless communication device, characterized in that it comprises: at least one processor configured to perform the method according to any of claims 17-30.