CN113766665A - Apparatus and method for codebook-based UL transmission in multiple TRP scenarios - Google Patents

Abstract

The present disclosure provides apparatuses and methods for codebook-based UL transmission in multiple TRP scenarios. The apparatus for a UE includes: an RF interface circuit configured to receive DCI from a TRP, the DCI for scheduling a codebook-based PUSCH transmission to a plurality of TRPs; and processing circuitry coupled with the RF interface circuitry and configured to: encoding and multiplexing a plurality of codebook-based PUSCH repetitions based on the DCI and PUSCH configuration information from higher layers; and repeatedly providing the encoded and multiplexed PUSCH to the RF interface circuitry for transmission to the plurality of TRPs.

Description

Apparatus and method for codebook-based UL transmission in multiple TRP scenarios

Technical Field

Embodiments of the present disclosure relate generally to wireless communications, and in particular, to an apparatus and method for codebook-based Physical Uplink Shared Channel (PUSCH) transmission in a multiple Transmission Reception Point (TRP) scenario with a single Downlink Control Information (DCI).

Background

In fifth generation (5G) or New Radio (NR) mobile communications, it is important to allow dynamic switching between single-TRP and multi-TRP transmissions to make the coordinated multi-point (CoMP) scheme more useful. In release 16 of the 3GPP technical specification for 5G/NR systems (hereinafter referred to as "5G/NR Rel-16"), multi-TRP related operations are introduced mainly for Physical Downlink Shared Channel (PDSCH) transmissions. Depending on different backhaul assumptions (e.g., ideal backhaul assumptions and non-ideal backhaul assumptions), the operations related to multiple TRPs may include single DCI operations and multiple DCI operations.

The multiple DCI operation may correspond to a non-ideal backhaul assumption. With multiple DCIs, each TRP may have one Physical Downlink Control Channel (PDCCH) for scheduling a corresponding PDSCH transmission. A single DCI operation may correspond to an ideal backhaul hypothesis. With a single DCI, a single PDCCH may be used to schedule multiple PDSCH transmissions from multiple TRPs.

Disclosure of Invention

An aspect of the present disclosure provides an apparatus for a user equipment UE, including: a Radio Frequency (RF) interface circuit configured to receive Downlink Control Information (DCI) from a Transmit Reception Point (TRP), the DCI being for scheduling a codebook-based Physical Uplink Shared Channel (PUSCH) transmission to a plurality of TRPs; and processing circuitry coupled with the RF interface circuitry and configured to: encoding and multiplexing a plurality of codebook-based PUSCH repetitions based on the DCI and PUSCH configuration information from higher layers; and repeatedly providing the encoded and multiplexed PUSCH to the RF interface circuitry for transmission to the plurality of TRPs.

An aspect of the present disclosure provides a method performed at a UE, comprising: receiving downlink control information, DCI, from a transmission reception point, TRP, the DCI being for scheduling a codebook-based physical uplink shared channel, PUSCH, transmission to a plurality of TRPs; encoding and multiplexing a plurality of codebook-based PUSCH repetitions based on the DCI and PUSCH configuration information from higher layers; and repeatedly sending the encoded and multiplexed PUSCH to the plurality of TRPs.

An aspect of the present disclosure provides an apparatus for transmitting a reception point TRP, including: a radio frequency, RF, interface circuit configured to receive one or more sounding reference signals, SRSs, from a user equipment, UE, via one or more SRS resources of one or more SRS resource sets whose usage is set to 'codebook'; and processing circuitry coupled with the RF interface circuitry and configured to: generating downlink control information, DCI, for scheduling codebook-based PUSCH transmissions to a plurality of TRPs based on the measurements of the one or more SRS resources and configuration information associated with physical uplink shared channel, PUSCH, repetitions from higher layers; and provide the DCI to the RF interface circuitry for transmission to the UE.

An aspect of the present disclosure provides a method performed at a transmission reception point TRP, including: receiving one or more Sounding Reference Signals (SRS) from a User Equipment (UE) via one or more SRS resources in one or more SRS resource sets whose usage conditions are set to 'codebook'; generating downlink control information, DCI, to schedule codebook-based PUSCH transmissions to a plurality of TRPs based on measurements of the one or more SRS resources and configuration information associated with physical uplink shared channel, PUSCH, repetitions from higher layers; and transmitting the DCI to the UE.

Drawings

Embodiments of the present disclosure will be described by way of example, and not limitation, in the figures of the accompanying drawings in which like references indicate similar elements.

Fig. 1 illustrates exemplary multiple TRP related operations for downlink transmissions in accordance with some embodiments of the present disclosure.

Fig. 2 illustrates an example of a discrete fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) transmitter, in accordance with some embodiments of the present disclosure.

Fig. 3 illustrates an example process of codebook-based and non-codebook-based PUSCH transmissions, in accordance with some embodiments of the present disclosure.

Fig. 4 illustrates an example scheme of Frequency Division Multiplexing (FDM) -based PUSCH repetitions (repeats) in frequency range 1(FR1) according to some embodiments of the present disclosure.

Fig. 5 illustrates another example scheme of FDM based PUSCH repetition in FR1 in accordance with some embodiments of the present disclosure.

Fig. 6 illustrates an example scheme of FDM based PUSCH repetition in frequency range 2(FR2) according to some embodiments of the present disclosure.

Fig. 7 illustrates another example scheme of FDM based PUSCH repetition in FR2 in accordance with some embodiments of the present disclosure.

Fig. 8 illustrates an example scheme of FDM-based PUSCH repetition with DFT-s-OFDM waveforms in two TRP scenarios, in accordance with some embodiments of the present disclosure.

Fig. 9 illustrates an example scheme of FDM-based PUSCH repetition with DFT-s-OFDM waveforms in four TRP scenarios, in accordance with some embodiments of the present disclosure.

Fig. 10 illustrates an example scheme of Time Division Multiplexing (TDM) based PUSCH repetition in FR1, according to some embodiments of the present disclosure.

Fig. 11 illustrates another example scheme of TDM-based PUSCH repetition in FR1, according to some embodiments of the present disclosure.

Fig. 12 shows an example scheme of TDM-based PUSCH repetition in FR2, according to some embodiments of the present disclosure.

Fig. 13 illustrates another example scheme of TDM-based PUSCH repetition in FR2, according to some embodiments of the present disclosure.

Fig. 14 illustrates an example scheme of TDM-based PUSCH repetition with DFT-s-OFDM waveforms and different sizes of frequency resource allocation in two TRP scenarios, according to some embodiments of the present disclosure.

Fig. 15 illustrates an example scheme of Spatial Division Multiplexing (SDM) based PUSCH repetition in FR2, according to some embodiments of the present disclosure.

Fig. 16 illustrates an example process associated with PUSCH repeated codebook-based transmission at a User Equipment (UE), in accordance with some embodiments of the present disclosure.

Fig. 17 illustrates an example process associated with PUSCH repeated codebook-based transmission at a TRP, in accordance with some embodiments of the present disclosure.

Fig. 18 illustrates an example network according to various embodiments of the present disclosure.

Fig. 19 schematically illustrates a wireless network in accordance with various embodiments of the present disclosure.

Fig. 20 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some example embodiments.

Detailed Description

Various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of the disclosure to others skilled in the art. However, it will be readily appreciated by those skilled in the art that many alternative embodiments may be practiced using portions of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. However, it will be apparent to one skilled in the art that alternative embodiments may be practiced without the specific details. In other instances, well-known features may be omitted or simplified in order not to obscure the illustrative embodiments.

Further, various operations will be described as multiple discrete operations, in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.

The phrases "in an embodiment," "in one embodiment," and "in some embodiments" are used repeatedly herein. The phrase generally does not refer to the same embodiment; however, it may refer to the same embodiment. The terms "comprising," "having," and "including" are synonymous, unless the context dictates otherwise. The phrases "A or B" and "A/B" mean "(A), (B) or (A and B)".

In 5G/NR Rel-16, multi-TRP related operations are introduced mainly for PDSCH transmissions. Depending on different backhaul assumptions (e.g., ideal backhaul assumptions and non-ideal backhaul assumptions), the operations related to multiple TRPs may include single DCI operations and multiple DCI operations. The multiple DCI operation may correspond to a non-ideal backhaul assumption. With multiple DCIs, each TRP may have one PDCCH for scheduling a corresponding PDSCH transmission. A single DCI operation may correspond to an ideal backhaul hypothesis. With a single DCI, a single PDCCH may be used to schedule multiple PDSCH transmissions from multiple TRPs.

Fig. 1 illustrates exemplary multiple TRP related operations for downlink transmissions in accordance with some embodiments of the present disclosure. As an example, two TRPs (TRP # a and TRP # B) are provided to communicate with a UE having a plurality of antenna panels. As shown in fig. 1, for an ideal backhaul assumption, a single PDCCH from TRP # a carrying a single DCI may schedule both PDSCH transmission from TRP # a to the UE (PDSCH #1) and PDSCH transmission from TRP # B to the UE (PDSCH # 2); for non-ideal backhaul assumptions, TRP # a may have PDCCH #1 for scheduling a corresponding PDSCH transmission from TRP # a to the UE (PDSCH #1), while TRP # B may have PDSCH #2 for scheduling a corresponding PDSCH transmission from TRP # B to the UE (PDSCH # 2).

As described above, operations related to multiple TRP may include single DCI operations and multiple DCI operations. On the other hand, the multi-TRP related operations may include multi-TRP related operations for a downlink (e.g., PDSCH) and multi-TRP related operations for an uplink (e.g., PUSCH). In 5G/NR Rel-16, multi-TRP related operations are introduced mainly for PDSCH transmission, but multi-TRP related operations for PUSCH transmission are not defined. In this application, operations related to multiple TRP for PUSCH transmission with a single DCI will be discussed in detail.

In a 5G/NR communication system, a waveform for PUSCH transmission may be a cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) waveform or a discrete fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) waveform. Fig. 2 illustrates an example of a DFT-s-OFDM transmitter in accordance with some embodiments of the present disclosure. As shown in fig. 2, the DFT-s-OFDM transmitter may be configured to generate a DFT-s-OFDM waveform for PUSCH transmission by: the DFT spreading is first applied to PUSCH data in the time domain, then OFDM modulation is applied to PUSCH data via Inverse Discrete Fourier Transform (IDFT), and finally a cyclic prefix is added.

In addition, according to 5G/NR Rel-16, two schemes for PUSCH transmission are defined, namely codebook-based transmission and non-codebook-based transmission. Fig. 3 illustrates an example process of codebook-based and non-codebook-based PUSCH transmissions, in accordance with some embodiments of the present disclosure.

For codebook-based transmission, a UE may be configured with one set of Sounding Reference Signal (SRS) resources, which consists of one or more SRS resources. The 'usage (usage)' of the SRS resource set is set to 'codebook'. The UE needs to transmit one or more SRSs to the next generation nodeb (gnb) via SRS resources for link adaptation, and the SRS may not be precoded. After the gNB measures the SRS resources, the gNB may send DCI including an uplink grant to schedule PUSCH transmission. In the uplink grant, a Transmission Precoding Matrix Index (TPMI) and an SRS Resource Indicator (SRI) are included. In the corresponding PUSCH transmission, the UE may apply the precoder indicated by the TPMI. The number of antenna ports for PUSCH transmission may be the same as the SRS resource indicated by the SRI. In frequency range 2(FR2), PUSCH transmission may use the same spatial relationship (same beam) as the SRS resource indicated by the SRI.

For non-codebook based transmissions, a UE may be configured with one set of SRS resources consisting of one or more SRS resources. The 'use case' of the SRS resource set is set to 'non codebook'. All SRS resources may be configured with only one antenna port. For non-codebook based transmissions, a UE may be configured with non-zero power (NZP) channel state information reference signal (CSI-RS) resources associated with a set of SRS resources. Based on the measurements of the CSI-RS resources, the UE may calculate a precoder for SRS transmission. In other words, for non-codebook based transmissions, one or more SRSs transmitted via SRS resources for link adaptation are precoded. After measuring SRS, the gNB may indicate one or several SRIs for PUSCH transmission. The UE may select a precoder for PUSCH transmission according to the indicated SRI. In FR2, the spatial relationship for PUSCH transmission may be based on SRI or on measurements on CSI-RS resources.

In a multiple TRP scenario, to improve reliability, the UE may repeatedly transmit PUSCH to multiple TRPs. In the present application, codebook-based PUSCH transmission schemes, such as resource allocation, TPMI selection, spatial relationship, etc., with a single DCI will be provided to enable a UE to transmit PUSCH repetitions to multiple TRPs in a multiple TRP scenario.

In general, for PUSCH transmission with a single DCI operation, a PUSCH may be transmitted in conjunction with repetition for different TRPs, which may be configured with the same cell Identification (ID) or different cell IDs, to improve reliability. The type of PUSCH repetition may be a Frequency Division Multiplexing (FDM) -based PUSCH repetition, a Time Division Multiplexing (TDM) -based PUSCH repetition, or a Space Division Multiplexing (SDM) -based PUSCH repetition, which will be described in detail later. Note that the UE may support some type of PUSCH repetition, so the UE may need to report the UE's capability to the TRP or higher layers as to which type of PUSCH repetition is supported.

In addition, a new Radio Resource Control (RRC) Information Element (IE), PUSCH-Config, may be introduced in the new IE, repeatschemestusch, to indicate the type of PUSCH repetition. Another parameter, e.g., number of puschpeepiechoices, may also be introduced in the PUSCH-Config to indicate the number of PUSCH repetitions.

According to some embodiments of the application, forFor codebook-based transmission, the TPMI used for PUSCH transmission may be the same or different for PUSCH repetitions. If different TPMI is used for different PUSCH repetition, multiple TPMI should be indicated to the UE in DCI. For example, the precoding andmbuberoflayers field in the DCI may be extended to include multiple TPMIs. Number of TPMI transmitted in DCI N_TPMI,RepMay be predefined or configured by the higher layers.

Further, for codebook-based transmission, the number of antenna ports used for PUSCH transmission is indicated by SRI. When multiple SRS resources are indicated, the number of SRS antenna ports for the SRS resources may be the same or different. In FR2, spatial relationships are also indicated by SRIs. The indicated spatial relationships of the plurality of SRS resources may be the same or different. Thus, for PUSCH repetition, the SRI field in DCI may be extended to convey multiple SRIs. Number of SRIs N conveyed in the SRI field_SRI,RepMay be predefined or configured by the higher layers. N is a radical of_TPMI,RepAnd N_SRI,RepThe values of (c) may be the same or different.

In particular, in order to enable the UE to transmit PUSCH repetitions to a plurality of TRPs in a multi-TRP scenario using a single DCI, the DCI may include a precoding andnumberoflayers field including one or more TPMIs and an SRI field including one or more SRIs for PUSCH repetitions, and the number of the one or more TPMIs and the number of the one or more SRIs may be predefined or configured by the higher layer.

According to some embodiments of the application, may be implemented by

To determine the field length of the SRI field, where N_SRSIs the number of SRS resources, N, configured in an SRS resource set_SRI,RepIs the number of one or more SRIs to be used for PUSCH repetition. When N is present_SRI,RepEqual to 1, a single SRI contained in the SRI field may be used for all PUSCH repetitions; when N is present_SRI,RepWhen the number of the repeated PUSCH is equal to the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH can be in one-to-one mapping relation; when N is present_SRI,RepWhen the number of the repetitions of the PUSCH is smaller than the number of the repetitions of the PUSCH, the SRI and the repetitions of the PUSCH contained in the SRI field may be in a one-to-many mapping relationship. The one-to-many mapping relationship may include: repeat i (i ∈ (0,1, … numberof PUSCHrows-1)), SRI for PUSCH_j(j∈(0,1,…N_SRI,Rep-1)) is applied to PUSCH repetition i, where numberpuschhrepetitiones is the number of PUSCH repetitions, and j ═ i mod N_SRI,RepOr

According to some embodiments of the present application, N ═ L may be passed_TPMI×N_TPMI,RepDetermining the field length of the precoding AndNumberOfLayers field, where L_TPMIIs the field length of the precoding AndNumberOfLayers field when no PUSCH repetition is configured, and N_TPMI,RepIs the number of one or more TPMIs for PUSCH repetition. When N is present_TPMI,RepEqual to 1, a single TPMI contained in the precoding andmbumberbeolayers field can be used for all PUSCH repetitions; when N is present_TPMI,RepEqual to the number of PUSCH repetitions, the TPMI contained in the precoding andmbumberoflayers field may be in a one-to-one mapping relationship with the PUSCH repetitions; when N is present_TPMI,RepThe TPMI contained in the precoding andmbuberoflayers field may be in a one-to-many mapping relationship with PUSCH repetitions when smaller than the number of PUSCH repetitions. The one-to-many mapping relationship may include: repeat i (i ∈ (0,1, … numberof PUSCHrows-1)), TPMI for PUSCH_k(k∈(0,1,…N_TPMI,Rep-1)) is applied to the PUSCH repetition i, where numberpuschhrepetitionis is the number of PUSCH repetitions, and

according to some embodiments of the present application, one or more new fields may be introduced in DCI to convey multiple TPMIs or multiple SRIs for PUSCH repeated transmission. Alternatively, a new DCI format may be defined for PUSCH repeated transmission.

According to some embodiments, for codebook-based transmission, to support PUSCH repeated transmission for different TRPs, a UE may be configured with multiple SRS resource sets, whose usage is set to 'codebook'. The number of SRS resources in each set of SRS resources may be the same or different. Different sets of SRS resources may be associated with different TRPs. In the DCI, the SRI field may contain one or more SRIs, each SRI indicating an SRS resource from a respective SRS resource set of the plurality of SRS resource sets.

As described above, the type of PUSCH repetition may be FDM-based PUSCH repetition, TDM-based PUSCH repetition, or SDM-based PUSCH repetition. Various embodiments will be provided below with reference to fig. 4 to 15 to illustrate transmission schemes repeated for various types of PUSCH.

According to some embodiments of the present application, for codebook-based PUSCH transmission, PUSCH repetitions may be transmitted in an FDM-based manner. PUSCH repetition may occupy different portions of the frequency domain resources.

A Repetition Resource Group (RRG) may be defined for PUSCH repeated transmission. One RRG may include a plurality of consecutive Physical Resource Blocks (PRBs). The UE should apply the same TPMI/SRI/spatial relationship for PRBs within one RRG. The RRGs may be equally or unequally divided in the frequency band. One PUSCH repetition may correspond to one RRG, and the number of RRGs may be indicated by numberofpuschpeerations. The index of the RRG may be UE-specific and based on the frequency bandwidth allocated to the UE. Alternatively, the index of the RRG may be cell-specific and based on the reference number of the RRG relative to the common resource block # 0. For example, the UE may be allocated 24 PRBs, from PRB #36 to PRB #59, and may configure two RRGs, each of which may include 12 PRBs, for PUSCH repeated transmission. In this example, when UE-specific indices are used, RRGs may be numbered as RRG #0 and RRG #1, while when cell-specific indices are used, RRGs may be numbered as RRG #3 and RRG # 4.

Fig. 4 illustrates an example scheme of FDM based PUSCH repetition in FR1 in accordance with some embodiments of the present disclosure. As shown in fig. 4, two RRGs, RRG #0 and RRG #1, are allocated for transmitting PUSCH repetition to TRP # a and PUSCH repetition to TRP # B, respectively. The DCI includes two TPMI (TPMI #0 and TPMI #1) and two SRI (SRI #0 and SRI #1) for scheduling transmission of two PUSCH repetitions, so the TPMI and PUSCH repetitions are in one-to-one mapping relationship, and the SRI and PUSCH repetitions are in one-to-one mapping relationship.

Fig. 5 illustrates another example scheme of FDM based PUSCH repetition in FR1 in accordance with some embodiments of the present disclosure. As shown in fig. 5, four RRGs, RRG #0, RRG #1, RRG #2, and RRG #3, are allocated for transmitting two PUSCH repetitions to TRP # a and two PUSCH repetitions to TRP # B, respectively. The DCI includes two TPMI (TPMI #0 and TPMI #1) and two SRI (SRI #0 and SRI #1) for scheduling transmission of four PUSCH repetitions, so the TPMI and PUSCH repetitions are in a one-to-many mapping relationship, and the SRI and PUSCH repetitions are in a one-to-many mapping relationship.

Fig. 6 illustrates an example scheme of FDM based PUSCH repetition in FR2 in accordance with some embodiments of the present disclosure. As shown in fig. 6, similar to fig. 4, two RRGs are allocated for transmission of PUSCH repetition to TRP # a and PUSCH repetition to TRP # B, respectively, and DCI contains two TPMI and two SRI for scheduling transmission of two PUSCH repetitions. TPMI is a one-to-one mapping relationship with PUSCH repetition, and SRI is a one-to-one mapping relationship with PUSCH repetition. Fig. 6 differs from fig. 4 in that: in FR2, different spatial relationships may be applied to PUSCH repeated transmissions destined for different TRPs. For example, the PUSCH repetition destined for TRP # a may be transmitted via spatial relationship #0 and the PUSCH repetition destined for TRP # B may be transmitted via spatial relationship # 1.

Fig. 7 illustrates another example scheme of FDM based PUSCH repetition in FR2 in accordance with some embodiments of the present disclosure. As shown in fig. 7, similar to fig. 5, four RRGs are allocated for transmission of two PUSCH repetitions to TRP # a and two PUSCH repetitions to TRP # B, respectively, and DCI contains two TPMI and two SRI for scheduling transmission of the four PUSCH repetitions. TPMI is a one-to-many mapping relationship with PUSCH repetition, and SRI is a one-to-many mapping relationship with PUSCH repetition. Fig. 7 differs from fig. 5 in that: in FR2, different spatial relationships may be applied to PUSCH repeated transmissions destined for different TRPs. For example, the PUSCH repetition destined for TRP # a may be transmitted via spatial relationship #0 and the PUSCH repetition destined for TRP # B may be transmitted via spatial relationship # 1.

As described above, the waveform used for PUSCH transmission may be a CP-OFDM waveform or a DFT-s-OFDM waveform. As shown in fig. 2, the DFT-s-OFDM transmitter may be configured to generate a DFT-s-OFDM waveform for PUSCH transmission by: the DFT spreading is first applied to PUSCH data in the time domain, then OFDM modulation is applied to PUSCH data via Inverse Discrete Fourier Transform (IDFT), and finally a cyclic prefix is added.

Fig. 8 illustrates an example scheme of FDM-based PUSCH repetition with DFT-s-OFDM waveforms in two TRP scenarios, in accordance with some embodiments of the present disclosure. Fig. 9 illustrates an example scheme of FDM-based PUSCH repetition with DFT-s-OFDM waveforms in four TRP scenarios, in accordance with some embodiments of the present disclosure. As shown in fig. 8 and 9, the DFT-s-OFDM transmitter may be configured to generate and multiplex a PUSCH repetition into a DFT-s-OFDM waveform by: the method includes applying DFT spreading to PUSCH data in a time domain, copying the PUSCH data after the DFT spreading to generate a PUSCH repetition, mapping the PUSCH repetition to each RRG, and repeatedly applying OFDM modulation to the PUSCH via IDFT.

According to some embodiments of the present application, for codebook-based PUSCH transmission, PUSCH repetitions may be transmitted in a TDM-based manner. PUSCH repetition may occupy different time periods of the time domain resources. The PUSCH repetition may be within one slot (intra-slot) or across multiple slots (inter-slot). There may be a gap period between two PUSCH repetitions, and the gap period may also be zero, meaning that the PUSCH repetitions are back-to-back.

Fig. 10 shows an example scheme of TDM-based PUSCH repetition in FR1, according to some embodiments of the present disclosure. As shown in fig. 10, two time periods are allocated for transmission of PUSCH repetition to TRP # a and PUSCH repetition to TRP # B, respectively. The DCI includes two TPMI (TPMI #0 and TPMI #1) and two SRI (SRI #0 and SRI #1) for scheduling transmission of two PUSCH repetitions, so the TPMI and PUSCH repetitions are in one-to-one mapping relationship, and the SRI and PUSCH repetitions are in one-to-one mapping relationship.

Fig. 11 illustrates another example scheme of TDM-based PUSCH repetition in FR1, according to some embodiments of the present disclosure. As shown in fig. 11, four time periods are allocated for transmission of two PUSCH repetitions to TRP # a and two PUSCH repetitions to TRP # B, respectively. The DCI includes two TPMI (TPMI #0 and TPMI #1) and two SRI (SRI #0 and SRI #1) for scheduling transmission of four PUSCH repetitions, so the TPMI and PUSCH repetitions are in a one-to-many mapping relationship, and the SRI and PUSCH repetitions are in a one-to-many mapping relationship.

Fig. 12 shows an example scheme of TDM-based PUSCH repetition in FR2, according to some embodiments of the present disclosure. As shown in fig. 12, similar to fig. 10, two time periods are allocated for transmission of PUSCH repetition to TRP # a and PUSCH repetition to TRP # B, respectively, and DCI contains two TPMI and two SRI for scheduling transmission of two PUSCH repetitions. TPMI is a one-to-one mapping relationship with PUSCH repetition, and SRI is a one-to-one mapping relationship with PUSCH repetition. Fig. 12 differs from fig. 10 in that: in FR2, different spatial relationships may be applied to PUSCH repeated transmissions destined for different TRPs. For example, the PUSCH repetition destined for TRP # a may be transmitted via spatial relationship #0 and the PUSCH repetition destined for TRP # B may be transmitted via spatial relationship # 1.

Fig. 13 illustrates another example scheme of TDM-based PUSCH repetition in FR2, according to some embodiments of the present disclosure. As shown in fig. 13, similar to fig. 11, four time periods are allocated for transmission of two PUSCH repetitions to TRP # a and two PUSCH repetitions to TRP # B, respectively, and DCI contains two TPMI and two SRI for scheduling transmission of the four PUSCH repetitions. TPMI is a one-to-many mapping relationship with PUSCH repetition, and SRI is a one-to-many mapping relationship with PUSCH repetition. Fig. 13 differs from fig. 11 in that: in FR2, different spatial relationships may be applied to PUSCH repeated transmissions destined for different TRPs. For example, the PUSCH repetition destined for TRP # a may be transmitted via spatial relationship #0 and the PUSCH repetition destined for TRP # B may be transmitted via spatial relationship # 1.

For TDM-based PUSCH repetition, the Frequency Domain Resource Allocation (FDRA) of each TRP or PUSCH repetition may be the same or different. Thus, the phase tracking reference signal (PT-RS) pattern used to transmit different PUSCH repetitions may be the same or different depending on the frequency bandwidth allocated for the PUSCH repetitions. The PT-RS pattern may be different if the allocated frequency bandwidth is different for different PUSCH repetitions.

Fig. 14 illustrates an example scheme of TDM-based PUSCH repetition with DFT-s-OFDM waveforms and different sizes of frequency resource allocation in two TRP scenarios, according to some embodiments of the present disclosure. As shown in fig. 14, two periods (period T1 and period T2) are allocated for transmitting PUSCH repetition to TRP # a and PUSCH repetition to TRP # B, respectively. In addition, the PUSCH repetition to TRP # a and the PUSCH repetition to TRP # B are allocated with different frequency bandwidths.

According to some embodiments of the present application, in FR2, for codebook-based PUSCH repetition, PUSCH repetition may be transmitted in SDM-based manner. PUSCH repetition may occupy the same resources in the time and frequency domains. The PUSCH repetition may be transmitted via a different spatial relationship or a different UE antenna panel. To implement SDM-based PUSCH repetition, a UE should support simultaneous transmissions originating from multiple spatial relationships or multiple antenna panels.

Fig. 15 shows an example scheme of SDM-based PUSCH repetition in FR2, according to some embodiments of the present disclosure. As shown in fig. 15, different spatial relationships may be applied to PUSCH repeated transmissions to different TRPs. For example, PUSCH repetition #0 destined for TRP # a may be transmitted via spatial relationship #0 and PUSCH repetition #1 destined for TRP # B may be transmitted via spatial relationship # 1. PUSCH repetition #0 and PUSCH repetition #1 may occupy the same resources in the time and frequency domains.

In the foregoing embodiments, various schemes for transmitting PUSCH repetition for a plurality of TRPs have been described in detail. As described above, PUSCH repetitions may be transmitted between a UE and multiple TRPs according to codebook-based PUSCH transmission. For purposes of illustration, operations associated with PUSCH repeated codebook-based transmission to be performed at the UE and the TRP will be described below with reference to fig. 16 and 17, respectively.

Fig. 16 illustrates an example process associated with PUSCH repeated codebook-based transmission at a UE in accordance with some embodiments of the present disclosure. The example process 1600 may include operations 1610 through 1630.

In operation 1610, the UE may receive DCI from the TRP, the DCI being used to schedule a codebook-based PUSCH transmission to a plurality of TRPs.

In operation 1620, the UE may encode and multiplex a plurality of codebook-based PUSCH repetitions based on the DCI and the PUSCH configuration information from higher layers. According to some embodiments of the present application, the PUSCH repetition may be encoded and multiplexed into a CP-OFDM waveform or a DFT-s-OFDM waveform, and the PUSCH configuration information may include an IE for indicating a type of PUSCH repetition and a number of PUSCH repetitions. The types of PUSCH repetitions may include FDM based PUSCH repetitions, TDM based PUSCH repetitions, or SDM based PUSCH repetitions.

According to some embodiments of the present application, the DCI may include: a precoding andmbuberoflayers field containing one or more TPMI; and an SRI field containing one or more SRIs, and the number of the one or more TPMIs and the number of the one or more SRIs are predefined or configured by the higher layer.

In particular, the field length of the SRI field may be determined by

To determine, wherein N_SRSIs the number of SRS resources configured in an SRS resource set, and N_SRI,RepIs the number of one or more SRIs to be used for PUSCH repetition. When N is present_SRI,RepEqual to 1, a single SRI contained in the SRI field may be used for all PUSCH repetitions; when N is present_SRI,RepWhen the number of the repeated PUSCH is equal to the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH can form a one-to-one mapping relation; and when N is_SRI,RepWhen the number of the repetitions of the PUSCH is smaller than the number of the repetitions of the PUSCH, the SRI contained in the SRI field and the repetitions of the PUSCH may be mapped one to many. The one-to-many mapping relationship may include: for PUSCH repetition i, SRI_jIs applied to the PUSCH repeats i, where i ∈ (0,1, … numberof PUSCHRepetitiongs-1), numberof PUSCHRepetitiongs is the number of PUSCH repeats, and j ∈ (0,1, … N)_SRI,Rep-1), and j ═ imodN_SRI,RepOr

In addition, the field length of the precoding AndNumberOfLayers field can be changed from N to L_TPMI×N_TPMI,RepTo determine wherein L_TPMIIs the field length of the precoding AndNumberOfLayers field when no PUSCH repetition is configured, and N_TPMI,RepIs the number of one or more TPMIs to be used for PUSCH repetition. When N is present_TPMI,RepEqual to 1, a single TPMI contained in the precoding andmbumberbeolayers field can be used for all PUSCH repetitions; when N is present_TPMI,RepWhen the number of the PUSCH repetitions is equal, the TPMI contained in the precoding AndNumberOfLayers field and the PUSCH repetitions can be in one-to-one mapping relation; and when N is_TPMI,RepThe TPMI contained in the precoding andmbuberoflayers field may be mapped one-to-many with PUSCH repetitions less than the number of PUSCH repetitions. The one-to-many mapping relationship may include: for PUSCH repetition i, TPMI_kIs applied to PUSCH repetition i, where i ∈ (0,1, … number of PUSCH repetition-1), number of PUSCH repetition is the number of PUSCH repetitions, k ∈ (0,1, … N)_TPMI,Rep-1), and k ═ i mod N_TPMI,RepOr

In operation 1630, the UE may repeatedly send the encoded and multiplexed PUSCH to a plurality of TRPs.

According to some embodiments of the present application, the UE may determine and report to the TRP or higher layers the UE's capability as to which type of PUSCH repetition is supported. The UE may be configured with one set of sounding reference signal, SRS, resources whose usage is set to 'codebook', the set of SRS resources including one or more SRS resources, and may transmit the one or more SRS to the TRP via the one or more SRS resources. Alternatively, the UE may be configured with a plurality of sounding reference signal, SRS, resource sets whose usage is set to 'codebook', each of the plurality of SRS resource sets may include one or more SRS resources and be associated with a respective TRP of the plurality of TRPs, and the UE may transmit the one or more SRSs to the respective TRP via the one or more SRS resources of each SRS resource set. Thus, the DCI may include an SRI field including one or more SRIs, each SRI indicating SRS resources from a respective SRS resource set of the plurality of SRS resource sets.

According to some embodiments of the present application, the PUSCH repetition may be an FDM-based PUSCH repetition, and the UE may map the PUSCH repetition to a respective RRG, each RRG comprising a plurality of consecutive PRBs. As an example, the UE may generate and multiplex a PUSCH repetition with a DFT-s-OFDM waveform by: applying DFT spreading to PUSCH data in the time domain; copying the PUSCH data after DFT spreading to generate a PUSCH repetition; repeatedly mapping the PUSCH to a corresponding RRG; and repeatedly applying the OFDM modulation to the PUSCH by IDFT. The RRGs for the respective PUSCH repetitions may have the same size of frequency resource allocation. The UE may apply the same PT-RS pattern to PUSCH repeated transmissions. The index of the RRG may be UE-specific and based on the frequency bandwidth allocated to the UE, or cell-specific and based on a reference number of the RRG relative to the common resource block.

According to some embodiments of the present application, when the UE is operating in FR2 and supports simultaneous transmissions from multiple spatial relationships or multiple antenna panels, the UE may determine the multiple spatial relationships or multiple antenna panels based on the DCI and repeatedly send the PUSCH on a respective RRG to multiple TRPs via the respective spatial relationships or antenna panels.

According to some embodiments of the present application, the PUSCH repetition may be a TDM-based PUSCH repetition, and the UE may map the PUSCH repetition to a corresponding time period within the same slot or across multiple slots. The gap period between two adjacent PUSCH repetitions may be zero. The UE may repeatedly allocate the same frequency domain resource or different frequency domain resources for the PUSCH based on the DCI. The UE may apply the same PT-RS pattern to PUSCH repeated transmission when the same frequency domain resources are allocated to the PUSCH repetition, and may apply different PT-RS patterns to PUSCH repeated transmission when different frequency domain resources are allocated to the PUSCH repetition. When the UE is operating in FR2 and supports simultaneous transmissions from multiple spatial relationships or multiple antenna panels, the UE may determine the multiple spatial relationships or multiple antenna panels based on the DCI and repeatedly transmit PUSCH to multiple TRPs via the respective spatial relationships or antenna panels over respective time periods.

According to some embodiments of the present application, when the UE is operating in FR2 and supports simultaneous transmissions from multiple spatial relationships or multiple antenna panels, the PUSCH repetition may be an SDM-based PUSCH repetition, and the UE may determine the multiple spatial relationships or multiple antenna panels based on the DCI and send the PUSCH repetition to the multiple TRPs via the respective spatial relationships or antenna panels. The UE may repeatedly allocate the same frequency domain resource and the same time domain resource for the PUSCH based on the DCI.

Fig. 17 illustrates an example process associated with PUSCH repeated codebook-based transmission at a TRP, in accordance with some embodiments of the present disclosure. Exemplary process 1700 may include operations 1710 to 1730.

In operation 1710, the TRP may receive one or more SRS from the UE via one or more SRS resources of the one or more SRS resource sets whose usage is set to 'codebook'.

At operation 1720, the TRP may generate DCI based on the measurement of the one or more SRS resources and configuration information associated with PUSCH repetition from higher layers for scheduling codebook-based PUSCH transmissions to the plurality of TRPs.

According to some embodiments of the present application, the DCI may include: a precoding andmbuberoflayers field containing one or more TPMI; and an SRI field containing one or more SRIs, and the number of the one or more TPMIs and the number of the one or more SRIs are predefined or configured by the higher layer.

In particular, the field length of the SRI field may be determined by

To determine, wherein N_SRSIs the number of SRS resources configured in an SRS resource set, and N_SRI,RepIs the number of one or more SRIs to be used for PUSCH repetition. When N is present_SRI,RepEqual to 1, a single SRI contained in the SRI field may be used for all PUSCH repetitions; when N is present_SRI,RepWhen the number of the repeated PUSCH is equal to the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH can form a one-to-one mapping relation; and when N is_SRI,RepWhen the number of the repetitions of the PUSCH is smaller than the number of the repetitions of the PUSCH, the SRI contained in the SRI field and the repetitions of the PUSCH may be mapped one to many. The one-to-many mapping relationship may include: for PUSCH repetition i, SRI_jIs applied to PUSCH repetition i, where i ∈ (0,1, … numberfPUSCHRepetitions-1), numberfPUSCHRepetitions is the number of PUSCH repetitions, j ∈ (0,1, … N)_SRI,Rep-1), and j ═ i mod N_SRI,RepOr

In addition, the field length of the precoding AndNumberOfLayers field can be changed from N to L_TPMI×N_TPMI,RepTo determine wherein L_TPMIIs the field length of the precoding AndNumberOfLayers field when no PUSCH repetition is configured, and N_TPMI,RepIs the number of one or more TPMIs to be used for PUSCH repetition. When N is present_TPMI,RepEqual to 1, a single TPMI contained in the precoding andmbumberbeolayers field can be used for all PUSCH repetitions; when N is present_TPMI,RepWhen the number of the PUSCH repetitions is equal, the TPMI contained in the precoding AndNumberOfLayers field and the PUSCH repetitions can be in one-to-one mapping relation; and when N is_TPMI,RepThe TPMI contained in the precoding andmbuberoflayers field may be mapped one-to-many with PUSCH repetitions less than the number of PUSCH repetitions. The one-to-many mapping relationship may include: for PUSCH repetition i, TPMI_kIs applied to PUSCH repetition i, where i ∈ (0,1, … number of PUSCH repetition-1), number of PUSCH repetition is the number of PUSCH repetitions, i ∈ (0,1, … N)_TPMI,Rep-1), and k ═ i mod N_TPMI，RepOr

In operation 1730, the TRP may transmit the DCI to the UE. Accordingly, the UE may generate and transmit a PUSCH repetition to a plurality of TRPs based on the DCI and PUSCH configuration information from a higher layer.

Fig. 18 and 19 illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments.

Fig. 18 shows a diagram of a network 1800, according to various embodiments of the present disclosure. The network 1800 may operate in a manner consistent with the 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this respect, and the described embodiments may be applied to other networks, such as future 3GPP systems and the like, that benefit from the principles described herein.

The network 1800 may include a UE 1802, which may include any mobile or non-mobile computing device designed to communicate with the RAN 1804 via an over-the-air connection. The UE 1802 may be, but is not limited to, a smartphone, a tablet, a wearable computer device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, an instrument cluster, a heads-up display device, an in-vehicle diagnostic device, a dashboard mobile device, a mobile data terminal, an electronic engine management system, an electronic/engine control unit, an electronic/engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine-type communication device, an M2M or D2D device, an IoT device, and/or the like.

In some embodiments, the network 1800 may include multiple UEs directly coupled to each other through edge link interfaces. The UE may be an M2M/D2D device that communicates using a physical side link channel (e.g., without limitation, a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), a physical side link control channel (PSCCH), a physical side link fundamental channel (PSFCH), etc.).

In some embodiments, the UE 1802 may also communicate with the AP 1806 over an over-the-air connectionThe letter is sent. The AP 1806 may manage WLAN connections that may be used to offload some/all network traffic from the RAN 1804. The connection between the UE 1802 and the AP 1806 may be in accordance with any IEEE 802.13 protocol, where the AP 1806 may be wireless fidelity

A router. In some embodiments, the UE 1802, RAN 1804, and AP 1806 may utilize cellular WLAN aggregation (e.g., LTE-WLAN aggregation (LWA)/lightweight ip (lwip)). Cellular WLAN aggregation may involve a UE 1802 configured by a RAN 1804 utilizing both cellular radio resources and WLAN resources.

The RAN 1804 may include one or more Access Nodes (ANs), such as AN 1808. The AN 1808 may terminate the air interface protocol of the UE 1802 by providing access stratum protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Medium Access Control (MAC), and L1 protocols. In this manner, the AN 1808 may enable data/voice connectivity between the CN 1820 and the UE 1802. In some embodiments, AN 1808 may be implemented in a separate device or as one or more software entities running on a server computer, as part of a virtual network, for example, which may be referred to as a CRAN or virtual baseband unit pool. AN 1808 may be referred to as a Base Station (BS), a gNB, a RAN node, AN evolved node b (eNB), a next generation eNB (ng-eNB), a node b (nodeb), a roadside unit (RSU), a TRxP, a TRP, etc. AN 1808 may be a macrocell base station or a low-power base station for providing microcells, picocells, or other similar cells having smaller coverage areas, smaller user capacities, or higher bandwidths than macrocells.

In embodiments where the RAN 1804 comprises multiple ANs, they may be coupled to each other over AN X2 interface (in the case where the RAN 1804 is AN LTE RAN) or AN Xn interface (in the case where the RAN 1804 is a 5G RAN). The X2/Xn interface, which may be separated into a control plane interface/user plane interface in some embodiments, may allow the AN to communicate information related to handover, data/context transfer, mobility, load management, interference coordination, etc.

The ANs of the RANs 1804 may each manage one or more cells, groups of cells, component carriers, etc., to provide the UE 1802 with AN air interface for network access. The UE 1802 may be simultaneously connected with multiple cells provided by the same or different ANs of the RAN 1804. For example, UE 1802 and RAN 1804 may use carrier aggregation to allow UE 1802 to connect with multiple component carriers, each corresponding to a primary cell (Pcell) or a secondary cell (Scell). In a dual connectivity scenario, the first AN may be a primary node providing a Master Cell Group (MCG) and the second AN may be a secondary node providing a Secondary Cell Group (SCG). The first/second AN can be any combination of eNB, gNB, ng-eNB, etc.

RAN 1804 may provide an air interface over a licensed or unlicensed spectrum. To operate in unlicensed spectrum, a node may use a Licensed Assisted Access (LAA), enhanced LAA (elaa), and/or further enhanced LAA (felaa) mechanism based on Carrier Aggregation (CA) technology with PCell/Scell. Prior to accessing the unlicensed spectrum, the node may perform a media/carrier sensing operation based on, for example, a Listen Before Talk (LBT) protocol.

In a vehicle-to-everything (V2X) scenario, the UE 1802 or AN 1808 may be or act as a roadside unit (RSU), which may refer to any transport infrastructure entity for V2X communications. The RSU may be implemented in or by AN appropriate AN or stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU"; RSUs implemented in the next generation nodeb (gNB) or by the gNB may be referred to as "gNB-type RSUs"; and so on. In one example, the RSU is a computing device coupled with radio frequency circuitry located at the curb side that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications/software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, e.g., collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU may provide other cellular/WLAN communication services. The components of the RSU may be enclosed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., ethernet) to a traffic signal controller or backhaul network.

In some embodiments, RAN 1804 may be an LTE RAN 1810 including an evolved node b (eNB), e.g., eNB 1812. The LTE RAN 1810 may provide an LTE air interface with the following characteristics: SCS at 15 kHz; a CP-OFDM waveform for DL and an SC-FDMA waveform for UL; turbo codes for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; relying on a PDSCH/PDCCH demodulation reference signal (DMRS) for PDSCH/PDCCH demodulation; and relying on CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operate over the sub-6 GHz band.

In some embodiments, RAN 1804 may be a Next Generation (NG) -RAN 1814 with a gNB (e.g., gNB 1816) or gn-eNB (e.g., NG-eNB 1818). The gNB 1816 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 1816 may be connected to the 5G core through an NG interface, which may include an N2 interface or an N3 interface. The Ng-eNB 1818 may also connect with the 5G core over the Ng interface, but may connect with the UE over the LTE air interface. The gNB 1816 and ng-eNB 1818 may be connected to each other through an Xn interface.

In some embodiments, the NG interface may be divided into two parts, a NG user plane (NG-U) interface, which carries traffic data between nodes of the NG-RAN 1814 and the UPF 1848, and a NG control plane (NG-C) interface, which is a signaling interface (e.g., N2 interface) between the NG-RAN 1814 and nodes of the access and mobility management function (AMF) 1844.

The NG-RAN 1814 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM for UL, and DFT-s-OFDM; polarity, repetition, simplex, and Reed-Muller (Reed-Muller) codes for control, and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; performing phase tracking of the PDSCH using the PTRS; and time tracking using the tracking reference signal. The 5G-NR air interface may operate over the FR1 frequency band, which includes the sub-6 GHz band, or the FR2 frequency band, which includes the 24.25GHz to 52.6GHz band. The 5G-NR air interface may include SSBs, which are regions of a downlink resource grid including PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may use BWP for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, the UE 1802 may be configured with multiple BWPs, where each BWP configuration has a different SCS. When the BWP is indicated to the UE 1802 to change, the SCS of the transmission also changes. Another use case for BWP is related to power saving. In particular, the UE 1802 may be configured with multiple BWPs having different numbers of frequency resources (e.g., PRBs) to support data transmission in different traffic load scenarios. BWPs containing a smaller number of PRBs may be used for data transmission with smaller traffic load while allowing power savings at the UE 1802 and, in some cases, the gNB 1816. BWPs containing a large number of PRBs may be used in scenarios with higher traffic loads.

The RAN 1804 is communicatively coupled to a CN 1820, which includes network elements, to provide various functions to support data and telecommunications services to customers/subscribers (e.g., users of the UE 1802). The components of CN 1820 may be implemented in one physical node or in different physical nodes. In some embodiments, NFV may be used to virtualize any or all of the functions provided by the network elements of CN 1820 onto physical computing/storage resources in servers, switches, and the like. Logical instances of CN 1820 may be referred to as network slices, and logical instantiations of portions of CN 1820 may be referred to as network subslices.

In some embodiments, the CN 1820 may be an LTE CN 1822, which may also be referred to as an Evolved Packet Core (EPC). The LTE CN 1822 may include a Mobility Management Entity (MME)1824, a Serving Gateway (SGW)1826, a Serving GPRS Support Node (SGSN)1828, a Home Subscriber Server (HSS)1830, a Proxy Gateway (PGW)1832, and a policy control and charging rules function (PCRF)1834, which are coupled to each other by an interface (or "reference point") as shown. The functions of the elements of LTE CN 1822 may be briefly introduced as follows.

The MME 1824 may implement mobility management functions to track the current location of the UE 1802 for ease of patrol, bearer activation/deactivation, handover, gateway selection, authentication, and so forth.

The SGW 1826 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 1822. SGW 1826 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful interception, billing, and some policy enforcement.

The SGSN 1828 may track the location of the UE 1802 and perform security functions and access control. In addition, the SGSN 1828 may perform EPC inter-node signaling for mobility between different RAT networks; PDN and S-GW selection specified by MME 1824; MME selection for handover, etc. The S3 reference point between the MME 1824 and the SGSN 1828 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active state.

HSS 1830 may include a database for network users that includes subscription-related information that supports network entities handling communication sessions. The HSS 1830 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. The S6a reference point between the HSS 1830 and the MME 1824 may enable the transmission of subscription and authentication data to authenticate/authorize user access to the LTE CN 1820.

The PGW 1832 may terminate the SGi interface towards a Data Network (DN)1836, which may include an application/content server 1838. The PGW 1832 may route data packets between the LTE CN 1822 and the data network 1836. The PGW 1832 may be coupled with the SGW 1826 through the S5 reference point to facilitate user plane tunneling and tunnel management. PGW 1832 may also include a node (e.g., PCEF) for policy enforcement and charging data collection. Additionally, the SGi reference point between the PGW 1832 and the data network 1836 may be, for example, an operator external public, private PDN, or an operator internal packet data network for providing IMS services. PGW 1832 may be coupled with PCRF 1834 via the Gx reference point.

PCRF 1834 is the policy and charging control element of LTE CN 1822. PCRF 1834 may be communicatively coupled to application/content server 1838 to determine the appropriate QoS and charging parameters for a service flow. PCRF 1832 may provide the associated rules to the PCEF (via the Gx reference point) with the appropriate TFT and QCI.

In some embodiments, CN 1820 may be a 5G core network (5GC) 1840. The 5GC 1840 may include an authentication server function (AUSF)1842, an access and mobility management function (AMF)1844, a Session Management Function (SMF)1846, a User Plane Function (UPF)1848, a Network Slice Selection Function (NSSF)1850, a network open function (NEF)1852, an NF storage function (NRF)1854, a Policy Control Function (PCF)1856, a Unified Data Management (UDM)1858, and an Application Function (AF)1860, which are coupled to each other by an interface (or "reference point") as shown. The functions of the elements of the 5GC 1840 may be briefly described as follows.

The AUSF 1842 may store data for authentication of the UE 1802 and handle authentication related functions. The AUSF 1842 may facilitate a common authentication framework for various access types. The AUSF 1842 may exhibit a Nausf service based interface in addition to communicating with other elements of the 5GC 1840 through reference points as shown.

The AMF 1844 may allow other functions of the 5GC 1840 to communicate with the UE 1802 and the RAN 1804 and subscribe to notifications about mobility events of the UE 1802. The AMF 1844 may be responsible for registration management (e.g., registering the UE 1802), connection management, reachability management, mobility management, lawful interception of AMF related events, and access authentication and authorization. The AMF 1844 may provide transport of Session Management (SM) messages between the UE 1802 and the SMF 1846 and act as a transparent proxy for routing SM messages. The AMF 1844 may also provide for the transmission of SMS messages between the UE 1802 and the SMSF. The AMF 1844 may interact with the AUSF 1842 and the UE 1802 to perform various security anchoring and context management functions. Further, the AMF 1844 may be a termination point of the RAN CP interface, which may include or be an N2 reference point between the RAN 1804 and the AMF 1844; the AMF 1844 may act as a termination point for NAS (N1) signaling and perform NAS ciphering and integrity protection. The AMF 1844 may also support NAS signaling with the UE 1802 over the N3 IWF interface.

The SMF 1846 may be responsible for SM (e.g., session establishment, tunnel management between UPF 1848 and AN 1808); UE IP address assignment and management (including optional authorization); selection and control of the UP function; configuring flow control at the UPF 1848 to route the flow to the appropriate destination; termination of the interface to the policy control function; controlling a portion of policy enforcement, charging, and QoS; lawful interception (for SM events and interface to the LI system); terminate the SM portion of the NAS message; a downlink data notification; initiating AN specific SM message (sent to AN 1808 over N2 through AMF 1844); and determining an SSC pattern for the session. SM may refer to management of PDU sessions, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables exchange of PDUs between the UE 1802 and the data network 1836.

The UPF 1848 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with the data network 1836, and a branch point to support multi-homed PDU sessions. The UPF 1848 may also perform packet routing and forwarding, perform packet inspection, perform the user plane part of policy rules, lawful intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 1848 may include an uplink classifier to support routing of traffic flows to a data network.

The NSSF 1850 may select a set of network slice instances that serve the UE 1802. NSSF 1850 may also determine allowed Network Slice Selection Assistance Information (NSSAI) and mapping to a single NSSAI (S-NSSAI) of the subscription, if desired. The NSSF 1850 may also determine a set of AMFs to be used to serve the UE 1802, or determine a list of candidate AMFs, based on a suitable configuration and possibly by querying the NRF 1854. The selection of a set of network slice instances for the UE 1802 may be triggered by the AMF 1844 (with which the UE 1802 registers by interacting with the NSSF 1850), which may result in a change in the AMF. The NSSF 1850 may interact with the AMF 1844 via the N22 reference point; and may communicate with another NSSF in the visited network via an N31 reference point (not shown). Further, NSSF 1850 may expose an interface based on the NSSF service.

NEF 1852 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal disclosure/re-disclosure, AF (e.g., AF 1860), edge computing or fog computing systems, and the like. In these embodiments, NEF 1852 may authenticate, authorize, or throttle AF. NEF 1852 may also translate information exchanged with AF 1860 and information exchanged with internal network functions. For example, the NEF 1852 may convert between the AF service identifier and the internal 5GC information. NEF 1852 may also receive information from other NFs based on their public capabilities. This information may be stored as structured data at NEF 1852 or at data store NF using a standardized interface. NEF 1852 may then re-disclose the stored information to other NFs and AFs, or for other purposes such as analysis. In addition, NEF 1852 may expose an interface based on the Nnef service.

The NRF 1854 may support a service discovery function, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. The NRF 1854 also maintains information of available NF instances and their supported services. As used herein, the terms "instantiate," "instance," and the like may refer to creating an instance, "instance" may refer to a specific occurrence of an object, which may occur, for example, during execution of program code. Further, the NRF 1854 may expose an interface based on the nrrf service.

PCF 1856 may provide policy rules to control plane functions to enforce them and may also support a unified policy framework to manage network behavior. PCF 1856 may also implement a front end to access subscription information related to policy decisions in the UDR of UDM 1858. In addition to communicating with functions through reference points as shown, PCF 1856 also exhibits an Npcf service-based interface.

The UDM 1858 may process subscription-related information to support network entities handling communication sessions and may store subscription data for the UE 1802. For example, subscription data may be communicated via the N8 reference point between UDM 1858 and AMF 1844. The UDM 1858 may comprise two parts: front end and UDR are applied. The UDR may store policy data and subscription data for UDMs 1858 and PCFs 1856, and/or structured data and application data for disclosure (including PFD for application detection, application request information for multiple UEs 1802) for NEFs 1852. UDR 221 may expose an Nudr service-based interface to allow UDM 1858, PCF 1856, and NEF 1852 to access specific collections of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM may include a UDM-FE that is responsible for handling credentials, location management, subscription management, and the like. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, UDM 1858 may also expose a numm service based interface.

AF 1860 may provide application impact on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

In some embodiments, the 5GC 1840 may enable edge computing by selecting an operator/third party service geographically close to the point where the UE 1802 attaches to the network. This may reduce latency and load on the network. To provide an edge computing implementation, the 5GC 1840 may select a UPF 1848 close to the UE 1802 and perform traffic steering from the UPF 1848 to the data network 1836 through an N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 1860. In this way, the AF 1860 may influence UPF (re) selection and traffic routing. Based on operator deployment, the network operator may permit AF 1860 to interact directly with the relevant NFs when AF 1860 is considered a trusted entity. In addition, the AF 1860 may expose a Naf service-based interface.

The data network 1836 may represent various network operator services, internet access, or third party services that may be provided by one or more servers, including, for example, an application/content server 1838.

Fig. 19 schematically illustrates a wireless network 1900 in accordance with various embodiments. The wireless network 1900 may include a UE 1902 in wireless communication with AN 1904. The UE 1902 and the AN 1904 may be similar to, and substantially interchangeable with, the co-located components described elsewhere herein.

The UE 1902 may be communicatively coupled with AN 1904 via a connection 1906. The connection 1906 is shown as an air interface to enable communicative coupling and may be consistent with a cellular communication protocol operating at millimeter wave (mmWave) or sub-6 GHz frequencies, such as the LTE protocol or the 5G NR protocol.

The UE 1902 may include a host platform 1908 coupled with a modem platform 1910. Host platform 1908 may include application processing circuitry 1912, which may be coupled with protocol processing circuitry 1914 of modem platform 1910. The application processing circuitry 1912 may run various applications of source/receiver application data for the UE 1902. The application processing circuitry 1912 may also implement one or more layers of operations to transmit/receive application data to/from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

The protocol processing circuitry 1914 may implement one or more layers of operations to facilitate the transmission or reception of data over the connection 1906. Layer operations implemented by the protocol processing circuit 1914 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

The modem platform 1910 may further include digital baseband circuitry 1916, the digital baseband circuitry 1916 may implement one or more layer operations that are "lower" than the layer operations performed by the protocol processing circuitry 1914 in the network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/demapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, wherein these functions may include one or more of: space-time, space-frequency, or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

Modem platform 1910 may further include transmit circuitry 1918, receive circuitry 1920, RF circuitry 1922, and RF front-end (RFFE) circuitry 1924, which may include or be connected to one or more antenna panels 1926. Briefly, the transmit circuit 1918 may include a digital-to-analog converter, a mixer, Intermediate Frequency (IF) components, and so forth; the receiving circuitry 1920 may include analog-to-digital converters, mixers, IF components, etc.; the RF circuitry 1922 may include low noise amplifiers, power tracking components, and the like; the RFFE circuitry 1924 may include filters (e.g., surface/bulk acoustic wave filters), switches, antenna tuners, beam forming components (e.g., phased array antenna components), and so forth. The selection and arrangement of the components of the transmit circuitry 1918, receive circuitry 1920, RF circuitry 1922, RFFE circuitry 1924, and antenna panel 1926 (collectively, "transmit/receive components") may be specific to details of a particular implementation, such as whether the communication is TDM or FDM, at mmWave or sub-6 GHz frequencies, and so forth. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, and may be arranged in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 1914 may include one or more instances of control circuitry (not shown) to provide control functionality for the transmit/receive components.

UE reception may be established by and via antenna panel 1926, RFFE circuitry 1924, RF circuitry 1922, receive circuitry 1920, digital baseband circuitry 1916, and protocol processing circuitry 1914. In some embodiments, the antenna panel 1926 may receive transmissions from AN 1904 by receiving beamformed signals received by multiple antennas/antenna elements of one or more antenna panels 1926.

UE transmissions may be established via and through protocol processing circuitry 1914, digital baseband circuitry 1916, transmit circuitry 1918, RF circuitry 1922, RFFE circuitry 1924, and antenna panel 1926. In some embodiments, the transmit components of UE 1904 may apply spatial filters to the data to be transmitted to form transmit beams transmitted by the antenna elements of antenna panel 1926.

Similar to UE 1902, AN 1904 may include a host platform 1928 coupled with a modem platform 1930. Host platform 1928 may include application processing circuitry 1932 coupled with protocol processing circuitry 1934 of modem platform 1930. The modem platform may also include digital baseband circuitry 1936, transmit circuitry 1938, receive circuitry 1940, RF circuitry 1942, RFFE circuitry 1944, and antenna panel 1946. The components of the AN 1904 can be similar to, and substantially interchangeable with, the synonymous components of the UE 1902. In addition to performing data transmission/reception as described above, the components of AN 1908 may also perform various logical functions including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Fig. 20 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some example embodiments. In particular, FIG. 20 shows a diagrammatic representation of hardware resources 2000, which includes one or more processors (or processor cores) 2010, one or more memory/storage devices 2020, and one or more communication resources 2030, each of which may be communicatively coupled via a bus 2040. Hardware resources 2000 may be part of a UE, AN, or LMF. For embodiments utilizing node virtualization (e.g., NFV), hypervisor 2002 may be executed to provide an execution environment for one or more network slices/subslices to utilize hardware resources 2000.

Processor 2010 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP) such as a baseband processor, an Application Specific Integrated Circuit (ASIC), a Radio Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 2012 and processor 2014.

The memory/storage 2020 may include main memory, magnetic disk storage, or any suitable combination thereof. The memory/storage 2020 may include, but is not limited to, any type of volatile or non-volatile memory, such as Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid state storage, and the like.

The communication resources 2030 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 2004 or one or more databases 2006 via a network 2008. For example, communication resources 2030 can include a wired communication component (e.g., for coupling via a Universal Serial Bus (USB)), a cellular communication component, an NFC component, a bluetooth component

Components (e.g., bluetooth low energy), Wi-Fi components, and other communication components.

Instructions 2050 may include software, a program, an application, an applet, an app, or other executable code to at least cause any processor 2010 to perform any one or more of the methodologies discussed herein. The instructions 2050 may reside, completely or partially, within at least one of: the processor 2010 (e.g., within a cache memory of the processor), the memory/storage 2020, or any suitable combination thereof. Further, any portion of instructions 2050 may be communicated to hardware resource 2000 from any combination of peripherals 2004 or databases 2006. Thus, the processor 2010, memory/storage 2020, peripherals 2004, and memory of database 2006 are examples of computer-readable and machine-readable media.

The following paragraphs describe examples of various embodiments.

Example 1 includes an apparatus for a user equipment, UE, comprising: a Radio Frequency (RF) interface circuit configured to receive Downlink Control Information (DCI) from a Transmit Reception Point (TRP), the DCI being for scheduling a codebook-based Physical Uplink Shared Channel (PUSCH) transmission to a plurality of TRPs; and processing circuitry coupled with the RF interface circuitry and configured to: repeatedly encoding and multiplexing a plurality of codebook-based PUSCHs based on the DCI and PUSCH configuration information from higher layers; and repeatedly providing the encoded and multiplexed PUSCH to the RF interface circuitry for transmission to the plurality of TRPs.

Example 2 includes the apparatus of example 1, wherein the processing circuitry is configured to repeatedly code and multiplex the PUSCH into a cyclic prefix-orthogonal frequency division multiplexing, CP-OFDM, waveform or a discrete fourier transform-spread-orthogonal frequency division multiplexing, DFT-s-OFDM, waveform.

Example 3 includes the apparatus of example 1, wherein the PUSCH configuration information includes an information element IE to indicate the type of PUSCH repetition and the number of PUSCH repetitions.

Example 4 includes the apparatus of example 3, wherein the type of PUSCH repetition includes a PUSCH repetition based on frequency division multiplexing, FDM, time division multiplexing, TDM, or a PUSCH repetition based on spatial division multiplexing, SDM.

Example 5 includes the apparatus of example 1, wherein the processing circuitry is further configured to: determining a capability of the UE with respect to which type of PUSCH repetition is supported; encoding an indication of the capability of the UE; and providing the encoded indication of the capability of the UE to the RF interface circuitry for reporting to the TRP or the higher layers.

Example 6 includes the apparatus of example 1, wherein the DCI comprises: a precoding andmbumberoflayers field containing one or more transmission precoding matrix indices TPMI; and a sounding reference signal, SRS, resource indicator, SRI, field containing one or more SRIs, and a number of the one or more TPMIs and a number of the one or more SRIs are predefined or configured by the higher layer.

Example 7 includes the apparatus of example 6, wherein a field length of the SRI field is defined by

To determine, wherein N_SRSIs the number of SRS resources configured in an SRS resource set, and N_SRI,RepIs a number of the one or more SRIs to be used for the PUSCH repetition.

Example 8 includes the method of example 7Device, wherein when N_SRI,RepEqual to 1, a single SRI contained in the SRI field is used for all the PUSCH repetitions; when N is present_SRI,RepWhen the number of the repeated PUSCH is equal to the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH are in a one-to-one mapping relation; and when N is_SRI,RepAnd when the number of the repeated PUSCH is less than the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH form a one-to-many mapping relation.

Example 9 includes the apparatus of example 8, wherein the one-to-many mapping comprises: for PUSCH repetition i, SRI_jIs applied to the PUSCH repetition i, wherein i ∈ (0,1, … number of PUSCH repetition-1), number of PUSCH repetition is the number of PUSCH repetitions, j ∈ (0,1, … N)_SRI，Rep-1), and j ═ i mod N_SRI，RepOr

Example 10 includes the apparatus of example 6, wherein a field length of the precoding andmbumberoflayers field is defined by N ═ L_TPMI×N_TPMI，RepTo determine wherein L_TPMIIs the field length of the precoding AndNumberOfLayers field when no PUSCH repetition is configured, and N_TPMI，RepIs a number of the one or more TPMIs to be used for the PUSCH repetition.

Example 11 includes the apparatus of example 10, wherein when N_TPMI，RepEqual to 1, a single TPMI contained in the precoding andmbumberomlayers field is used for all the PUSCH repetitions; when N is present_TPMI，RepEqual to the number of PUSCH repetitions, a one-to-one mapping of the TPMI contained in the precoding AndNumberOfLayers field to the PUSCH repetitions; and when N is_TPMI，RepLess than the number of PUSCH repetitions, the TPMI contained in the precoding AndNumberOfLayers field is in a one-to-many mapping relationship with the PUSCH repetitions.

Example 12 includes the apparatus of example 11, wherein the one-to-many mapping includes: for PUSCH repetition i, TPMI_kIs applied to the PUSCH repetition i, where i ∈ (0,1, … number PUSCH repetition-1), number PUSCH repetition is the number of PUSCH repetitions, k ∈ (0,1, … N)_TPMI，Rep-1), and k ═ i mod N_TPMI，RepOr

Example 13 includes the apparatus of example 1, wherein the UE is configured with one set of sounding reference signal, SRS, resources with usage set to 'codebook', the set of SRS resources including one or more SRS resources, and the processing circuitry is further configured to encode the one or more SRS and provide the one or more SRS to the RF interface circuitry for transmission to the TRP via the one or more SRS resources.

Example 14 includes the apparatus of example 1, wherein the UE is configured with a plurality of sounding reference signal, SRS, resource sets whose usage is set to 'codebook', each SRS resource set of the plurality of SRS resource sets including one or more SRS resources and being associated with a respective TRP of the plurality of TRPs, and the processing circuitry is further configured to encode one or more SRSs and provide the one or more SRSs to the RF interface circuitry for transmission to the respective TRP via the one or more SRS resources of each SRS resource set.

Example 15 includes the apparatus of example 14, wherein the DCI includes an SRS resource indicator, SRI, field containing one or more SRIs, each SRI indicating an SRS resource from a respective SRS resource set of the plurality of SRS resource sets.

Example 16 includes the apparatus of any of examples 1 to 15, wherein when the type of PUSCH repetition is a frequency division multiplexing, FDM, PUSCH repetition, the processing circuitry is configured to multiplex the PUSCH repetition by: repeatedly mapping the PUSCH to respective sets of repeated resources RRG, each RRG comprising a plurality of consecutive physical resource blocks PRB.

Example 17 includes the apparatus of example 16, wherein the processing circuitry is configured to repeatedly code and multiplex the PUSCH into a discrete fourier transform-spread-orthogonal frequency division multiplexing, DFT-s-OFDM, waveform by: applying Discrete Fourier Transform (DFT) spread spectrum to PUSCH data in a time domain; copying the PUSCH data after the DFT spreading to generate the PUSCH repetition; repeatedly mapping the PUSCH to the corresponding RRG; and repeatedly applying OFDM modulation to the PUSCH by inverse discrete fourier transform, IDFT.

Example 18 includes the apparatus of example 17, wherein the RRGs for the respective PUSCH repetitions have frequency resource allocations of the same size.

Example 19 includes the apparatus of example 17, wherein the processing circuitry is further configured to apply the same phase tracking reference signal, PT-RS, pattern to the PUSCH repeated transmission.

Example 20 includes the apparatus of any one of examples 16 to 19, wherein the index of the RRG is UE-specific and based on a frequency bandwidth allocated to the UE.

Example 21 includes the apparatus of any one of examples 16 to 19, wherein the index of the RRG is cell-specific and is based on a reference number of the RRG relative to a common resource block.

Example 22 includes the apparatus of any of examples 16 to 21, wherein when the UE is operating in frequency range 2FR2 and supports simultaneous transmissions from multiple spatial relationships or multiple antenna panels, the processing circuitry is further configured to: determining the plurality of spatial relationships or the plurality of antenna panels based on the DCI; and repeatedly providing the PUSCH to the RF interface circuitry for transmission to the plurality of TRPs on respective RRGs via respective spatial relationships or antenna panels.

Example 23 includes the apparatus of any one of examples 1 to 15, wherein when the type of PUSCH repetition is a time division multiplexing, TDM, based PUSCH repetition, the processing circuitry is configured to multiplex the PUSCH repetition by: repeatedly mapping the PUSCH to a corresponding time period within the same slot or across multiple slots.

Example 24 includes the apparatus of example 23, wherein an interval period between two adjacent PUSCH repetitions is zero.

Example 25 includes the apparatus of example 23, wherein the processing circuitry is configured to repeatedly allocate the same frequency domain resources or different frequency domain resources for the PUSCH based on the DCI.

Example 26 includes the apparatus of example 25, wherein the processing circuitry is further configured to: applying the same phase tracking reference signal (PT-RS) pattern to the PUSCH repeated transmission when the same frequency domain resource is allocated to the PUSCH repetition, and applying a different PT-RS pattern to the PUSCH repeated transmission when the different frequency domain resource is allocated to the PUSCH repetition.

Example 27 includes the apparatus of any of examples 23 to 26, wherein when the UE is operating in frequency range 2FR2 and supports simultaneous transmissions from multiple spatial relationships or multiple antenna panels, the processing circuitry is further configured to: determining the plurality of spatial relationships or the plurality of antenna panels based on the DCI; and repeatedly providing the PUSCH to the RF interface circuitry for transmission to the plurality of TRPs via the respective spatial relationship or antenna panel over the respective time period.

Example 28 includes the apparatus of any of examples 1-15, wherein when the UE is operating in frequency range 2FR2 and supports simultaneous transmissions from multiple spatial relationships or multiple antenna panels, and when the type of PUSCH repetition is a PUSCH repetition based on spatial division multiplexing, SDM, the processing circuitry is further configured to: determining the plurality of spatial relationships or the plurality of antenna panels based on the DCI; and repeatedly providing the PUSCH to the RF interface circuitry for transmission to the plurality of TRPs via the respective spatial relationships or antenna panels.

Example 29 includes the apparatus of example 28, wherein the processing circuitry is configured to repeatedly allocate the same frequency domain resources and the same time domain resources for the PUSCH based on the DCI.

Example 30 includes a method performed at a user equipment, UE, comprising: receiving downlink control information, DCI, from a transmission reception point, TRP, the DCI being for scheduling a codebook-based physical uplink shared channel, PUSCH, transmission to a plurality of TRPs; repeatedly encoding and multiplexing a plurality of codebook-based PUSCHs based on the DCI and PUSCH configuration information from higher layers; and repeatedly sending the encoded and multiplexed PUSCH to the plurality of TRPs.

Example 31 includes the method of example 30, wherein repeatedly encoding and multiplexing PUSCH includes: and repeatedly coding and multiplexing the PUSCH into a cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) waveform or a discrete Fourier transform-spread spectrum-orthogonal frequency division multiplexing (DFT-s-OFDM) waveform.

Example 32 includes the method of example 30, wherein the PUSCH configuration information includes an information element IE to indicate the type of PUSCH repetition and the number of PUSCH repetitions.

Example 33 includes the method of example 32, wherein the type of PUSCH repetition comprises a PUSCH repetition based on frequency division multiplexing, FDM, time division multiplexing, TDM, or a PUSCH repetition based on spatial division multiplexing, SDM.

Example 34 includes the method of example 30, further comprising: determining a capability of the UE with respect to which type of PUSCH repetition is supported; reporting the capability of the UE to the TRP or the higher layer.

Example 35 includes the method of example 30, wherein the DCI comprises: a precoding andmbumberoflayers field containing one or more transmission precoding matrix indices TPMI; and a sounding reference signal, SRS, resource indicator, SRI, field containing one or more SRIs, and a number of the one or more TPMIs and a number of the one or more SRIs are predefined or configured by the higher layer.

Example 36 includes the method of example 35, wherein a field length of the SRI field is defined by

To determine, wherein N_SRSIs the number of SRS resources configured in an SRS resource set, and N_SRI，RepIs a number of the one or more SRIs to be used for the PUSCH repetition.

Example 37 includes the method of example 36, wherein when N_SRI，RepEqual to 1, a single SRI contained in the SRI field is used for all the PUSCH repetitions; when N is present_SRI，RepWhen the number of the repeated PUSCH is equal to the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH are in a one-to-one mapping relation; and when N is_SRI，RepAnd when the number of the repeated PUSCH is less than the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH form a one-to-many mapping relation.

Example 38 includes the method of example 37, wherein the one-to-many mapping includes: for PUSCH repetition i, SRI_jIs applied to the PUSCH repetition i, wherein i ∈ (0,1, … number of PUSCH repetition-1), number of PUSCH repetition is the number of PUSCH repetitions, j ∈ (0,1, … N)_SRI，Rep-1), and j ═ i mod N_SRI，RepOr

Example 39 includes the method of example 35, wherein a field length of the precoding andmbumberoflayers field is defined by N ═ L_TPMI×N_TPMI，RepTo determine wherein L_TPMIIs the field length of the precoding AndNumberOfLayers field when no PUSCH repetition is configured, and N_TPMI，RepIs a number of the one or more TPMIs to be used for the PUSCH repetition.

Example 40 includes the method of example 39, wherein when N_TPMI，RepEqual to 1, a single TPMI contained in the precoding andmbumberomlayers field is used for all the PUSCH repetitions; when N is present_TPMI，RepTPMI and the PUS contained in the precoding AndNumberOfLayers field equal to the number of PUSCH repetitionsThe CH is repeated into a one-to-one mapping relation; and when N is_TPMI，RepLess than the number of PUSCH repetitions, the TPMI contained in the precoding AndNumberOfLayers field is in a one-to-many mapping relationship with the PUSCH repetitions.

Example 41 includes the method of example 40, wherein the one-to-many mapping comprises: for PUSCH repetition i, TPMI_kIs applied to the PUSCH repetition i, where i ∈ (0,1, … number PUSCHRepositions-1), number PUSCHRepositions is the number of PUSCH repetitions, k ∈ (0,1, … N)_TPMI，Rep-1), and k ═ i mod N_TPMI，RepOr

Example 42 includes the method of example 30, wherein the UE is configured with one set of sounding reference signal, SRS, resources with usage set to 'codebook', the set of SRS resources comprising one or more SRS resources, and the method further comprises transmitting one or more SRS to the TRP via the one or more SRS resources.

Example 43 includes the method of example 30, wherein the UE is configured with a plurality of sounding reference signal, SRS, resource sets whose usage is set to 'codebook', each SRS resource set of the plurality of SRS resource sets including one or more SRS resources and being associated with a respective TRP of the plurality of TRPs, and the method further comprises transmitting one or more SRSs to the respective TRP via the one or more SRS resources of each SRS resource set.

Example 44 includes the method of example 43, wherein the DCI includes an SRS resource indicator, SRI, field containing one or more SRIs, each SRI indicating an SRS resource from a respective SRS resource set of the plurality of SRS resource sets.

Example 45 includes the method of any of examples 30 to 44, wherein, when the type of PUSCH repetition is a frequency division multiplexing, FDM, PUSCH repetition, encoding and multiplexing the PUSCH repetition comprises: repeatedly mapping the PUSCH to respective sets of repeated resources RRG, each RRG comprising a plurality of consecutive physical resource blocks PRB.

Example 46 includes the method of example 45, wherein repeatedly encoding and multiplexing the PUSCH includes: applying Discrete Fourier Transform (DFT) spread spectrum to PUSCH data in a time domain; copying the PUSCH data after the DFT spreading to generate the PUSCH repetition; repeatedly mapping the PUSCH to the corresponding RRG; and repeatedly applying OFDM modulation to the PUSCH by inverse discrete fourier transform, IDFT.

Example 47 includes the method of example 46, wherein the RRGs for the respective PUSCH repetitions have frequency resource allocations of a same size.

Example 48 includes the method of example 46, further comprising: applying the same phase tracking reference signal PT-RS pattern to the PUSCH repeated transmission.

Example 49 includes the method of any one of examples 45 to 48, wherein the index of the RRG is UE-specific and based on a frequency bandwidth allocated to the UE.

Example 50 includes the method of any one of examples 45 to 48, wherein the index of the RRG is cell-specific and is based on a reference number of the RRG relative to a common resource block.

Example 51 includes the method of any one of examples 45 to 50, wherein when the UE is operating in frequency range 2FR2 and supports simultaneous transmissions from multiple spatial relationships or multiple antenna panels, the method further comprises: determining the plurality of spatial relationships or the plurality of antenna panels based on the DCI; and transmitting the PUSCH repetition to the plurality of TRPs on respective RRGs via respective spatial relationships or antenna panels.

Example 52 includes the method of any of examples 30 to 44, wherein, when the type of PUSCH repetition is a time division multiplexing, TDM, based PUSCH repetition, encoding and multiplexing the PUSCH repetition comprises: repeatedly mapping the PUSCH to a corresponding time period within the same slot or across multiple slots.

Example 53 includes the method of example 52, wherein an interval period between two adjacent PUSCH repetitions is zero.

Example 54 includes the method of example 52, further comprising: repeatedly allocating the same frequency domain resource or different frequency domain resources for the PUSCH based on the DCI.

Example 55 includes the method of example 54, further comprising: applying the same phase tracking reference signal (PT-RS) pattern to the PUSCH repeated transmission when the same frequency domain resource is allocated to the PUSCH repetition, and applying a different PT-RS pattern to the PUSCH repeated transmission when the different frequency domain resource is allocated to the PUSCH repetition.

Example 56 includes the method of any of examples 52-55, wherein when the UE is operating in frequency range 2FR2 and supports simultaneous transmissions from multiple spatial relationships or multiple antenna panels, the method further comprises: determining the plurality of spatial relationships or the plurality of antenna panels based on the DCI; and transmitting the PUSCH repetition to the plurality of TRPs via the respective spatial relationship or antenna panel over the respective time period.

Example 57 includes the method of any of examples 30 to 44, wherein when the UE is operating in frequency range 2FR2 and supports simultaneous transmissions from multiple spatial relationships or multiple antenna panels, and when the type of PUSCH repetition is a PUSCH repetition based on spatial division multiplexing, SDM, the method further comprises: determining the plurality of spatial relationships or the plurality of antenna panels based on the DCI; and transmitting the PUSCH repetition to the plurality of TRPs via the respective spatial relationships or antenna panels.

Example 58 includes the method of example 57, further comprising: and repeatedly allocating the same frequency domain resource and the same time domain resource for the PUSCH based on the DCI.

Example 59 includes an apparatus for transmitting a reception point TRP, comprising: a radio frequency, RF, interface circuit configured to receive one or more sounding reference signals, SRSs, from a user equipment, UE, via one or more SRS resources of one or more SRS resource sets whose usage is set to 'codebook'; and processing circuitry coupled with the RF interface circuitry and configured to: generating downlink control information, DCI, for scheduling codebook-based PUSCH transmissions to a plurality of TRPs based on the measurements of the one or more SRS resources and configuration information associated with physical uplink shared channel, PUSCH, repetitions from higher layers; and provide the DCI to the RF interface circuitry for transmission to the UE.

Example 60 includes the apparatus of example 59, wherein the DCI comprises: a precoding andmbumberoflayers field containing one or more transmission precoding matrix indices TPMI; and a sounding reference signal, SRS, resource indicator, SRI, field containing one or more SRIs, and a number of the one or more TPMIs and a number of the one or more SRIs are predefined or configured by the higher layer.

Example 61 includes the apparatus of example 60, wherein a field length of the SRI field is defined by

To determine, wherein N_SRSIs the number of SRS resources configured in an SRS resource set, and N_SRI，RepIs a number of the one or more SRIs to be used for the PUSCH repetition.

Example 62 includes the apparatus of example 61, wherein when N is_SRI，RepEqual to 1, a single SRI contained in the SRI field is used for all the PUSCH repetitions; when N is present_SRI，RepWhen the number of the repeated PUSCH is equal to the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH are in a one-to-one mapping relation; and when N is_SRI，RepAnd when the number of the repeated PUSCH is less than the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH form a one-to-many mapping relation.

Example 63 includes the apparatus of example 62, wherein the one-to-many mapping comprises: for PUSCH repetition i, SRI_jIs applied to the PUSCH repetition i, where i ∈ (0,1, … numberof PUSCHreppetitations-1), number of PUSCH repetition is the number of PUSCH repetitions, j ∈ (0,1, … N_SRI，Rep-1), and j ═ i mod N_SRI，RepOr

Example 64 includes the apparatus of example 60, wherein a field length of the precoding andmbumberoflayers field is defined by N-L_TPMI×N_TPMI，RepTo determine wherein L_TPMIIs the field length of the precoding AndNumberOfLayers field when no PUSCH repetition is configured, and N_TPMI,RepIs a number of the one or more TPMIs to be used for the PUSCH repetition.

Example 65 includes the apparatus of example 64, wherein when N is_TPMI，RepEqual to 1, a single TPMI contained in the precoding andmbumberomlayers field is used for all the PUSCH repetitions; when N is present_TPMI，RepEqual to the number of PUSCH repetitions, a one-to-one mapping of the TPMI contained in the precoding AndNumberOfLayers field to the PUSCH repetitions; and when N is_TPMI，RepLess than the number of PUSCH repetitions, the TPMI contained in the precoding AndNumberOfLayers field is in a one-to-many mapping relationship with the PUSCH repetitions.

Example 66 includes the apparatus of example 65, wherein the one-to-many mapping comprises: for PUSCH repetition i, TPMI_kIs applied to the PUSCH repetition i, where i ∈ (0,1, … number PUSCH repetition-1), number PUSCH repetition is the number of PUSCH repetitions, k ∈ (0,1, … N)_TPMI,Rep-1), and k ═ i mod N_TPMI,RepOr

Example 67 includes a method performed at a transmit receive point, TRP, comprising: receiving one or more Sounding Reference Signals (SRS) from a User Equipment (UE) via one or more SRS resources in one or more SRS resource sets whose usage conditions are set to 'codebook'; generating downlink control information, DCI, to schedule codebook-based PUSCH transmissions to a plurality of TRPs based on measurements of the one or more SRS resources and configuration information associated with physical uplink shared channel, PUSCH, repetitions from higher layers; and transmitting the DCI to the UE.

Example 68 includes the method of example 67, wherein the DCI comprises: a precoding andmbumberoflayers field containing one or more transmission precoding matrix indices TPMI; and a sounding reference signal, SRS, resource indicator, SRI, field containing one or more SRIs, and a number of the one or more TPMIs and a number of the one or more SRIs are predefined or configured by the higher layer.

Example 69 includes the method of example 68, wherein a field length of the SRI field is defined by

To determine, wherein N_SRSIs the number of SRS resources configured in an SRS resource set, and N_SRI,RepIs a number of the one or more SRIs to be used for the PUSCH repetition.

Example 70 includes the method of example 69, wherein when N_SRI,RepEqual to 1, a single SRI contained in the SRI field is used for all the PUSCH repetitions; when N is present_SRI,RepWhen the number of the repeated PUSCH is equal to the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH are in a one-to-one mapping relation; and when N is_SRI,RepAnd when the number of the repeated PUSCH is less than the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH form a one-to-many mapping relation.

Example 71 includes the method of example 70, wherein the one-to-many mapping comprises: for PUSCH repetition i, SRI_jIs applied to the PUSCH repetition i, wherein i ∈ (0,1, … number of PUSCH repetition-1), number of PUSCH repetition is the number of PUSCH repetitions, j ∈ (0,1, … N)_SRI,Rep-1), and j ═ i mod N_SRI,RepOr

Example 72 includes the method of example 68, wherein a field length of the precoding andmbumberoflayers field is defined by N ═ L_TPMI×N_TPMI,RepTo determine, wherein N_TPMIIs the field length of the precoding AndNumberOfLayers field when no PUSCH repetition is configured, and N_TPMI,RepIs a number of the one or more TPMIs to be used for the PUSCH repetition.

Example 73 includes the method of example 72, wherein when N_TPMI，RepEqual to 1, a single TPMI contained in the precoding andmbumberomlayers field is used for all the PUSCH repetitions; when N is present_TPMI,RepEqual to the number of PUSCH repetitions, a one-to-one mapping of the TPMI contained in the precoding AndNumberOfLayers field to the PUSCH repetitions; and when N is_TPMI，RepLess than the number of PUSCH repetitions, the TPMI contained in the precoding AndNumberOfLayers field is in a one-to-many mapping relationship with the PUSCH repetitions.

Example 74 includes the method of example 73, wherein the one-to-many mapping includes: for PUSCH repetition i, TPMI_kIs applied to the PUSCH repetition i, where i ∈ (0,1, … number PUSCH repetition-1), number PUSCH repetition is the number of PUSCH repetitions, k ∈ (0,1, … N)_TPMI,Rep-1), and k ═ i mod N_TPMI,RepOr

Example 75 includes a computer-readable medium having instructions stored thereon, wherein the instructions, when executed by processing circuitry of a user equipment, UE, cause the processing circuitry to perform the method of any of examples 30-58.

Example 76 includes a computer-readable medium having instructions stored thereon, wherein the instructions, when executed by a processing circuit that transmits a reception point TRP, cause the processing circuit to perform the method of any one of examples 67 to 74.

Example 77 includes an apparatus for a user equipment, UE, comprising means for performing operations of the method of any of examples 30 to 58.

Example 78 includes an apparatus for transmitting a reception point TRP, including means for performing operations of a method as described in any one of examples 67-74.

Although certain embodiments have been illustrated and described herein for purposes of description, various alternative and/or equivalent embodiments or implementations calculated to achieve the same purposes may be substituted for the embodiments shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is manifestly intended that the embodiments described herein be limited only by the claims and the equivalents thereof.

Claims (29)

1. An apparatus for a User Equipment (UE), comprising:

a Radio Frequency (RF) interface circuit configured to receive Downlink Control Information (DCI) from a Transmit Reception Point (TRP), the DCI being for scheduling a codebook-based Physical Uplink Shared Channel (PUSCH) transmission to a plurality of TRPs; and

processing circuitry coupled with the RF interface circuitry and configured to:

encoding and multiplexing a plurality of codebook-based PUSCH repetitions based on the DCI and PUSCH configuration information from higher layers; and

repeatedly providing the encoded and multiplexed PUSCH to the RF interface circuitry for transmission to the plurality of TRPs.

2. The apparatus of claim 1, wherein the processing circuitry is configured to repeatedly encode and multiplex the PUSCH into a cyclic prefix-orthogonal frequency division multiplexing, CP-OFDM, waveform or a discrete fourier transform-spread-orthogonal frequency division multiplexing, DFT-s-OFDM, waveform.

3. The apparatus of claim 1, wherein the PUSCH configuration information comprises an information element IE for indicating a type of the PUSCH repetition and a number of the PUSCH repetitions.

4. The apparatus of claim 3, wherein the type of PUSCH repetition comprises a PUSCH repetition based on Frequency Division Multiplexing (FDM), a PUSCH repetition based on Time Division Multiplexing (TDM), or a PUSCH repetition based on Space Division Multiplexing (SDM).

5. The apparatus of claim 1, wherein the processing circuit is further configured to:

determining a capability of the UE with respect to which type of PUSCH repetition is supported;

encoding an indication of the capability of the UE; and

providing the encoded indication of the capability of the UE to the RF interface circuitry for reporting to the TRP or the higher layer.

6. The apparatus of claim 1, wherein the DCI comprises: a precoding andmbumberoflayers field containing one or more transmission precoding matrix indices TPMI; and a sounding reference signal, SRS, resource indicator, SRI, field containing one or more SRIs, and a number of the one or more TPMIs and a number of the one or more SRIs are predefined or configured by the higher layer.

7. The apparatus of claim 6, wherein a field length of the SRI field is defined by

To determine, wherein N_SRSIs the number of SRS resources configured in an SRS resource set, and N_SRI，RepIs the one or to be used for the PUSCH repetitionA number of SRIs.

8. The apparatus of claim 7, wherein when N is_SRI，RepEqual to 1, a single SRI contained in the SRI field is used for all the PUSCH repetitions; when N is present_SRI，RepWhen the number of the repeated PUSCH is equal to the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH are in a one-to-one mapping relation; and when N is_SRI，RepAnd when the number of the repeated PUSCH is less than the number of the repeated PUSCH, the SRI contained in the SRI field and the repeated PUSCH form a one-to-many mapping relation.

9. The apparatus of claim 8, wherein the one-to-many mapping comprises: for PUSCH repetition i, SRI_jIs applied to the PUSCH repetition i, wherein i ∈ (0, 1.. nu-PUSCH repetition-1), which is the number of PUSCH repetitions, j ∈ (0, 1.. N)_SRI，Rep-1), and j ═ i mod N_SRI，RepOr

10. The apparatus of claim 6, wherein the field length of the precoding andnbumberoflayers field is set by N-L_TPMI×N_TPMI，RepTo determine wherein L_TPMIIs the field length of the precoding AndNumberOfLayers field when no PUSCH repetition is configured, and N_TPMI，RepIs a number of the one or more TPMIs to be used for the PUSCH repetition.

11. The apparatus of claim 10, wherein when N is_TPMI，RepEqual to 1, a single TPMI contained in the precoding andmbumberomlayers field is used for all the PUSCH repetitions; when N is present_TPMI，RepEqual to the number of PUSCH repetitions, a one-to-one mapping of the TPMI contained in the precoding AndNumberOfLayers field to the PUSCH repetitions; and when N is_TPMI，RepLess than the number of PUSCH repetitions, the TPMI contained in the precoding AndNumberOfLayers field is in a one-to-many mapping relationship with the PUSCH repetitions.

12. The apparatus of claim 11, wherein the one-to-many mapping comprises: for PUSCH repetition i, TPMI_kIs applied to the PUSCH repetition i, wherein i ∈ (0, 1.. nu-PascHRepoetin-1), which is the number of PUSCH repetitions, k ∈ (0, 1.. N)_TPMI，Rep-1), and k ═ i mod N_TPMI，RepOr

13. The apparatus of claim 1, wherein the UE is configured with a set of sounding reference signal, SRS, resources with usage set to 'codebook', the set of SRS resources comprising one or more SRS resources, and the processing circuitry is further configured to encode the one or more SRS and provide the one or more SRS to the RF interface circuitry for transmission to the TRP via the one or more SRS resources.

14. The apparatus of claim 1, wherein the UE is configured with a plurality of sounding reference signal, SRS, resource sets with usage set to 'codebook', each SRS resource set of the plurality of SRS resource sets comprising one or more SRS resources and being associated with a respective TRP of the plurality of TRPs, and the processing circuitry is further configured to encode one or more SRSs and provide the one or more SRSs to the RF interface circuitry for transmission to the respective TRP via the one or more SRS resources of each SRS resource set.

15. The apparatus of claim 14, wherein the DCI comprises an SRS resource indicator, SRI, field containing one or more SRIs, each SRI indicating an SRS resource from a respective SRS resource set of the plurality of SRS resource sets.

16. The apparatus according to any of claims 1-15, wherein when the type of PUSCH repetition is a frequency division multiplexing, FDM, PUSCH repetition, the processing circuitry is configured to multiplex the PUSCH repetition by: repeatedly mapping the PUSCH to respective sets of repeated resources RRG, each RRG comprising a plurality of consecutive physical resource blocks PRB.

17. The apparatus of claim 16, wherein the processing circuitry is configured to repeatedly encode and multiplex the PUSCH into a discrete fourier transform-spread-orthogonal frequency division multiplexing, DFT-s-OFDM, waveform by:

applying Discrete Fourier Transform (DFT) spread spectrum to PUSCH data in a time domain;

copying the PUSCH data after the DFT spreading to generate the PUSCH repetition;

repeatedly mapping the PUSCH to the corresponding RRG; and

repeatedly applying OFDM modulation to the PUSCH by Inverse Discrete Fourier Transform (IDFT).

18. The apparatus of claim 17, wherein RRGs for respective PUSCH repetitions have frequency resource allocations of a same size.

19. The apparatus of claim 17, wherein the processing circuitry is further configured to apply the same phase tracking reference signal (PT-RS) pattern to the PUSCH repeated transmission.

20. The apparatus of claim 16, wherein the index of the RRG is UE-specific and is based on a frequency bandwidth allocated to the UE.

21. The apparatus of claim 16, wherein the index of the RRG is cell-specific and is based on a reference number of the RRG relative to a common resource block.

22. The apparatus of claim 16, wherein when the UE is operating in frequency range 2FR2 and supports simultaneous transmissions from multiple spatial relationships or multiple antenna panels, the processing circuitry is further configured to:

determining the plurality of spatial relationships or the plurality of antenna panels based on the DCI; and

repeatedly providing the PUSCH to the RF interface circuitry for transmission to the plurality of TRPs over respective RRGs via respective spatial relationships or antenna panels.

23. The apparatus of any of claims 1 to 15, wherein when the type of PUSCH repetition is a time division multiplexing, TDM, based PUSCH repetition, the processing circuitry is configured to multiplex the PUSCH repetition by: repeatedly mapping the PUSCH to a corresponding time period within the same slot or across multiple slots.

24. The apparatus of claim 23, wherein a gap period between two adjacent PUSCH repetitions is zero.

25. The apparatus of claim 23, wherein the processing circuitry is configured to repeatedly allocate the PUSCH on the same frequency domain resources or different frequency domain resources based on the DCI.

26. The apparatus of claim 25, wherein the processing circuit is further configured for: applying the same phase tracking reference signal (PT-RS) pattern to the PUSCH repeated transmission when the same frequency domain resource is allocated to the PUSCH repetition, and applying a different PT-RS pattern to the PUSCH repeated transmission when the different frequency domain resource is allocated to the PUSCH repetition.

27. The apparatus of claim 23, wherein when the UE is operating in frequency range 2FR2 and supports simultaneous transmissions from multiple spatial relationships or multiple antenna panels, the processing circuitry is further configured to:

determining the plurality of spatial relationships or the plurality of antenna panels based on the DCI; and

repeatedly providing the PUSCH to the RF interface circuitry for transmission to the plurality of TRPs via respective spatial relationships or antenna panels over respective time periods.

28. The apparatus according to any of claims 1-15, wherein when the UE is operating in frequency range 2FR2 and supports simultaneous transmissions from multiple spatial relationships or multiple antenna panels, and when the type of PUSCH repetition is a PUSCH repetition based on spatial division multiplexing, SDM, the processing circuitry is further configured to:

determining the plurality of spatial relationships or the plurality of antenna panels based on the DCI; and

repeatedly providing the PUSCH to the RF interface circuitry for transmission to the plurality of TRPs via respective spatial relationships or antenna panels.

29. The apparatus of claim 28, wherein the processing circuitry is configured to repeatedly allocate the PUSCH on the same frequency domain resources and the same time domain resources based on the DCI.

Images