PUSCH resource allocation method using multiple TRPs

Abstract

Physical uplink shared channel (PUSCH) resource allocation with multiple TRPs is provided. The embodiments described herein provide details for facilitating multiple transmission / reception point (TRP) transmissions on the PUSCH for user equipment (UE) implementation and application scenarios. The spacing between consecutive PUSCH transmission instances towards different TRPs (e.g., transmissions associated with different spatial transmit filters) can be signaled semi-statically or dynamically. In the case of dynamic signaling, the spacing can be configured in the time domain resource allocation (TDRA) table and indicated in the downlink control information (DCI). In the case of semi-static signaling, it can be accomplished through radio resource control (RRC).

Description

[0001] Related applications

[0002] This application claims the benefit of provisional patent application (Serial No. 63 / 003695) filed on April 1, 2020, the disclosure of which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present disclosure relates to shared channel resource allocation employing multiple transmit / receive points (TRPs). Background Art

[0004] NR frame structure and resource grid

[0005] New Radio (NR) uses cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) in both the downlink (DL) (e.g., from a network node, gNB, or other base station to a user equipment (UE)) and uplink (UL) (e.g., from a UE to a gNB). Discrete Fourier transform (DFT)-spread orthogonal frequency division multiplexing (OFDM) is also supported in the UL. In the time domain, NR DL and UL are organized into equally sized subframes, each lasting 1 millisecond (ms). A subframe is further divided into multiple slots of equal duration. The slot length depends on the subcarrier spacing. For a subcarrier spacing of Δf = 15 kilohertz (kHz), there is only one slot per subframe, and each slot consists of 14 OFDM symbols.

[0006] Figure 1 The following is a schematic diagram of the time domain structure for data scheduling in NR. Data scheduling in NR is usually based on time slots. Figure 1 The first two symbols contain the Physical DL Control Channel (PDCCH), while the remaining symbols contain the Physical Shared Data Channel (Physical DL Shared Channel (PDSCH) or Physical UL Shared Channel (PUSCH)).

[0007] Different subcarrier spacing values ​​are supported in NR. The supported subcarrier spacing values ​​(also called different numerologies) are given by Δf=(15×2 μ )kHz, where μ∈{0,1,2,3,4}. Δf=15kHz is the basic subcarrier spacing. The time slot duration at different subcarrier spacings is given by Given.

[0008] Figure 2This is a schematic block diagram of the physical time-frequency resource grid used for data scheduling in NR. In the frequency domain, the system bandwidth is divided into resource blocks (RBs), where each RB corresponds to 12 contiguous subcarriers. RBs are numbered starting from 0 at one end of the system bandwidth. In the illustrated basic NR physical time-frequency resource grid, only one RB within a 14-symbol slot is shown. One OFDM subcarrier during one OFDM symbol interval forms one resource element (RE).

[0009] In NR Release 15 (Rel-15), UL data transmission can be dynamically scheduled using the PDCCH. The UE first decodes the UL grant in the PDCCH and then transmits data over the PUSCH based on the control information (such as modulation order, coding rate, UL resource allocation, etc.) decoded in the UL grant.

[0010] In the dynamic scheduling of PUSCH, there is also the possibility of using configured grants (CGs) to configure semi-persistent transmission of PUSCH. Two types of CG-based PUSCH are defined in NR Rel-15. In CG type 1, the periodicity and time domain offset of PUSCH transmission are configured by radio resource control (RRC). In CG type 2, the periodicity of PUSCH transmission is configured by RRC and the activation and release of such transmission are then controlled by DL control information (DCI) (e.g., using PDCCH).

[0011] In NR, it is possible to schedule PUSCH with time repetition via the RRC parameters pusch-AggregationFactor (for dynamically scheduled PUSCH) and repK (for PUSCH with UL CG). In this case, PUSCH is scheduled but transmitted in multiple adjacent slots (if slots are available for UL) until the number of repetitions is reached as determined by the configured RRC parameters.

[0012] In the case of PUSCH with UL CG, when repetition is used, the redundancy version (RV) sequence to be used is configured by the repK-RV field. If repetition is not used for PUSCH with UL CG, the repK-RV field does not exist.

[0013] In NR Rel-15, there are two supported mapping types applicable to PDSCH and PUSCH transmissions, Type A and Type B. Type A is often referred to as slot-based while Type B transmissions may be referred to as non-slot-based or mini-slot-based.

[0014] Mini-slot transmissions can be dynamically scheduled and for NR Rel-15:

[0015] • For DL ​​it can be 7, 4 or 2 symbols in length, while for UL it can be any length.

[0016] Can start and end at any symbol within a time slot.

[0017] Note that mini-slot transmissions in NR Rel-15 may not cross slot boundaries.

[0018] In the information element (IE) PUSCH-Config for dynamic transmission or the IE configuredGrantConfig for type 1 and type 2 CGs, one of two frequency hopping modes (inter-slot and intra-slot frequency hopping) can be configured via higher layers for PUSCH transmission in NR Rel-15.

[0019] PUSCH transmission scheme

[0020] In NR, two transmission schemes are specified for PUSCH.

[0021] Codebook-based PUSCH

[0022] Codebook-based UL transmission is used on both NR and Long Term Evolution (LTE) and is enabled for non-calibrated UEs and / or UL frequency domain duplexing (FDD). Codebook-based PUSCH in NR is enabled if the higher layer parameter txConfig=codebook. For dynamically scheduled PUSCH and CG PUSCH type 2, the codebook-based PUSCH transmission scheme can be summarized as follows:

[0023] • The UE transmits one or two Sounding Reference Signal (SRS) resources (ie one or two SRS resources configured in the SRS resource set associated with the higher layer parameter usage of the value 'CodeBook').

[0024] The gNB determines from the codebook the preferred multiple-input multiple-output (MIMO) transmit precoder for the PUSCH (e.g., transmit precoding matrix indicator (TPMI)) and the associated number of layers corresponding to the one or two SRS resources.

[0025] If two SRS resources are configured in the SRS resource set, the gNB indicates the selected SRS resource via a 1-bit 'SRSresourceindicator' field. If only one SRS resource is configured in the SRS resource set, the 'SRSresourceindicator' field is not indicated in the DCI.

[0026] The gNB indicates the TPMI and the associated number of layers corresponding to the indicated SRS resource (in case two SRS resources are used) or the configured SRS resource (in case one SRS resource is used). The TPMI and the number of PUSCH layers are indicated by the 'Precoding information and number of layers' field in DCI formats 0_1 and 0_2.

[0027] The UE performs PUSCH transmissions using the indicated number of layers and TPMI. If one SRS resource is configured in the SRS resource set associated with the higher-layer parameter usage value of 'CodeBook', the PUSCH demodulation parameter signal (DMRS) spatially refers to the nearest SRS transmission in this SRS resource. If two SRS resources are configured in the SRS resource set associated with the higher-layer parameter usage value of 'CodeBook', the PUSCH DMRS spatially refers to the nearest SRS transmission in the SRS resource indicated by the 'SRS resource indicator' field.

[0028] Non-codebook-based PUSCH

[0029] Non-codebook based UL transmission is available in NR, enabling reciprocity based UL transmission. By assigning DL channel state information reference signal (CSI-RS) to the UE, it can measure and infer the appropriate precoder weights for PUSCH transmission of up to four spatial layers. The candidate precoder weights are transmitted using up to four single-port SRS resources corresponding to the spatial layers. The gNB then instructs the UE to use bits and jointly coded multiple SRS resource indicators and transmission ranks, where N SRS Indicates the number of configured SRS resources, and L max is the maximum number of supported layers for PUSCH.

[0030] PUSCH repetition

[0031] When transmitting PUSCH scheduled by DCI format 0_1 ​​in PDCCH with cyclic redundancy check (CRC), which is scrambled with Cell Radio Network Temporary Identifier (C-RNTI), Modulation and Coding Scheme C-RNTI (MCS-C-RNTI), or Scheduling Radio Network Temporary Identifier (CS-RNTI) with New Data Indicator (NDI) = 1, if the UE is configured with the higher layer parameter pusch-AggregationFactor, the same symbol allocation is applied across pusch-AggregationFactor consecutive time slots and the PUSCH is restricted to a single transmission layer. The UE should repeat the transport block (TB), such as data payload transmitted on multiple RBs, across pusch-AggregationFactor consecutive time slots with the same symbol allocation applied in each time slot.

[0032] NR Release 16 PUSCH Enhancement

[0033] In NR Release 16 (Rel-16), PUSCH repetition enhancements were made for both PUSCH Type A and Type B for the purpose of further latency reduction (i.e., for Rel-16 Ultra-Reliable Low Latency Communication (URLLC)).

[0034] PUSCH repetition type A (slot-based) enhancement

[0035] In NR Rel-15, the number of aggregated slots for both dynamic grants and CG type 2 is RRC configured. In NR Rel-16, this is enhanced so that the number of repetitions can be indicated dynamically, i.e., changes from one PUSCH scheduling opportunity to the next PUSCH scheduling opportunity. That is, in addition to the start symbol S and the length L of the PUSCH, there is also a nominal number of repetitions K that is signaled as part of the time domain resource allocation (TDRA). In addition, the maximum number of aggregated slots is increased to K=16 to take into account the DL-heavy time domain duplex (TDD) pattern. Inter-slot and intra-slot hopping can be applied to type A repetitions. The number of repetitions K is nominal because some slots can be DL slots for PUSCH transmission and are then skipped. So K is the maximum number of possible repetitions.

[0036] PUSCH repetition type B (mini-slot-based) enhancement

[0037] PUSCH repetition Type B applies to both dynamic and configured grants. In Rel-16, Type B PUSCH repetitions can cross slot boundaries. When scheduling a transmission with PUSCH repetition Type B, in addition to the start symbol S and the length L of the PUSCH, a nominal number of repetitions K is signaled as part of the TDRA in NR Rel-16. Inter-slot frequency hopping and inter-repetition frequency hopping can be configured for Type B repetitions. To determine the actual time domain allocation of Type B PUSCH repetitions, a two-step process is used:

[0038] 1) Allocate K nominal repetitions of length L back-to-back (adjacent in time), ignoring slot boundaries and TDD type.

[0039] 2) If a nominal repetition crosses a slot boundary or occupies symbols that are not available for UL transmission (e.g., due to a UL / DL switching point caused by TDD), the offending nominal repetition may be split into two or more shorter actual repetitions. If the number of potentially valid symbols for PUSCH repetition type B transmission for a certain nominal repetition is greater than zero, then the nominal repetition is composed of one or more actual repetitions, where each actual repetition consists of a contiguous set of potentially valid symbols that can be used for PUSCH repetition type B transmission within the slot.

[0040] Figure 3A is a schematic block diagram of an example allocation of nominal repetitions, wherein one of the nominal repetitions spans a slot boundary. Figure 3B It will Figure 3A Schematic diagram of a nominal repetition being divided into actual repetitions. In this example, four nominal repetitions are assigned back-to-back, starting in slot 1 and continuing in slot 2. The second nominal repetition crosses a slot boundary and is divided into two actual repetitions.

[0041] Each repetition contains a DMRS, wherein the position of the DMRS in each repetition follows the Rel-15 rule.

[0042] Redundant version

[0043] Channel coding can be controlled by RV. In NR, information payload can be encoded with four different RVs to allow increased redundancy decoding. The redundancy version to be applied on the nth transmission opportunity of a TB (where n=0, 1, ... K-1) is determined according to Table 1 below.

[0044] Table 1: Redundancy versions used for PUSCH transmission

[0045]

[0046] UE UL multi-panel switching

[0047] A UE may be equipped with multiple UL panels. However, in some cases, it may only have one UL processing chain for transmission, and switching between panels requires additional processing time. If the number of processing chains is smaller than the number of panels, the UE may also share processing chains between panels. Here, a panel can also be interpreted as a collection of antenna ports. The UE may require different panel switching times depending on the UE hardware or software design. The UE may use different panels to transmit to different transmit / receive points (TRPs).

[0048] Frequency Hopping

[0049] To achieve frequency diversity in the UL, frequency hopping can be used, where data in the first set of OFDM symbols in a slot is transmitted on RBs, as indicated by the scheduling grant. In the remaining OFDM symbols, data is transmitted on a different set of RBs given by a configurable offset from the first set. UL frequency hopping can be dynamically controlled using a certain bit in the DCI that schedules the transmission.

[0050] NR rel-15 supports inter-slot and intra-slot frequency hopping, where the equations describing the starting RB are given by the following equations 1 and 2, where RB start Is the starting RB in the UL bandwidth part (BWP), RB offset is the frequency offset in RBs between the two frequency hops.

[0051] Frequency hopping within a timeslot:

[0052]

[0053] Wherein, i=0 and i=1 are the first transition and the second transition respectively.

[0054] Frequency hopping between time slots:

[0055]

[0056] in is the current slot number within the radio frame where multi-slot PUSCH transmission can occur.

[0057] NR Rel-16 introduces PUSCH repetition type B, for which inter-repetition frequency hopping and inter-slot frequency hopping can be configured.

[0058] In the case of inter-repetition frequency hopping, the starting RB for the actual repetition within the nth nominal repetition (as defined in Section 6.1.2.1) is given by Equation 3:

[0059]

[0060] Among them RB start is the starting RB within the UL BWP calculated from the resource block assignment information of resource allocation type 1 (described in subsection 6.1.2.2.2), and RB offset is the frequency offset in RBs between the two frequency hops.

[0061] Spatial relationship definition

[0062] Spatial relationship is used in NR to refer to the relationship between a transmitted UL reference signal (RS) (such as PUCCH / PUSCH DMRS) and another previously transmitted or received RS, which can be a DL RS (such as CSI-RS or synchronization signal frame (SSB)) or a UL RS (such as SRS). This is also defined from the UE perspective.

[0063] If the UL transmitted RS is spatially correlated with the DL RS, it means that the UE should transmit the UL RS in the opposite (mutual) direction to the one in which it previously received the DL RS. More precisely, the UE should apply the "same" transmit (TX) spatial filtering configuration for the transmission of the UL RS as the receive (RX) spatial filtering configuration it previously used to receive the spatially correlated DL RS. Here, the term 'spatial filtering configuration' may refer to antenna weights that are applied to a transmitter or receiver for data / control transmission / reception. Another way to describe this is that the same "beam" that was used to receive the previous DL RS signal should be used to transmit the signal from the UE. The DL RS is also called a spatial filtering reference signal.

[0064] On the other hand, if the first UL RS is spatially correlated with the second UL RS, the UE should apply the same TX spatial filtering configuration for transmission of the first UL RS as it previously used to transmit the second UL RS. In other words, the same beam is used to transmit the first and second UL RSs, respectively.

[0065] Because the UL RS is associated with a layer transmitted by PUSCH or PUCCH, it is understood that the PUSCH / PUCCH is also transmitted using the same TX spatial filter as the associated UL RS.

[0066] In some cases, the spatial relationship information can also be provided in the Transport Configuration Information (TCI) status, which is indicated to the UE.

[0067] TCI status for UL

[0068] In NR Rel-15, the handling of spatial transport attributes is different for PUSCH, PUCCH, and SRS. For PUCCH, the spatial relationship information is defined in the IE PUCCH-SpatialRelationInfo, and for SRS, the spatial relationship information is configured as part of the SRS resource configuration. For PUSCH, the spatial transport attributes are given by the spatial transport attributes associated with the SRS(s) that are configured with either 'codebook' or 'non-codebook' usage in the SRS resource set. In the 3rd Generation Partnership Project (3GPP) Tdoc R1-1909225, it was shown that the Rel-15 approach to handling spatial transport attributes is cumbersome and rigid when it comes to UL multi-panel transmissions in NR. Therefore, in Tdoc-1909225, TCI states for UL are proposed, which can be used to control the spatial attributes of all UL transmissions (e.g., PUSCH, PUCCH, and SRS). The focus in Tdoc R1-1909225 is to be able to use the UL TCI status indication to select one of the UL panels and the corresponding transmit beam (eg, transmit properties) in the UE to transmit UL PUSCH / PUCCH / SRS (when the UE is equipped with multiple panels).

[0069] Typically, the TCI state for UL is configured by higher layers (eg, RRC) for the UE. There are multiple ways to configure the UL TCI state.

[0070] In one case, the UL TCI state is dedicated only to the UL and is configured separately from the TCI state corresponding to the DL. For example, the UL TCI state can be configured as part of the PUSCH-Config IE. Each UL TCI state can indicate a transmission configuration containing a DL RS (e.g., non-zero power (NZP) CSI-RS or SSB) or a UL RS (e.g., SRS) with the purpose of indicating the spatial relationship for the PUSCH DMRS. Alternatively, the UL TCI state can be configured as part of the BWP-UplinkDedicated IE so that the same UL TCI state can be used to indicate a DL RS or UL RS that provides a spatial relationship for more than one PUSCH DMRS, PUCCH DMRS, and SRS.

[0071] In another case, the same list of TCI states is used for both DL and UL, so the UE is configured with a single list of TCI states that can be used for both UL and DL scheduling. The single list of TCI states in this case is configured as part of, for example, PUSCH-Config or BWP-UplinkDedicated IE.

[0072] Problems and existing solutions

[0073] There are currently challenges. In NR Rel-16, PUSCH repetitions involving multiple TRPs can only be supported with separate PUSCH scheduling or separate activations. In NR Rel-17 and future releases, a single DCI can be used to trigger PUSCH transmissions involving multiple TRPs. However, the details of repetition in such cases need to be addressed to facilitate resource allocation and frequency hopping performance. Summary of the Invention

[0074] A physical uplink shared channel (PUSCH) resource allocation with multiple transmit / receive points (TRPs) is provided. The embodiments described herein provide details for facilitating multi-TRP transmissions on PUSCH with respect to user equipment (UE) implementation and application scenarios. The interval between consecutive PUSCH transmission instances towards different TRPs (e.g., transmissions associated with different spatial transmit filters) can be signaled semi-statically or dynamically. In the case of dynamic signaling, the interval can be configured in the time domain resource allocation (TDRA) table and indicated in the downlink control information (DCI). In the case of semi-static signaling, it can be done through radio resource control (RRC).

[0075] The interval may be applicable only when certain conditions are met, such as one or more of the following: 1) multiple TRPs are indicated in the DCI, 2) Type B repetition, and 3) multiple panels are used at the UE. When PUSCH repetition is configured, the association of each PUSCH repetition with a TRP can be done by either cycling the PUSCH repetition through the multiple TRPs or dividing the PUSCH repetitions among the multiple TRPs and consecutive PUSCH repetitions are associated with and sent to each TRP.

[0076] Frequency hopping between PUSCH repetitions can be accomplished in one of the following ways: Inter-TRP hopping, where frequency hopping is performed over PUSCH across TRPs. Intra-TRP hopping, where frequency hopping is performed only over the PUSCH associated with each TRP. The frequency hopping offset can be signaled semi-statically via RRC or dynamically in the DCI.

[0077] RRC-configurable redundancy version (RV) transfer may be signaled to the UE to be applied (when determining the RV for PUSCH transmission towards each TRP (except the first TRP)).

[0078] Various embodiments are provided herein that address one or more of the issues disclosed herein. In some embodiments, a method is performed by a wireless device for transmitting data to multiple transmission paths (TRPs). The method includes receiving control information for scheduling multiple TRP transmissions, the control information including an indication of an interval between transmissions of each TRP; transmitting the data to a first TRP according to the control information; and, after the interval, transmitting the data to a second TRP according to the control information.

[0079] In some embodiments, each TRP is characterized by a reference signal transmitted from the TRP and previously received by the wireless device or previously transmitted from the wireless device to the TRP, and is indicated to the wireless device by a spatial relationship, the spatial relationship including the reference signal or a transmission configuration information (TCI) state, the TCI state including the reference signal.

[0080] In some embodiments, the method further comprises, prior to receiving the control information, indicating to a network node the capability of the wireless device to support one or more active panels.

[0081] In some embodiments, the control information is received from a network node via a DCI message; and the interval is indicated in a TDRA field of the DCI message. In some embodiments, the multi-TRP transmission is configured with PUSCH repetition type B. In some embodiments, the wireless device supports multi-panel transmission; and at least one of the fields in the DCI message indicates more than one TRP transmission.

[0082] In some embodiments, the gap is indicated as a minimum number of symbols in which the wireless device is not scheduled to transmit or receive over a shared channel between transmitting to the first TRP and transmitting to the second TRP. In some embodiments, the symbols including the gap after transmitting to the first TRP are treated as downlink symbols or invalid symbols. In some embodiments, the method further includes transmitting to the second TRP on the remaining symbols of the resource block if the symbols including the gap are in a resource block indicated for transmission to the second TRP.

[0083] In some embodiments, the interval is indicated as the number of symbols after starting transmission to the first TRP and before starting transmission to the second TRP.

[0084] In some embodiments, the interval is implicitly indicated by using a TDRA that is repeated for a shared channel associated with the multiple TRP transmissions.

[0085] In some embodiments, the intervals are configured by a higher layer.

[0086] In some embodiments, K repetitions are configured for the PUSCH used for the multi-TRP transmission. In some embodiments, the configured repetitions K are applied to each TRP of the multi-TRP transmission. In some embodiments, the configured repetitions K are distributed between the first TRP and the second TRP. In some embodiments, each TRP of the multi-TRP transmission is transmitted sequentially and repeated until the configured repetitions K are reached.

[0087] In some embodiments, the control information further includes a flag to enable frequency hopping for the multi-TRP transmission. In some embodiments, the method further includes applying a frequency hopping offset indicated by the control information to all TRPs of the multi-TRP transmission. In some embodiments, the method further includes applying a frequency hopping offset, wherein the frequency hopping offset is associated with a resource allocation for the TRPs of the multi-TRP transmission and is indicated by a higher layer configuration.

[0088] In some embodiments, the method further includes applying a frequency hopping offset, wherein the control information indicates a single resource allocation for all TRPs of the multi-TRP transmission and the frequency hopping offset is configured by a higher layer. In some embodiments, the frequency hopping occurs within a transmission to each TRP; and the transmission to the second TRP occurs after the frequency hopping within the transmission to the first TRP and after the interval. In some embodiments, the frequency hopping occurs between transmissions to the same TRP; and the method further includes transmitting to the first TRP using the frequency hopping offset after the transmission to the second TRP and after another interval.

[0089] In some embodiments, the method further comprises: applying an RV offset to the multi-TRP transmission according to a received configuration. In some embodiments, the control information indicates a first RV for a first repetition toward the first TRP. In some embodiments, a second RV for a first repetition toward the second TRP is given by applying the RV offset to the first RV.

[0090] In some embodiments, a method is performed by a network node for facilitating transmission to multiple TRPs. The method includes: receiving an indication of a UE's capability to support one or more active panels; scheduling multiple TRP transmissions by the UE based on the indication of the capability; and sending control information for the multiple TRP transmissions to the UE, the control information including an indication of an interval between each TRP transmission.

[0091] In some embodiments, the control information is transmitted via a DCI message; and the interval is indicated in a TDRA field of the DCI message. In some embodiments, the method further comprises configuring the multiple TRP transmissions using PUSCH repetition type B. In some embodiments, the UE has the capability to support multiple active panels; and at least one of the fields in the DCI message indicates more than one TRP transmission.

[0092] In some embodiments, the method further comprises not scheduling the UE to transmit or receive over the shared channel during the interval between each TRP transmission.

[0093] In some embodiments, the method further comprises configuring K repetitions for the PUSCH used for the multi-TRP transmission.

[0094] In some embodiments, the method further includes enabling frequency hopping for the multi-TRP transmission. In some embodiments, the method further includes providing a frequency hopping offset to the UE.

[0095] In some embodiments, the method further comprises configuring an RV offset for the multi-TRP transmission. In some embodiments, the method further comprises: signaling the RV offset to the UE using an RRC message; and signaling a first RV to the UE via a DCI message, the DCI message including the control information for the multi-TRP transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0096] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0097] Figure 1 This is a schematic block diagram of the time domain structure used for data scheduling in the New Radio (NR).

[0098] Figure 2 Figure 1 is a schematic diagram of the physical time-frequency resource grid used for data scheduling in NR.

[0099] Figure 3A is a schematic block diagram of an example allocation of nominal repetitions, wherein one of the nominal repetitions spans a slot boundary.

[0100] Figure 3B It will Figure 3A Schematic diagram of the nominal repetition divided into actual repetitions.

[0101] Figure 4An example of a cellular communication system is shown in which embodiments of the present disclosure may be implemented.

[0102] Figure 5A is a schematic block diagram of a transmission scheme for multiple Physical Uplink Shared Channel (PUSCH) transmission instances, each PUSCH transmission instance toward a different transmission / reception point (TRP) according to embodiments described herein.

[0103] Figure 5B is a table showing exemplary parameters for signaling intervals Figure 5A Schematic block diagram of the transmission scheme.

[0104] Figure 6A is a schematic block diagram of a transmission scheme for an embodiment using type B repetition.

[0105] Figure 6B FIG. 4 is a schematic block diagram of a transmission scheme of another embodiment adopting type B repetition.

[0106] Figure 7A is a schematic block diagram illustrating an example of frequency hopping within a TRP in a first scenario, where frequency hopping occurs within a PUSCH transmission to each TRP.

[0107] Figure 7B is a schematic block diagram illustrating an example of frequency hopping within a TRP in a second scenario, where frequency hopping occurs between PUSCH transmissions to the same TRP.

[0108] Figure 8 is a flow chart illustrating a method for transmitting to multiple TRPs according to one embodiment.

[0109] Figure 9 is a flow chart illustrating a method for facilitating delivery to multiple TRPs according to one embodiment.

[0110] Figure 10 is a schematic block diagram of a network node according to some embodiments of the present disclosure.

[0111] Figure 11 is a schematic block diagram illustrating an embodiment of virtualization of a network node according to some embodiments of the present disclosure.

[0112] Figure 12 is a schematic block diagram of a network node according to some other embodiments of the present disclosure.

[0113] Figure 13 is a schematic block diagram of a wireless communication device according to some embodiments of the present disclosure.

[0114] Figure 14is a schematic block diagram of a wireless communication device according to some other embodiments of the present disclosure. DETAILED DESCRIPTION

[0115] The embodiments described below represent information to enable those skilled in the art to implement the embodiments and to illustrate the best mode of implementing the embodiments. When reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will recognize applications of these concepts not specifically disclosed herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.

[0116] Radio node: As used herein, a "radio node" is a radio access node or a radio communication device.

[0117] Radio access node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a radio access network (RAN) of a cellular communication network that operates to wirelessly transmit and / or receive signals. Some examples of radio access nodes include, but are not limited to, a base station (e.g., a new radio (NR) base station (gNB) in a 3rd Generation Partnership Project (3GPP) fifth generation (5G) NR network or an enhanced or evolved Node B (eNB) in 3GPP Long Term Evolution (LTE)), a high power or macro base station, a low power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB central unit (gNB-CU) or a network node that implements a gNB distributed unit (gNB-DU)), or a network node that implements part of the functionality of some other type of radio access node.

[0118] Core network node: As used herein, a "core network node" is any type of node in a core network or any node that implements core network functions. Some examples of core network nodes include, for example, a mobility management entity (MME), a packet data network gateway (P-GW), a service capability exposure function (SCEF), a home subscriber server (HSS), or the like. Some other examples of core network nodes include nodes that implement the following functions: access and mobility management function (AMF), user plane function (UPF), session management function (SMF), authentication server function (AUSF), network slice selection function (NSSF), network exposure function (NEF), network function (NF) repository function (NRF), policy control function (PCF), unified data management (UDM), or the like.

[0119] Communication device: As used herein, a "communication device" is any type of device that has access to an access network. Some examples of communication devices include, but are not limited to, mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical appliances, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting fixtures, tablet computers, laptops, or personal computers (PCs). A communication device can be a portable, handheld, computer-included, or vehicle-mounted mobile device that enables the communication of voice and / or data via a wireless or wired connection.

[0120] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device having access to (i.e., being served by) a wireless network, such as a cellular network. Some examples of wireless communication devices include, but are not limited to, User Equipment (UE) devices in 3GPP networks, Machine Type Communication (MTC) devices, and Internet of Things (IoT) devices. Such wireless communication devices may be or may be integrated into mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical appliances, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting arrangements, tablets, laptops, or PCs. A wireless communication device may be a portable, handheld, computer-included, or vehicle-mounted mobile device that enables the communication of voice and / or data via a wireless connection.

[0121] Network node: As used herein, a "network node" is any node that is part of the core network or RAN of a cellular communication network / system.

[0122] It is noted that the description given herein focuses on 3GPP cellular communication systems and therefore, 3GPP terminology or 3GPP-like terminology is often used. However, the concepts disclosed herein are not limited to 3GPP systems.

[0123] It is noted that reference may be made to the term "cell" in the description herein; however, particularly for 5GNR concepts, beams may be used instead of cells and therefore, it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0124] Figure 4An example of a cellular communication system 400 is shown in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communication system 400 is a 5G system (5GS) including an NR RAN or an LTE RAN (i.e., an Evolved Universal Terrestrial Radio Access (E-UTRA) RAN) or an Evolved Packet System (EPS) including an LTE RAN. In this example, the RAN includes base stations 402-1 and 402-2, which are referred to as gNBs in 5G NR (e.g., LTE RAN nodes connected to the 5G Core (5GC), which are referred to as gn-eNBs), controlling corresponding (macro) cells 404-1 and 404-2. Base stations 402-1 and 402-2 are generally referred to herein as base stations (stations) 402 and individually as base stations (stations) 402. Similarly, (macro) cells 404-1 and 404-2 are generally referred to herein as (macro) cells (cells) 404 and individually as (macro) cells (cells) 404. The RAN may further include a plurality of low-power nodes 406-1 to 406-4 that control corresponding small cells 408-1 to 408-4. The low-power nodes 406-1 to 406-4 can be small base stations (such as pico or femto base stations) or remote radio heads (RRHs) or the like. In particular, not shown, one or more of the small cells 408-1 to 408-4 may alternatively be provided by the base station 402. The low-power nodes 406-1 to 406-4 are generally referred to herein as low-power nodes (nodes) 406 and each as a low-power node (node) 406. Similarly, the small cells 408-1 to 408-4 are generally referred to herein as small cells (cells) 408 and each as a small cell (cell) 408. The cellular communication system 400 also includes a core network 410, which is referred to as 5GC in 5GS. The base station 402 (and optionally, the low-power node 406) is connected to the core network 410.

[0125] Base station 402 and low power node 406 provide services to wireless communication devices 412-1 through 412-5 in corresponding cells 404 and 408. Wireless communication devices 412-1 through 412-5 are generally referred to herein collectively as wireless communication devices 412 and individually as wireless communication devices 412. In the following description, wireless communication device 412 is often a UE, but the present disclosure is not limited to UEs.

[0126] Throughout this disclosure, the term "physical uplink shared channel (PUSCH) transmission towards two or more transmit / receive points (TRPs)" is used. This means that the UE uses different (e.g., two or more) spatial transmit filters to target the PUSCH transmission towards the two or more TRPs. The spatial transmit information to be used by the UE is indicated to the UE via a transmit configuration information (TCI) state or spatial relationship of a source reference signal (RS) (the source RS can be a downlink (DL) RS or an uplink (UL) RS), from which the spatial transmit filter to be used for the PUSCH demodulation RS (DMRS) is derived. Typically, there will be one spatial transmit filter (provided by the spatial relationship or TCI state) for targeting the PUSCH transmission towards the TRP. That is, if the UE is to target the PUSCH towards two different TRPs, two spatial relationships or two TCI states need to be indicated to the UE. In some other cases, transmission of a PUSCH towards a TRP may mean that the UE uses one of the panels for this transmission (e.g., different panels are used to transmit PUSCH towards different TRPs). In these cases, the UE may also be instructed with one or more panel identifiers that tell the UE which panels to use (e.g., which TRPs to aim the PUSCH towards).

[0127] Figure 5A is a schematic block diagram of a transmission scheme for multiple PUSCH transmission instances according to the embodiments described herein, each PUSCH transmission instance is directed to a different TRP. Figure 4 When a wireless communication device 412 of a wireless communication device 412 transmits multiple PUSCH transmission instances or actual repetitions toward two or more TRPs (e.g., base station 402, low power node 406, and the like), the minimum interval between two consecutive PUSCH transmission instances toward different TRPs can be determined by the network (e.g., Figure 4 Further to the above discussion, each TRP can be characterized by reference signals transmitted from the TRP and previously received by the wireless device or previously transmitted from the wireless device to the TRP, and indicated to the wireless device by including the spatial relationship (or TCI state) of the reference signals. In some embodiments, whether the UE supports having a minimum interval and the value of the required minimum interval is reported to the network as part of the UE capabilities. The reason for configuring this minimum interval is to allow the UE to switch between multiple panels. The interval can be considered a guard period during which the UE is not expected to perform any transmission or reception, but rather the UE is switching from transmitting a first PUSCH instance towards a first TRP to transmitting a second PUSCH instance towards another TRP.

[0128] In an exemplary aspect, a UE that supports only one active panel at a time (eg, only one panel in the UE UL panel is capable of transmitting PUSCH at a time) indicates that capability via radio resource control (RRC) signaling, for which a longer interval time is required.

[0129] In another exemplary aspect, a UE that supports two or more active panels simultaneously indicates its capability via RRC signaling, for which a much shorter interval or even zero switching time is required when the number of TRPs being switched is less than the number of panels that the UE can simultaneously support. For the UE, other conditions may exist to achieve zero switching time, such as the number of ports required for transmission per TRP, the reference signal constellation, and / or the time between reception of the physical downlink control channel (PDCCH) and transmission of the corresponding PUSCH. The gNB should respect the spacing requirements when scheduling a UE with multiple TRPs.

[0130] Interval signaling

[0131] Figure 5B is a table showing exemplary parameters for signaling intervals Figure 5A Schematic block diagram of the transmission scheme.

[0132] Embodiment A: When a PUSCH transmission involves two or more TRPs, the interval between PUSCH transmission instances used to facilitate switching of PUSCH transmission from one TRP to another TRP can be dynamically indicated (e.g., via downlink control information (DCI) that schedules the PUSCH).

[0133] Embodiment A1: In one embodiment, if a single DCI is used to schedule multiple TRP transmissions, an interval Z in the number of symbols is indicated in the Time Domain Resource Allocation (TDRA) field. The TDRA indicated in the DCI applies to the first TRP transmission instance. Subsequent PUSCH transmission instances towards the next TRP begin Z symbols after the end of the PUSCH transmission targeting the first TRP as indicated by the DCI.

[0134] In this regard, as in Figure 5BAs shown in , if the transmission instance towards the first TRP starts at time slot X with start symbol S and length L (as indicated in the TDRA table), the transmission instance towards the second TRP starts at time slot X+floor((S+L+Z) / numberOfSymbolsPerSlot), and the start symbol relative to the start of the starting time slot of the second TRP is given by mod(S+L+Z,numberOfSymbolsPerSlot). The end slot is given by X+floor((S+2*L+Z-1) / numberOfSymbolsPerSlot), and the end symbol relative to the start of the end slot of the second TRP is given by mod(S+2*L+Z-1,numberOfSymbolsPerSlot).

[0135] Embodiment A2: In one embodiment, the Z symbols following the previous TRP transmission are treated as DL symbols or invalid symbols. If any of these Z symbols are within the symbols indicated to transmit a PUSCH instance for the next TRP, the UE considers those symbols invalid and transmits them on the remaining symbols of the same transport block (TB). The range of the transmission length L can be further constrained using L>Z or L>(Z+1).

[0136] In this regard, transmission using the second TRP starts at time slot X+floor((S+L+Z) / numberOfSymbolsPerSlot), and the starting symbol relative to the start of the starting time slot of the second TRP is given by mod(S+L+Z, numberOfSymbolsPerSlot). The ending slot is given by X+floor((S+2*L-1) / numberOfSymbolsPerSlot), and the ending symbol relative to the start of the ending slot of the second TRP is given by mod(S+2*L-1, numberOfSymbolsPerSlot).

[0137] Embodiment A3: In one embodiment, a gap can be configured in the TDRA field only when the DCI scheduling the PUSCH is configured with PUSCH repetition type B.

[0138] Embodiment A4: In one embodiment, an interval can be configured in the TDRA field only in the following cases:

[0139] PUSCH is configured with PUSCH repetition type B;

[0140] UE supports multi-panel transmission; and

[0141] At least one of the fields in the DCI can indicate PUSCH transmission towards more than one TRP (e.g., by indicating multiple spatial relationships or multiple TCIs). The field can be 'Precoding information and number of layers', 'SRS resource indicator', or 'Antenna ports'. In some embodiments, the field can also be TCI status. The DCI format can be 0_1 or 0_2.

[0142] Embodiment A5: In one embodiment, the spacing is implicitly indicated by using a TDRA for one of the PUSCH repetitions at the end of each repetition bundle for the same TRP in all TRPs except the last TRP.

[0143] Embodiment B: When a PUSCH transmission involves two or more TRPs, the interval between PUSCH transmission instances when switching TRPs can be configured by higher layers.

[0144] Apply repetition on each TRP with interval

[0145] Denote K as the repetition configured by pusch-AggregationFactor, repK or numberOfRepetitions. Denote P as the number of TRPs associated with a PUSCH transmission indicated by one DCI. The order of TRPs used to perform transmissions and the number of TRPs are indicated by the DCI and / or higher layer configuration. The interval is expressed as the number of symbols Z in the following embodiments. If the interval is given as a time duration T and T s represents the time duration of the OFDM symbol used for the scheduled PUSCH transmission, then Z can be expressed as a ceiling (T / T s ) and is exported.

[0146] Embodiment C: Gaps can be applied between PUSCH transmission instances when switching TRPs. Upon receiving a DCI indicating a PUSCH transmission, the UE reads K2 and the start symbol S and length L from the TDRA field (S and L can be derived from the start and length indicator value (SLIV)) for its first PUSCH transmission instance with the first TRP.

[0147] Determination of the number of repetitions for each TRP

[0148] Embodiment C1: In one embodiment, the configured K (nominal) PUSCH repetitions should be applied to each TRP.

[0149] Embodiment C2: In one embodiment, the configured repetitions K for PUSCH repetition type A or PUSCH repetition type B shall be distributed across each TRP. For the first P–1 TRPs, the repetitions are determined by R = floor(K / P) or R = ceiling(K / P). The UE transmits R (nominal) PUSCH repetitions in each TRP within the first (P–1) TRPs, and the UE transmits the remaining K–R*(P–1) (nominal) repetitions in the last TRP.

[0150] Embodiment C3: In one embodiment, the UE transmits one (nominal) PUSCH transmission instance per TRP in the order indicated by the DCI across the P TRPs and repeats until K nominal transmissions have been reached.

[0151] Embodiment C4: In one embodiment, after Z symbols of a PUSCH transmission instance with the latest TRP, the UE transmits a PUSCH transmission instance with the next TRP. The number of symbols used for the PUSCH repetition with the next TRP is the same as the number of symbols indicated in SLIV.

[0152] For embodiments C2 and C3, K=1 implicitly indicates a single TRP transmission. Sufficient signaling flexibility can be achieved to switch between the required number of TRPs for transmission.

[0153] TDRA for each TRP with duplication

[0154] For Examples C1 and C2, the number of repetitions for each TRP is represented as R1, R2, ..., R P R0 = 0. The following method can be applied to determine the resource allocation for each repetition.

[0155] In one method of embodiment C3, the Z symbols following the previous TRP transmission are treated as DL symbols or invalid symbols. If any of these Z symbols are within the symbols indicated to transmit a PUSCH transmission instance for the next TRP, the UE considers those symbols invalid and transmits them on the remaining symbols in the same TB. The range of the transmission length L can be further constrained using L>Z or L>(Z+1). This method can be applied to both Type A and Type B PUSCH repetitions.

[0156] Figure 6A is a schematic block diagram of a transmission scheme for embodiment C3 using type B repetition. In this regard, for type B repetition and using the nominal repetition n i (i=0,…,R p -1) when TRP p is transmitted, each repetition is in the time slot The start symbol relative to the start of the start time slot of the pTRP is represented by The end slot of each repetition is given by and the end symbol relative to the start of the end slot of the second TRP is given by The UE may be required to send additional DMRS symbols after the gap.

[0157] For Type A repetition, the UE may be required to send additional DMRS symbols if the gap is within the PUSCH allocation.

[0158] Figure 6B is a schematic block diagram of a transmission scheme for embodiment C4 using type B repetition. In this regard, for type B repetition and using the nominal repetition n i (i=0,…,R p -1) when TRP p is transmitted, each repetition is in the time slot The start symbol relative to the start of the start time slot of the pTRP is represented by The end slot of each repetition is given by and the end symbol relative to the start of the end slot of the second TRP is given by Given.

[0159] Applying frequency hopping to multiple TRPs

[0160] In order to achieve diversity in the frequency domain within each TRP, if frequency hopping is enabled in a single DCI that triggers multiple TRP transmissions, the hopping positions should be specified. In the following embodiments, the case when a single DCI addresses multiple TRPPUSCH transmissions with the frequency hopping flag enabled is considered.

[0161] In one embodiment, a hopping offset is indicated in the DCI that should be applied across all TRPs. Within each TRP, hopping is performed independently as a single TRP transmission. If a TRP is not the first TRP (in order) for performing a transmission, the set of symbols transmitted for the first transmission associated with this TRP should be derived from the transmission of the previous TRP associated with the same DCI.

[0162] In this regard, when applying the hopping equation, the hop number n is counted separately for each TRP. Alternatively, n is counted jointly considering all TRPs associated with this DCI. As another alternative, n can be counted as the nominal repetition for PUSCH Type B repetitions or the number of slots for inter-slot repetitions. For intra-slot repetitions, n is the number of slots in the frame and is independent of the order in which the TRPs are numbered.

[0163] In one embodiment, the resource block (RB) at which each actual repetition begins is determined by the number of nominal repetitions aggregated over all transmitted repetitions within all TRPs. In this regard, P represents the total number of TRPs, and R i Each TRP i,…,n i The total number of nominal repetitions is expressed as the number of nominal repetitions of the current TRP i, where i = 0, 1, 2, ..., P-1, n i =0, 1, .., R i -1:

[0164]

[0165] in

[0166] In one embodiment, the hopping offset is associated with the resource allocation for the TRP and is indicated by a higher-layer configuration. If the resource configuration for the set of RBs is indicated as (RBset1, RBset2, RBset3) in the frequency domain for TRP1, TRP2, and TRP3 for the first transmission associated with each TRP, then the second transmission for TRP1, TRP2, and TRP3 uses the RB set (RBset2, RBset3, RBset1). The frequency-domain resource allocation thus rotates between the TRPs.

[0167] In yet another embodiment, a single resource allocation is indicated in the DCI for all TRPs, and the hopping offset is configured by higher layers and applies to PUSCH transmissions to all TRPs. Additionally, only intra-TRP frequency hopping is supported, where frequency hopping is performed on a per-TRP basis.

[0168] Figure 7A is a schematic block diagram illustrating an example of frequency hopping within a TRP in scenario A, where frequency hopping occurs within a PUSCH transmission to each TRP. Figure 7B is a schematic block diagram illustrating an example of frequency hopping within a TRP in scenario B, where frequency hopping occurs between PUSCH transmissions to the same TRP.

[0169] RV allocation to PUSCH transmissions towards different TRPs

[0170] In some embodiments, when PUSCH transmission towards two TRPs is indicated to the UE, the redundancy version to be applied for PUSCH transmission towards the first TRP is based on rv id And is given, the rv id Indicated by the DCI that schedules PUSCH and follows the pattern given in Table 1. The redundancy version to be applied to the PUSCH transmission corresponding to the second TRP is based on rv idAnd is given, the rv id Indicated by a DCI that schedules PUSCH and follows the pattern given in Table 2, where specific to ULrv UL,s The RRC configurable parameter n is used to transfer RV. In this embodiment, only transmissions towards a given TRP are counted. For example, when the UE transmits to TRP1 in transmit opportunities 1 and 2 and to TRP2 in transmit opportunities 3 and 4:

[0171] For transmission opportunities 1 and 2, the corresponding n values ​​are 1 and 2 respectively.

[0172] For transmission opportunities 3 and 4, the corresponding n values ​​are 1 and 2 respectively.

[0173] The benefit of using such configurable RV transfer in the UL is to allow the application of Rel-15 RV sequences towards every PUSCH transmission per TRP.

[0174] Table 2: Redundancy versions corresponding to the second UL TCI state when the redundancy version transition parameter is configured in the UL.

[0175]

[0176]

[0177] Figure 8 8 is a flow chart illustrating a method for transmitting data to multiple TRPs according to one embodiment. The method can be implemented in a wireless device. Optional steps are indicated by dashed lines. In optional step 800, the wireless device indicates to a base station the ability of the wireless device to support one or more active panels. In step 802, the wireless device receives control information for scheduling multiple TRP transmissions, the control information including an indication of an interval between each TRP transmission. In step 804, the wireless device transmits data to a first TRP in accordance with the control information. In step 806, after the interval, the wireless device transmits data (e.g., the same data) to a second TRP in accordance with the control information. In optional step 808, the wireless device applies a frequency hopping offset for the multiple TRP transmissions (e.g., received via DCI). In optional step 810, the wireless device applies an RV offset to the multiple TRP transmissions in accordance with a received configuration (e.g., received via RRC).

[0178] Figure 9is a flow chart illustrating a method for facilitating transmission to multiple TRPs according to one embodiment. The method may be implemented in a network node (e.g., a base station or other network node). Optional steps are indicated by dashed lines. In step 900, the network node receives an indication of the capability of a UE to support one or more active panels. In step 902, the network node schedules multiple TRP transmissions by the UE based on the indication of the capability. In step 904, the network node sends control information for the multiple TRP transmissions to the UE, the control information including an indication of the interval between each TRP transmission. In optional step 906, the network node configures K repetitions for the PUSCH for the multiple TRP transmissions. In optional step 908, the network node enables frequency hopping for the multiple TRP transmissions. In optional step 910, the network node configures an RV offset for the multiple TRP transmissions.

[0179] Figure 10 is a schematic block diagram of a network node 1000 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. Network node 1000 may be, for example, base station 402 or 406, or another network node that implements all or part of the functionality of base station 402 or gNB described herein. As shown, network node 1000 includes a control system 1002, which includes one or more processors 1004 (e.g., a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and / or the like), a memory 1006, and a network interface 1008. The one or more processors 1004 are also referred to herein as processing circuitry. Furthermore, network node 1000 may include one or more radio units 1010, each of which includes one or more transmitters 1012 and one or more receivers 1014 coupled to one or more antennas 1016. Radio unit 1010 may refer to or be part of a radio interface circuitry. In some embodiments, the radio unit(s) 1010 are external to the control system 1002 and connected to the control system 1002 via, for example, a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) 1010, and potentially also the antenna(s) 1016, are integrated with the control system 1002. The one or more processors 1004 operate to provide one or more functions of the radio access node 1000 as described herein. In some embodiments, the function(s) are implemented in software stored (e.g., in the memory 1006) and executed by the one or more processors 1004.

[0180] Figure 11 1 is a schematic block diagram illustrating a virtualized embodiment of a network node 1000 according to some embodiments of the present disclosure. This discussion is equally applicable to radio access nodes or other types of network nodes. Further, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.

[0181] As used herein, a "virtualized" network node is an implementation of network node 1000 in which at least a portion of the functionality of network node 1000 is implemented as virtual component(s) (e.g., via virtual machine(s) executing on physical processing node(s) in network(s)). As shown, in this example, network node 1000 may include a control system 1002 and / or the one or more radio units 1010, as described above. Control system 1002 may be connected to radio unit(s) 1010 via, for example, fiber optic cables or the like. Network node 1000 includes one or more processing nodes 1100, which are connected to or included as part of network(s) 1102. If present, control system 1002 or the radio unit(s) 1010 are connected to the processing node(s) 1100 via network 1102. Each processing node 1100 includes one or more processors 1104 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 1106, and a network interface 1108.

[0182] In this example, the functionality 1110 of the network node 1000 described herein is implemented in any desired manner at the one or more processing nodes 1100 or distributed across the one or more processing nodes 1100 and the control system 1002 and / or the radio(s) 1010. In some specific embodiments, some or all of the functionality 1110 of the network node 1000 described herein is implemented as virtual components that are executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 1100. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 1100 and the control system 1002 is used to perform at least some of the desired functionality 1110. Note that in some embodiments, the control system 1002 may not be included, in which case the radio(s) 1010 communicate directly with the processing node(s) 1100 via appropriate network interface(s).

[0183] In some embodiments, a computer program comprising instructions is provided that, when executed by at least one processor, causes the at least one processor to perform the functionality of a network node 1000 or a node (e.g., processing node 1100) that implements one or more functions of the functions 1110 of the network node 1000 in a virtual environment (according to any of the embodiments described herein). In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of the following: an electronic signal, an optical signal, a radio signal, or a computer-readable medium (e.g., a non-transitory computer-readable medium such as a memory).

[0184] Figure 12 is a schematic block diagram of a network node 1000 according to some other embodiments of the present disclosure. The network node 1000 includes one or more modules 1200, each of which is implemented in software. The (one or more) modules 1200 provide the functionality of the network node 1000 described herein. This discussion applies equally to Figure 11 1100, wherein module 1200 may be implemented on one of processing nodes 1100 or distributed across multiple processing nodes 1100 and / or distributed across the processing node(s) 1100 and control system 1002.

[0185] Figure 13 is a schematic block diagram of a wireless communication device 1300 according to some embodiments of the present disclosure. As shown, the wireless communication device 1300 includes one or more processors 1302 (e.g., a CPU, ASIC, FPGA, and / or the like), memory 1304, and one or more transceivers 1306, each of which includes one or more transmitters 1308 and one or more receivers 1310 coupled to one or more antennas 1312. The transceiver(s) 1306 include a radio front-end circuit module connected to the antenna(s) 1312, which conditions signals communicated between the antenna(s) 1312 and the processor(s) 1302, as will be appreciated by one of ordinary skill in the art. The processor 1302 is also referred to herein as a processing circuit module. The transceiver 1306 is also referred to herein as a radio circuit module. In some embodiments, the functionality of the wireless communication device 1300 described above may be implemented in whole or in part in software (e.g., stored in memory 1304 and executed by the processor(s) 1302). It should be noted that the wireless communication device 1300 may include Figure 13Additional components shown in the figure, such as one or more user interface components (e.g., including a display, buttons, touch screen, microphone, (one or more) speakers and / or input / output interfaces such as the like and / or any other components that allow information to be input to the wireless communication device 1300 and / or allow information to be output from the wireless communication device 1300), a power source (e.g., a battery and associated power circuit modules), etc.

[0186] In some embodiments, a computer program comprising instructions is provided that, when executed by at least one processor, causes the at least one processor to perform the functionality of the wireless communication device 1300 (according to any of the embodiments described herein). In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of the following: an electronic signal, an optical signal, a radio signal, or a computer-readable medium (e.g., a non-transitory computer-readable medium such as a memory).

[0187] Figure 14 1 is a schematic block diagram of a wireless communication device 1300 according to some other embodiments of the present disclosure. The wireless communication device 1300 includes one or more modules 1400, each of which is implemented in software. The module(s) 1400 provide the functionality of the wireless communication device 1300 described herein.

[0188] Any appropriate steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple of these functional units. These functional units may be implemented via a processing circuit module, which may include one or more microprocessors or microcontrollers and may include digital signal processors (DSPs), dedicated digital logic and other digital hardware of the same type. The processing circuit module may be configured to execute program code stored in a memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory device, optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In some implementations, according to one or more embodiments of the present disclosure, the processing circuit module may be used to cause the corresponding functional unit to perform the corresponding function.

[0189] Although the processes in the figures may illustrate a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.).

[0190] Group A Examples

[0191] Embodiment 1: A method performed by a wireless device for transmitting to multiple TRPs, the method comprising at least one of: receiving control information for scheduling multiple TRP transmissions, the control information comprising an indication of an interval between each TRP transmission; transmitting to a first TRP according to the control information; and after the interval, transmitting to a second TRP according to the control information.

[0192] Embodiment 2: The method of embodiment 1 further comprises: before receiving the control information, indicating to the base station the capability of the wireless device to support one or more active panels.

[0193] Embodiment 3: The method of any of embodiments 1 to 2, wherein: the control information is received from a base station via a DCI message; and the interval is indicated in a TDRA field of the DCI message.

[0194] Embodiment 4: The method of embodiment 3, wherein the multi-TRP transmission is configured with PUSCH repetition type B.

[0195] Embodiment 5: The method of embodiment 4, wherein: the wireless device supports multi-panel transmission; and at least one of the fields in the DCI message indicates more than one TRP transmission.

[0196] Embodiment 6: The method of any embodiment of Embodiments 1 to 5, wherein the interval is indicated as a minimum number of symbols in which the wireless device is not scheduled to transmit or receive over the shared channel between transmitting to the first TRP and transmitting to the second TRP.

[0197] Embodiment 7: The method of embodiment 6, wherein the symbol including the interval after transmission to the first TRP is treated as a DL symbol or an invalid symbol.

[0198] Embodiment 8: The method of embodiment 7, wherein if the symbols including the interval are in a resource block indicated for transmission to the second TRP, transmission to the second TRP is performed on the remaining symbols of the resource block.

[0199] Embodiment 9: The method of any of embodiments 1 to 5, wherein the interval is indicated as the number of symbols after starting to transmit to the first TRP and before starting to transmit to the second TRP.

[0200] Embodiment 10: The method of any of embodiments 1 to 9, wherein the interval is implicitly indicated by using a TDRA repeated for a shared channel associated with the multiple TRP transmissions.

[0201] Embodiment 11: The method of any of Embodiments 1 to 10, wherein the spacing is configured by a higher layer.

[0202] Embodiment 12: The method of any embodiment of embodiments 1 to 11, wherein K repetitions are configured for the PUSCH used for the multi-TRP transmission.

[0203] Embodiment 13: The method of embodiment 12, wherein the configured repetition K is applied to each TRP of the multi-TRP transmission.

[0204] Embodiment 14: The method of embodiment 12, wherein the configured repetition K is distributed between the first TRP and the second TRP.

[0205] Example 15: The method of Example 12, wherein each TRP of the multiple TRP transmissions is transmitted in sequence and repeated until the configured repetition K is reached.

[0206] Embodiment 16: The method of any embodiment of Embodiments 1 to 15, wherein the control information further includes a flag to enable frequency hopping for the multi-TRP transmission.

[0207] Embodiment 17: The method of embodiment 16, wherein the control information indicates a frequency hopping offset applied on all TRPs transmitted by the multi-TRP.

[0208] Embodiment 18: The method of embodiment 16, wherein the frequency hopping offset is associated with resource allocation for the TRP of the multi-TRP transmission and is indicated by a higher layer configuration.

[0209] Embodiment 19: The method of any of the preceding embodiments, further comprising: providing user data; and forwarding the user data to a host computer via transmission to a base station.

[0210] Group B Examples

[0211] Embodiment 20: A method performed by a base station to facilitate transmissions to multiple TRPs, the method comprising at least one of: receiving an indication of a UE's capability to support one or more active panels; scheduling multiple TRP transmissions by the UE based on the indication of the capability; and sending control information for the multiple TRP transmissions to the UE, the control information comprising an indication of an interval between each TRP transmission.

[0212] Embodiment 21: The method of embodiment 20, wherein: the control information is transmitted via a DCI message; and the interval is indicated in a TDRA field of the DCI message.

[0213] Example 22: The method of Example 21 further includes using PUSCH repetition type B to configure the multi-TRP transmission.

[0214] Embodiment 23: The method of embodiment 22, wherein: the UE has the capability of supporting multiple active panels; and at least one of the fields in the DCI message indicates more than one TRP transmission.

[0215] Embodiment 24: The method of any embodiment of embodiments 20 to 23 further includes: not scheduling the UE to transmit or receive through the shared channel during the interval between each TRP transmission.

[0216] Embodiment 25: The method of any embodiment of Embodiments 20 to 24 further comprises: configuring K repetitions for the PUSCH used for the multi-TRP transmission.

[0217] Example 26: The method of any of Examples 20 to 25, further comprising enabling frequency hopping for the multi-TRP transmission.

[0218] Example 27: The method of Example 26 further includes providing a frequency hopping offset to the UE.

[0219] Embodiment 28: The method of any of the preceding embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or wireless device.

[0220] Group C Examples

[0221] Embodiment 29: A wireless device for transmitting to multiple TRPs, the wireless device comprising: a processing circuit module configured to perform any of the steps of any of the embodiments of Group A; and a power supply circuit module configured to provide power to the wireless communication device.

[0222] Embodiment 30: A base station for facilitating transmission to multiple TRPs, the base station comprising: a processing circuit module configured to perform any of the steps of any of the embodiments of Group B; and a power circuit module configured to provide power to the base station.

[0223] Embodiment 31: A UE for transmitting to multiple TRPs, the UE comprising: an antenna configured to send and receive wireless signals; a radio front-end circuit module connected to the antenna and a processing circuit module, and configured to adjust the signals communicated between the antenna and the processing circuit module; the processing circuit module is configured to perform any step of the steps of any embodiment of Group A; an input interface connected to the processing circuit module, and configured to allow information processed by the processing circuit module to be input into the UE; an output interface connected to the processing circuit module, and configured to output information processed by the processing circuit module from the UE; and a battery connected to the processing circuit module, and configured to provide power to the UE.

[0224] Embodiment 32: A communication system includes a host computer, the host computer comprising: a processing circuit module configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a UE; wherein the cellular network includes a base station having a radio interface and a processing circuit module, the processing circuit module of the base station being configured to perform any steps of any embodiment of Group B.

[0225] Example 33: The communication system of the previous embodiment further includes the base station.

[0226] Embodiment 34: The communication system of the first two embodiments further comprises the UE, wherein the UE is configured to communicate with the base station.

[0227] Embodiment 35: The communication system of the first three embodiments, wherein: the processing circuit module of the host computer is configured to execute a host application, thereby providing the user data; and the UE includes a processing circuit module, and the processing circuit module is configured to execute a client application associated with the host application.

[0228] Embodiment 36: A method implemented in a communication system, the communication system comprising a host computer, a base station and a UE, the method comprising: providing user data at the host computer; and initiating at the host computer a transmission carrying the user data to the UE via a cellular network including the base station, wherein the base station performs any of the steps of any embodiment of Group B.

[0229] Embodiment 37: The method of the previous embodiment further includes transmitting the user data at the base station.

[0230] Embodiment 38: The method of the preceding two embodiments, wherein the user data is provided on the host computer by executing a host application, the method further comprising executing a client application associated with the host application on the UE.

[0231] Embodiment 39: A UE configured to communicate with a base station, the UE comprising a radio interface and a processing circuit module, the processing circuit module configured to execute the methods of the first three embodiments.

[0232] Embodiment 40: A communication system comprises a host computer, the host computer including: a processing circuit module configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a UE; wherein the UE includes a radio interface and a processing circuit module, and the components of the UE are configured to perform any steps of any embodiment of Group A.

[0233] Embodiment 41: The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

[0234] Embodiment 42: The communication system of the first two embodiments, wherein: the processing circuit module of the host computer is configured to execute a host application, thereby providing the user data; and the processing circuit module of the UE is configured to execute a client application associated with the host application.

[0235] Embodiment 43: A method implemented in a communication system, the communication system comprising a host computer, a base station and a UE, the method comprising: providing user data at the host computer; and initiating at the host computer a transmission carrying the user data to the UE via a cellular network including the base station, wherein the UE performs any step of the steps of any embodiment of Group A.

[0236] Embodiment 44: The method of the previous embodiment further includes receiving the user data from the base station at the UE.

[0237] Embodiment 45: A communication system includes a host computer, the host computer comprising: a computer configured to receive user data originating from a transmission from a UE to a base station; wherein the UE includes a radio interface and a processing circuit module, and the components of the UE are configured to perform any steps of any embodiment of Group A.

[0238] Example 46: The communication system of the previous embodiment further includes the UE.

[0239] Embodiment 47: The communication system of the previous two embodiments further comprises the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward the user data carried by the transmission from the UE to the base station to the host computer.

[0240] Embodiment 48: The communication system of the first three embodiments, wherein: the processing circuit module of the host computer is configured to execute a host application; and the processing circuit module of the UE is configured to execute a client application associated with the host application, thereby providing the user data.

[0241] Example 49: The communication system of the first four embodiments, wherein: the processing circuit module of the host computer is configured to execute a host application, thereby providing request data; and the processing circuit module of the UE is configured to execute a client application associated with the host application, thereby providing the user data (in response to the request data).

[0242] Embodiment 50: A method implemented in a communication system, the communication system comprising a host computer, a base station and a UE, the method comprising: receiving user data transmitted from the UE to the base station at the host computer, wherein the UE performs any step of the steps of any embodiment of Group A.

[0243] Example 51: The method of the previous embodiment further includes providing the user data to the base station by the UE.

[0244] Embodiment 52: The method of the first two embodiments further comprises: executing a client application on the UE, thereby providing the user data for transmission; and executing a host application on the host computer in conjunction with the client application.

[0245] Example 53: The method of the first three embodiments further includes: executing a client application on the UE; and receiving input data of the client application on the UE, the input data being provided on the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application (in response to the input data).

[0246] Embodiment 54: A communication system comprises a host computer, the host computer including a communication interface, the communication interface configured to receive user data originating from a transmission from a UE to a base station, wherein the base station includes a radio interface and a processing circuit module, the processing circuit module of the base station is configured to perform any steps of any embodiment of Group B.

[0247] Example 55: The communication system of the previous embodiment further includes the base station.

[0248] Embodiment 56: The communication system of the first two embodiments further comprises the UE, wherein the UE is configured to communicate with the base station.

[0249] Embodiment 57: The communication system of the first three embodiments, wherein: the processing circuit module of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing the user data for receipt by the host computer.

[0250] Embodiment 58: A method implemented in a communication system comprising a host computer, a base station, and a UE, the method comprising: receiving user data at the host computer from the base station, the user data originating from a transmission that the base station has received from the UE, wherein the UE performs any of the steps of any of the embodiments of Group A.

[0251] Example 59: The method of the previous embodiment further includes receiving the user data from the UE at the base station.

[0252] Embodiment 60: The method of the preceding two embodiments further comprises initiating, at the base station, transmission of the received user data to the host computer.

[0253] At least some of the following abbreviations may be used in this disclosure. If there is inconsistency between an abbreviation, then priority should be given to how it is used above. If listed below multiple times, the first listing should take precedence over any subsequent (one or more) listings.

[0254] 3GPP Third Generation Partnership Project

[0255] 5G fifth generation

[0256] 5GC fifth generation core

[0257] 5GS fifth generation system

[0258] AMF access and mobility management function

[0259] ASIC Application-Specific Integrated Circuit

[0260] AUSF authentication server function

[0261] BWP Bandwidth Part

[0262] CG configuration license

[0263] CP-OFDM Cyclic Prefix Orthogonal Frequency Division Multiplexing

[0264] CPU Central Processing Unit

[0265] C-RNTI Cell Radio Network Temporary Identifier

[0266] CRC Cyclic Redundancy Check

[0267] CSI-RS Channel State Information Reference Signal

[0268] CS-RNTI configured Scheduling Radio Network Temporary Identifier

[0269] DCI Downlink Control Information

[0270] DFT Discrete Fourier Transform

[0271] DL Downlink

[0272] DMRS Demodulation Reference Signal

[0273] DSP digital signal processor

[0274] eNB Enhanced or Evolved Node B

[0275] EPC Evolved Packet Core

[0276] EPS Evolved Packet System

[0277] E-UTRA Evolved Universal Terrestrial Radio Access

[0278] FDD frequency domain duplexing

[0279] FPGA Field Programmable Gate Array

[0280] gNB new air interface base station

[0281] gNB-CU new radio base station central unit

[0282] gNB-DU new air interface base station distributed unit

[0283] HSS Home Subscriber Server

[0284] IE Information Element

[0285] IoT

[0286] LTE Long Term Evolution

[0287] MCS-C-RNTI Modulation and Coding Scheme Cell Radio Network Temporary Identifier

[0288] MIMO Multiple Input Multiple Output

[0289] MME Mobility Management Entity

[0290] MTC Machine Type Communication

[0291] NDI New Data Indicator

[0292] NEF network open function

[0293] NF Network Function

[0294] NR New Radio

[0295] NRF Network Function Repository functionality

[0296] NSSF network slice selection function

[0297] NZP Non-Zero Power

[0298] OFDM Orthogonal Frequency Division Multiplexing

[0299] PC personal computer

[0300] PCF policy control function

[0301] PDCCH Physical Downlink Control Channel

[0302] PDSCH Physical Downlink Shared Channel

[0303] P-GW Packet Data Network Gateway

[0304] PUSCH Physical Uplink Shared Channel

[0305] RAM Random Access Memory

[0306] RAN Radio Access Network

[0307] RB Resource Block

[0308] RE resource element

[0309] ROM Read Only Memory

[0310] RRC Radio Resource Control

[0311] RRH Remote Radio Head

[0312] RS reference signal

[0313] RV Redundant Version

[0314] RX

[0315] SCEF service capability exposure function

[0316] SLIV start and length indicator value

[0317] SMF session management capabilities

[0318] SRS Sounding Reference Signal

[0319] SSB Synchronous Signal Block

[0320] TB transport block

[0321] TCI transmission configuration information

[0322] TDD Time Domain Duplex

[0323] TDRA Time Domain Resource Allocation

[0324] TPMI Transmit Precoding Matrix Indicator

[0325] TRP Transmit / Receive Point

[0326] TX transmission

[0327] UDM unified data management

[0328] UE User Equipment

[0329] UL uplink

[0330] UPF User Plane Function

[0331] URLLC Ultra-Reliable Low Latency Communication

[0332] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure.All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

Claims

1. A method performed by a wireless device (412) for transmitting data to a plurality of transmission / reception points (TRPs), the method comprising: - receiving (802) control information for scheduling multiple TRP transmissions, said control information comprising an indication of an interval between each TRP transmission; - transmitting (804) the data to a first TRP according to the control information; - after the interval, transmitting (806) the data to a second TRP according to the control information; as well as - Applying (810) the redundancy version RV offset to the multi-TRP transmission according to the received configuration.

2. The method according to claim 1, wherein Each TRP is characterized by a reference signal transmitted from the TRP and previously received by the wireless device or previously transmitted from the wireless device to the TRP, and is indicated to the wireless device by a spatial relationship, the spatial relationship including the reference signal or a transmission configuration information TCI state, the TCI state including the reference signal.

3. The method according to any one of claims 1 to 2, further comprising: Prior to receiving (802) the control information, an ability of the wireless device (412) to support one or more active panels is indicated (800) to a network node (1000).

4. The method according to any one of claims 1 to 2, wherein: - receiving (802) said control information from the network node (1000) via a downlink control information DCI message; and - The interval is indicated in the Time Domain Resource Allocation TDRA field of the DCI message.

5. The method according to claim 4, wherein: The multi-TRP transmission is configured with physical uplink shared channel PUSCH repetition type B.

6. The method of claim 5, wherein: - the wireless device (412) supports multi-panel transmission; and -At least one field in the DCI message indicates more than one TRP transmission.

7. The method according to any one of claims 1 to 2, wherein: The interval is indicated as the minimum number of symbols in which the wireless device (412) is not scheduled to transmit or receive over the shared channel between transmitting to the first TRP (804) and transmitting to the second TRP (806).

8. The method of claim 7, wherein: The symbols including the interval after transmission to the first TRP (804) are treated as downlink symbols or invalid symbols.

9. The method of claim 8, further comprising, if the symbol including the gap is in a resource block indicated for transmission to the second TRP, transmitting to the second TRP on the remaining symbols of the resource block (806).

10. The method according to any one of claims 1 to 2, wherein: The interval is indicated as the number of symbols after starting to transmit to the first TRP (804) and before starting to transmit to the second TRP (806).

11. The method according to any one of claims 1 to 2, wherein: The interval is implicitly indicated by using a time domain resource allocation TDRA that is repeated for a shared channel associated with the multiple TRP transmissions.

12. The method according to any one of claims 1 to 2, wherein: The intervals are configured by higher layers.

13. The method according to any one of claims 1 to 2, wherein: K repetitions are configured for the physical uplink shared channel PUSCH used for the multiple TRP transmissions.

14. The method of claim 13, wherein: The configured repetition K is applied to each TRP of the multi-TRP transmission.

15. The method of claim 13, wherein: The configured repetitions K are distributed between the first TRP and the second TRP.

16. The method of claim 13, wherein: Each TRP of the multi-TRP transmission is transmitted in sequence and repeated until the configured repetition k is reached.

17. The method according to any one of claims 1 to 2, wherein: The control information further includes a flag for enabling frequency hopping for the multi-TRP transmission.

18. The method of claim 17, further comprising: A frequency hopping offset indicated by the control information is applied (808) on all TRPs of the multi-TRP transmission.

19. The method of claim 17, further comprising: A frequency hopping offset is applied (808), wherein the control information indicates a single resource allocation for all TRPs of the multi-TRP transmission and the frequency hopping offset is configured by a higher layer.

20. The method of claim 19, wherein: - the frequency hopping occurs within the transmission to each TRP; as well as - The transmission to the second TRP (806) occurs after a frequency jump within the transmission to the first TRP and after the interval.

21. The method of claim 19, wherein: - the frequency hopping occurs between transmissions to the same TRP; as well as - The method further comprises: transmitting to the first TRP using the frequency hopping offset after the transmission (806) to the second TRP and after another interval.

22. The method of claim 1, wherein: The control information indicates a first RV for a first repetition to the first TRP.

23. The method of claim 22, wherein: A second RV for the first repetition to the second TRP is given by applying the RV offset to the first RV.

24. The method of claim 22, wherein: The RV offset is configured by the Radio Resource Control (RRC) and is applied according to the following table: Among them rv id refers to the first RV, rv UL,s refers to the RV offset, and DCI refers to a downlink control information message in which the control information is received.

25. A method performed by a network node (1000) for facilitating transmission to a plurality of transmission / reception points (TRPs), the method comprising: - receiving (900) an indication of the capability of the user equipment UE to support one or more active panels; - scheduling (902) multiple TRP transmissions by the UE based on the indication of the capability; - sending (904) control information for the multiple TRP transmissions to the UE, the control information comprising an indication of an interval between each TRP transmission; and -Configuring (910) the redundancy version RV offset for the multi-TRP transmission.

26. The method of claim 25, wherein: - the control information is transmitted via a Downlink Control Information (DCI) message; and - The interval is indicated in the Time Domain Resource Allocation TDRA field of the DCI message.

27. The method of claim 26, further comprising: The physical uplink shared channel PUSCH repetition type B is used to configure the multi-TRP transmission.

28. The method of claim 27, wherein: - the UE has the capability to support multiple active panels; and -At least one field in the DCI message indicates more than one TRP transmission.

29. The method of any one of claims 25 to 28, further comprising: The UE is not scheduled to transmit or receive over the shared channel during the interval between each TRP transmission.

30. The method of any one of claims 25 to 28, further comprising: K repetitions are configured (906) for a physical uplink shared channel PUSCH for the multi-TRP transmission.

31. The method of any one of claims 25 to 28, further comprising: Enable (908) frequency hopping for the multi-TRP transmission.

32. The method of claim 31 , further comprising: A frequency hopping offset is provided to the UE.

33. The method of claim 25, further comprising: - signaling the RV offset to the UE using a radio resource control (RRC) message; as well as -Signaling a first RV to the UE via a downlink control information DCI message, the downlink control information DCI message including the control information for the multiple TRP transmission.

Images