SYSTEM AND METHOD FOR NON-CODEBOOK BASED MULTI-TRP PUSCH - Patent application

Abstract

A system and method are provided for a non-codebook-based multi-transmission / reception point (TRP) physical uplink shared channel (PUSCH). In some embodiments, the method performed by a wireless device includes receiving a configuration of first or second phase tracking reference signal (PT-RS) port indexes per SRS resource in two sounding reference signal (SRS) resource sets for the non-codebook-based PUSCH, receiving an indication of a first set of SRS resource indicators (SRIs) from the first SRS resource set and / or a second set of SRIs from the second SRS resource set, determining at least one of a first number of UL PT-RS ports to be transmitted according to the SRS resources indicated in the first set of SRIs and a second number of UL PT-RS ports to be transmitted according to the SRS resources indicated in the second set of SRIs, and transmitting the determined number of UL PT-RS ports with multiple PUSCH repetitions.

Description

[Technical Field]

[0001] Related Applications This application claims the benefit of Provisional Patent Application Serial No. 63 / 170,001, filed April 2, 2021, the disclosure of which is incorporated herein by reference in its entirety.

[0002] TECHNICAL FIELD This disclosure relates generally to non-codebook based transmission. [Background technology]

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

[0004] Data scheduling in NR is typically performed on a slot-by-slot basis, as shown in Figure 1, where an example of a 14-symbol slot is shown. The first two symbols contain the Physical Downlink Control Channel (PDCCH), and the remaining symbols contain the physical shared data channels, either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

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

[0006] In the frequency domain, the system bandwidth is divided into resource blocks (RBs), each corresponding to 12 consecutive subcarriers. RBs start at one end of the system bandwidth, numbered 0. The basic NR physical time-frequency resource grid is shown in Figure 2, which shows only one resource block (RB) in a 14-symbol slot. One OFDM subcarrier in one OFDM symbol interval forms one resource element (RE).

[0007] In NR Release 15, uplink (UL) data transmissions can be dynamically scheduled by uplink grants included in downlink control information (DCI) transmitted on the physical downlink control channel (PDCCH). The UE first decodes the uplink grant and then transmits the PUSCH based on the control information in the decoded uplink grant.

[0008] In addition to dynamic scheduling, NR also supports PUSCH transmission via configured grants (CGs). NR defines two types of CGs: Type 1 and Type 2. In CG Type 1, the start and stop of PUSCH transmission as well as the periodicity are semi-statically configured by RRC. In CG Type 2, the periodicity is configured by RRC, and the start and stop of PUSCH transmission are dynamically signaled by DCI.

[0009] Three UL DCI formats are supported in NR: DCI format 0_0, DCI format 0_1, and DCI format 0_2. Each DCI contains several bit fields that contain one or more of the following information: Sounding Reference Signal (SRS) Resource Indicator (SRI) Precoding information and number of layers Scheduled PUSCH TPC (Transmit Power Control) commands

[0010] SRI is used to indicate the SRS resource or resources associated with the PUSCH. "Precoding information and layer number" is used to indicate the transmit precoding matrix indicator (TPMI) and rank of the PUSCH. TPC is used to indicate the closed-loop power correction for the PUSCH.

[0011] NR Release 15 supports slot-based PUSCH repetition (or PUSCH repetition type A), where the number of aggregate slots for both dynamic scheduling and configuration grant type 2 is configured by RRC. In NR Release 16, this functionality is enhanced to allow the number of repetitions to be dynamically indicated (i.e., from one PUSCH scheduling opportunity to the next). That is, a nominal number of repetitions, K, is signaled as part of the time domain resource allocation (TDRA) in addition to the starting symbol, S, and the PUSCH length, L.

[0012] PUSCH repetition type B was introduced in NR Release 16 and allows the PUSCH to be repeated over multiple minislots. When scheduling a transmission with PUSCH repetition type B, the nominal number of repetitions K, in addition to the starting symbol S and the PUSCH length L, are signaled as part of the TDRA.

[0013] PUSCH transmission method

[0014] In NR, there are two PUSCH transmission schemes: codebook scheme and non-codebook scheme.

[0015] Codebook-based PUSCH scheme

[0016] Codebook-based PUSCH is enabled by the higher layer parameter txConfig=codebook. For dynamically scheduled PUSCH and configuration grant PUSCH type 2, the codebook-based PUSCH transmission scheme can be summarized as follows: The PUSCH is associated with one of the two SRS resources in the SRS resource set whose upper layer parameter utilization is set to "CodeBook". Note that only one SRS resource set set to "Codebook" can be configured. The gNB determines the rank in the codebook and the preferred UL precoder based on the UL sounding reference signal (SRS) resource selected from one or two SRS resources configured in the SRS resource set. The gNB indicates the selected SRS resource via a 1-bit SRI field in the DCI for scheduling the PUSCH. If only one SRS resource is configured in the SRS resource set, the SRI field is not present in the DCI. The gNB also indicates the rank of the UL precoder and the number of preferred layers via the “Precoding information and number of layers” field in the DCI. The UE performs a PUSCH transmission on the antenna port associated with the indicated SRS resource using the indicated TPMI and rank. The PUSCH is spatially related to the most recent SRS transmission on the indicated SRS resource.

[0017] Up to NR Release 16, only a single SRS resource set can be configured with usage set to "codebook".

[0018] Non-codebook-based PUSCH schemes

[0019] Non-codebook-based UL transmission is possible in NR, and reciprocal-based UL transmission is possible. Non-codebook-based PUSCH in NR is enabled when the higher layer parameter txConfig=nonCodebook is set. Note that in NR Release 15 / 16, the number of SRS resource sets with the higher layer parameter set to "nonCodeBook" is limited to one (i.e., only one SRS resource set can be configured for non-Codebook-based PUSCH transmission). The maximum number of SRS resources that can be configured for non-codebook-based uplink transmission is four.

[0020] By allocating DL CSI-RS to the UE, the UE can measure and infer suitable precoder weights for PUSCH transmissions on up to four spatial layers. The candidate precoder weights are transmitted using up to four single-port SRS resources corresponding to the spatial layers. The gNB then determines the transmission rank and multiple SRS resource indicators. TIFF0007753383000001.tif1156 is used to show the joint image. SRS is the number of configured SRS resources, and L max is the maximum number of layers supported by PUSCH. max Different numbers of N when =4 SRS The following shows the mapping between the code points of the SRI field and the SRI for the N SRS = 4 and the SRI bit field is mapped to index 12, the PUSCH is transmitted using the same antenna ports as the SRS ports of the first, third, and fourth SRS resources configured in the SRS resource set (i.e., three PUSCH layers are transmitted). N SRS= 4 and the SRI bit field is mapped to index 5, the PUSCH is transmitted using the same antenna port as the SRS port of the first and third SRS resources configured in the SRS resource set (i.e., two PUSCH layers are transmitted). N SRS = 4 and the SRI bit field is mapped to index 3, the PUSCH is transmitted using the same antenna port as the SRS port of the fourth SRS resource configured in the SRS resource set (i.e., one PUSCH layer is transmitted). Table 1: SRI indication for non-codebook based PUSCH transmission, L max =4 (Reused from 3GPP TS38.212 v16.4.0, Table 7.3.1.1.2-31). TIFF0007753383000002.tif78147

[0021] For non-codebook based PUSCH, 3GPP TS38.214 V16.0.0 specifies the following:

[0022] "For non-codebook based transmission, the UE may calculate the precoder to use for SRS transmission based on measurements of the associated NZP CSI-RS resource. The UE may be configured with only one NZP CSI-RS resource for the SRS resource set with the higher layer parameter use of SRS-ResourceSet set to 'nonCodebook' if configured."

[0023] Therefore, for non-codebook-based PUSCH transmission, only one NZP CSI-RS resource is configured in an SRS resource set, and the UE can use this associated NZP CSI-RS resource to calculate the precoder used for SRS transmission. The single NZP CSI-RS resource configured per SRS resource set is part of the SRS-Config information element and is shown below. The condition "NonCodebook" means that for SRS resource sets whose use is set to "nonCodeBook", the associated NZP CSI-RS is optionally present; otherwise, this field is not present. SRS-Config information element TIFF0007753383000003.tif212170

[0024] Furthermore, 3GPP TS38.214 specifies that if a UE is configured with an SRS resource set that has associated NZP CSI-RS resources, the UE shall not configure spatial relationship information for any of the SRS resources in the SRS resource set.

[0025] In NR, for non-codebook-based PUSCH, the UE performs a one-to-one mapping from the indicated SRI(s) to the indicated demodulation reference signal (DM-RS) port(s) and their corresponding PUSCH layers {0...ν-1} in ascending order. The UE must transmit the PUSCH using the same antenna port as the SRS port of the SRS resource(s) indicated by the SRI(s). (The SRS port of the (i+1)th SRS resource in the SRS resource set is p i =1000+i).

[0026] Until NR Release 16, only a single SRS resource set can be configured with the usage set to "nonCodebook".

[0027] Phase Tracking Reference Signal (PT-RS) for PUSCH in NR

[0028] In NR, a phase tracking reference signal (PT-RS) can be configured for PUSCH transmissions to allow the receiver to correct errors related to phase noise. The PT-RS can be configured by the upper layer parameter PTRS-UplinkConfig of DMRS-UplinkConfig for PUSCHs scheduled with DCI format 0_1 ​​or DCI format 0_2.

[0029] NR Release 15 supports one or two PT-RS ports for PUSCH. Each PT-RS port is associated with one DM-RS port for PUSCH. The maximum number of PT-RS ports configured is specified by the higher layer parameter maxNrofPorts in PTRS-UplinkConfig, based on the UE's reported need. If the UE reports the capability to support fully coherent UL transmission, it is expected that one PT-RS port will be configured as needed.

[0030] In the frequency domain, a PT-RS can reside on a maximum of one subcarrier per two PRBs. The subcarrier used for a PT-RS port must also be one of the subcarriers used for the DM-RS port associated with the PT-RS port. For DM-RS configuration type 1, a DM-RS port is mapped to every two subcarriers. As a result, the associated PT-RS can only be mapped to one of six subcarriers. A configurable offset can be configured to determine which subcarrier the DM-RS is mapped to (see Table 6.4.1.2.2.1-1 in 3GPP TS38.211).

[0031] In the time domain, the PT-RS can be configured with a time density of 1, 2, or 4, corresponding to a PT-RS every OFDM symbol, every second OFDM symbol, or every fourth OFDM symbol in a slot, respectively. The modulation symbols used for the PT-RS are the same as those for the associated DM-RS in the same subcarrier.

[0032] An example of a PT-RS is shown in Figure 3. The PT-RS port is associated with DM-RS port 0, with a subcarrier offset of 4 and a time density of 2. An example of REs for a PT-RS in an RB with a time density of 2 and a subcarrier offset of 4.

[0033] Non-codebook-based PUSCH uplink PT-RS transmission

[0034] For non-codebook-based PUSCH, the maximum number of uplink PT-RS ports is configured in the UE via the RRC PTRS-UplinkConfig information element (see 3GPP TS38.331 V16.2.0). Each SRS resource configured in the SRS resource set and with its usage set to "nonCodeBook" is configured with a PT-RS port index (i.e., ptrs-PortIndex) as follows: SRS-Config information element TIFF0007753383000004.tif242170

[0035] According to 3GPP TS38.214 V16.4.0, in a non-codebook-based PUSCH transmission, the actual number of UL PT-RS ports that the UE transmits from is determined based on the SRI(s) indicated in the non-codebook-based PUSCH transmission. The SRI may be indicated via a DCI (either DCI Format 0_1 ​​or DCI Format 0_2) or via a higher layer SRS Resource Indicator field configured via the RRC configuration parameter rrc-ConfiguredUplinkGrant.

[0036] If all indicated SRI(s) have the same PT-RS port index, then only a single PT-RS port is transmitted for the non-codebook-based PUSCH. However, if some of the indicated SRI(s) have corresponding SRS resources configured with PT-RS port index n0 and other indicated SRI(s) have corresponding SRS resources configured with PT-RS port index n1, then two PT-RS ports are transmitted for the non-codebook-based PUSCH.

[0037] Transmission of UL signals to multiple TRPs

[0038] Until NR Release 16, it was assumed that the PUSCH was always transmitted by the UE to the same single transmission / reception point (TRP). NR Release 17 introduces a PUSCH extension that allows a PUSCH scheduled by one DCI or configured grant (using the rrc-ConfiguredUplinkGrant parameter defined in 3GPP TS38.331 V16.2.0) to be repeated to two TRPs (i.e., a multi-TRP PUSCH repetition scheme). To support this, it was agreed that two SRS resource sets, each associated with one of two TRPs, can be configured for both codebook-based and non-codebook-based PUSCH schemes. Furthermore, a UE is indicated by two SRIs, two TMPIs, and two TPCs, each associated with one of the two TRPs.

[0039] At the RAN1#104e-bis meeting held in January and February 2021, it was agreed that for multi-TRP PUSCH repetition, two SRI fields should be included in DCI formats 0_1 and 0_2, which schedule the multi-TRP PUSCH repetition scheme. Each of the two SRI fields is used to indicate an SRI from each of two SRS resource sets configured for non-codebook-based PUSCH transmission. That is, the first SRI field can indicate one or more SRS resources from the first SRS resource set configured for the non-codebook-based PUSCH, and the second SRI field can indicate one or more SRS resources from the second SRS resource set configured for the non-codebook-based PUSCH.

[0040] Also, in the RAN1#104e-bis meeting, it was agreed that the same number of PUSCH layers are transmitted in different iterations targeting different TRPs. Note that the different TRPs here correspond to different SRS resource sets configured for non-codebook-based PUSCH. Due to the fact that the same number of PUSCH layers are transmitted in two TRPs, in NR Release 17, the number of SRS resources indicated by the two SRI fields (i.e., the number of SRIs) is the same.

[0041] Currently, a problem exists. In the existing NR Release 15 and Release 16 specifications, the actual number of UL PT-RS ports transmitted for a non-codebook-based PUSCH is determined based on the indicated SRI. In NR Release 15 and Release 16, only one set of SRI is indicated to the UE for non-codebook-based PUSCH transmission, and this existing solution supports non-codebook-based PUSCH transmission for a single TRP. However, in the multi-TRP case, two different sets of SRI are indicated to the UE, so this solution is not suitable for non-codebook-based PUSCHs transmitted for two different TRPs. Therefore, how to determine the actual number of UL PT-RS ports for a non-codebook-based multi-TRP PUSCH remains an open problem. Summary of the Invention

[0042] In some embodiments, a method for a non-codebook-based multi-transmission point (TRP) physical uplink shared channel (PUSCH) transmission performed by a wireless device includes receiving a configuration of first or second uplink (UL) phase tracking reference signal (PT-RS) port indices for each SRS resource among a plurality of sounding reference signal (SRS) resources comprised of two SRS resource sets for the non-codebook-based PUSCH, receiving an indication of at least one of a first set of SRS resource indicators (SRIs) indicating SRS resources from the first SRS resource set and a second set of SRIs indicating SRS resources from the second SRS resource set, determining at least one of a first number of UL PT-RS ports to transmit according to the SRS resources indicated in the first set of SRIs and a second number of UL PT-RS ports to transmit according to the SRS resources indicated in the second set of SRIs, and transmitting the determined number of UL PT-RS ports with multiple PUSCH repetitions.

[0043] In some embodiments, a first subset of PUSCH repetitions of the plurality of PUSCH repetitions are transmitted according to SRS resources indicated in a first set of SRIs, the first subset of PUSCH repetitions comprising transmissions of the first number of UL PT-RS ports.

[0044] In some embodiments, a second subset of PUSCH repetitions disjoint from a first subset of PUSCH repetitions of the plurality of PUSCH repetitions are transmitted according to SRS resources indicated in a second set of SRIs, the second subset of PUSCH repetitions comprising transmissions of the second number of UL PT-RS ports.

[0045] In some embodiments, all of the plurality of PUSCH repetitions are transmitted according to SRS resources indicated in a first set of the SRI, and the plurality of PUSCH repetitions include transmissions of the first number of UL PT-RS ports.

[0046] In some embodiments, all of the plurality of PUSCH repetitions are transmitted according to SRS resources indicated in a second set of the SRI, and the plurality of PUSCH repetitions include transmissions of the second number of UL PT-RS ports.

[0047] In some embodiments, the first number of UL PT-RS ports is the same as the second number of UL PT-RS ports, hi some embodiments, the first number of UL PT-RS ports is different from the second number of UL PT-RS ports.

[0048] In some embodiments, the first number of UL PT-RS ports is determined to be 1 if all SRS resources indicated in the first set of SRIs are configured with the same PT-RS port index. In some embodiments, the second number of UL PT-RS ports is determined to be 1 if all SRS resources indicated in the second set of SRIs are configured with the same PT-RS port index.

[0049] In some embodiments, the first number of UL PT-RS ports is determined to be 2 if the SRS resources indicated in the first set of SRIs are configured with two different PT-RS port index values. In some embodiments, the second number of UL PT-RS ports is determined to be 2 if the SRS resources indicated in the second set of SRIs are configured with two different PT-RS port index values.

[0050] In some embodiments, the first set of SRIs and the second set of SRIs are indicated via first and second SRI fields, respectively, in a downlink control indicator (DCI) that schedules the PUSCH repetitions. In some embodiments, the first set of SRIs and the second set of SRIs are indicated via first and second indices, respectively, configured as part of a configured grant PUSCH configuration.

[0051] In some embodiments, the first SRS resource set corresponds to a first transmission / reception point (TRP) and the second SRS resource set corresponds to a second TRP. In some embodiments, the wireless device (1700) operates in a fifth generation (5G) New Radio (NR) network.

[0052] A method is proposed for determining the actual number of UL PT-RS ports for non-codebook-based multi-TRP PUSCH transmissions. In the proposed solution, a first number of UL PT-RS ports corresponding to a first TRP is determined according to SRS resources indicated in a first SRI set from a first configured SRS resource set. A second number of UL PT-RS ports corresponding to a second TRP is determined according to SRS resources indicated in a second SRI set from a second configured SRS resource set. In some embodiments, the UE transmits the same number of UL PT-RS ports to the two TRPs. In another embodiment, the number of UL PT-RS ports is determined independently for TRP1 and TRP2.

[0053] Various embodiments are proposed herein that address one or more of the problems disclosed herein.

[0054] Certain embodiments may provide one or more of the following technical advantages: In embodiment 1, the same number of UL PT-RS ports are transmitted toward two TRPs, which is beneficial when the same number of UE panels are used for PUSCH repetitions toward TRP1 and TRP2. When a single UE panel is used to transmit PUSCH layers toward both TRP1 and TRP2, a single UL PT-RS port is sufficient for PUSCH repetitions toward both TRP1 and TRP2. When two UE panels are used to transmit PUSCH layers toward both TRP1 and TRP2, two UL PT-RS ports are required to repeat PUSCH toward both TRP1 and TRP2.

[0055] Embodiment 2 is beneficial for a UE with multiple antenna panels, where the UE uses N1 panels to transmit a PUSCH toward a first TRP and N2 panels to transmit a PUSCH toward a second TRP, where N1 may be different from N2.

[0056] Embodiment 3 is useful for determining the number of UL PT-RS ports when there is dynamic switching between single-TRP-based PUSCH and multi-TRP-based PUSCH. [Brief explanation of the drawings]

[0057] The accompanying drawing figures, which are incorporated in and constitute a part of this specification, illustrate several aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

[0058] [Figure 1] It shows that data scheduling in New Radio (NR) is slot-based, typically with a slot of 14 symbols. The first two symbols contain the Physical Downlink Control Channel (PDCCH), and the remaining symbols contain the Physical Shared Data Channel, either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0059] [Figure 2] 1 shows a basic NR physical time-frequency resource grid, with only one resource block (RB) in a 14-symbol slot shown.

[0060] [Figure 3] 1 illustrates an example of a phase tracking reference signal (PT-RS) with a subcarrier offset of 4 and a time density of 2, where the PT-RS port is associated with demodulation reference signal (DM-RS) port 0.

[0061] [Figure 4] 1 illustrates an example of a cellular communication system in which embodiments of the present disclosure may be implemented.

[0062] [Figure 5] 1 illustrates a method performed by a wireless device for non-codebook based PUSCH transmission, in accordance with some embodiments of the present disclosure.

[0063] [Figure 6] 1 illustrates a method performed by a base station for non-codebook-based PUSCH reception, in accordance with some embodiments of the present disclosure.

[0064] [Figure 7] FIG. 1 is an illustration of PUSCH repetitions directed to two TRPs, with some PUSCH repetitions directed to TRP1 and other PUSCH repetitions directed to TRP2, in accordance with some embodiments of the present disclosure.

[0065] [Figure 8] 1 illustrates two uplink (UL) PT-RS ports corresponding to PUSCH repetitions for both TRP1 and TRP2, according to some embodiments of the present disclosure. [Figure 9] 1 illustrates two uplink (UL) PT-RS ports corresponding to PUSCH repetitions for both TRP1 and TRP2, according to some embodiments of the present disclosure.

[0066] [Figure 10] 1 illustrates that even if the number of UL PT-RS ports transmitted towards TRP1 and TRP2 are the same, the exact UL PT-RS port indexes transmitted towards TRP1 and TRP2 may be different, according to some embodiments of the present disclosure.

[0067] [Figure 11] 1 illustrates an option to configure the same UL PT-RS port index for all sounding reference signal (SRS) resources in an SRS resource set, according to some embodiments of the present disclosure.

[0068] [Figure 12]10 illustrates an example in which, based on configured SRS resource sets and indicated first and second SRS resource indicator (SRI) sets, a UE initially determines that the UL PT-RS ports associated with the indicated first set of SRIs are n0 and n1, and that the UL PT-RS port associated with the indicated second set of SRIs is n0, in accordance with some embodiments of the present disclosure.

[0069] [Figure 13] 10 illustrates an example in which a first set of SRIs indicates to a UE that for a PUSCH repetition toward TRP1, two PUSCH layers are transmitted using the same antenna port as the SRS port(s) for resources 0 and 1 from SRS resource set 1, in accordance with some embodiments of the present disclosure.

[0070] [Figure 14] 1 is a schematic block diagram of a radio access node according to some embodiments of the present disclosure.

[0071] [Figure 15] FIG. 1 is a schematic block diagram illustrating a virtualized embodiment of a radio access node in accordance with some embodiments of the present disclosure.

[0072] [Figure 16] FIG. 10 is a schematic block diagram of a radio access node according to some other embodiments of the present disclosure.

[0073] [Figure 17] 10 is a schematic block diagram of a wireless communication device according to some other embodiments of the present disclosure.

[0074] [Figure 18] 10 is a schematic block diagram of a wireless communication device according to some other embodiments of the present disclosure.

[0075] [Figure 19]1 illustrates a communication system including a communication network, such as a 3GPP-type cellular network, consisting of an access network, such as a RAN, and a core network, in accordance with some embodiments of the present disclosure.

[0076] [Figure 20] 1 illustrates a communication system in which a host computer comprises hardware including a communication interface configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system in accordance with some embodiments of the present disclosure.

[0077] [Figure 21] 1 is a flowchart illustrating a method implemented in a communication system, according to one embodiment. [Figure 22] 1 is a flowchart illustrating a method implemented in a communication system, according to one embodiment. [Figure 23] 1 is a flowchart illustrating a method implemented in a communication system, according to one embodiment. [Figure 24] 1 is a flowchart illustrating a method implemented in a communication system, according to one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0078] The embodiments described below represent information to enable those skilled in the art to practice the embodiments and illustrate the best modes for practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the present disclosure and will recognize applications of these concepts not specifically addressed herein. It is understood that these concepts and applications are within the scope of the present disclosure.

[0079] Wireless Node: As used herein, a "wireless node" is either a wireless access node or a wireless communication device.

[0080] Radio Access Node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a Radio Access Network (RAN) of a cellular communications network that operates to transmit and / or receive signals wirelessly. Examples of radio access nodes include, but are not limited to, base stations (e.g., a New Radio (NR) base station (gNB) in a 3rd Generation Partnership Project (3GPP) fifth-generation (5G) NR network, or an enhanced or evolved Node B (eNB) in a 3GPP long-term evolution (LTE) network), high-power or macro base stations, low-power base stations (e.g., a micro base station, a pico base station, a Home eNB, etc.), a relay node, a network node implementing some of the functionality of a base station (e.g., a network node implementing a gNB central unit (gNB-CU), a network node implementing a gNB distributed unit (gNB-DU), etc.), or a network node implementing some of the functionality of another radio access node, etc.

[0081] Core Network Node: As used herein, "core network node" refers to any type of node in a core network or any node that implements a core network function. Some examples of core network nodes include, for example, a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), etc. Other examples of core network nodes include nodes that implement an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), etc.

[0082] Communications Device: As used herein, a "communications device" refers to any type of device that can access an access network. Examples of communications devices include, but are not limited to, a mobile phone, a smartphone, a sensor device, a meter, a vehicle, a home appliance, a medical appliance, a media player, a camera, or any type of consumer electronics, such as a television, a radio, a lighting fixture, a tablet computer, a laptop, a personal computer (PC), etc. A communications device may be a portable, handheld, computer-based, or vehicle-mounted mobile device capable of communicating voice and / or data via wireless or wired connections.

[0083] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that accesses (i.e., receives service from) a wireless network (e.g., a cellular network). Examples of wireless communication devices include, but are not limited to, user equipment (UE) in a 3GPP network, machine-type communication (MTC) devices, Internet of Things (IoT) devices, etc. Such wireless communication devices may be, or may be integrated into, mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting fixtures, tablet computers, laptops, PCs, etc. Wireless communication devices may be portable, handheld, computer-embedded, or vehicle-mounted mobile devices capable of communicating voice and / or data over a wireless connection.

[0084] Network Node: As used herein, a "network node" refers to a node that is part of the RAN or core network of a cellular communications network / system.

[0085] Transmit / Receive Point (TRP): In some embodiments, a TRP may be a network node, a radio head, a spatial relationship, or a transmission configuration indicator (TCI) state. In some embodiments, a TRP may be represented by a spatial relationship or a TCI state. In some embodiments, a TRP may use multiple TCI states. In some embodiments, a TRP may be part of a gNB that transmits and receives radio signals to and from a UE according to physical layer characteristics and parameters specific to that element. In some embodiments, in multiple TRP (multi-TRP) operation, a serving cell can schedule a UE from two TRPs, providing better physical downlink shared channel (PDSCH) coverage, reliability, and / or data rates. Multi-TRP has two different modes of operation: single downlink control information (DCI) and multi-DCI. In both modes, uplink and downlink operation control is performed by both the physical layer and medium access control (MAC). In single-DCI mode, the UE is scheduled by the same DCI for both TRPs, while in multi-DCI mode, the UE is scheduled by independent DCI from each TRP.

[0086] 4 illustrates an example of a cellular communication system 400 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communication system 400 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC), or an Evolved Packet System (EPS) including an Evolved Universal Terrestrial RAN (E-UTRAN) and an Evolved Packet Core (EPC). In this example, the RAN includes base stations 402-1 and 402-2, which in 5GS include NR base stations (gNBs) and optionally Next Generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to 5GC), and in EPS include eNBs, controlling corresponding (macro) cells 404-1 and 404-2. Base stations 402-1 and 402-2 are generally referred to herein collectively as base stations 402 and individually as base stations 402. Similarly, (macro) cells 404-1 and 404-2 are generally referred to herein collectively as (macro) cells 404, and individually as (macro) cells 404. The RAN may also include multiple low power nodes 406-1 through 406-4 that control corresponding small cells 408-1 through 408-4. The low power nodes 406-1 through 406-4 may be small base stations (such as pico or femto base stations) or remote radio heads (RRHs), or the like. Notably, although not shown, one or more of the small cells 408-1 through 408-4 may alternatively be provided by the base station 402. The low power nodes 406-1 through 406-4 are generally referred to herein collectively as low power nodes 406, and individually as low power nodes 406. Similarly, small cells 408-1 through 408-4 are generally referred to herein collectively as small cells 408 and individually as small cells 408. The cellular communication system 400 also includes a core network 410, referred to as 5GC in 5G systems (5GS). The base stations 402 (and optionally low power nodes 406) are connected to the core network 410.

[0087] Base station 402 and low power node 406 serve wireless communication devices 412-1 through 412-5 within corresponding cells 404 and 408. Wireless communication devices 412-1 through 412-5 are generally referred to herein collectively as wireless communication devices 412 and individually as wireless communication devices 412. In the following description, wireless communication devices 412 are often UEs, although the disclosure is not limited thereto.

[0088] In some embodiments, a set of transmission points (TPs) is a set of geographically co-located transmit antennas (e.g., antenna arrays (having one or more antenna elements)) for a cell, a portion of a cell, or a positioning reference signal (PRS)-only TP. The TPs may include base station (eNB) antennas, remote radio heads (RRHs), remote antennas of base stations, antennas of PRS-only TPs, etc. A cell can be formed by one or more TPs. In the case of a homogeneous deployment, each TP may correspond to one cell.

[0089] In some embodiments, a set of TRPs is a set of geographically co-located antennas (e.g., antenna arrays (having one or more antenna elements)) that support TP and / or receiving point (RP) functionality.

[0090] It should be noted that this specification will focus on 3GPP cellular communication systems and therefore 3GPP terminology or terminology similar to 3GPP terminology will often be used, however the concepts disclosed herein are not limited to 3GPP systems.

[0091] In the description herein, reference may be made to the term "cell", however, it is important to note that, particularly with regard to 5G NR concepts, beams may be used instead of cells, and therefore the concepts described herein are equally applicable to both cells and beams.

[0092] For ease of discussion, this disclosure considers two TRPs, but it should be noted that the presented solution can be easily extended to more than two TRPs.

[0093] Assume that a UE is configured with two SRS resource sets with "usage" set to "non-codebook", and each of the SRS resource sets is associated with a TRP.

[0094] Note that the term TRP may not be part of the 3GPP standard specification. Instead, "SRS resource set", SRI field (one SRI field in the DCI corresponds to the TRP), or "TCI state" may be used as part of the standard.

[0095] FIG. 5 illustrates a method performed by a wireless device for non-codebook-based physical uplink shared channel (PUSCH) transmission in accordance with some embodiments of the present disclosure. The method includes one or more of the following: receiving a configuration of first or second uplink (UL) phase tracking reference signal (PT-RS) port indices for each sounding reference signal (SRS) resource among a plurality of SRS resources comprised of two SRS resource sets for a non-codebook-based PUSCH (step 500); receiving an indication of at least one of a first set of SRS resource indicators (SRIs) indicating SRS resources from the first SRS resource set and a second set of SRIs indicating SRS resources from the second SRS resource set (step 502); determining at least one of a first number of UL PT-RS ports to transmit on in accordance with the SRS resources indicated in the first set of SRIs and a second number of UL PT-RS ports to transmit on in accordance with the SRS resources indicated in the second set of SRIs (step 504); and transmitting the determined number of UL PT-RS ports with multiple PUSCH repetitions (step 506).

[0096] FIG. 6 illustrates a method performed by a base station for non-codebook-based PUSCH reception in accordance with some embodiments of the present disclosure. The method includes one or more of the following: transmitting a configuration of first or second uplink (UL) phase tracking reference signal (PT-RS) port indices for each sounding reference signal (SRS) resource among a plurality of SRS resources comprised of two SRS resource sets for a non-codebook-based PUSCH (step 600); transmitting an indication of at least one of a first set of SRS resource indicators (SRIs) indicating SRS resources from the first SRS resource set and a second set of SRIs indicating SRS resources from the second SRS resource set (step 602); determining at least one of a first number of UL PT-RS ports to be received according to the SRS resources indicated in the first set of SRIs and a second number of UL PT-RS ports to be received according to the SRS resources indicated in the second set of SRIs (step 604); and receiving the determined number of UL PT-RS ports with multiple PUSCH repetitions (step 606).

[0097] In some embodiments, two SRI fields in an UL DCI (e.g., a DCI scheduled in DCI format 0_1 ​​or DCI format 0_2) are used to indicate two sets of SRIs, one for each TRP, for PUSCH transmission to two TRPs. The SRI indicated in the first SRI field corresponds to the SRS resources in the first SRS resource set, and the SRI indicated in the second SRI field corresponds to the SRS resources in the second SRS resource set.

[0098] In some other embodiments, for configured grant PUSCH transmissions, two indicators indicating two sets of SRIs may be configured in the UE as part of the ConfiguredGrantConfig information element of the RRC configuration. For example, a first srs-ResourceIndicator in the ConfiguredGrantConfig corresponds to the SRS resource(s) in the first SRS resource set, and a second srs-ResourceIndicator in the ConfiguredGrantConfig corresponds to the SRS resource(s) in the second SRS resource set.

[0099] In one embodiment, the same number of PTRS ports may be configured for PUSCH transmission to a single TRP and for PUSCH transmission to multiple TRPs. In another embodiment, the number of PTRS ports may be configured separately for PUSCH transmission to a single TRP and for PUSCH transmission to multiple TRPs.

[0100] 7 is an explanatory diagram of PUSCH repetitions for two TRPs, with some PUSCH repetitions directed to TRP1 and other PUSCH repetitions directed to TRP2. The number of PUSCH layers and the number of UL PT-RS ports N1 transmitted for TRP1 are determined using a first SRI set indicated (e.g., using a first SRI field) corresponding to SRS resources indicated from a first SRS resource set with "usage" set to "non-codebook." The number of PUSCH layers and the number of UL PT-RS ports N2 transmitted for TRP2 are determined using a second SRI set indicated (e.g., using a second SRI field) corresponding to SRS resources indicated from a second SRS resource set with "usage" set to "non-codebook." How the numbers of UL PT-RS ports N1 and N2 are determined is covered by different embodiments given below. FIG. 7 is an illustration of PUSCH repetitions for two TRPs with UL PT-RS ports of N1 and N2 targeting TRPs 1 and 2, respectively.

[0101] Embodiment 1: The same number of UL PT-RS ports for different TRPs

[0102] Provide a block diagram showing the system / structure / node-level architecture / platform and explain the solution in detail with reference to the diagram. New structures / blocks are indicated by graphical emphasis and other indications in the text and diagram.

[0103] In one embodiment, the number of UL PT-RS ports corresponding to the PUSCH repetitions transmitted towards TRP1 is first determined based on a first set of SRIs indicated from a first SRS resource set with "usage" set to "non-codebook". · If the SRS resources indicated in the first set of SRIs from the first SRS resource set are all configured with the same PT-RS port index (e.g., either n0 or n1), a single UL PT-RS port N1=1 is determined for transmission towards TRP1. If the SRS resources indicated in the first set of SRIs from the first SRS resource set have different configured PT-RS port indices (e.g., some indicated SRS resources have PT-RS port index n0 while other indicated SRS resources have PT-RS port index n1), two UL PT-RS ports N1=2 are determined for transmission towards TRP1.

[0104] Once the number N1 of UL PT-RS ports for transmissions toward TRP1 is determined as above, the same number N2 of UL PT-RS ports (i.e., N2 = N1) is used for transmissions of PUSCH repetitions toward TRP2. This means that the SRS resources indicated in the second SRS resource set from the second SRS resource set with "usage" set to "non-codebook" must have the same number of UL PT-RS ports as N1. This embodiment can be captured in the 3GPP specifications as a rule that a UE expects the number of UL PT-RS ports associated with PUSCH repetitions corresponding to a first SRS resource set (e.g., a first TRP) to be the same as the number of UL PT-RS ports associated with PUSCH repetitions corresponding to a second SRS resource set (e.g., a second TRP).

[0105] If a single UE panel is used to transmit PUSCH layers toward both TRP1 and TRP2, a single UL PT-RS port is sufficient to transmit PUSCH layers toward both TRP1 and TRP2 (i.e., N1 = N2 = 1). If two UE panels are used to transmit PUSCH layers toward both TRP1 and TRP2, two UL PT-RS ports are required to repeat the PUSCH toward both TRP1 and TRP2 (i.e., N1 = N2 = 2).

[0106] A first example illustrating two UL PT-RS ports corresponding to PUSCH repetitions destined for both TRP1 and TRP2 is shown in FIG. 8 in accordance with some embodiments of the present disclosure. In this example, a first set of SRIs indicates to the UE that, for the PUSCH repetition destined for TRP1, the two PUSCH layers are transmitted using the same antenna ports as the SRS ports on resources 0 and 1 from SRS resource set 1. Because UL PT-RS ports n0 and n1 are configured on these two resources, the number of UL PT-RS ports transmitted toward TRP1 is determined to be two (i.e., N1=2). Next, a second set of SRIs indicates two SRS resources (0 and 2) from a second SRS resource set (i.e., N2=N1=2) such that the number of UL PT-RS ports configured on these two resources is also two. As shown in FIG. 8, UL PT-RS ports n0 and n1 are configured on the two SRS resources indicated by the second set of SRIs, and therefore UL PT-RS ports n0 and n1 are transmitted toward TRP2.

[0107] A second example illustrating two UL PT-RS ports corresponding to PUSCH repetitions destined for both TRP1 and TRP2 is shown in FIG. 9 in accordance with some embodiments of the present disclosure. In this example, a first set of SRIs indicates to the UE that, for the PUSCH repetition destined for TRP1, the two PUSCH layers are transmitted using the same antenna port as the SRS ports on resources 0 and 2 from SRS resource set 1. Because only UL PT-RS port n0 is configured on these two resources, the number of UL PT-RS ports transmitted toward TRP1 is determined to be 1 (i.e., N1=1). Next, a second set of SRIs indicates two SRS resources (0 and 2) from a second SRS resource set (i.e., N2=N1=2) such that the number of UL PT-RS ports configured on these two resources is also 1. As shown in FIG. 9, UL PT-RS port n0 is configured on the two SRS resources indicated by the second set of SRIs, and therefore, UL PT-RS port n0 is transmitted toward TRP2.

[0108] It should be noted that in this embodiment, even if the number of UL PT-RS ports transmitted toward TRP1 and TRP2 are the same, the exact UL PT-RS port indexes transmitted toward TRP1 and TRP2 may be different. Such an example is shown in Figure 10. In this example, the two SRS resources indicated by the first set of SRIs are configured with UL PT-RS port n0. Therefore, UL PT-RS port n0 is transmitted toward TRP1. However, the two SRS resources indicated by the second set of SRIs are configured with PT-RS port n1. Therefore, UL PT-RS port n1 is transmitted toward TRP2.

[0109] In this example, the first set of SRIs indicates to the UE that for the PUSCH repetitions toward TRP1, the two PUSCH layers are transmitted using the same antenna ports as the SRS ports of resources 0 and 2 from SRS resource set 1. Because only UL PT-RS port n0 is configured on these two resources, the number of UL PT-RS ports transmitted toward TRP1 is determined to be 1 (i.e., N1=1). Next, the second set of SRIs indicates two SRS resources (0 and 2) from the second SRS resource set (i.e., N2=N1=2) so that the number of UL PT-RS ports configured on these two resources is also 1. As shown in FIG. 9, the two SRS resources indicated by the second set of SRIs are configured with UL PT-RS port n0, and therefore, UL PT-RS port n0 is transmitted toward TRP2.

[0110] In another embodiment, when PUSCH repetitions for two TRPs are scheduled by the network (i.e., by configuring two SRS resource sets with use set to "nonCodebook" and indicating two SRS resource sets), only a single UL PT-RS port (e.g., the UL PT-RS port with index n0) is allowed to transmit toward both TRP1 and TRP2. This is beneficial when a UE transmits toward one TRP using only one panel, in which case it is sufficient for the UE to transmit one UL PT-RS port capable of performing phase tracking. One option is to configure the same UL PT-RS port index for all SRS resources in an SRS resource set, as shown in FIG. 11. As shown, UL PT-RS port index n0 is configured for all SRS resources in SRS resource set 1, and UL PT-RS port index n1 is configured for all SRS resources in SRS resource set 2. In this example, UL PT-RS port index n0 is transmitted toward TRP1, and UL PT-RS port index n1 is transmitted toward TRP2.

[0111] In an alternative embodiment, only UL PT-RS port index n0 is associated with all SRS resources configured in the two SRS resource sets. That is, UL PT-RS port index n0 is associated with all SRS resources in SRS resource set 1, and UL PT-RS port index n0 is associated with all SRS resources in SRS resource set 2. In this case, it is not necessary to explicitly configure UL PT-RS port index n0 for each SRS resource. Therefore, in this alternative embodiment, when PUSCH repetitions for two TRPs are scheduled by the network (i.e., by configuring two SRS resource sets with use set to "nonCodebook" and indicating two SRI sets), the UL PT-RS port index is not explicitly configured for each SRS resource, and the UE uses UL PT-RS port index n0 for TRP1 and TRP2. This alternative embodiment eliminates the need for an RRC parameter to configure the PT-RS port index for each SRS resource, thereby reducing configuration overhead.

[0112] In yet another embodiment, the UE independently determines the number of UL PT-RS ports for the two TRPs and transmits only the smaller of the two determined numbers of UL PT-RS ports. For example, consider the example of FIG. 12 in which the UE initially determines, based on the configured SRS resource set and the indicated first and second SRI sets, that the UL PT-RS ports associated with the first set of indicated SRIs are n0 and n1, and that the UL PT-RS port associated with the second set of indicated SRIs is n0. However, according to this embodiment, to ensure that the same number of UL PT-RS ports are transmitted toward TRP1 and TRP2, the UE drops n1 and transmits only UL PT-RS port n0 for the PUSCH transmission(s) associated with the first set of indicated SRIs. That is, the UE transmits UL PT-RS port n0 toward both TRP1 and TRP2.

[0113] Embodiment 2: Independent determination of the number of UL PT-RS ports for different TRPs

[0114] In this embodiment, the number of UL PT-RS ports corresponding to the PUSCH repetitions transmitted towards TRP1 is first determined based on a first set of SRIs indicated from a first SRS resource set with "usage" set to "non-codebook". · If the SRS resources indicated in the first set of SRIs from the first SRS resource set are all configured with the same PT-RS port index (e.g., either n0 or n1), a single UL PT-RS port N1=1 is determined for transmission towards TRP1. If the SRS resources indicated in the first set of SRIs from the first SRS resource set have different configured PT-RS port indices (e.g., some indicated SRS resources have PT-RS port index n0 while other indicated SRS resources have PT-RS port index n1), two UL PT-RS ports N1=2 are determined for transmission towards TRP1.

[0115] Once the number N1 of UL PT-RS ports for transmissions towards TRP1 is determined as above, the number N2 of UL PT-RS ports for transmissions of PUSCH repetitions towards TRP2 is determined based on the second SRI set indicated from the second SRS resource set with "usage" set to "non-codebook". · If the SRS resources indicated in the second SRI set from the second SRS resource set all configure the same PT-RS port index (e.g., either n0 or n1), a single UL PT-RS port N2=1 is determined for transmission towards TRP2. If the indicated SRS resources in the second set of SRIs from the second SRS resource set have different configured PT-RS port indices (e.g., some indicated SRS resources have PT-RS port index n0 while other indicated SRS resources have PT-RS port index n1), two UL PT-RS ports N2=2 are determined for transmission towards TRP2.

[0116] Note that in this embodiment, the numbers of UL PT-RS ports N1 (corresponding to TRP1) and N2 (corresponding to TRP2) are independently determined based on the indicated first set of SRIs and the indicated second set of SRIs, respectively. In some cases, the number N1 of UL PT-RS ports determined based on the indicated first set of SRIs may be different from the number N2 of UL PT-RS ports determined based on the indicated second set of SRIs. This embodiment is beneficial for a UE with multiple antenna panels, where the UE uses N1 panels to transmit PUSCHs toward the first TRP and N2 panels to transmit PUSCHs toward the second TRP, where N1 may be different from N2.

[0117] Consider the example of Figure 13. In this example, the first set of SRI indicates to the UE that for PUSCH repetitions toward TRP1, two PUSCH layers are transmitted using the same antenna ports as the SRS ports of resources 0 and 1 from SRS resource set 1. Because these two resources are configured with UL PT-RS ports n0 and n1, the number of UL PT-RS ports transmitted toward TRP1 is determined to be two (i.e., N1 = 2). The second set of SRI indicates two SRS resources (0 and 1) from the second SRS resource set, both of which are configured with UL PT-RS port n0. Therefore, the number of UL PT-RS ports transmitted toward TRP2 is determined to be one (i.e., N2 = 1). After determining the numbers of UL PT-RS ports N1 and N2, the UE transmits some of the PUSCH repetitions toward TRP1 with N1 UL PT-RS ports and transmits other PUSCH repetitions toward TRP2 with N2 UL PT-RS ports.

[0118] Embodiment 3: Determining the number of UL PT-RS ports when dynamically switching between PUSCH repetition for single TRP and PUSCH repetition for multi-TRP

[0119] In this embodiment, the UE may be indicated with two SRI fields in the DCI, and when scheduling a PUSCH repetition transmission, only one of the SRI fields in the DCI is enabled, while the second SRI field in the DCI is disabled. This case corresponds to a PUSCH repetition for a single TRP. That is, the PUSCH repetition is transmitted using the SRS resources of one SRS resource set corresponding to the enabled SRI field. Note that in this case, the UE remains configured with two SRS resource sets with "usage" set to "non-codebook," with two SRI fields in the DCI corresponding to the two SRS resource sets. This configuration can be used to dynamically switch between single-TRP PUSCH transmission and multi-TRP PUSCH transmission. To schedule PUSCH repetitions only toward TRP1, the UE may indicate SRS resources from the first SRS resource set via the first SRI field in the DCI. The second SRI field is disabled (e.g., the second SRI field does not indicate any SRS resources and may point to a reserved codepoint). The UE determines the number of UL PT-RS ports, N1, from the set of SRIs indicated by the first SRI field of the DCI. The UE then transmits all PUSCH repetitions with N1 UL PT-RS ports toward TRP1. If the indicated SRS resources are associated with the same UL PT-RS port, a single UL PT-RS port is transmitted (i.e., N1 = 1). Otherwise, if the indicated SRS resources are associated with two UL PT-RS ports, two UL PT-RS ports are transmitted (i.e., N1 = 2). To schedule PUSCH repetitions only toward TRP2, the UE may indicate SRS resources from a second SRS resource set via the second SRI field in the DCI. The first SRI field is disabled (e.g., the first SRI field does not indicate an SRS resource and may point to a reserved codepoint). The UE determines the number of UL PT-RS ports, N2, from the set of SRIs indicated by the second SRI field of the DCI. The UE then transmits all PUSCH repetitions with N2 UL PT-RS ports toward TRP2. If the indicated SRS resources are associated with the same UL PT-RS port, a single UL PT-RS port is transmitted (i.e., N2 = 1). Otherwise, if the indicated SRS resources are associated with two UL PT-RS ports, two UL PT-RS ports are transmitted (i.e., N2 = 2). · Scheduling of PUSCH repetitions for both TRP1 and TRP2 is achieved according to the embodiments described in embodiments 1 and 2.

[0120] FIG. 14 is a schematic block diagram of a radio access node 1400 according to some embodiments of the present disclosure. Optional functionality is represented by dashed boxes. The radio access node 1400 may be, for example, a base station 402 or 406, or a network node that implements all or a portion of the functionality of the base station 402 or gNB described herein. As shown, the radio access node 1400 includes a control system 1402 including one or more processors 1404 (e.g., a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and / or the like), a memory 1406, and a network interface 1408. The one or more processors 1404 are also referred to herein as processing circuits. Additionally, the radio access node 1400 may include one or more radio units 1410, each including one or more transmitters 1412 and one or more receivers 1414 coupled to one or more antennas 1416. The radio unit 1410 may refer to or be part of air interface circuitry. In some embodiments, the wireless unit(s) 1410 are external to the control system 1402 and are connected to the control system 1402, for example, via a wired connection (e.g., an optical cable). However, in some other embodiments, the wireless unit(s) 1410 and potentially the antenna(s) 1416 are integrated with the control system 1402. The one or more processors 1404 operate to provide one or more functions of the wireless access node 1400 described herein. In some embodiments, the function(s) are implemented in software that is stored, for example, in the memory 1406 and executed by the one or more processors 1404.

[0121] 15 is a schematic block diagram illustrating a virtualized embodiment of a radio access node 1400 in accordance with some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Furthermore, other types of network nodes may have similar virtualization architectures. Again, optional functionality is represented by dashed boxes.

[0122] As used herein, a “virtualized” radio access node is an implementation of the radio access node 1400 in which at least a portion of the functionality of the radio access node 1400 is implemented as virtual component(s) (e.g., via virtual machine(s) running on physical processing node(s) in network(s)). As shown, in this example, the radio access node 1400 may include a control system 1402 and / or one or more radio units 1410, as described above. The control system 1402 may be connected to the radio unit(s) 1410 via, for example, optical cables. The radio access node 1400 includes one or more processing nodes 1500 coupled to or included as part of a network(s) 1502. If present, the control system 1402 or radio units are connected to the processing nodes 1500 via the network 1502. Each processing node 1500 includes one or more processors 1504 (e.g., CPUs, ASICs, FPGAs, etc.), memory 1506, and a network interface 1508.

[0123] In this example, the functionality 1510 of the radio access node 1400 described herein is implemented in one or more processing nodes 1500, or distributed in any desired manner between one or more processing nodes 1500 and the control system 1402 and / or radio unit(s) 1410. In some particular embodiments, some or all of the functionality 1510 of the radio access node 1400 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment hosted by the processing node 1500. As will be appreciated by those skilled in the art, additional signaling or communication between the processing node 1500 and the control system 1402 is used to perform at least some of the desired functionality 1510. Of note, in some embodiments, a control system 1402 may not be included, in which case the radio unit 1410 communicates directly with the processing node 1500 via an appropriate network interface.

[0124] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform the functionality of the radio access node 1400 or the functionality of a node (e.g., processing node 1500) that implements one or more of the functionality 1510 of the radio access node 1400 in a virtual environment in accordance with any of the embodiments described herein. In some embodiments, a carrier is provided that includes the aforementioned computer program product. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0125] 16 is a schematic block diagram of a radio access node 1400 in accordance with some other embodiments of the present disclosure. The radio access node 1400 includes one or more modules 1600, each implemented in software. The modules 1600 provide the functionality of the radio access node 1400 described herein. This discussion is equally applicable to the processing node 1500 of FIG. 15, where the modules 1600 may be implemented on one of the processing nodes 1500 or may be distributed across multiple processing nodes 1500 and / or may be distributed across the processing nodes 1500 and the control system 1402.

[0126] 17 is a schematic block diagram of a wireless communication device 1700 according to some embodiments of the present disclosure. As shown, the wireless communication device 1700 includes one or more processors 1702 (e.g., CPUs, ASICs, FPGAs, and / or the like), a memory 1704, and one or more transceivers 1706, each including one or more transmitters 1708 and one or more receivers 1710 coupled to one or more antennas 1712. The transceiver(s) 1706 include radio front-end circuitry connected to the antenna(s) 1712 configured to condition signals communicated between the antenna(s) 1712 and the processor(s) 1702, as will be understood by those skilled in the art. The processor 1702 is also referred to herein as a processing circuit. The transceiver 1706 is also referred to herein as a radio circuit. In some embodiments, the functionality of the wireless communication device 1700 described above may be implemented, fully or partially, in software, for example, stored in the memory 1704 and executed by the processor(s) 1702. It should be noted that the wireless communication device 1700 may include additional components not shown in FIG. 17 , such as, for example, one or more user interface components (e.g., an input / output interface including a display, buttons, a touchscreen, a microphone, a speaker(s), and / or any other components for enabling the input of information into the wireless communication device 1700 and / or the output of information from the wireless communication device 1700), a power source (e.g., a battery and associated power circuitry), etc.

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

[0128] 18 is a schematic block diagram of a wireless communication device 1700 according to some other embodiments of the present disclosure. The wireless communication device 1700 includes one or more modules 1800, each implemented in software. The modules 1800 provide the functionality of the wireless communication device 1700 described herein.

[0129] 19 , according to an embodiment, a communications system includes a telecommunications network 1900, such as a 3GPP-type cellular network, comprised of an access network 1902, such as a RAN, and a core network 1904. The access network 1902 is comprised of multiple base stations 1906A, 1906B, 1906C, such as Node Bs, eNBs, gNBs, or other types of wireless access points (APs), each defining a corresponding coverage area 1908A, 1908B, 1908C. Each base station 1906A, 1906B, 1906C can be connected to the core network 1904 via a wired or wireless connection 1910. A first UE 1912 located in the coverage area 1908C is configured to wirelessly connect to or be paged by the corresponding base station 1906C. A second UE 1914 located in the coverage area 1908A can wirelessly connect to the corresponding base station 1906A. Although multiple UEs 1912, 1914 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is within the coverage area or where only one UE connects to the corresponding base station 1906.

[0130] The telecommunications network 1900 is itself connected to a host computer 1916, which may be embodied in hardware and / or software as a standalone server, a cloud-implemented server, a distributed server, or a processing resource within a server farm. The host computer 1916 may be under the ownership or control of a service provider and may be operated by or on behalf of the service provider. Connections 1918 and 1920 between the telecommunications network 1900 and the host computer 1916 may extend directly from the core network 1904 to the host computer 1916 or may go through an optional intermediate network 1922. The intermediate network 1922 may be one or a combination of two or more of a public, private, or hosted network; the intermediate network 1922, if any, may be a backbone network or the Internet; in particular, the intermediate network 1922 may be comprised of two or more subnetworks (not shown).

[0131] The communication system of FIG. 19 as a whole enables connectivity between connected UEs 1912, 1914 and a host computer 1916. This connectivity can be described as an over-the-top (OTT) connection 1924. The host computer 1916 and connected UEs 1912, 1914 are configured to communicate data and / or signaling via the OTT connection 1924 using the access network 1902, the core network 1904, any intermediate networks 1922, and possible further infrastructure (not shown) as intermediaries. The OTT connection 1924 can be transparent in the sense that participating communication devices through which the OTT connection 1924 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 1906 may not, and need not, be informed about the past routing of incoming downlink communications having data originating from the host computer 1916 that is forwarded (e.g., handed off) to the connected UE 1912. Similarly, base station 1906 does not need to be aware of the future routing of outgoing uplink communications originating from UE 1912 towards host computer 1916 .

[0132] An exemplary implementation of the UE, base station, and host computer described in the previous paragraph according to an embodiment will now be described with reference to FIG. 20. In communication system 2000, host computer 2002 comprises hardware 2004 including communication interface 2006 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of communication system 2000. Host computer 2002 further comprises processing circuitry 2008, which may have memory and / or processing capabilities. In particular, processing circuitry 2008 may be comprised of one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. Host computer 2002 further comprises software 2010 stored on or accessible by host computer 2002 and executable by processing circuitry 2008. Software 2010 includes host application 2012. The host application 2012 may be operable to provide services to a remote user, such as the UE 2014, connecting via an OTT connection 2016 that terminates at the UE 2014 and the host computer 2002. In providing services to the remote user, the host application 2012 may provide user data that is transmitted using the OTT connection 2016.

[0133] The communications system 2000 further includes a base station 2018 provided in the telecommunications system and comprising hardware 2020 that enables communication with the host computer 2002 and communication with the UE 2014. The hardware 2020 may include a communications interface 2022 for setting up and maintaining wired or wireless connections with interfaces of different communications devices of the communications system 2000, as well as a wireless interface 2024 for setting up and maintaining at least a wireless connection 2026 with a UE 2014 located within a coverage area (not shown in FIG. 20) provided by the base station 2018. The communications interface 2022 may be configured to facilitate a connection 2028 to the host computer 2002. The connection 2028 may be direct, may pass through a core network of the telecommunications system (not shown in FIG. 20), and / or may pass through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 2020 of the base station 2018 further includes processing circuitry 2030, which may be comprised of one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The base station 2018 further has software 2032 stored therein or accessible via an external connection.

[0134] The communications system 2000 further includes the previously mentioned UE 2014. The hardware 2034 of the UE 2014 may include a wireless interface 2036 configured to establish and maintain a wireless connection 2026 with a base station serving the coverage area in which the UE 2014 is currently located. The hardware 2034 of the UE 2014 further includes processing circuitry 2038, which may be comprised of one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The UE 2014 further includes software 2040, which is stored on or accessible by the UE 2014 and executable by the processing circuitry 2038. The software 2040 includes a client application 2042. The client application 2042, with support from the host computer 2002, may be operable to provide services to a human or non-human user via the UE 2014. In the host computer 2002, an executing host application 2012 can communicate with an executing client application 2042 via the UE 2014 and an OTT connection 2016 that terminates at the host computer 2002. In providing a service to a user, the client application 2042 may receive request data from the host application 2012 and provide user data in response to the request data. The OTT connection 2016 may transfer both the request data and the user data. The client application 2042 may interact with the user to generate the user data to provide.

[0135] It should be noted that the host computer 2002, base station 2018, and UE 2014 illustrated in Figure 20 may be similar to or identical to the host computer 1916, one of the base stations 1906A, 1906B, and 1906C, and one of the UEs 1912 and 1914, respectively, of Figure 19. That is, the internal operation of these entities may be as in Figure 20, and independently, the surrounding network topology may be as in Figure 19.

[0136] 20, the OTT connection 2016 is depicted abstractly to illustrate communication between the host computer 2002 and the UE 2014 via the base station 2018, without explicitly referring to any intermediary devices and the exact routing of messages through these devices. The network infrastructure may determine the routing, which may be configured to be hidden from the UE 2014, or from the service provider operating the host computer 2002, or both. While the OTT connection 2016 is active, the network infrastructure may further determine to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0137] The wireless connection 2026 between the UE 2014 and the base station 2018 follows the teachings of embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 2014 using the OTT connection 2016 of which the wireless connection 2026 forms the final segment. More precisely, the teachings of these embodiments may improve, for example, data rates, latency, power consumption, etc., thereby providing benefits such as, for example, reduced user latency, relaxed file size limitations, improved responsiveness, and extended battery life.

[0138] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve. There may also be optional network functionality for reconfiguring the OTT connection 2016 between the host computer 2002 and the UE 2014 in response to fluctuations in the measurement results. The measurement procedures and / or the network functionality for reconfiguring the OTT connection 2016 may be implemented in the software 2010 and hardware 2004 of the host computer 2002, or in the software 2040 and hardware 2034 of the UE 2014, or both. In some embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 2016 passes, and the sensors may participate in the measurement procedures by supplying values ​​of the monitored quantities exemplified above, or by supplying values ​​of other physical quantities from which the software 2010, 2040 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 2016 may include message formats, retransmission settings, priority routing, etc., and the reconfiguration need not affect the base station 2018 and may be unknown or imperceptible to the base station 2018. Such procedures and functionality are known in the art and may be implemented. In particular embodiments, measurements may include proprietary UE signaling that facilitates the host computer 2002 measurements of throughput, propagation time, latency, etc. Measurements may be implemented by having the OTT connection 2016 send messages, particularly empty or "dummy" messages, while the software 2010 and 2040 monitors propagation times, errors, etc.

[0139] FIG. 21 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIGS. 19 and 20. To simplify this disclosure, only a drawing reference to FIG. 21 is included in this section. In step 2100, the host computer provides user data. In sub-step 2102 of step 2100 (which may be optional), the host computer provides the user data by executing a host application. In step 2104, the host computer initiates a transmission to transmit the user data to the UE. In step 2106 (which may be optional), the base station transmits the user data carried in the host computer-initiated transmission to the UE, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2108 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0140] FIG. 22 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIGS. 19 and 20. To simplify this disclosure, only a drawing reference to FIG. 22 is included in this section. In step 2200 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 2202, the host computer initiates a transmission to send the user data to the UE. This transmission may be via a base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2204, which may be optional, the UE receives the user data carried in the transmission.

[0141] FIG. 23 is a flowchart illustrating a method implemented in a communications system according to one embodiment. The communications system includes a host computer, a base station, and a UE, which may be as described with reference to FIGS. 19 and 20. To simplify this disclosure, only drawing references to FIG. 23 are included in this section. In step 2300 (which may be optional), the UE receives input data provided by the host computer. Additionally, or alternatively, in step 2302, the UE provides user data. In sub-step 2304 of step 2300 (which may be optional), the UE provides the user data by executing a client application. In sub-step 2306 of step 2302 (which may be optional), the UE executes the client application, which provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the specific manner in which the user data is provided, the UE begins transmitting the user data to the host computer in sub-step 2308 (which may be optional). In step 2310 of the method, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0142]

[0013] Figure 24 is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to Figures 19 and 20. To simplify this disclosure, only drawing references to Figure 24 are included in this section. In step 2400 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 2402 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 2404 (which may be optional), the host computer receives the user data carried in a transmission initiated by the base station.

[0143] Pertinent steps, methods, features, functions, or advantages disclosed herein may be performed through one or more functional units or modules of one or more virtual devices. Each virtual device may be composed of a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware including digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for implementing one or more telecommunications and / or data communication protocols, as well as instructions for executing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a function corresponding to the respective functional unit in accordance with one or more embodiments of the present disclosure.

[0144] While the steps in the figures may indicate a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, or overlap certain operations).

[0145] Embodiment

[0146] Group A Embodiments

[0147]

[0023] Embodiment 1: A method performed by a wireless device (1700) for non-codebook-based Physical Uplink Shared Channel (PUSCH) transmission, the method comprising: receiving (500) a configuration of first or second uplink (UL) phase tracking reference signal (PT-RS) port indexes for each SRS resource among a plurality of SRS resources comprised of two SRS resource sets for the non-codebook-based PUSCH; and receiving a first set of SRS resource indicators (SRIs) indicating SRS resources from the first SRS resource set. and a second set of SRIs indicating SRS resources from a second SRS resource set (502); determining at least one of a first number of UL PT-RS ports to transmit in accordance with the SRS resources indicated in the first set of SRIs and a second number of UL PT-RS ports to transmit in accordance with the SRS resources indicated in the second set of SRIs (504); and transmitting the determined number of UL PT-RS ports with multiple PUSCH repetitions (506).

[0148] Embodiment 2: The method of embodiment 1, wherein a first subset of PUSCH repetitions of the plurality of PUSCH repetitions are transmitted according to SRS resources indicated in a first set of SRIs, and the first subset of PUSCH repetitions includes transmissions of the first number of UL PT-RS ports.

[0149] Embodiment 3: The method of embodiment 1, wherein a second subset of PUSCH repetitions separated from a first subset of PUSCH repetitions of the plurality of PUSCH repetitions are transmitted according to SRS resources indicated in a second set of SRIs, and the second subset of PUSCH repetitions includes transmission of the second number of UL PT-RS ports.

[0150] Embodiment 4: The method of embodiment 1, wherein all of the plurality of PUSCH repetitions are transmitted according to SRS resources indicated in a first set of the SRI, and the plurality of PUSCH repetitions include transmissions of the first number of UL PT-RS ports.

[0151] Embodiment 5: The method of embodiment 1, wherein all of the plurality of PUSCH repetitions are transmitted according to SRS resources indicated in a second set of the SRI, and the plurality of PUSCH repetitions include transmissions of the second number of UL PT-RS ports.

[0152] Embodiment 6: The method according to any one of embodiments 1 to 3, wherein the first number of UL PT-RS ports is the same as the second number of UL PT-RS ports.

[0153] Embodiment 7: The method according to any one of embodiments 1 to 3, wherein the first number of UL PT-RS ports is different from the second number of UL PT-RS ports.

[0154] Embodiment 8: A method according to any one of embodiments 1 to 7, wherein the first number of UL PT-RS ports is determined to be 1 if the SRS resources indicated in the first set of SRIs are all configured with the same PT-RS port index.

[0155] Embodiment 9: A method as described in any of embodiments 1 to 7, wherein the second number of UL PT-RS ports is determined to be 1 if the SRS resources indicated in the second set of SRIs are all configured with the same PT-RS port index.

[0156] Embodiment 10: A method according to any one of embodiments 1 to 7, wherein the first number of UL PT-RS ports is determined to be two if the SRS resources indicated in the first set of SRIs are configured with two different PT-RS port index values.

[0157] Embodiment 11: A method as described in any of embodiments 1 to 7, wherein the second number of UL PT-RS ports is determined to be 2 when the SRS resources indicated in the second set of SRIs are configured with two different PT-RS port index values.

[0158] Embodiment 12: A method according to any one of embodiments 1 to 11, wherein the first set of SRIs and the second set of SRIs are indicated via a first SRI field and a second SRI field, respectively, in a downlink control indicator (DCI) that schedules the PUSCH repetition.

[0159] Embodiment 13: A method according to any one of embodiments 1 to 11, wherein the first set of SRIs and the second set of SRIs are indicated via a first index and a second index, respectively, configured as part of a configured grant PUSCH configuration.

[0160] Embodiment 14: The method according to any one of embodiments 1 to 13, wherein the first SRS resource set corresponds to a first transmission / reception point (TRP), and the second SRS resource set corresponds to a second TRP.

[0161] Embodiment 15: The method of any preceding embodiment, further comprising providing user data and transferring the user data to the host computer via transmission to a base station.

[0162] Group B Embodiments

[0163]

[0023] Embodiment 16: A method performed by a base station (1400) for receiving a non-codebook-based physical uplink shared channel (PUSCH), the method comprising: transmitting (600) a configuration of a first or second uplink (UL) phase tracking reference signal (PT-RS) port index for each SRS resource among a plurality of sounding reference signal (SRS) resources configured in two SRS resource sets for the non-codebook-based PUSCH; and transmitting (600) a first section of an SRS resource indicator (SRI) indicating an SRS resource from the first SRS resource set. and a second set of SRIs indicating SRS resources from a second SRS resource set (602); determining at least one of a first number of UL PT-RS ports to be received according to the SRS resources indicated in the first set of SRIs and a second number of UL PT-RS ports to be received according to the SRS resources indicated in the second set of SRIs (604); and receiving the determined number of UL PT-RS ports with multiple PUSCH repetitions (606).

[0164] Embodiment 17: The method of embodiment 16, wherein a first subset of PUSCH repetitions is received according to SRS resources indicated in a first set of the SRI, and the first subset of PUSCH repetitions includes reception of the first number of UL PT-RS ports.

[0165] Embodiment 18: The method of embodiment 16, wherein a second subset of PUSCH repetitions separated from a first subset of PUSCH repetitions is received according to SRS resources indicated in a second set of the SRI, and the second subset of PUSCH repetitions includes reception of the second number of UL PT-RS ports.

[0166] Embodiment 19: The method of embodiment 16, wherein all of the plurality of PUSCH repetitions are received according to SRS resources indicated in a first set of the SRI, and the plurality of PUSCH repetitions include reception of the first number of UL PT-RS ports.

[0167] Embodiment 20: The method of embodiment 16, wherein all of the plurality of PUSCH repetitions are received according to SRS resources indicated in a second set of the SRI, and the plurality of PUSCH repetitions include reception of the second number of UL PT-RS ports.

[0168] Embodiment 21: The method of any one of embodiments 16 to 18, wherein the first number of UL PT-RS ports is the same as the second number of UL PT-RS ports.

[0169] Embodiment 22: The method of any one of embodiments 16 to 18, wherein the first number of UL PT-RS ports is different from the second number of UL PT-RS ports.

[0170] Embodiment 23: A method according to any one of embodiments 16 to 22, wherein the first number of UL PT-RS ports is determined to be 1 if the SRS resources indicated in the first set of SRIs are all configured with the same PT-RS port index.

[0171] Embodiment 24: A method according to any one of embodiments 16 to 22, wherein the second number of UL PT-RS ports is determined to be two if the SRS resources indicated in the second set of SRIs are configured with two different PT-RS port index values.

[0172] Embodiment 25: A method according to any one of embodiments 16 to 24, wherein the first set of SRIs and the second set of SRIs are indicated via a first SRI field and a second SRI field, respectively, in a downlink control indicator (DCI) that schedules the PUSCH repetition.

[0173] Embodiment 26: A method according to any one of embodiments 16 to 24, wherein the first set of SRIs and the second set of SRIs are indicated via a first index and a second index, respectively, configured as part of a configured grant PUSCH configuration.

[0174] Embodiment 27: The method of any one of embodiments 16 to 26, wherein the first SRS resource set corresponds to a first transmission / reception point (TRP), and the second SRS resource set corresponds to a second TRP.

[0175] Embodiment 28: The method of any preceding embodiment, further comprising obtaining user data and transferring the user data to a host computer or a wireless device.

[0176] Group C Embodiments

[0177] Embodiment 29: A wireless device for non-codebook-based physical uplink shared channel (PUSCH) transmission, comprising: a processing circuit configured to perform the steps of any of the embodiments of group A; and a power supply circuit configured to supply power to the wireless device.

[0178] Embodiment 30: A base station for non-codebook-based physical uplink shared channel (PUSCH) reception, comprising: a processing circuit configured to perform the steps of any of the embodiments of Group B; and a power supply circuit configured to supply power to the base station.

[0179] Embodiment 31: A user equipment (UE) for non-codebook-based physical uplink shared channel (PUSCH) transmission, comprising: an antenna configured to transmit and receive radio signals; and a radio front-end circuit connected to the antenna and a processing circuit and configured to condition signals communicated between the antenna and the processing circuit, the processing circuit being configured to perform any of the steps of the embodiments of Group A; an input interface connected to the processing circuit and configured to enable input of information to the UE to be processed by the processing circuit; an output interface connected to the processing circuit and configured to output information from the UE that has been processed by the processing circuit; and a battery connected to the processing circuit and configured to provide power to the UE.

[0180] Embodiment 32: A communication system including a host computer having a processing circuit configured to provide user data and a communication interface configured to transfer the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network includes a base station having a radio interface and a processing circuit, and the processing circuit of the base station is configured to perform the steps of any of the embodiments of Group B.

[0181] Embodiment 33: The communication system of the preceding embodiment, further comprising a base station.

[0182] Embodiment 34: The communication system according to the preceding two embodiments, further including a UE, wherein the UE is configured to communicate with the base station.

[0183] Embodiment 35: A communication system as described in the preceding three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, thereby providing user data, and the UE comprises processing circuitry configured to execute a client application associated with the host application.

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

[0185] Embodiment 37: The method according to any preceding embodiment, further comprising, in the base station, transmitting user data.

[0186] Embodiment 38: The method described in the preceding two embodiments, wherein the user data is provided in the host computer by executing a host application, and the method further includes executing, in the UE, a client application associated with the host application.

[0187] Embodiment 39: A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and a processing circuit configured to perform the methods of the previous three embodiments.

[0188] Embodiment 40: A communication system including a host computer having a processing circuit configured to provide user data and a communication interface configured to transfer the user data to a cellular network for transmission to a user equipment (UE), the UE having a radio interface and a processing circuit, and the components of the UE configured to perform the steps of any of the embodiments of Group A.

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

[0190] Embodiment 42: A communication system as described in the preceding two embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, thereby providing user data, and the processing circuitry of the UE is configured to execute a client application associated with the host application.

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

[0192] Embodiment 44: The method according to any preceding embodiment, further comprising receiving, in the UE, user data from a base station.

[0193] Embodiment 45: A communications system including a host computer having a communications interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station; wherein the UE has a radio interface and processing circuitry, and the processing circuitry of the UE is configured to perform the steps of any of the embodiments of Group A.

[0194] Embodiment 46: The communication system described in the preceding embodiment, further including a UE.

[0195] Embodiment 47: The communication system described in the preceding two embodiments, further including a base station, the base station having a radio interface configured to communicate with the UE and a communication interface configured to transfer user data carried by transmissions from the UE to the base station to a host computer.

[0196] Embodiment 48: A communication system as described in the preceding three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, and the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0197] Embodiment 49: A communication system as described in the preceding four embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, thereby providing the requested data, and the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing user data in response to the requested data.

[0198] Embodiment 50: A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), comprising: receiving, at the host computer, user data transmitted from the UE to the base station, wherein the UE performs the steps of any of the embodiments of Group A.

[0199] Embodiment 51: The method according to any preceding embodiment, further comprising, in the UE, providing user data to the base station.

[0200] Embodiment 52: The method described in the preceding two embodiments, further including: executing, in the UE, a client application thereby providing user data to be transmitted; and executing, in the host computer, a host application associated with the client application.

[0201] Embodiment 53: The method described in the preceding three embodiments, further including the steps of: executing a client application in the UE; and receiving input data for the client application in the UE, the input data being provided on a host computer by executing a host application associated with the client application; and the user data to be transmitted being provided by the client application in response to the input data.

[0202] Embodiment 54: A communications system including a host computer including a communications interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, the base station including a radio interface and processing circuitry, the processing circuitry of the base station configured to perform the steps of any of the Group B embodiments.

[0203] Embodiment 55: The communication system described in the preceding embodiment, further including a base station.

[0204] Embodiment 56: The communication system according to the preceding two embodiments, further including a UE, wherein the UE is configured to communicate with the base station.

[0205] Embodiment 57: A communication system as described in the preceding three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, and the UE is configured to execute a client application associated with the host application, thereby providing user data received by the host computer.

[0206] Embodiment 58: A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), comprising: receiving, in the host computer, from the base station, user data derived from a transmission received by the base station from the UE; and the UE performing any of the steps of the embodiments of Group A.

[0207] Embodiment 59: The method according to any preceding embodiment, further comprising receiving, at the base station, user data from the UE.

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

[0209] In this disclosure, at least some of the following abbreviations may be used. In case of conflict between abbreviations, the above usage shall prevail. If multiple occurrences below occur, the first occurrence shall prevail over subsequent occurrences. 3GPP 3rd Generation Partnership Project 5G (fifth generation) 5GC 5th generation core 5GS 5th Generation System AF application function AMF access and mobility features ·AN Access Network AP access point ASIC Application Specific Integrated Circuit AUSF authentication server function CPU Central Processing Unit ·DN Data Network DSP Digital Signal Processor eNB Enhanced or evolved Node B EPS Evolutionary Packet System E-UTRA Evolved Universal Terrestrial Radio Access FPGA Field Programmable Gate Array gNB new radio base station gNB-DUN New Radio Base Station Distributed Unit HSS Home Subscriber Server IoT Internet of Things IP Internet Protocol LTE Long Term Evolution MME Mobility Management Entity MTC Machine Type Communication NEF Network Exposure Function NF network function ·NR New Radio NRF Network Function Repository Function NSSF network slice selection function OTT (Over-the-Top) PC Personal Computer PCF policy control function P-GW Packet Data Network Gateway QoS Quality of Service RAM Random Access Memory RAN Radio Access Network ROM (Read-Only Memory) RRH Remote Radio Head RTT (round trip time) SCEF Service Capability Exposure Function SMF session management function ·UDM Unified Data Management UE User Equipment UPF User Plane Function

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

Claims

1. 17. A method performed by a wireless device (1700) for non-codebook-based physical uplink shared channel (PUSCH) transmission, the method comprising: receiving 500 a configuration of a first or second uplink (UL) phase tracking reference signal (PT-RS) port index for each sounding reference signal (SRS) resource among a plurality of SRS resources comprising two SRS resource sets for a non-codebook-based PUSCH; receiving (502) an indication of a first set of SRS resource indicators (SRIs) indicating SRS resources from a first SRS resource set and a second set of SRIs indicating SRS resources from a second SRS resource set; determining a first number of UL PT-RS ports to be used for PUSCH transmission according to the SRS resources indicated in the first set of SRIs, and determining a second number of UL PT-RS ports to be used for PUSCH transmission according to the SRS resources indicated in the second set of SRIs (504); transmitting a plurality of PUSCH repetitions using the determined first number of UL PT-RS ports and the determined second number of UL PT-RS ports (506); A method comprising:

2. A first subset of PUSCH repetitions of the plurality of PUSCH repetitions are transmitted according to SRS resources indicated in a first set of SRIs, the first subset of PUSCH repetitions including transmissions for the first number of UL PT-RS ports. The method of claim 1.

3. A second subset of PUSCH repetitions separate from the first subset of PUSCH repetitions of the plurality of PUSCH repetitions are transmitted according to SRS resources indicated in a second set of SRIs, the second subset of PUSCH repetitions including transmissions on the second number of UL PT-RS ports. The method of claim 1.

4. The first number of UL PT-RS ports is the same as the second number of UL PT-RS ports. The method of claim 1.

5. The first number of UL PT-RS ports is different from the second number of UL PT-RS ports. The method of claim 1.

6. The first number of UL PT-RS ports is determined to be 1 if the SRS resources indicated in the first set of SRIs are all configured with the same PT-RS port index. The method of claim 1.

7. The second number of UL PT-RS ports is determined to be 1 if the SRS resources indicated in the second set of SRIs are all configured with the same PT-RS port index. The method of claim 1.

8. The first number of UL PT-RS ports is determined to be 2 if the SRS resources indicated in the first set of SRIs are configured with two different PT-RS port index values. The method of claim 1.

9. The second number of UL PT-RS ports is determined to be 2 if the SRS resources indicated in the second set of SRIs are configured with two different PT-RS port index values. The method of claim 1.

10. The first set of SRIs and the second set of SRIs are indicated via a first SRI field and a second SRI field, respectively, in a downlink control indicator (DCI) that schedules the PUSCH repetition. The method of claim 1.

11. The first set of SRIs and the second set of SRIs are indicated via a first index and a second index, respectively, configured as part of a configured grant PUSCH configuration. The method of claim 1.

12. The first SRS resource set corresponds to a first transmission / reception point (TRP), and the second SRS resource set corresponds to a second TRP. The method of claim 1.

13. The wireless device (1700) operates within a fifth generation (5G) New Radio (NR) network. The method of claim 1.

14. 1. A method performed by a base station (1400) for non-codebook-based physical uplink shared channel (PUSCH) reception, the method comprising: transmitting (600) a configuration of a first or second uplink (UL) phase tracking reference signal (PT-RS) port index for each sounding reference signal (SRS) resource among a plurality of SRS resources comprising two SRS resource sets for a non-codebook-based PUSCH; transmitting (602) an indication of a first set of SRS resource indicators (SRIs) indicating SRS resources from a first SRS resource set and a second set of SRIs indicating SRS resources from a second SRS resource set; determining a first number of UL PT-RS ports to be used for PUSCH reception according to the SRS resources indicated in the first set of SRIs, and determining a second number of UL PT-RS ports to be used for PUSCH reception according to the SRS resources indicated in the second set of SRIs (604); receiving a plurality of PUSCH repetitions using the determined first number of UL PT-RS ports and the determined second number of UL PT-RS ports (606); A method comprising:

15. A first subset of PUSCH repetitions of the plurality of PUSCH repetitions are received according to SRS resources indicated in a first set of SRIs, the first subset of PUSCH repetitions including reception on the first number of UL PT-RS ports.

15. The method of claim 14.

16. A second subset of PUSCH repetitions separate from the first subset of PUSCH repetitions of the plurality of PUSCH repetitions are received according to SRS resources indicated in a second set of SRIs, the second subset of PUSCH repetitions including reception on the second number of UL PT-RS ports.

15. The method of claim 14.

17. The first number of UL PT-RS ports is the same as the second number of UL PT-RS ports.

15. The method of claim 14.

18. The first number of UL PT-RS ports is different from the second number of UL PT-RS ports.

15. The method of claim 14.

19. The first number of UL PT-RS ports is determined to be 1 if the SRS resources indicated in the first set of SRIs are all configured with the same PT-RS port index.

15. The method of claim 14.

20. The second number of UL PT-RS ports is determined to be 2 if the SRS resources indicated in the second set of SRIs are configured with two different PT-RS port index values.

15. The method of claim 14.

21. The first set of SRIs and the second set of SRIs are indicated via a first SRI field and a second SRI field, respectively, in a downlink control indicator (DCI) that schedules the PUSCH repetition.

15. The method of claim 14.

22. The first set of SRIs and the second set of SRIs are indicated via a first index and a second index, respectively, configured as part of a configured grant PUSCH configuration.

15. The method of claim 14.

23. The first SRS resource set corresponds to a first transmission / reception point (TRP), and the second SRS resource set corresponds to a second TRP.

15. The method of claim 14.

24. 17. A wireless device (1700) including one or more processors (1702), the one or more processors (1702) configured to cause the wireless device (1700) to: receiving a first or second uplink (UL) phase tracking reference signal (PT-RS) port index configuration for each sounding reference signal (SRS) resource among a plurality of SRS resources comprising two SRS resource sets for a non-codebook-based PUSCH; receiving an indication of a first set of SRS resource indicators (SRIs) indicating SRS resources from a first SRS resource set and a second set of SRIs indicating SRS resources from a second SRS resource set; determining a first number of UL PT-RS ports to be used for PUSCH transmission according to the SRS resources indicated in the first set of SRIs; and determining a second number of UL PT-RS ports to be used for PUSCH transmission according to the SRS resources indicated in the second set of SRIs; transmitting a plurality of PUSCH repetitions using the determined first number of UL PT-RS ports and the determined second number of UL PT-RS ports; A wireless device (1700) configured to:

25. The wireless device (1700) of claim 24, wherein the one or more processors (1702) are further configured to cause the wireless device (1700) to perform any step of the method of any one of claims 2 to 13.

26. A base station (1400) including one or more processors (1402), the one or more processors (1402) configured to cause the base station (1400) to: transmit a configuration of a first or second uplink (UL) phase tracking reference signal (PT-RS) port index for each sounding reference signal (SRS) resource among a plurality of SRS resources comprising two SRS resource sets for a non-codebook-based PUSCH; transmitting an indication of a first set of SRS resource indicators (SRIs) indicating SRS resources from a first SRS resource set and a second set of SRIs indicating SRS resources from a second SRS resource set; determining a first number of UL PT-RS ports to be used for PUSCH reception according to SRS resources indicated in a first set of SRIs; and determining a second number of UL PT-RS ports to be used for PUSCH reception according to SRS resources indicated in a second set of SRIs; receiving a plurality of PUSCH repetitions using the determined first number of UL PT-RS ports and the determined second number of UL PT-RS ports; A base station (1400) configured to:

27. The base station (1400) of claim 26, wherein the one or more processors (1402) are further configured to cause the base station (1400) to perform any step of the method of any one of claims 15 to 23.

Images