Signaling solutions for reliability enhancements for uplink transmissions

Abstract

Systems and methods are provided for enhancing reliability of uplink transmissions. A wireless communication device can receive, from a wireless communication node, a scheduling grant for an uplink channel. The wireless communication device can transmit, to the wireless communication node, the uplink channel. The wireless communication device can transmit, to the wireless communication node, a transport block indication for determining a transport block size (TBS) of the uplink channel.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication, including but not limited to systems and methods for enhancing reliability of uplink transmissions. BACKGROUND

[0002] The Third Generation Partnership Project (3GPP) is currently specifying a new radio interface, referred to as 5G New Radio (5G NR), and 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, impact, and / or impinge on the transmission and / or exchange of indicators, messages, data, and / or information. Thus, blocking can impact and / or impinge on the reliability of uplink / downlink transmissions. SUMMARY

[0003] The example embodiments disclosed herein are directed to solving problems related to one or more difficulties presented in the prior art, as well as providing additional features that will become apparent to those of ordinary skill in the art upon reading the following detailed description in conjunction with the drawings. In accordance with various embodiments, example systems, methods, devices, and computer program products are disclosed herein. It should be understood, however, that these embodiments are presented by way of example only, and are not limiting, and that it will be apparent to one of ordinary skill in the art reading the present disclosure that various modifications can be made to the disclosed embodiments while remaining within the scope of the present disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer readable medium. A wireless communication device can receive a scheduling grant 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 transport block indication to the wireless communication node. The transport block indication can be used to determine a transport block size (TBS) of the uplink channel.

[0005] In some embodiments, the scheduling grant can include downlink control information (DCI) or higher layer configuration to schedule the uplink channel. In some embodiments, the transport block indication can indicate whether the TBS of the uplink channel is determined from information of the scheduling grant. In some embodiments, the transport block indication can indicate whether the TBS of the uplink channel is determined from information of a grant associated with the scheduling grant. In some embodiments, the wireless communication device can schedule a repeated transmission of the uplink channel, or a repeated transmission of a same data block, using the scheduling grant and the grant associated with the scheduling grant.

[0006] In some embodiments, scheduling grants and the grants associated with scheduling grants can be configured, activated, or indicated through independent Transport Configuration Indicator (TCI) states. In some embodiments, scheduling grants and the grants associated with scheduling grants can come from different Control Resource Sets (CORESETs) or can be associated with different values ​​of the coresetPoolIndex-r16 parameter. In some embodiments, scheduling grants and the grants associated with scheduling grants can indicate the same Hybrid Automatic Repeat Request (HARQ) process number or identifier, or the same New Number Indicator (NDI). In some embodiments, the wireless communication device can receive higher-layer configuration. In some embodiments, the wireless communication device can transmit transport block indications in the uplink channel to the wireless communication node according to the higher-layer configuration. In some embodiments, the higher-layer configuration can be configured based on each CORESET, each search space (SS), or each CORESET pool.

[0007] In some embodiments, if the value of the Uplink Shared Channel (UL-SCH) indicator is 1, the wireless communication device may transmit a transport block indication to the wireless communication node. In some embodiments, the wireless communication device may transmit a transport block indication in the uplink channel using at least one procedure of the Uplink Control Information (UCI) on the Physical Uplink Shared Channel (PUSCH). The procedure of the UCI on the PUSCH may include code block segmentation, Cyclic Redundancy Check (CRC) attachment, channel coding, rate matching, code block concatenation, or multiplexing of encoded UCI bits to the PUSCH, wherein the UCI includes at least one of Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK), Channel State Information (CSI) Part 1, or CSI Part 2.

[0008] In some embodiments, an offset value defined for a wireless communication device for determining the amount of resources used for uplink control information (UCI) in a multiplexed uplink channel can be used to determine the amount of resources used for transport block indication in the multiplexed uplink channel. In some embodiments, the offset value defined for a wireless communication device for determining the amount of resources used for transport block indication information in a multiplexed uplink channel can be configured by a higher-layer configuration or indicated by scheduling authority. In some embodiments, one or more bits of the transport block indication can be arranged as adjacent uplink control information (UCI) bit sequences. In some embodiments, one or more coded bits of the transport block indication can be arranged as adjacent coded bits of the uplink control information (UCI).

[0009] In some embodiments, the frequency hopping of the uplink channel, the modulation resource elements (REs) for the transport block indication can be mapped after the first symbol carrying a demodulation reference signal (DMRS). In some embodiments, the frequency hopping of the uplink channel, the modulation resource elements (REs) for the transport block indication can be mapped starting from the first symbol of the uplink channel that does not carry a DMRS.

[0010] At least one aspect relates to a system, a method, an apparatus, or a computer readable medium. A wireless communication node can transmit a scheduling grant of 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 transport block indication from the wireless communication device for determining a transport block size (TBS) of the uplink channel.

[0011] In some embodiments, the scheduling grant can include a downlink control information (DCI) or a higher layer configuration to schedule the uplink channel. In some embodiments, the transport block indication can indicate whether the TBS of the uplink channel is determined according to information of the scheduling grant. In some embodiments, the transport block indication can indicate whether the TBS of the uplink channel is determined according to information of a grant associated with the scheduling grant. In some embodiments, scheduling a repeated transmission of the uplink channel or scheduling a repeated transmission of a same data block can include using the scheduling grant and the grant associated with the scheduling grant.

[0012] In some embodiments, the scheduling grant and the grant associated with the scheduling grant can be configured, activated, or indicated by independent transmission configuration indicator (TCI) states. In some embodiments, the scheduling grant and the grant associated with the scheduling grant can be from different control resource sets (CORESETs) or can be associated with different values of a coresetPoolIndex-r16 parameter. In some embodiments, the scheduling grant and the grant associated with the scheduling grant can indicate a same hybrid automatic repeat request (HARQ) process number or identifier, or a same new number indicator (NDI). In some embodiments, the wireless communication node can transmit a higher layer configuration. In some embodiments, the wireless communication node can receive the transport block indication in the uplink channel from the wireless communication device according to the higher layer configuration. In some embodiments, the higher layer configuration can be configured on a per-CORESET, per-search space (SS), or per-CORESET pool basis.

[0013] In some embodiments, if a value of an uplink shared channel (UL-SCH) indicator is 1, a wireless communication node can receive a transport block indication from a wireless communication device. In some embodiments, the wireless communication node can receive the transport block indication in an uplink channel using at least one procedure of uplink control information (UCI) on a physical uplink shared channel (PUSCH). The procedure of UCI on the PUSCH can include code block segmentation, cyclic redundancy check (CRC) attachment, channel coding, rate matching, code block concatenation, or multiplexing of coded UCI bits to the PUSCH, where the UCI includes at least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK), channel state information (CSI) part 1, or CSI part 2.

[0014] In some embodiments, an offset value defined for a wireless communication device for determining a number of resources used for multiplexing uplink control information (UCI) in an uplink channel can be used to determine a number of resources used for multiplexing a transport block indication in the uplink channel. In some embodiments, an offset value defined for a wireless communication device for determining a number of resources used for multiplexing transport block indication information in an uplink channel can be configured by higher layer configuration or indicated by a scheduling grant. In some embodiments, one or more bits of the transport block indication can be arranged adjacent to a sequence of uplink control information (UCI) bits. In some embodiments, one or more coded bits of the transport block indication can be arranged adjacent to coded bits of uplink control information (UCI).

[0015] In some embodiments, frequency hopping of the uplink channel, modulation resource elements (REs) used for the transport block indication can be mapped after a first symbol carrying a demodulation reference signal (DMRS). In some embodiments, frequency hopping of the uplink channel, modulation resource elements (REs) used for the transport block indication can be mapped starting from a first symbol of the uplink channel that does not carry a DMRS. BRIEF DESCRIPTION OF DRAWINGS

[0016] Various example embodiments of the present solution are described in detail below with reference to the following illustrations or drawings. The drawings are provided for purposes of illustration only and merely depict example embodiments of the present solution to facilitate the reader’s understanding of the present solution. Consequently, the drawings should not be considered limiting the breadth, scope, or applicability of the present solution. It should be noted that for purposes of clarity and brevity, these drawings are not necessarily to scale.

[0017] Figure 1 An example cellular communication network in which the techniques disclosed herein can be implemented is shown in accordance with embodiments of the present disclosure;

[0018] Figure 2Block diagrams illustrating example base stations and user equipment according to some embodiments of the present disclosure are shown;

[0019] Figures 3-5 Various methods for transmitting downlink data with multiple transmission-reception points (MTRPs) and one or more scheduling grants according to some embodiments of the present disclosure are shown;

[0020] Figure 6 Example methods for transmitting uplink data with MTRPs and two or more scheduling grants according to some embodiments of the present disclosure are shown; and

[0021] Figure 7 A flow diagram illustrating example methods of enhancing reliability of uplink transmissions using a signaling solution according to embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0022] Various example embodiments of the present solution are described below with reference to the accompanying drawings, to enable one of ordinary skill in the art to make and use the present solution. As would be obvious to one of ordinary skill in the art after reading this disclosure, various changes or modifications to the examples described herein can be made 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. Moreover, the specific order or hierarchy of steps in the methods disclosed herein are merely example methods. Based on the description herein, a person of ordinary skill in the art can rearrange the specific order or hierarchy of the steps of the disclosed methods or processes while remaining within the scope of the present solution. Therefore, one of ordinary skill 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 specifically stated otherwise.

[0023] The following abbreviations are used throughout this disclosure:

[0024]

[0025]

[0026]

[0027]

[0028] 1. Mobile communication technology and environment

[0029] Figure 1An example wireless communication network and / or system 100 in accordance with embodiments of the present disclosure is shown in which the techniques disclosed herein can be implemented. In the following discussion, the wireless communication network 100 can be any wireless network, such as a cellular network or a Narrowband Internet of Things (NB-IoT) network, and is referred to herein as the “network 100.” Such example networks 100 include base stations 102 (hereinafter “BS 102”; also referred to as wireless communication nodes) and user equipment 104 (hereinafter “UE 104”; also referred to as wireless communication devices) that can communicate with each other via communication links 110 (e.g., wireless communication channels), as well as cell groups 126, 130, 132, 134, 136, 138, and 140 that cover geographic areas 101. In Figure 1 In the example shown, the BS 102 and the UE 104 are contained within the respective geographic boundaries of the cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 can include at least one base station operating with its allocated bandwidth to provide sufficient radio coverage to its intended users.

[0030] For example, the BS 102 can operate under an allocated channel transmission bandwidth to provide sufficient coverage to the UE 104. The BS 102 and the UE 104 can communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, which can include data symbols 122 / 128. In the present disclosure, the BS 102 and the UE 104 are described herein as non-limiting examples of “communication nodes,” which can generally implement the methods disclosed herein. According to various embodiments of the present solution, such communication nodes can be capable of wireless and / or wired communication.

[0031] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) in accordance with some embodiments of the present solution is shown. The system 200 can include components and elements configured to support known or conventional operational features that need not be described in detail herein. In one illustrative embodiment, the 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 described above. Figure 1

[0032] ​The system 200 generally includes a base station 202 (hereinafter "BS 202") and a user equipment 204 (hereinafter "UE 204"). The BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each coupled and interconnected to each other as needed via a data communication bus 220. The UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each coupled and interconnected to each other as needed via a data communication bus 240. The BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.

[0033] As understood by one of ordinary skill in the art, the system 200 can also include any number of modules other than those shown. Those of skill in the art will appreciate that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality, without Figure 2 illustrative components, blocks, modules, circuits, and steps. Whether such functionality is implemented in hardware, firmware, or software depends on the particular application and design constraints imposed on the overall system. Skilled persons familiar with the concepts described herein can implement this functionality in an appropriate manner for each particular application, but such an implementation decision should not be interpreted as a limitation on the scope of the present disclosure.

[0034] According to some embodiments, the UE transceiver 230 can be referred to herein as an "uplink" transceiver 230, which includes radio frequency (RF) transmitters and RF receivers, each including circuitry coupled with the antennas 232. A duplex switch (not shown) can alternatively couple the uplink transmitters or receivers with the uplink antennas in a time duplexed manner. Similarly, according to some embodiments, the BS transceiver 210 can be referred to herein as a "downlink" transceiver 210, which includes RF transmitters and RF receivers, each including circuitry coupled with the downlink antennas 212. A downlink duplex switch can alternatively couple the downlink transmitters or receivers with the downlink antennas 212 in a time duplexed manner. The operation of the two transceiver modules 210 and 230 can be coordinated in time so that the uplink receiver circuitry is coupled with the uplink antennas 232 for receiving transmissions over the wireless transmission link 250 at the same time that the downlink transmitters are coupled with the downlink antennas 212. Conversely, the operation of the two transceivers 210 and 230 can be coordinated in time so that the downlink receiver is coupled with the downlink antennas 212 for receiving transmissions over the wireless transmission link 250 at the same time that the uplink transmitters are coupled with the uplink antennas 232. In some embodiments, there is a tight time synchronization with minimal guard time between changes in duplex direction.

[0035] The UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, in cooperation with appropriately configured RF antenna arrangements 212 / 232, which can support particular wireless communication protocols and modulation schemes. In some illustrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it will be appreciated that the present disclosure is not necessarily limited to application with particular standards and related protocols. Rather, the UE transceiver 230 and the base station transceiver 210 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0036] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. In some embodiments, UE 204 may be embodied in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized by a general-purpose processor, content-addressable memory, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, intended to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.

[0037] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly embodied in the hardware, firmware, or software modules executed by processor modules 214 and 236, or in any actual combination thereof. Memory modules 216 and 234 can be implemented as RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 can be coupled to processor modules 210 and 230, respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 can also be integrated into the respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include a cache for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0038] The network communications module 218 generally represents the hardware, software, firmware, processing logic and / or other components of the base station 202 that enable bi-directional communications 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 communications module 218 can be configured to support Internet or WiMAX traffic. In a typical deployment, the network communications module 218 provides an 802.3 Ethernet interface, without limitation, such that the base station transceiver 210 can communicate with a conventional Ethernet-based computer network. In this manner, the network communications module 218 can include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). The terms "configured to," "adapted to," and "arranged to," and their conjugations, as used herein with respect to a specified operation or function to be performed, refer to a device, component, circuit, structure, machine, signal, and / or the like that is physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0039] The Open Systems Interconnection (OSI) model (referred to herein as the "open systems interconnection model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) that are open for interconnection and communication with other systems. The model is divided into seven subcomponents or layers, each representing a conceptual set of services provided to and from the layers above and below. The OSI model also defines a logical network and effectively describes computer packet transmission by using different layer protocols. The OSI model can also be referred to as the seven-layer OSI model or seven-layer model. In some embodiments, the first layer can be a physical layer. In some embodiments, the second layer can be a medium access control (MAC) layer. In some embodiments, the third layer can be a radio link control (RLC) layer. In some embodiments, the fourth layer can be a packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer can be a radio resource control (RRC) layer. In some embodiments, the sixth layer can be a non-access stratum (NAS) layer or an internet protocol (IP) layer, and the seventh layer is other layers.

[0040] 2. Systems and methods for enhancing uplink transmission reliability

[0041] In a wireless communication system, two or more scheduling grants (e.g., downlink control information (DCI), higher layer configurations, and / or other information) of uplink channels can trigger, cause, and / or result in transmission of two or more uplink channels (e.g., physical uplink shared channels (PUSCHs) and / or other uplink channels). For example, two DCIs can trigger / cause / result in transmission of two corresponding PUSCHs. The two or more uplink channels can carry and / or include corresponding / same data blocks and / or separate / distinct data blocks. If the two or more scheduling grants cause transmission / scheduling of the same data blocks, the uplink channels can use the same data block size to carry / include the same data blocks. A wireless communication node (e.g., a ground terminal, a base station, a gNB, an eNB, a transmit-receive point (TRP), or a serving node) can receive and / or obtain the same data blocks to perform soft combining (or any other method of combining or integrating data from multiple transmissions to minimize / avoid incomplete information and / or errors). If the two or more scheduling grants cause transmission / scheduling of separate / distinct data blocks, the uplink channels can use separate / distinct data block sizes to carry / include the separate / distinct data blocks.

[0042] In some embodiments, a wireless communication device (e.g., a UE, a terminal, or a served node) can receive / obtain less than all of the two or more scheduling grants transmitted / transmitted by a wireless communication node. For example, blockage (e.g., blockage caused by physical entities, signal interference, and / or other sources of blockage) can cause the wireless communication device to receive one of two DCIs transmitted by the wireless communication node. In some embodiments, a wireless communication node can receive / obtain less than all of the two or more uplink channels transmitted / transmitted by a wireless communication device. For example, blockage can cause the wireless communication node to receive one of two PUSCHs transmitted by the wireless communication device.

[0043] The wireless communication node and the wireless communication device can extract, obtain, determine, and / or share the size of the one or more data blocks. The wireless communication device can send, transmit, provide, and / or broadcast a transport block indication of the uplink channel to the wireless communication node. The transport block indication of the uplink channel can inform and / or provide information of the size of the one or more data blocks. For example, if the size of the one or more data blocks of the uplink channel (e.g., PUSCH) is determined / specified / indicated by information of a scheduling grant (e.g., scheduling DCI), the wireless communication device can inform the wireless communication node via the transport block indication. The scheduling grant can be used to schedule the uplink channel. In another example, if the size of the one or more data blocks of the uplink channel (e.g., PUSCH) is determined / specified / indicated by information of a grant (not the scheduling grant itself, but associated with the scheduling grant), the wireless communication device can inform the wireless communication node via the transport block indication.

[0044] If the size of the one or more data blocks is determined / specified / indicated by the scheduling grant, the first uplink channel (e.g., first PUSCH carrying data blocks) can be distinguished from / independent of the second uplink channel (e.g., second PUSCH carrying separate data blocks). The first and / or second uplink channel can include / carry the one or more data blocks using separate / distinct data block sizes. If the size of the one or more data blocks is determined / specified / indicated by the grant associated with the scheduling grant, the first uplink channel (e.g., first PUSCH carrying data blocks) can carry and / or include the same one or more data blocks as the second uplink channel (e.g., second PUSCH carrying the same data blocks). The grant associated with the scheduling grant can be used to schedule the second uplink channel. The first and / or second uplink channel can include / carry the one or more data blocks using corresponding / equal data block sizes.

[0045] Reference is now made to Figure 3FIG. 3 depicts a representation 300 of an example downlink transmission utilizing multiple transmission-reception points (MTRPs) and a single scheduling grant (e.g., DCI). Certain systems can support transmissions using a single DCI and MTRPs. In one or more MTRP transmissions based on a single DCI, one or more wireless communication nodes can schedule one or more downlink channel transmissions (e.g., physical downlink shared channel (PDSCH) transmissions and / or other downlink channel transmissions) using one scheduling grant (e.g., DCI, radio resource control (RRC) signaling, and / or other indicator). For example, a PDSCH transmission from TRP0 and / or a PDSCH transmission from TRP1 can be scheduled using DCI0. Any of the one or more transmission-reception points (TRPs) can send / transmit / broadcast the scheduling grant (e.g., DCI, RRC signaling, and / or other grant). For example, TRP1 or TRP0 can send / transmit DCI0 to a wireless communication device. In some embodiments, two or more TRPs can send / transmit to a wireless communication device (e.g., UE 302) via one or more layers at a given time. For example, TRP0 and TRP1 can send / transmit to UE 302 via layer 0 and layer 1, respectively. In the case of ideal backhaul between two or more TRPs (e.g., TRP0 and TRP1), a single scheduling grant (e.g., DCI0 or another indicator) can provide and / or indicate information for scheduling downlink channel (e.g., PDSCH via one or more layers from both TRPs) transmissions. Downlink channel transmissions from a TRP can use at least two layers (e.g., layer 0, layer 1, and / or other layers). The at least two layers can be spatially multiplexed in the same physical time and / or frequency resources (e.g., the at least two layers can utilize a spatial division multiplexing (SDM) scheme).

[0046] Reference is now made to Figure 4FIG. 4 depicts a representation 400 of an example downlink transmission utilizing MTRP and a single scheduling grant (e.g., DCI). In some embodiments, one or more TRPs can transmit / broadcast one or more downlink channels (e.g., PDSCH or other downlink channels) to a wireless communication device (e.g., 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 UE 302 using TDM. In some embodiments, one or more downlink channels can include / carry (e.g., transport, communicate, convey) the same block of data and / or information. For example, PDSCH0 and PDSCH1 can include / carry the same block of data and / or information. In another example, PDSCH2 and PDSCH3 can include / carry the same block of data and / or information. A downlink channel (e.g., PDSCH) that includes / carries the same block of data can be referred to as a repetition occasion or a repetition transmission. A scheduling grant (e.g., DCI0) can provide / specify information for scheduling one or more downlink transmissions (e.g., PDSCH0, PDSCH1, PDSCH2, and / or PDSCH3) from one or more TRPs (e.g., TRP0 and / or TRP1). Any of the one or more TRPs can generate / transmit / provide the scheduling grant (e.g., DCI, RRC signaling, and / or other indicator). For example, TRP0 or TRP1 can generate / send / transmit DCI0. One or more wireless communication nodes can save / reduce the overhead (e.g., transmission, processing) related to DCI and / or improve / increase the transmission reliability of PDSCH transmissions by using a single DCI.

[0047] Carrier frequencies of a frequency range 2 (FR2) can exceed carrier frequencies of other frequency ranges. For example, carrier frequencies of FR2 can exceed carrier frequencies of a frequency range 1 (FR1) or other frequency ranges. In some embodiments, a blockage can occur in FR2 (or other frequency ranges). If a blockage occurs, the blockage can impact / impact / impede one or more transmissions from one or more TRPs. For example, the blockage can impact / impact / impede PDSCH (e.g., PDSCH0, PDSCH1, PDSCH2, and / or PDSCH3) transmissions from TRP0 and / or TRP1. If the blockage impacts / interrupts / impacts transmissions from one TRP, the wireless communication device can still receive / obtain / detect one or more complete transmissions from another TRP (e.g., a TRP not impacted by the blockage). For example, if the blockage impacts one or more transmissions from TRP0, the wireless communication device can receive one or more complete transmissions from TRP1 (e.g., the transmissions are repetition occasions). Thus, using MTRP can enhance / improve robustness of downlink channel transmissions (e.g., PDSCH transmissions) in FR2 (or other frequency ranges).

[0048] In some embodiments, a blockage can interrupt / impact a single scheduled grant (e.g., DCI) transmission from a wireless communication node (e.g., TRP). If the scheduled grant transmission is blocked, the wireless communication device can not be able to receive / obtain / decode a downlink channel transmission. For example, if a DCI0 transmission from TRP0 is blocked, the UE 302 can not be able to receive / decode PDSCH0 and / or PDSCH1 transmissions. A DCI (or other scheduled grant) can include / provide scheduling information for a PDSCH, such as time / frequency resource locations, a modulation and coding scheme (MCS), and / or other information. The wireless communication device / node can use the information provided / indicated / specified by the DCI for a downlink channel (e.g., PDSCH) transmission.

[0049] Reference is now made to Figure 5FIG. 5 depicts a representation 500 of an example downlink transmission utilizing MTRP and two or more scheduling grants (e.g., two or more DCIs). MTRP transmission based on multiple DCIs can be used to address scheduling grant transmission blocking. In some embodiments, two or more wireless communication nodes (e.g., TRPs) can each transmit / send at least one scheduling grant. For example, TRP0 and TRP1 can each send / transmit a DCI (e.g., DCI0 and DCI1, respectively). The scheduling grants (e.g., DCI0 and / or DCI1) can provide / specify information for scheduling downlink channel transmissions. For example, DCI0 and DCI1 can provide / specify information for scheduling PDSCH0 and PDSCH1, respectively. One or more scheduling grant transmissions from two or more TRPs can provide / specify information for scheduling separate / distinct downlink channel (e.g., PDSCH) transmissions. For example, DCI0 can provide / specify information for scheduling PDSCH0, which can be separate or distinct from PDSCH1. One or more values of a RRC parameter coresetPoolIndex-r16 (e.g., corresponding to a CORESET pool index or other parameter) can be used to configure / determine a scheduling grant (e.g., DCI). In some embodiments, one or more values of coresetPoolIndex-r16 can indicate / correspond to a particular TRP.

[0050] Using MTRP and multiple scheduling grants can enhance / improve reliability of downlink channel transmissions (e.g., PDSCH transmissions) in FR2 (or other frequency ranges). However, certain systems can not be able to provide similar enhancements / improvements for uplink channel (e.g., PUSCH or other uplink channel) transmissions. Transmission power of uplink channel transmissions can be less than transmission power of downlink channel transmissions. Thus, it can be difficult to ensure uplink coverage and / or reliability. Systems and methods presented herein include a novel approach for improving and / or increasing reliability of uplink channel transmissions via redundancy / duplication, such as at least 25% (e.g., 35%, 45%, or other percentage).

[0051] In some embodiments, utilizing MTRP and transmission of a single scheduling grant (e.g., DCI) can improve reliability of uplink data transmission. For example, one or more wireless communication devices can transmit two or more PUSCH repetitions using TDM and a single DCI (or other scheduling grant). In FR2, using analog beams can enable beamforming gain and / or compensate for large path loss. The narrow bandwidth of analog beams can result in the analog beams being very susceptible to being blocked by an entity (e.g., a human body). If the beam bandwidth is narrow, utilizing a single DCI and MTRP can be an ineffective approach. However, a wireless communication device can transmit / transmit / broadcast one or more uplink channels (e.g., PUSCHs) to one or more wireless communication nodes (e.g., TRPs). For example, a wireless communication device can transmit one or more PUSCHs via one or more beam directions using one or more analog beams. In some embodiments, a wireless communication node can transmit a single scheduling grant (e.g., DCI) using a single beam. If the single beam is blocked, the wireless communication device can not be able to receive / obtain the scheduling grant. As a result, the wireless communication device can not be able to transmit the intended repetitions (e.g., PUSCH repetitions).

[0052] Referring now to Figure 6 depicted is a representation 600 of an example uplink transmission utilizing MTRP and two or more scheduling grants (e.g., two or more DCIs). Two or more uplink channel transmissions (e.g., PUSCH transmissions) can carry / include the same block of data to improve and / or increase reliability of the uplink channel transmissions via redundancy / duplication. For example, PUSCH0 and PUSCH1 can carry / include the same block of data to increase reliability via redundancy / duplication.

[0053] A wireless communication node can receive / obtain uplink channel transmissions and perform soft combining on the received transmissions. Thus, two or more uplink channel transmissions (e.g., PUSCH0 and PUSCH1) can carry a same data block with a same / corresponding transport block size (TBS). For example, PUSCH0 and PUSCH1 can carry / include a data block with an equal / corresponding TBS. The wireless communication node can receive / obtain the transmissions and perform soft combining on PUSCH0 and PUSCH1. A scheduling grant (e.g., a scheduling DCI and / or higher layer configuration) can specify / provide / indicate scheduling information (e.g., a time resource amount, a frequency resource amount, an MCS, and / or other information). In some embodiments, the scheduling information can be used to determine the TBS. The wireless communication node can determine / identify / configure the TBS of an uplink channel transmission by using scheduling information provided by a corresponding scheduling grant (e.g., a corresponding DCI and / or higher layer configuration). For example, the wireless communication node can determine the TBS of PUSCH0 by using scheduling information provided by DCI0. In another example, the wireless communication node can determine the TBS of PUSCH1 by using scheduling information provided by DCI1.

[0054] Two or more scheduling grants (e.g., DCIs) can include / indicate / provide distinct and / or different scheduling information. For example, DCI0 can include / indicate scheduling information that is distinct from the scheduling information provided by DCI1. If the scheduling information of the scheduling grants is distinct / separate, the TBS of the uplink channel transmissions can be distinct / different. For example, DCI0 and DCI1 can specify / indicate separate scheduling information. Thus, the TBS of PUSCH0 and the TBS of PUSCH1 can be distinct / different as specified by the corresponding scheduling grants (e.g., DCI0 and DCI1, respectively). To ensure equal / corresponding TBS between two or more uplink channel transmissions, a scheduling grant corresponding to a first uplink transmission can be used to determine / configure the TBS of a second (or other) uplink transmission. For example, a wireless communication device can utilize a scheduling grant (e.g., DCI0) corresponding to PUSCH0 to determine / configure the TBS of PUSCH1. In another example, the wireless communication device can utilize DCI1 to determine / configure the TBS of PUSCH0. In this example, the wireless communication device can utilize the corresponding scheduling grant of an uplink transmission (e.g., PUSCH0) to determine other types of scheduling information (e.g., a frequency resource allocation, an antenna port indication, and / or other types of information). For example, the wireless communication device can utilize DCI1 to determine the TBS of PUSCH0 and utilize DCI0 to determine an antenna port indication.

[0055] In some embodiments, a wireless communication device can receive / obtain at least one (but less than the full amount) of two or more scheduling grants transmitted / transmitted by a wireless communication node (e.g., due to blocking). The wireless communication node can configure / activate / indicate the scheduling grants using independent / separate analog beams. A single analog beam can correspond to a transmission configuration indicator (TCI) state, a quasi co-location (QCL) configuration set, spatial relation information, and / or a sounding reference signal (SRS) indicator (SRI). In some embodiments, a wireless communication node can receive / obtain at least one (but less than the full amount) of two or more uplink transmissions from a wireless communication device (e.g., due to blocking). The wireless communication node and / or the wireless communication device can not be able to predict / anticipate the blocking (e.g., the blocking occurs randomly).

[0056] In some embodiments, a wireless communication node can transmit / transmit at least one (but less than the full amount) of two or more scheduling grants (e.g., DCI and / or higher layer configuration) to improve flexibility and / or capability. In some embodiments, one or more uplink channel transmissions can carry / include separate data blocks with separate transport block sizes. For example, PUSCH1 and PUSCH0 can carry / include distinct data blocks with separate transport block sizes (e.g., the PUSCH transmissions can represent / correspond to separate / distinct transmissions).

[0057] In some embodiments, one or more uplink channel transmissions can include / carry the same data block (e.g., the transmissions can have corresponding / equal TBS). Two or more scheduling grants can be associated if they are used to schedule two or more uplink transmissions that carry / include the same data block. For example, if DCI0 and DCI1 are used to schedule two PUSCHs that carry / include the same data block, they can be associated. The wireless communication node can inform / indicate / specify to the wireless communication device that the two or more scheduling grants (e.g., DCI and / or higher layer configuration) are associated / linked. For example, TRP0 and / or TRP1 can provide UE 302 with information indicating that DCI0 and DCI1 are associated.

[0058] A wireless communication node can provide / specify association information via an indicator, a scheduling grant, a message, a transmission, and / or other methods. For example, a wireless communication node can transmit / two or more DCIs (e.g., DCI0 and DCI1) carrying / including a same / associated hybrid automatic repeat request (HARQ) process number (or other indicator / number). Higher layer signaling (or other type of signaling) can configure and / or pre-determine whether the two or more HARQ process numbers are associated. A wireless communication device can receive / obtain the two or more DCIs (or other scheduling 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 including / carries a HARQ process number. The UE 302 can determine whether 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) scheduled with the DCIs are repetition transmissions. Thus, the wireless communication device can determine that the DCIs (e.g., DCI0 and DCI1) are associated. If the HARQ numbers are distinct / not equal, the wireless communication device can determine that the two or more uplink transmissions (e.g., PUSCH0 and PUSCH1) are distinct / independent (e.g., the DCIs are unassociated).

[0059] In some embodiments, a scheduling grant can be associated with a distinct / separate control resource set (CORESET) and / or coresetPoolIndex-r16 (or other higher layer signaling parameter). The coresetPoolIndex-r16 can indicate / specify / provide an index of a CORESET pool. Two or more scheduling grants associated with a separate CORESET and / or coresetPoolIndex-r16 can include / indicate / specify a same HARQ process number (e.g., the two or more scheduling grants can be associated). For example, DCI1 and DCI0 can carry / include a same HARQ process number, and each is associated with a separate CORESET. Thus, DCI1 and DCI0 can be associated / linked (e.g., the DCIs carry / include a same HARQ number). In some embodiments, a new number indicator (NDI) can provide information indicating / specifying whether two or more scheduling grants are associated. For example, two DCIs (or other scheduling grants) carrying / specifying / including a same NDI can be associated.

[0060] In some embodiments, misalignment / miscommunication can occur between a wireless communication node and a wireless communication device. Embodiments discussed herein are non-limiting examples describing alignment and / or misalignment scenarios.

[0061] Case 1: A wireless communication node can transmit / send two or more scheduling grants to schedule two or more repeated uplink transmissions (e.g., repetition occasions). A wireless communication device can receive / obtain the two or more scheduling grants.

[0062] • The wireless communication device can transmit / send / broadcast the two or more uplink transmissions using the same TBS. The wireless communication device can determine / configure the TBS with one of the two or more scheduling grants. For example, the wireless communication device can transmit PUSCH0 and PUSCH1 using the same TBS. The wireless communication device can determine the TBS with DCIO (or DCI1).

[0063] • The wireless communication node can receive / obtain / detect the uplink transmissions. The wireless communication node can determine that the TBS is configured based on information provided by one of the two or more scheduling grants.

[0064] Case 2: A wireless communication node can transmit / send a single scheduling grant to schedule a single uplink transmission. In some embodiments, the wireless communication node can transmit / send two or more scheduling grants to schedule independent / distinct / separate uplink channel transmissions.

[0065] • The wireless communication device can transmit / send one or more uplink transmissions using corresponding scheduling grants. The wireless communication device can determine a TBS for a particular uplink channel transmission based on the corresponding scheduling grant for the particular uplink channel transmission.

[0066] • The wireless communication node can receive / obtain / detect the one or more uplink transmissions. The corresponding scheduling grants can indicate / specify the TBS for the one or more uplink transmissions.

[0067] Case 3: A wireless communication node can send / transmit two or more scheduling grants to schedule two or more repeated transmissions (e.g., repetition occasions). Due to blocking, a wireless communication device can receive / obtain less than all of the two or more scheduling grants. In some embodiments, the wireless communication device can receive / obtain one of the two or more scheduling grants.

[0068] • The wireless communication device can receive / obtain at least one (but less than the full amount) of the two or more scheduled grants. The wireless communication device can determine / assume that Case 2 is occurring. The wireless communication device can transmit / send at least one (but less than the full amount) of the uplink transmissions. The wireless communication device can use the corresponding scheduled grant to determine the TBS of the at least one uplink transmission. For example, the wireless communication device can transmit PUSCH1 using the TBS indicated / specified by DCI1.

[0069] • In some embodiments, the wireless communication node can determine / assume that Case 1 is occurring. The wireless communication node can receive / obtain at least one uplink transmission under the assumption that the TBS is determined using the grant associated with the corresponding scheduled grant. For example, the wireless communication node can receive PUSCH1 under the assumption that the TBS is determined using DCI0. The wireless communication node can not receive PUSCH0, and thus determine that PUSCH0 is blocked. Misalignment can occur between the wireless communication node and the wireless communication device.

[0070] In some embodiments, the wireless communication device can send / transmit a transport block (TB) indication to the wireless communication node to determine information (e.g., TBS) of a scheduled uplink data transmission. The wireless communication device can report / indicate whether the TBS of the uplink transmission is determined using the corresponding scheduled grant. In some embodiments, the wireless communication device can report / indicate whether the TBS of the uplink transmission is determined using a grant associated with the scheduled grant (e.g., a grant associated with the scheduled grant). For example, the UE 302 can report / indicate whether the TBS of PUSCH0 is determined using the scheduling information of the corresponding scheduled DCI (e.g., DCI0). In another example, the UE 302 can report / indicate whether the TBS of PUSCH0 is determined using the scheduling information of a grant associated with the scheduled grant (e.g., DCI1).

[0071] In some embodiments, the wireless communication device can transmit / send / report / communicate / convey a TB indication. The TB indication can report / specify / indicate whether the TBS of the uplink channel transmission is determined using the scheduling information of the scheduled grant (e.g., DCI, higher layer configuration, or other grant). The TB indication can report / specify / indicate whether the TBS of the uplink channel transmission is determined using the scheduling information of a grant associated with the scheduled grant. The association between the scheduled grant and the one or more grants associated with the scheduled grant can indicate that the grants can schedule repeated transmissions of the same data block. The uplink transmission scheduled using the associated grant can be a repeated transmission (e.g., a repetition occasion).

[0072] The scheduling grant and the grant associated with the scheduling grant can be from different CORESETs and / or associated with different values of coresetPoolIndex-r16 (or CORESET pools). The beams (e.g., corresponding to TCI states and / or spatial relation information) can be configured on a per-CORESET basis. Thus, the scheduling grant and the grant associated with the scheduling grant can be from different CORESETs (or associated with different values of coresetPoolIndex-r16) to achieve beam diversity gain. In some embodiments, the scheduling grant and the grant associated with the scheduling grant can be from separate TRPs.

[0073] In some embodiments, the TB indication can specify whether the TBS of the uplink transmission is determined by using the scheduling grant or the grant associated with the scheduling grant. For example, the TB indication can specify / indicate that the TBS is determined by using the scheduling information of the scheduling grant. In another example, the TB indication can specify / indicate that the TBS is determined by using the scheduling information of the grant associated with the scheduling grant. If the TBS is determined by using the scheduling grant (e.g., the scheduling DCI), the uplink channel transmission can be independent / distinct from other uplink transmissions. For example, if the TBS of PUSCH0 is determined / configured by using DCI0, PUSCH0 can be independent / distinct from PUSCH1. In this example, the wireless communication device can schedule PUSCH1 by using the scheduling information of DCI1.

[0074] If the TBS is determined by using the grant associated with the scheduling grant (e.g., the associated DCI), the uplink channel transmission can be a repeated transmission (e.g., a repetition occasion) of another uplink channel transmission. For example, if the TBS of two PUSCHs is determined / configured by using DCI1, for example, PUSCH0 and PUSCH1 can be repeated transmissions. The wireless communication device can determine the TBS of the repeated transmissions by using the grant associated with the scheduling grant. The TBS of the repeated transmissions can be the same. If the uplink transmission is a repeated transmission, the scheduling grant and the grant associated with the scheduling grant can be associated / linked. The associated grants of the repeated transmissions can include / carry / specify the same / corresponding / associated HARQ process number / identifier (or other indicator). The associated grants can be from separate / different CORESETs and / or associated with separate / different values of coresetPoolIndex-r16. In some embodiments, the associated grants can include / carry / specify the same / corresponding / associated NDI. In some embodiments, the associated grants can include / carry / specify the same / corresponding / associated carrier indicator and / or bandwidth part indicator.

[0075] In some embodiments, an uplink channel transmission can carry, include, provide, and / or specify a TB indication. A higher layer configuration (e.g., RRC signaling, medium access control element (MAC-CE) signaling, or other configuration / signaling) can determine / indicate whether an uplink transmission (e.g., PUSCH) includes a TB indication. The higher layer configuration can be configured per CORESET, search space (SS), and / or CORESET pool (e.g., per coresetPoolIndex-r16 and / or TRP). A wireless communication node can schedule an uplink transmission using a scheduling grant (e.g., DCI) associated with a CORESET, SS, or TRP. The uplink channel transmission can carry / include a TB indicator to report / specify / indicate whether the uplink channel transmission is a repetition transmission. For example, if a PUSCH is scheduled by a DCI associated with a CORESET, SS, or TRP configured with a TB indication, the PUSCH can carry / include a TB indication. The PUSCH can carry a TB indication to indicate / specify that the TBS of the PUSCH is based on the scheduling DCI or a DCI associated with the scheduling DCI. If the PUSCH is scheduled by a DCI associated with a CORESET, SS, or TRP not configured with a TB indication, the indicator can be excluded from the PUSCH. The TBS of the PUSCH can be based on the scheduling DCI, rather than another DCI. In some embodiments, the higher layer signaling can include RRC signaling or MAC-CE signaling.

[0076] A wireless communication node and / or device can utilize the TB indicator to determine / specify the TBS. Thus, a wireless communication device can transmit / send the TB indicator only when the value of an uplink shared channel indicator (UL-SCH) of a scheduling grant (e.g., DCI) is 1. The TB indication can be used to determine the data block size. Thus, the TB indication can only exist when the value of the UL-SCH (uplink shared channel and / or UL data) indicator in the DCI is 1. The UL-SCH can include one or more bits. If the value of the UL-SCH is 1, the uplink channel transmission can include / indicate / specify the UL-SCH. If the value of the UL-SCH is 0, the uplink channel transmission can exclude the UL-SCH.

[0077] DCI can be used to schedule uplink channel transmissions (e.g., PUSCH). In some embodiments, RRC configuration (or RRC signal) can determine, indicate, and / or specify scheduling of semi-persistent uplink channel transmissions (e.g., semi-persistent PUSCH occasions). Accordingly, the systems and methods disclosed herein can be utilized for PUSCH transmissions scheduled using RRC configuration. In some embodiments, RRC configuration can replace / substitute DCI. Independent / separate beams can configure, activate, and / or indicate PUSCH transmissions scheduled using at least two grants (e.g., DCI and / or RRC configuration).

[0078] A. Mapping TB indicator to uplink channel transmission

[0079] A wireless communication node can receive / obtain a TB indication from a wireless communication device. The wireless communication node can decode the received TB indication to determine a TBS of an uplink channel. The wireless communication device can utilize information provided by the decoded TB indication to decode the uplink channel. In some embodiments, the uplink channel can carry / include the TB indication. The wireless communication device can transmit / transmit the TB indication of the uplink channel with UL-SCH using at least one procedure of uplink control information (UCI) transmission. The UCI can include at least one of HARQ acknowledgement (HARQ-ACK), channel state information (CSI) part 1, and / or CSI part 2. In some embodiments, the wireless communication device can transmit the TB indication using at least one of code block segmentation, cyclic redundancy check (CRC) attachment, channel coding, rate matching, code block concatenation, and / or multiplexing of coded UCI bits to PUSCH. Embodiments discussed herein are non-limiting examples describing options or implementations of mapping TB indicator to uplink channel (e.g., PUSCH).

[0080] • Option 1: The wireless communication device can transmit / transmit the TB indication using HARQ-ACK multiplexed on the uplink channel with UL-SCH utilizing the uplink channel. Channel coding and / or resource element (RE) mapping can follow / imitate / adopt one or more specific procedures of HARQ-ACK.

[0081] • Option 1-1: If the uplink channel (e.g., PUSCH) includes HARQ-ACK, one or more HARQ-ACK bits can include or correspond to the TB indication. In some embodiments, an offset value may include or correspond to the TB indication. The wireless communication device can configure the offset value to determine a number of resources used to multiplex HARQ-ACK information in the uplink channel. For example, in a bit sequence a0, a1, a2, a3,..., a A-1In this example, bit a0 can include or correspond to a TB indication. In this example, bits a1 to a A-1 may include or correspond to HARQ-ACK bits. In another example, bits a A-1 may include or correspond to a TB indication, while the remaining bits correspond to HARQ-ACK bits. One or more bits of the bit sequence can include or correspond to a TB indication. Other bits (e.g., a1, a2, and / or other bits) in the bit sequence can include or correspond to a TB indication.

[0082] ■If the uplink channel with UL-SCH excludes HARQ-ACK, the TB indicator can include or correspond to one or more HARQ-ACK bits. An offset value can be used for the TB indication transmission via the uplink channel with UL-SCH. The offset value may be defined for the wireless communication device to determine the number of resources used to multiplex HARQ-ACK information in PUSCH. The offset value may be used for the TB indication.

[0083] ■Option 1-2: If the uplink channel (e.g., PUSCH) includes HARQ-ACK, the TB indication can be mapped / placed / configured before or after (e.g., adjacent or contiguous to) one or more ACK / NACK bits. The wireless communication device can configure an offset value to determine the number of resources used to multiplex TB indication information in the uplink channel. One or more higher layer configurations (e.g., RRC signaling, MAC CE signaling, and / or other types of signaling) can determine / configure / define the offset value. The TB indication and HARQ-ACK can be separately channel coded. For example, in a coded bit sequence g0g1,..., g G-2 g G-1 , in this example, bits g0g1may include or correspond to TB indication coded bits. In this example, the remaining bits correspond to HARQ-ACK coded bits. In another example, bits g G-2 g G-1 may include or correspond to TB indication coded bits, and the remaining bits correspond to HARQ-ACK coded bits. One or more bits of the coded bit sequence can include or correspond to TB indication coded bits.

[0084] ■If the uplink channel with UL-SCH excludes HARQ-ACK, one or more RE mapping rules can follow / imitate one or more RE mapping rules of HARQ-ACK. Higher layer signaling (e.g., RRC, MAC CE, and / or other signaling) can configure / define / determine an offset value. In some embodiments, a scheduling grant (e.g., DCI) can indicate / specify the offset value.

[0085] The modulation REs for TB indication can be mapped / placed after the first symbol carrying / specified with a demodulation reference signal (DMRS). If intra-slot PUSCH frequency hopping is enabled, the modulation resource elements (REs) for transport block indication can be mapped after the first symbol carrying DMRS in the frequency hopping of the uplink channel.

[0086] In some embodiments, in the above solutions, the HARQ-ACK can be replaced by CSI part 1 and / or CSI part 2.

[0087] • Option 2: The wireless communication device can utilize the uplink channel to send / transmit the TB indication using the CSI part 1 transmission procedure on the uplink channel with UL-SCH. The channel coding and / or RE mapping can follow / imitate one or more procedures of the CSI part 1.

[0088] • Option 2-1: If the uplink channel (e.g., PUSCH) includes CSI part 1, one or more bits of the CSI part 1 can include or correspond to the TB indication. The TB indication can be mapped / linked before or after the CSI part 1 bits. The wireless communication device can configure an offset value to determine the number of resources used to multiplex the CSI part 1 information in the uplink channel. The offset value can include or correspond to the TB indication.

[0089] • 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 one or more bits of the CSI part 1. One or more higher layer configurations (e.g., RRC signaling, MAC CE signaling, and / or other types of signaling) can determine / configure / define the offset value. In some embodiments, the scheduling grant (e.g., DCI) can indicate / specify the offset value.

[0090] • Option 3: The wireless communication device can utilize the uplink channel to send / transmit the TB indication using the CSI part 2 transmission procedure on the uplink channel with UL-SCH. The channel coding and / or RE mapping can follow / imitate / adopt one or more specific procedures of the CSI part 2.

[0091] • Option 3-1: If the uplink channel (e.g., PUSCH) includes CSI part 2, one or more bits of the CSI part 2 can include or correspond to the TB indication. The TB indication can be mapped / linked before or after the CSI part 2 bits. The wireless communication device can configure an offset value To determine the number of resources for multiplexing CSI part 2 information in an uplink channel. The offset value can include or correspond to the TB indication.

[0092] 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 one or more bits of the CSI part 2. One or more higher layer configurations (e.g., RRC signaling, MAC CE signaling, and / or other types of signaling) can determine / configure / define the offset value. In some embodiments, a scheduling grant (e.g., DCI) can indicate / specify the offset value.

[0093] In some embodiments, the modulated REs of the TB indication can be mapped / placed starting from the first symbol of the uplink channel that does not carry DMRS. If intra-slot PUSCH frequency hopping is enabled, in a frequency hop of the uplink channel, the modulated resource elements (REs) for the transport block indication can be mapped starting from the first symbol of the uplink channel that excludes / omits DMRS.

[0094] B. Methods of Enhancing Uplink Transmission Reliability

[0095] Figure 7 A flow diagram illustrating a method 750 of enhancing uplink transmission reliability is shown. The method 750 can be implemented using any components and apparatus detailed herein in connection with Figure 1 -6. The method 750 can include receiving a scheduling grant (752). The method 750 can include transmitting an uplink channel (754). The method 750 can include determining whether a value of a UL-SCH indicator is 1 (756). The method 750 can include transmitting a transport block indication (758). The method 750 can include omitting the transport block indication (760).

[0096] Referring now to operation (752), and in some embodiments, a wireless communication device (e.g., terminal node or UE) can receive and / or obtain a scheduling grant from a wireless communication node (e.g., base station or gNB). The wireless communication node can generate / send / transfer / broadcast the scheduling grant to the wireless communication device. For example, the UE 302 can receive / obtain one or more scheduling grants from one or more TRPs (e.g., TRP0 and / or TRP1). The wireless communication node can use a downlink channel (e.g., PDCCH) and / or other types of channels to send / transfer the scheduling grant. The scheduling grant can include downlink control information (DCI), higher layer configuration, and / or other indicators / configuration for scheduling an uplink channel. The higher layer configuration can include RRC signaling, MAC CE signaling, and / or other types of signaling. The scheduling grant can support transmission of an uplink / downlink channel (e.g., DL-SCH, UL-SCH, and / or other channels). The scheduling grant can include / provide resource allocation information, one or more modulation and coding schemes, transmission power information, HARQ number / indicator information, precoding information, and / or other types of information.

[0097] Referring now to operation (754), and in some embodiments, the wireless communication device can transfer and / or send an uplink channel to the wireless communication node. The uplink channel can include a physical uplink shared 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 a UE 302. In some embodiments, the wireless communication device can configure the uplink channel transfer with the scheduling grant. For example, the UE 302 can configure the transfer of the PUSCH0 with the information provided by the DCI0. The wireless communication device can configure the uplink channel transfer with the TBS information indicated / provided by the scheduling grant. In some embodiments, the wireless communication device can send / transfer the uplink channel in response to receiving the scheduling grant.

[0098] Referring now to operation (756), and in some embodiments, the wireless communication device may determine whether the value of the UL-SCH indicator is 1. A scheduling grant may include / include / specify / carry the UL-SCH indicator and / or other indicators. Before transmitting the TB indicator, the wireless communication device may determine whether the value of the UL-SCH indicator (or other indicator) is 1. For example, the wireless communication device may receive a scheduling grant (e.g., DCI0) from a wireless communication node. In response to receiving the scheduling grant, the wireless communication device may determine whether the value of the UL-SCH indicator included in the scheduling grant is 1. If the value of the UL-SCH indicator is 1 (e.g., indicating the presence of data for transmission), the wireless communication device may transmit / send the UL-SCH and / or TB indicator using an uplink channel (e.g., PUSCH0). In another example, if the value of the UL-SCH indicator is 0, the wireless communication device may exclude / omit the UL-SCH and / or TB indicator from the uplink transmission. Other values ​​distinct from 0 or 1 may be used to indicate the inclusion or exclusion of the UL-SCH and / or TB indicator in the uplink transmission. The TB indicator can indicate / specify the TBS information transmitted on the uplink channel.

[0099] Referring now to operation (758), and in some embodiments, the wireless communication device can transmit / configure / generate a Transport Block (TB) indication. The wireless communication device can transmit the TB indication in response to determining that the value of a UL-SCH indicator is 1. For example, the wireless communication device can determine that the value of a UL-SCH indicator included in a scheduling grant is 1. In response to this determination, the wireless communication device can transmit the TB indication to a wireless communication node. Thus, the wireless communication node can receive / obtain the TB indication from the wireless communication device. A scheduling grant value of 1 indicates that uplink data is available for transmission. The wireless communication device can transmit / transmit the TB indication and the uplink channel separately. For example, the wireless communication device can transmit / transmit the TB indication (e.g., via message, transmission, or signal) without using PUSCH transmission.

[0100] Referring now to operation (760), and in some embodiments, the wireless communication device may omit / skip the transmission / configuration / generation of the TB indication. In response to determining that the UL-SCH indicator has a value different from 1, the wireless communication device may omit / bypass / skip the TB indication. For example, the wireless communication device may determine that the value of the UL-SCH indicator included in the scheduling authorization is 0. In response to this determination, the wireless communication device may omit / exclude (e.g., not merge) the TB indication from uplink transmissions to the wireless communication node. The wireless communication node may receive uplink transmissions without the TB indication. A scheduling authorization value of 0 may indicate that uplink data is not available for transmission.

[0101] The TB indication can indicate / specify whether a TB of an uplink channel is determined from information of a scheduling grant and / or from information of a grant associated with the scheduling grant. For example, the TB indication can indicate whether a TBS of PUSCH0 is determined from DCI0 or DCI1. The information of the grant can include an amount of time resources, an amount of frequency resources, a modulation and coding scheme, and / or other information. The wireless communication device can schedule the repeated transmissions of the uplink channel using the scheduling grant and / or the grant associated with the scheduling grant. The wireless communication device can schedule the repeated transmissions of the same block of data using the scheduling grant and / or the grant associated with the scheduling grant. For example, the wireless communication device can schedule the repeated transmissions of PUSCH with DCI0 or DCI1. The association between the grants can indicate / specify that two or more uplink transmissions are repeated transmissions (e.g., the uplink transmissions have the same TBS). For example, if DCI1 and DCI0 are associated with each other, the association can indicate that PUSCH0 and PUSCH1 are repeated transmissions.

[0102] In some embodiments, the wireless communication device can receive / obtain a higher layer configuration (e.g., RRC signaling, MAC CE signaling, and / or other types of signaling) to transmit a TB indication in an uplink channel. In some embodiments, the wireless communication device can utilize the higher layer configuration to determine whether the TB indication is included in the uplink channel. The wireless communication node can transmit / send the higher layer configuration to the wireless communication device. Thus, the wireless communication node can configure / indicate / specify whether the TB indication is included in the uplink channel. The wireless communication device can transmit / send the TB indication according to the higher layer configuration. For example, the RRC signaling can specify that the TB indication is included in the uplink channel. Thus, the wireless communication device can transmit / send the TB indication using the uplink channel. The wireless communication node can receive / obtain the TB indication according to the higher layer configuration. For example, the wireless communication node can transmit / send the higher layer configuration to the wireless communication device that specifies that the TB indication is excluded. Thus, the wireless communication node can receive / obtain the uplink channel transmission without the TB indication. The higher layer configuration can be configured / determined based on each CORESET, SS, and / or CORESET pool.

[0103] A wireless communication device can transmit / send a TB indication in an uplink channel using (e.g., employ, adjust) at least one procedure of UCI on PUSCH. These procedures can include code block segmentation, CRC attachment, channel coding, rate matching, code block concatenation, multiplexing of coded UCI bits to PUSCH, and / or other procedures. The UCI can include / contain at least one of HARQ-ACK, CSI part 1, or CSI part 2. In some embodiments, a wireless communication node can receive / obtain a TB indication in an uplink channel using at least one of the UCI procedures on PUSCH. For example, one or more mechanisms of UCI code block segmentation, CRC attachment, channel coding, rate matching, code block concatenation, and / or multiplexing of coded UCI bits can be reused or adapted for the TB indication. In some embodiments, 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 arranged before or after the sequence of UCI bits. In some embodiments, one or more coded bits of the TB indication can be arranged / placed / mapped adjacent to the sequence of UCI bits. For example, the coded bits of the TB indication can be arranged before and / or after the sequence of UCI bits. The coded bits of the TB indication can look distinct, but can be arranged adjacent to the sequence of UCI bits.

[0104] In some embodiments, a wireless communication node can configure / activate / indicate a scheduling grant and / or a grant associated with a scheduling grant with independent / separate / distinct TCI state(s). Thus, a scheduling grant and / or a grant associated with a scheduling grant can be associated / linked with independent TCI state(s). For example, a TRP can configure / activate / indicate DCI0 and / or DCI1 with independent TCI state(s). In some embodiments, a single analog beam can correspond to a single TCI state. A scheduling grant and / or a grant associated with a scheduling grant can be from different CORESETs. For example, DCI0 and DCI1 (associated with DCI0) can be from different CORESETs. A scheduling grant and / or a grant associated with a scheduling grant can be associated with different values of a coresetPoolIndex-r16 parameter. For example, two related grants (e.g., DCI0 and DCI1) can be from different CORESETs and / or associated with different values of a coresetPoolIndex-r16 parameter (or other parameter). In some embodiments, a scheduling grant and / or a grant associated with a scheduling grant can indicate / specify / include the same HARQ process number / identifier or other number / identifier. A scheduling grant and / or a grant associated with a scheduling grant can indicate / specify / include the same NDI and / or other indicator. For example, if two DCIs are associated, the DCIs can indicate / specify the same HARQ process number and / or NDI (or other number / indicator). In some embodiments, two or more scheduling grants from separate / distinct CORESETs (or associated with distinct values of a coresetPoolIndex-r16) can indicate / specify / include the same HARQ process number, NDI, and / or other number / indicator.

[0105] In some embodiments, an offset value can be defined for a wireless communication device. The offset value can be used to determine a number of resources for multiplexing TB indication in an uplink channel. The offset value can be used to determine a number of resources for multiplexing UCI and / or TB indication information in an uplink channel. The offset value can be configured / determined via higher layer configuration (e.g., RRC signaling, MAC CE signaling, and / or other types of signaling). In some embodiments, the offset value can be indicated / specified by a scheduling grant (e.g., DCI). An uplink channel (e.g., PUSCH) can contain / include two or more frequency hops. Each frequency hop can be scheduled via one or more frequency resources. A frequency hop of an uplink channel can contain / include modulated resource elements (REs) for TB indication. In some embodiments, the modulated REs can be mapped / associated after a first symbol carrying DMRS. In some embodiments, the modulated REs can be mapped / associated starting from a first symbol of an uplink channel that does not carry DMRS.

[0106] While various embodiments of the present solution have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various figures can depict example architectures or configurations, which can employ example hardware, software, circuits, and / or processes to implement one or more embodiments of the solution. However, those skilled in the art will appreciate that the solution is not limited to the example architectures or configurations depicted in the figures, but can be implemented using any other suitable architectures or configurations. Additionally, the features of one embodiment can be combined with features of another embodiment. Furthermore, the various embodiments can be implemented using any of a wide variety of programming languages, tools, and / or platforms. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described example embodiments.

[0107] It should also be understood that any reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” It should be understood that where the terms “comprising,” “including,” “containing,” etc. are used, they are intended to be equivalent to the term “including” and therefore do not exclude the presence of elements other than those listed. It should also be understood that, as used herein, “and / or” means “and” or “or” and / or “and” and “or.”

[0108] In addition, those skilled in the art will appreciate that any of a wide variety of different technologies and processes can be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols discussed above can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0109] Those skilled in the art will further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a number of logic circuits, an application- specific integrated circuit, a field programmable gate array, etc.), firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as “software” or a “software module”), or any combination thereof. To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality, while the specific illustrations above have tended to emphasize their structural implementations. The illustrative examples above, however, are non-limiting. Departures from specific design details of the illustrative examples can be made without departing from the scope of the disclosure. Those skilled in the art will appreciate that the described functionality can be implemented in any combination of hardware, firmware or software, and that the described functionality can be implemented at least in part as one or more software programs that operate on one or more computer system components or devices.

[0110] Furthermore, those of ordinary skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithms described herein can be implemented or performed with an integrated circuit (IC), which includes a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, or a combination of these or any other suitable device. The logical blocks, modules, and circuits can further include antennas and / or transceivers to communicate in or with various components within a network or device. The general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0111] If implemented in software, the functions can be stored on or transmitted over 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 with software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program or code from one place to another. Storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise 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 that can be accessed by a computer. Also, functional computer- readable media that stores program code in a modulated data signal, such as carrier waves or other transport mechanism, can be utilized. The modulated data signal is created by

[0112] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements that is used to implement the relevant functionality described herein. Furthermore, various modules described herein can be comprised of programming means for implementing the associated functionality; such programming means can be comprised of one or more software applications, routines or other code. Still further, a number of these modules can be combined into a single module to perform the described functionality.

[0113] Furthermore, in embodiments of the present solution, memories or other storage, as well as communication components can be employed. It should be appreciated that, for clarity, the above description has described embodiments of the present solution with reference to different functional units and processors. However, it will be apparent that any appropriate distribution of functionality between different functional units, processing logic elements or domains can be used without affecting the scope of the present solution. For example, functionality illustrated to be performed by separate processing logic elements or controllers can be performed by the same processing logic element or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

[0114] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other embodiments without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the novel features and principles disclosed herein and made apparent to others skilled in the art from the teachings herein when taken in conjunction with the foregoing description.

Claims

1. A wireless communication method, comprising: The wireless communication device receives the uplink channel scheduling authorization from the wireless communication node; The uplink channel is transmitted from the wireless communication device to the wireless communication node; as well as The wireless communication device transmits a transport block indication (TBS) to the wireless communication node for determining the transport block size (TBS) of the uplink channel. The TBS indicates whether the TBS of the uplink channel is determined based on the scheduling grant information or on scheduling grant information associated with the scheduling grant. The scheduling grant and the scheduling grant associated with the scheduling grant are two independent control signaling messages. The transmission of the uplink channel from the wireless communication device to the wireless communication node includes: scheduling the same data block using the scheduling grant and the scheduling grant associated with the scheduling grant.

2. The method according to claim 1, wherein, The scheduling authorization includes downlink control information (DCI) or higher-layer configuration for scheduling the uplink channel.

3. The method according to claim 1, wherein, The scheduling authorization and the scheduling authorization associated with the scheduling authorization are configured, activated or indicated using a separate Transport Configuration Indicator (TCI) state.

4. The method according to claim 1, wherein, The scheduling grants and the scheduling grants associated with the scheduling grants come from different control resource sets CORESET, or are associated with different values ​​of the coresetPoolIndex-r16 parameter.

5. The method according to claim 1, wherein, The scheduling grant and the scheduling grant indication associated with the scheduling grant are the same Hybrid Automatic Repeat Request (HARQ) process number or identifier, or the same New Number Indicator (NDI).

6. The method according to claim 1, comprising: The higher-level configuration is received by the wireless communication device; as well as The wireless communication device transmits a transport block indication in the uplink channel to the wireless communication node according to the higher-layer configuration, wherein the higher-layer configuration is configured based on each CORESET, each search space SS, or each CORESET pool.

7. The method of claim 1, further comprising transmitting the transport block indication from the wireless communication device to the wireless communication node if the value of the uplink shared channel UL-SCH indicator is 1.

8. The method of claim 1, comprising transmitting a transport block indication in the uplink channel using at least one of the following procedures of uplink control information UCI on the Physical Uplink Shared Channel (PUSCH): code block segmentation, cyclic redundancy check (CRC) attachment, channel coding, rate matching, code block concatenation, or multiplexing of UCI bits encoded into the PUSCH, wherein the UCI includes at least one of Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK), Channel State Information (CSI) Part 1, or CSI Part 2.

9. The method according to claim 1, wherein, An offset value defined for the wireless communication device for determining the number of resources used to multiplex uplink control information (UCI) in the uplink channel is used to determine the number of resources used to multiplex transport block indications in the uplink channel.

10. The method according to claim 1, wherein, The offset value defined for the wireless communication device for determining the number of resources used to multiplex transport block indication information in the uplink channel is configured via higher-layer configuration or indicated by the scheduling authorization.

11. The method according to claim 1, wherein, One or more bits indicated by the transport block are arranged as a sequence of adjacent uplink control information (UCI) bits.

12. The method according to claim 1, wherein, One or more coded bits indicated by the transport block are arranged adjacent to the coded bits used for uplink control information (UCI).

13. The method according to claim 1, wherein, In frequency hopping of the uplink channel, the modulation resource element (RE) for the transport block indication is mapped after the first symbol carrying the demodulation reference signal (DMRS), or is mapped starting from the first symbol of the uplink channel that does not carry the DMRS.

14. A wireless communication method, comprising: Scheduling authorization for uplink channels transmitted from wireless communication nodes to wireless communication devices; The uplink channel is received by the wireless communication node from the wireless communication device; as well as The wireless communication node receives from the wireless communication device a transport block indication (TBS) for determining the transport block size (TBS) of the uplink channel. The TBS indicates whether the TBS of the uplink channel is determined based on the scheduling grant information or on scheduling grant information associated with the scheduling grant. The scheduling grant and the scheduling grant associated with the scheduling grant are two independent control signaling messages. The scheduling authorization and the scheduling authorization associated with the scheduling authorization are used to schedule the same data block.

15. The method according to claim 14, wherein, The scheduling authorization includes downlink control information (DCI) or higher-layer configuration for scheduling the uplink channel.

16. The method of claim 14, wherein, The scheduling authorization and the scheduling authorization associated with the scheduling authorization are configured, activated or indicated using a separate Transport Configuration Indicator (TCI) state.

17. The method of claim 14, wherein, The scheduling grants and the scheduling grants associated with the scheduling grants come from different control resource sets CORESET, or are associated with different values ​​of the coresetPoolIndex-r16 parameter.

18. The method according to claim 14, wherein, The scheduling grant and the scheduling grant indication associated with the scheduling grant are the same Hybrid Automatic Repeat Request (HARQ) process number or identifier, or the same New Number Indicator (NDI).

19. The method of claim 14, comprising: Higher-level configuration is transmitted by the wireless communication node; as well as The wireless communication node receives a transport block indication in the uplink channel from the wireless communication device according to the higher-layer configuration, wherein the higher-layer configuration is configured based on each CORESET, each search space SS, or each CORESET pool.

20. The method of claim 14, further comprising receiving the transport block indication from the wireless communication device by the wireless communication node if the value of the uplink shared channel UL-SCH indicator is 1.

21. The method of claim 14, comprising receiving a transport block indication in the uplink channel using at least one of the following procedures for uplink control information (UCI) on the Physical Uplink Shared Channel (PUSCH): code block segmentation, cyclic redundancy check (CRC) attachment, channel coding, rate matching, code block concatenation, or multiplexing of UCI bits encoded into the PUSCH, wherein the UCI includes at least one of Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK), Channel State Information (CSI) Part 1, or CSI Part 2.

22. The method according to claim 14, wherein, An offset value defined for the wireless communication device for determining the number of resources used to multiplex uplink control information (UCI) in the uplink channel is used to determine the number of resources used to multiplex transport block indications in the uplink channel.

23. The method according to claim 14, wherein, The offset value defined for the wireless communication device for determining the number of resources used to multiplex transport block indication information in the uplink channel is configured via higher-layer configuration or indicated by the scheduling authorization.

24. The method according to claim 14, wherein, One or more bits indicated by the transport block are arranged as a sequence of adjacent uplink control information (UCI) bits.

25. The method according to claim 14, wherein, One or more coded bits indicated by the transport block are arranged adjacent to the coded bits used for uplink control information (UCI).

26. The method according to claim 14, wherein, In frequency hopping of the uplink channel, the modulation resource element (RE) for the transport block indication is mapped after the first symbol carrying the demodulation reference signal (DMRS), or is mapped starting from the first symbol of the uplink channel that does not carry the DMRS.

27. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1-26.

28. A wireless communication device, comprising: A memory and at least one processor, the at least one processor being configured to read instructions from the memory to implement the method according to any one of claims 1-26.

Images