Systems and methods for non-codebook-based multi-TRP PUSCH

Abstract

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

Description

[0001] Related applications

[0002] This application claims the benefit of provisional patent application No. 63 / 170,001, filed on April 2, 2021, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to non-codebook-based transmissions. Background Technology

[0004] 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 or UE) and the uplink (UL) (i.e., from the UE to the gNB). DFT-extended OFDM is also supported in the uplink. In the time domain, NR downlink and uplink are organized into equal-length subframes of 1 ms each. Subframes are further divided into multiple time slots of equal duration. The time slot length depends on the subcarrier spacing. For a subcarrier spacing of Δf = 15 kHz, each subframe has only one time slot, and each time slot consists of 14 OFDM symbols.

[0005] Data scheduling in NR is typically based on time slots. Figure 1 The example shown is a 14-symbol time slot, where the first two symbols contain the Physical Downlink Control Channel (PDCCH), and the remaining symbols contain the Physical Shared Data Channel, Physical Downlink Shared Channel (PDSCH), or Physical Uplink Shared Channel (PUSCH).

[0006] NR supports different subcarrier spacing values. The supported subcarrier spacing values ​​(also called different parameter sets) are determined by Δf = (15 × 2) / ( ... μ The time slot duration at different subcarrier intervals is given by )kHz, where μ∈{0,1,2,3,4}, and Δf=15kHz is the basic subcarrier spacing. Provided.

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

[0008] In NR Rel-15, uplink (UL) data transmission can be dynamically scheduled using the uplink grant contained in the downlink control information (DCI) carried on the physical downlink control channel (PDCCH). The UE first decodes the uplink grant, and then transmits the PUSCH based on the decoded control information in the uplink grant.

[0009] In addition to dynamic scheduling, NR also supports PUSCH transports with Configuration Grant (CG). Two types of CGs are defined in NR: Type 1 and Type 2. In a Type 1 CG, periodicity, as well as the start and stop of PUSCH transports, are semi-statically configured by the Recurrent Configuration Control (RRC). In a Type 2 CG, periodicity is configured by the RRC, while the start and stop of PUSCH transports are dynamically signaled by the Distributed Control Interface (DCI).

[0010] NR supports three UL DCI formats: DCI format 0_0, DCI format 0_1, and DCI format 0_2. Each DCI contains multiple bit fields, each conveying certain information, including one or more of the following:

[0011] • Sound Reference Signal (SRS) Resource Indicator (SRI)

[0012] • Precoding information and number of layers

[0013] • TPC (Transmit Power Control) commands for PUSCH used for scheduling

[0014] SRI is used to indicate one or more SRS resources associated with the PUSCH. "Precoding Information and Layer Number" indicates the Transport Precoding Matrix Indicator (TPMI) and the rank used for the PUSCH. TPC indicates the closed-loop power correction for this PUSCH.

[0015] In NR Rel-15, slot-based PUSCH repetition (or PUSCH repetition type A) is supported, where the number of aggregated slots for both dynamically scheduled and configured authorization type 2 is RRC-configured. In NR Rel-16, this is enhanced to allow dynamic indication of the number of repetitions, i.e., changing from one PUSCH scheduling timing to the next. Specifically, in addition to the start symbol S and the length of PUSCH L, the nominal repetition count K is signaled as part of the Time Domain Resource Allocation (TDRA).

[0016] In NR Rel-16, PUSCH repetition type B was introduced, where PUSCH can be repeated over multiple mini-slots. When scheduling a transmission with PUSCH repetition type B, the nominal repetition count K is signaled as part of the TDRA, in addition to the start symbol S and the length of PUSCH L.

[0017] PUSCH transmission scheme

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

[0019] Codebook-based PUSCH scheme

[0020] If the higher-level parameter txConfig = codebook, then codebook-based PUSCH is enabled. For dynamically scheduled PUSCH and configured authorized PUSCH type 2, the codebook-based PUSCH transport scheme can be summarized as follows:

[0021] • PUSCH is associated with one or two SRS resources in an SRS resource set whose higher-level parameter usage is set to 'codebook'. Note that only a single SRS resource set can be configured to have usage set to 'codebook'.

[0022] • gNB determines the rank-sum preferred UL precoder in the codebook based on the UL Probe Reference Signal (SRS) resource selected from one or two SRS resources configured in the SRS resource set.

[0023] The gNB indicates the selected SRS resource via a 1-bit SRI field in the DCI of the scheduling PUSCH. If only one SRS resource is configured in the SRS resource set, the SRI field is not present in the DCI.

[0024] The gNB also indicates the rank and preferred UL precoder via the 'Precoding Information and Layer Number' field in the DCI.

[0025] The UE performs PUSCH transmissions using the indicated TPMI and the rank on its antenna port associated with the indicated SRS resource. The PUSCH is spatially correlated with the most recent SRS transmission in the indicated SRS resource.

[0026] Until NR Rel-16, only a single SRS resource set could be configured for use as a "codebook".

[0027] PUSCH scheme based on non-codebook

[0028] Non-codebook-based UL transport is available in NR, and reciprocal UL transport is supported. Non-codebook-based PUSCH is enabled in NR if the higher-layer parameter txConfig = noncodebook. Note that in NR Rel-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 a non-codebook-based PUSCH transport). The maximum number of SRS resources that can be configured for a non-codebook-based uplink transport is four.

[0029] By assigning DL CSI-RS to the UE, the UE can measure and infer appropriate precoder weights for up to four spatial layers' PUSCH transmissions. Candidate precoder weights are transmitted using up to four single-port SRS resources corresponding to the spatial layers. Subsequently, the gNB indicates the transmission rank and multiple SRS resource indicators, using... Bit joint encoding, where N SRS Indicates the number of SRS resources configured, and L max This is the maximum number of layers supported by PUSCH. Table 1 shows the maximum number of layers supported by L. max When = 4, for different numbers of N SRS The number of SRIs mapped to the code point of the SRI field.

[0030] When N SRS When =4 and the SRI bit field is mapped to index 12, the PUSCH will be transmitted using the same antenna port as the SRS ports in the 1st, 3rd and 4th SRS resources configured in the SRS resource set (i.e., 3 PUSCH layers are transmitted).

[0031] When N SRS When =4 and the SRI bit field is mapped to index 5, the PUSCH will be transmitted using the same antenna port as the SRS port in the 1st and 3rd SRS resources configured in the SRS resource set (i.e., 2 PUSCH layers are transmitted).

[0032] When N SRS When the SRI bit field is mapped to index 3 and the SRI bit field is 4, the PUSCH will be transmitted using the same antenna port as the SRS port in the 4th SRS resource configured in the SRS resource set (i.e., 1 PUSCH layer is transmitted).

[0033] Table 1: SRI indication for non-codebook PUSCH-based transmissions, L max =4 (Reproduced from Table 7.3.1.1.2-31 of 3GPP TS38.212v16.4.0)

[0034]

[0035] Regarding non-codebook-based PUSCH, 3GPP TS 38.214 V16.0.0 specifies the following:

[0036] "For non-codebook-based transmissions, the UE can calculate the precoder for transmitting SRS based on measurements of the associated NZP CSI-RS resource. The UE can only be configured with one NZP CSI-RS resource, which is used by the SRS resource set in the SRS-ResourceSet that has higher-level parameters set as 'non-codebook' if it is already configured."

[0037] Therefore, for non-codebook-based PUSCH transmissions, only one NZP CSI-RS resource is configured in the SRS resource set. The UE can use this associated NZP CSI-RS resource to calculate the precoder for transmitting the SRS. The single NZP CSI-RS resource configured in each SRS resource set is part of the SRS-Config information element, as shown below. The condition 'non-codebook' means that the associated NZP CSI-RS optionally exists in the used SRS resource set configured as 'non-codebook'; otherwise, the field does not exist.

[0038] SRS-Config information element

[0039]

[0040]

[0041] 3GPP TS 38.214 further specifies that if a UE is configured with an SRS resource set that has associated NZP CSI-RS resources, the UE does not expect to be configured with spatial relationship information in any SRS resource in the SRS resource set.

[0042] In NR, for non-codebook-based PUSCH, the UE performs a one-to-one mapping from the indicated SRI to(multiple) indicated demodulation reference signal (DM-RS) ports and their corresponding PUSCH layers {0…v-1} in ascending order. The UE should transmit the PUSCH using the same antenna port as the SRS ports in(multiple) SRS resources indicated by(multiple) SRIs, where the SRS port in the (i+1)th SRS resource set is indexed as p. i =1000+i.

[0043] Until NR Rel-16, only a single SRS resource set was configured for use as “non-codebook”.

[0044] Phase tracking reference signal (PT-RS) used for PUSCH in NR

[0045] In NR, the Phase Tracking Reference Signal (PT-RS) can be configured for PUSCH transmission so that the receiver can correct errors associated with phase noise. PT-RS can be configured with a higher-level parameter PTRS-UplinkConfig in DMRS-UplinkConfig for scheduling PUSCH by DCI format 0_1 ​​or DCI format 0_2.

[0046] In NR Rel.15, one or two PT-RS ports are supported for PUSCH. Each PT-RS port is associated with one of the DM-RS ports used for PUSCH. The maximum number of PT-RS ports configured is given by the higher-level parameter maxNrofPorts in PTRS-UplinkConfig based on the UE's reported requirements. If the UE reports support for fully coherent UL transmission, it is expected that a PT-RS port will be configured if needed.

[0047] In the frequency domain, a PT-RS can be located on a subcarrier within every two PRBs. Furthermore, the subcarrier used for the PT-RS port must also be one of the subcarriers used for the DM-RS port associated with it. For DM-RS configuration type 1, DM-RS ports are mapped to every other subcarrier. Therefore, the associated PT-RS can only be mapped to one of the six subcarriers. An 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 TS 38.211).

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

[0049] Examples of PT-RS include Figure 3 As shown, the PT-RS port is associated with DM-RS port 0 and has a subcarrier offset of 4 and a time density of 2. An example of PT-RS REs in an RB with a time density of 2 and a subcarrier offset of 4 is given.

[0050] For uplink PT-RS transmission based on non-codebook PUSCH

[0051] For non-codebook-based PUSCH, the maximum number of PT-RS ports in the uplink is configured to the UE via the PTRS-UplinkConfig information element in the RRC (see 3GPP TS 38.331 V16.2.0). Each SRS resource configured in the SRS resource set is set to 'non-codebook' and is configured with the PT-RS port index shown below (i.e., ptrs-PortIndex).

[0052] SRS-Config information element

[0053]

[0054]

[0055] According to 3GPP TS 38.214 V16.4.0, for non-codebook-based PUSCH transmissions, the actual number of UL PT-RS ports transmitted by the UE is determined based on the SRI indicated for non-codebook-based PUSCH transmissions. The SRI can be indicated by the SRS Resource Indicator field in the DCI (DCI format 0_1 ​​or DCI format 0_2) or by a higher layer configured via the RRC configuration parameter rrc-ConfiguredUplinkGrant.

[0056] If all indicated SRIs have the same PT-RS port index, then only one PT-RS port is transmitted for a non-codebook-based PUSCH. However, if some indicated SRIs have a corresponding SRS resource configured with PT-RS port index n0, and other indicated SRIs have a corresponding SRS resource configured with PT-RS port index n1, then two PT-RS ports are transmitted for a non-codebook-based PUSCH.

[0057] Transmitting UL signals to multiple TRPs

[0058] Until NR Rel-16, it was assumed that PUSCH was always transmitted to the same single transmit and receive point (TRP) via the UE. In NR Rel-17, PUSCH enhancements will be introduced, where PUSCH scheduled by a single DCI or PUSCH, configured via configuration grant (i.e., via the rrc-ConfiguredUplinkGrant parameter defined in 3GPP TS 38.331 V16.2.0), can be repeated to two TRPs (i.e., a multi-TRP PUSCH repetition scheme). To support this, it is agreed that two SRS resource sets can be configured, each associated with one of the two TRPs for both codebook-based and non-codebook-based PUSCH schemes. Furthermore, the UE can be indicated with two SRIs, two TMPIs, and two TPCs, each associated with one of the two TRPs.

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

[0060] The RAN1#104e-bis meeting also agreed that the same number of PUSCH layers would be transmitted via different repetitions for different TRPs. Note that the different TRPs here correspond to different sets of SRS resources configured for non-codebook-based PUSCH. Since the same number of PUSCH layers will be transmitted to two TRPs, the number of SRS resources (i.e., the number of SRIs) indicated by the two SRI fields is the same in NR Rel-17.

[0061] There are certain challenges. In the existing NR Rel-15 and Rel-16 specifications, the actual number of UL PT-RS ports for non-codebook-based PUSCH transmissions is determined based on the indicated SRIs. In NR Rel-15 and Rel-16, only a single SRI set is indicated to the UE for non-codebook-based PUSCH transmissions, and this existing solution supports non-codebook-based PUSCH transmissions to a single TRP. However, this solution is not suitable for non-codebook-based PUSCH transmissions to two different TRPs because, in the case of multiple TRPs, two different SRI sets are indicated to the UE. Therefore, determining the actual number of UL PT-RS ports for non-codebook-based multi-TRP PUSCH transmissions is an open problem that needs to be solved. Summary of the Invention

[0062] Systems and methods are provided for non-codebook-based multiple transmit and receive points (TRP) physical uplink shared channel (PUSCH). In some embodiments, the method for non-codebook-based PUSCH transmission performed by a wireless device includes: receiving a configuration of a first or second uplink (UL) phase tracking reference signal (PT-RS) port index according to SRS resources configured in two probe reference signal (SRS) resource sets for non-codebook-based PUSCH; receiving an indication of at least one of the following: a first set of SRS resource indicators (SRIs) indicating SRS resources from a first set of SRS resources; and a second set of SRIs indicating SRS resources from a second set of SRS resources; determining at least one of the following: 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 along with the plurality of PUSCH repetitions.

[0063] In some embodiments, a first subset of PUSCH repeats in a plurality of PUSCH repeats is transmitted according to the SRS resources indicated in a first SRI set, and the first subset of PUSCH repeats includes transmissions of a first number of UL PT-RS ports.

[0064] In some embodiments, a second PUSCH repeat subset, which is separated from the first PUSCH repeat subset, is transmitted according to the SRS resources indicated in the second SRI set, and the second PUSCH repeat subset includes the transmission of a second number of UL PT-RS ports.

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

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

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

[0068] In some embodiments, when the SRS resources indicated in the first SRI set all have the same configured PT-RS port index, the first number of UL PT-RS ports is determined to be 1. In some embodiments, when the SRS resources indicated in the second SRI set all have the same configured PT-RS port index, the second number of UL PT-RS ports is determined to be 1.

[0069] In some embodiments, when the SRS resource indicated in the first SRI set has two different configured PT-RS port index values, the first number of UL PT-RS ports is determined to be 2. In some embodiments, when the SRS resource indicated in the second SRI set has two different configured PT-RS port index values, the second number of UL PT-RS ports is determined to be 2.

[0070] In some embodiments, the first SRI set and the second SRI set are indicated via the first SRI field and the second SRI field in the Downlink Control Indicator (DCI) for scheduled PUSCH repetition, respectively. In some embodiments, the first SRI set and the second SRI set are indicated via a first index and a second index, respectively, which are configured as part of the configured authorized PUSCH configuration.

[0071] In some embodiments, the first SRS resource set corresponds to the first Transmit and Receive Point (TRP), and the second SRS resource set corresponds to the second TRP.

[0072] 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 based on SRS resources indicated in a first SRI set from a first configuration SRS resource set. A second number of UL PT-RS ports corresponding to a second TRP is determined based on SRS resources indicated in a second SRI set from a second configuration SRS resource set. In some embodiments, the UE transmits the same number of UL PT-RS ports to both TRPs. In another embodiment, the number of UL PT-RS ports for TRP1 and TRP2 is determined independently.

[0073] This document presents various embodiments for solving one or more of the problems disclosed herein.

[0074] Some embodiments may provide one or more of the following technical advantages. In Embodiment 1, if the same number of UE panels are used for PUSCH repetition to TRP 1 and TRP 2, it is advantageous to transmit the same number of UL PT-RS ports to both TRPs. If a single UE panel is used to transmit the PUSCH layer to both TRP 1 and TRP 2, a single UL PT-RS port is sufficient for PUSCH repetition to both TRP 1 and TRP 2. If two UE panels are used to transmit the PUSCH layer to both TRP 1 and TRP 2, then two UL PT-RS ports are required for PUSCH repetition to both TRP 1 and TRP 2.

[0075] Example 2 is beneficial for a UE equipped with multiple antenna panels, wherein the UE uses N1 panels to transmit PUSCH to a first TRP and uses N2 panels to transmit PUSCH to a second TRP, wherein N1 may be different from N2.

[0076] Example 3 is helpful in determining the number of UL PT-RS ports in the case of dynamic switching between single-TRP-based PUSCH and multi-TRP-based PUSCH. Attached Figure Description

[0077] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate several aspects of this disclosure and, together with the specification, serve to explain the principles of this disclosure.

[0078] Figure 1 The diagram illustrates that data scheduling in New Radio (NR) is typically based on a 14-symbol time slot, where the first two symbols contain the Physical Downlink Control Channel (PDCCH), and the remaining symbols contain either the Physical Shared Data Channel, or the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0079] Figure 2 The diagram illustrates the basic NR physical time-frequency resource grid, showing only one resource block (RB) within 14 symbol slots;

[0080] Figure 3 An example of a phase tracking reference signal (PT-RS) is illustrated, where the PT-RS port is associated with demodulation reference signal (DM-RS) port 0 and has subcarriers with an offset of 4 and a time density of 2.

[0081] Figure 4 An example of a cellular communication system that can implement embodiments of the present disclosure is illustrated;

[0082] Figure 5 The illustration shows a method for non-codebook-based PUSCH transmission performed by a wireless device according to some embodiments of the present disclosure;

[0083] Figure 6 The illustration shows a method for receiving non-codebook-based PUSCH performed by a base station according to some embodiments of the present disclosure;

[0084] Figure 7 The illustration shows a pusch repeat toward two TRPs according to some embodiments of the present disclosure, some of which repeat toward TRP1 and others toward TRP2.

[0085] Figure 8 and Figure 9 The illustration shows two uplink (UL) PT-RS ports corresponding to PUSCH repetitions toward both TRP1 and TRP2 according to some embodiments of the present disclosure;

[0086] Figure 10 The illustration shows that even if the number of UL PT-RS ports transmitted toward TRP1 and TRP2 is the same, the exact UL PT-RS port indices transmitted toward TRP1 and TRP2 may be different according to some embodiments of the present disclosure.

[0087] Figure 11 The illustration shows an option to configure the same UL PT-RS port index across all SRS resources in a probe reference signal (SRS) resource set according to some embodiments of the present disclosure;

[0088] Figure 12The illustration shows that, in some embodiments according to this disclosure, the UE first determines, based on a configured SRS resource set and indicated first and second SRS resource indicator (SRI) sets, that the UL PT-RS ports associated with the indicated first SRI set are n0 and n1, and the UL PT-RS port associated with the indicated second SRI set is n0.

[0089] Figure 13 The illustration shows that, in an example of some embodiments according to this disclosure, the first SRI set indicates to the UE that, for the PUSCH repetition toward TRP1, the two PUSCH layers will use the same antenna port as the SRS ports(multiple) from resources 0 and 1 of SRS resource set 1 for transmission.

[0090] Figure 14 This is a schematic block diagram of a radio access node according to some embodiments of the present disclosure;

[0091] Figure 15 This is a schematic block diagram illustrating a virtualized embodiment of a radio access node according to some embodiments of the present disclosure;

[0092] Figure 16 This is a schematic block diagram of a radio access node according to some other embodiments of the present disclosure;

[0093] Figure 17 This is a schematic block diagram of a wireless communication device according to some other embodiments of the present disclosure;

[0094] Figure 18 This is a schematic block diagram of a wireless communication device according to some other embodiments of the present disclosure;

[0095] Figure 19 The illustrations depict communication systems according to some embodiments of the present disclosure, including telecommunications networks, such as 3GPP-type cellular networks, which include access networks, such as RANs, and core networks.

[0096] Figure 20 A communication system according to some embodiments of the present disclosure is illustrated, wherein a host computer includes hardware including a communication interface, configured to establish and maintain wired or wireless connections with interfaces of different communication devices of the communication system; and

[0097] Figures 21 to 24 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. Detailed Implementation

[0098] The embodiments described below illustrate information that enables those skilled in the art to practice the embodiments and demonstrate best practice patterns for the embodiments. Upon reading the following description in conjunction with the accompanying drawings, those skilled in the art will understand the concepts of this disclosure and recognize the application of these concepts, which are not specifically addressed herein. It should be understood that these concepts and applications fall within the scope of this disclosure.

[0099] Radio node: As used in this article, a “radio node” is a radio access node or wireless communication device.

[0100] 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) that operates to wirelessly transmit and / or receive signals in a cellular communication network. Some examples of radio access nodes include, but are not limited to, base stations (e.g., new radio (NR) base stations (gNBs) in 3GPP 5G NR networks or enhanced or evolved Node Bs (eNBs) in 3GPP LTE networks), high-power or macro base stations, low-power base stations (e.g., micro base stations, pico base stations, home eNBs, etc.), relay nodes, network nodes that implement partial functions of base stations (e.g., network nodes that implement gNB central units (gNB-CUs) or gNB distributed units (gNB-DUs), or network nodes that implement partial functions of some other type of radio access node.

[0101] Core Network Node: As used herein, a “core network node” is any type of node in the core network or any node that implements core network functions. Some examples of core network nodes include, for instance, Mobility Management Entities (MMEs), Packet Data Network Gateways (P-GWs), Service Capability Exposure Functions (SCEFs), Home Subscriber Servers (HSSs), etc. Other examples of core network nodes include nodes that implement Access and Mobility Management Functions (AMFs), User Plane Functions (UPFs), Session Management Functions (SMFs), Authentication Server Functions (AUSFs), Network Slice Selection Functions (NSSFs), Network Exposure Functions (NEFs), Network Functions (NF) Storage Functions (NRFs), Policy Control Functions (PCFs), Unified Data Management (UDMs), etc.

[0102] Communication equipment: As used herein, “communication equipment” is any type of device that can access a network. Some examples of communication equipment include, but are not limited to: mobile phones, smartphones, sensor devices, instruments, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronic device, such as, but not limited to, televisions, radios, lighting fixtures, tablets, laptops, or personal computers (PCs). Communication equipment can be portable, handheld, computer-based, or in-vehicle mobile devices capable of communicating voice and / or data via wireless or wired connections.

[0103] Wireless communication devices: One type of communication device is a wireless communication device, which can be any type of wireless device that can access (i.e., be served by) a wireless network (e.g., a cellular network). Some examples of wireless communication devices include, but are not limited to: User Equipment (UE) devices in 3GPP networks, Machine-Type Communication (MTC) devices, and Internet of Things (IoT) devices. Such wireless communication devices can be or can be integrated into mobile phones, smartphones, sensor devices, instruments, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronic device, such as, but not limited to, televisions, radios, lighting fixtures, tablets, laptops, or personal computers. Wireless communication devices can be portable, handheld, computer-based, or in-vehicle mobile devices capable of communicating voice and / or data via wireless connectivity.

[0104] Network node: As used in this article, a “network node” is any node in the core network of a RAN or a cellular communication network / system.

[0105] Transmit / Receive Point (TRP): In some embodiments, a TRP can be a network node, radio head, spatial relation, or Transmission Configuration Indicator (TCI) state. In some embodiments, a TRP can be represented by a spatial relation or a TCI state. In some embodiments, a TRP can use multiple TCI states. In some embodiments, a TRP can be part of a gNB, transmitting and receiving radio signals to and from the UE based on physical layer attributes and inherent parameters. In some embodiments, in multi-TRP operation, the serving cell can schedule UEs from two TRPs to provide better Physical Downlink Shared Channel (PDSCH) coverage, reliability, and / or data rate. Multi-TRP has two different operating modes: single downlink control information (DCI) and multiple DCI. For both modes, uplink and downlink operation control is performed by the physical layer and Media Access Control (MAC). In single DCI mode, the UE is scheduled by the same DCI for both TRPs; in multi-DCI mode, the UE is scheduled by an independent DCI for each TRP.

[0106] Figure 4An example of a cellular communication system 400 is shown, in which embodiments of the present disclosure can 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 the 5GS include an NR base station (gNB) and an optional next-generation eNB (ng-eNB) (e.g., an LTE RAN node connected to the 5GC), and in the EPS includes an eNB that controls the respective (macro)cells 404-1 and 404-2. Base stations 402-1 and 402-2 are generally referred to herein collectively as base station 402, and are individually referred to as base station 402. Similarly, (macro)cells 404-1 and 404-2 are generally referred to herein collectively as (macro)cell 404, and are individually referred to as (macro)cell 404. The RAN may also include multiple low-power nodes 406-1 to 406-4 that control the respective microcells 408-1 to 408-4. Low-power nodes 406-1 to 406-4 may be small base stations (e.g., pico or femtocells) or RRHs, etc. It is worth noting that, although not shown, one or more of microcells 408-1 to 408-4 may alternatively be provided by base station 402. Low-power nodes 406-1 to 406-4 are generally referred to herein collectively as low-power node 406, and are individually referred to as low-power node 406. Similarly, microcells 408-1 to 408-4 are generally referred to herein collectively as microcell 408, and are individually referred to as microcell 408. The cellular communication system 400 also includes a core network 410, which is referred to as 5GC in a 5G system (5GS). Base station 402 (and optional low-power nodes 406) is connected to core network 410.

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

[0108] In some embodiments, a collection of transmitting points (TPs) is a collection of geographically co-located transmitting antennas (e.g., an antenna array (with one or more antenna elements)) for a cell, a portion of a cell, or a Location Reference Signal (PRS) - TP only. A TP may include base station (eNB) antennas, remote radio heads (RRHs), remote antennas of a base station, PRS - TP-only antennas, etc. A cell may consist of one or more TPs. For homogeneous deployment, each TP may correspond to one cell.

[0109] In some embodiments, a TRP set is a collection of geographically co-located antennas (e.g., antenna arrays (with one or more antenna elements)) that support TP and / or receiver point (RP) functionality.

[0110] Note that the descriptions presented herein focus on 3GPP cellular communication systems; therefore, 3GPP terminology or similar terms are frequently used. However, the concepts disclosed herein are not limited to 3GPP systems.

[0111] Note that the term "cell" may be used in the description in this article; however, in particular regarding the 5G NR concept, beams may be used instead of cells, so it is important to note that the concepts described in this article apply equally to both cells and beams.

[0112] To simplify the discussion, this disclosure considers two TRPs in its entirety, but it should be noted that the proposed solution can be easily extended to more than two TRPs.

[0113] Suppose a UE is configured with two SRS resource sets set to "non-codebook" and "used", where each SRS resource set is associated with a TRP.

[0114] Note that the term 'TRP' may not be part of the 3GPP standard specification. Instead, it can be used as part of the standard as "SRS Resource Set", "SRI Field" (where one SRI field in the DCI corresponds to one TRP) or "TCI Status", which is equivalent to indicating a TRP.

[0115] Figure 5A method for non-codebook-based Physical Uplink Shared Channel (PUSCH) transmission performed by a wireless device according to some embodiments of the present disclosure is illustrated. The method includes one or more of the following: receiving a configuration of a first or second Uplink (UL) Phase Tracking Reference Signal (PT-RS) port index according to SRS resources configured in two Sounding Reference Signal (SRS) resource sets for non-codebook-based PUSCH (step 500); receiving at least one of the following indications: a first SRS Resource Indicator (SRI) set indicating SRS resources from the first SRS resource set; and a second SRI set indicating SRS resources from the second SRS resource set (step 502); determining at least one of the following: a first number of UL PT-RS ports to be transmitted according to the SRS resources indicated in the first SRI set; and a second number of UL PT-RS ports to be transmitted according to the SRS resources indicated in the second SRI set (step 504); and transmitting the determined number of UL PT-RS ports along with the plurality of PUSCH repetitions (step 506).

[0116] Figure 6 A method for receiving a non-codebook-based PUSCH, performed by a base station according to some embodiments of the present disclosure, is illustrated. The method includes one or more of the following: transmitting a configuration of a first or second UL PT-RS port index according to the SRS resources configured in two SRS resource sets (step 600); transmitting an indication of at least one of the following: indicating a first SRI set of SRS resources from the first SRS resource set; and indicating a second SRI set of SRS resources from the second SRS resource set (step 602); determining at least one of the following: a first number of UL PT-RS ports to be received according to the SRS resources indicated in the first SRI set; and a second number of UL PT-RS ports to be received according to the SRS resources indicated in the second SRI set (step 604); and receiving the determined number of UL PT-RS ports along with the plurality of PUSCH repetitions (step 606).

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

[0118] In some other embodiments, when configuring granted PUSCH transmission, two indicators indicating two SRI sets can be configured to the UE as part of the ConfiguredGrantConfig information element in the RRC configuration. For example, the first srs-ResourceIndicator in ConfiguredGrantConfig corresponds to (multiple) SRS resources in the first SRS resource set, and the second srs-ResourceIndicator in ConfiguredGrantConfig corresponds to (multiple) SRS resources in the second SRS resource set.

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

[0120] Figure 7 A diagram illustrating PUSCH repetitions for two TRPs is shown, with some PUSCH repetitions for TRP1 and others for TRP2. The number of PUSCH layers and the number N1 of UL PT-RS ports transmitted to TRP1 are determined using an indicated first SRI set (e.g., using a first SRI field), which corresponds to the SRS resources indicated from a first SRS resource set with "Use" set to "Non-Codebook". The number of PUSCH layers and the number N2 of UL PT-RS ports transmitted to TRP2 are determined using an indicated second SRI set (e.g., using a second SRI field), which corresponds to the SRS resources indicated from a second SRS resource set with "Use" set to "Non-Codebook". How the number of UL PT-RS ports N1 and N2 are determined is covered by the different embodiments given below. Figure 7 The PUSCH repeats for two TRPs are shown, where N1 and N2 UL PT-RS ports are for TRP 1 and 2, respectively.

[0121] Example 1: The same number of UL PT-RS ports facing different TRPs

[0122] Provide multiple block diagrams illustrating the system / structure / node-level architecture / platform, and describe the solution in detail with reference to multiple diagrams. Indicate new structures / blocks through text, graphical emphasis in the diagrams, or other indicators.

[0123] In one embodiment, the number of UL PT-RS ports corresponding to the PUSCH repeats transmitted to TRP 1 is initially determined based on a first SRI set indicated from a first SRS resource set whose "use" is set to "non-codebook".

[0124] • When the SRS resources indicated in the first SRI set from the first SRS resource set are all configured with the same PT-RS port index (e.g., n0 or n1), then the single UL PT-RS port N1=1 is determined to be transmitted to TRP1.

[0125] • When the SRS resources indicated from the first SRI set of the first SRS resource set are configured with different PT-RS port indices (e.g., some indicated SRS resources have PT-RS port indices),

[0126] When the RS port index is n0 and other indicated SRS resources have PT-RS port index n1, then the two UL PT-RS ports N1 = 2 are determined to be transmitted to TRP1.

[0127] Once the number N1 of UL PT-RS ports used for transmission to TRP1 is determined as above, the same number of UL PT-RS ports N2 (i.e., N2 = N1) are used for transmission of PUSCH repeats to TRP2. This means that SRS resources indicated in the second SRI set from the second SRS resource set with "Use" set to "Non-Codebook" need to have the same number of UL PT-RS ports as N1. This embodiment can be captured as a rule in the 3GPP specification, where the UE expects the same number of UL PT-RS ports associated with PUSCH repeats corresponding to the first SRS resource set (e.g., the first TRP) as the number associated with PUSCH repeats corresponding to the second SRS resource set (e.g., the second TRP).

[0128] Note that if the same number of UE panels are used for PUSCH repetition towards both TRP 1 and TRP 2, it is beneficial to use the same number of UL PT-RS ports for both TRPs. If a single UE panel is used to transmit the PUSCH layer to both TRP 1 and TRP 2, a single UL PT-RS port is sufficient for PUSCH repetition towards both TRP 1 and TRP 2 (i.e., N1 = N2 = 1). If two UE panels are used to transmit the PUSCH layer to both TRP 1 and TRP 2, then two UL PT-RS ports are needed for PUSCH repetition towards both TRP 1 and TRP 2 (i.e., N1 = N2 = 2).

[0129] According to some embodiments of this disclosure, the illustration shows a first example of two UL PT-RS ports corresponding to the PUSCH repetition for both TRP1 and TRP2. Figure 8 As shown in the example, the first SRI set indicates to the UE that for the PUSCH duplication to TRP1, the same antenna ports as the SRS ports in resources 0 and 1 from SRS resource set 1 will be used to transmit the two PUSCH layers. Since these two resources are already configured with UL PT-RS ports n0 and n1, the number of UL PT-RS ports transmitted to TRP1 is determined to be 2 (i.e., N1 = 2). Then, the second SRI set indicates two SRS resources (0 and 2) from the second SRS resource set such that the number of UL PT-RS ports configured in these two resources is also 2 (i.e., N2 = N1 = 2). Figure 8 As shown, the two SRS resources indicated by the second SRI set are configured with UL PT-RS ports n0 and n1, therefore, UL PT-RS ports n0 and n1 will transmit to TRP2.

[0130] According to some embodiments of this disclosure, the illustration shows a second example of two UL PT-RS ports corresponding to the PUSCH repetition for both TRP1 and TRP2. Figure 9 As shown in the example, the first SRI set indicates to the UE that the PUSCH duplication for TRP1 will use the same antenna port as the SRS ports in resources 0 and 2 from SRS resource set 1 to transmit two PUSCH layers. Since only UL PT-RS port n0 is configured in these two resources, the number of UL PT-RS ports transmitted to TRP1 is determined to be 1 (i.e., N1 = 1). Then, the second SRI set indicates two SRS resources (0 and 2) from the second SRS resource set such that the number of UL PT-RS ports configured in these two resources is also 1 (i.e., N2 = N1 = 2). Figure 9 As shown, the two SRS resources indicated by the second SRI set are configured with UL PT-RS port n0, therefore, UL PT-RS port n0 will transmit to TRP2.

[0131] In this embodiment, it should be noted that even if the number of UL PT-RS ports transmitted to TRP1 and TRP2 is the same, the exact UL PT-RS port indices transmitted to TRP1 and TRP2 may be different. Such examples are shown in... Figure 10As shown in the example, in this case, two SRS resources indicated by the first SRI set are configured with UL PT-RS port n0. Therefore, UL PT-RS port n0 will transmit to TRP1. However, two SRS resources indicated by the second SRI set are configured with PT-RS port n1, therefore, UL PT-RS port n1 will transmit to TRP2.

[0132] In this example, the first SRI set indicates to the UE that, for PUSCH duplication toward TRP1, the same antenna ports as the SRS ports in resources 0 and 2 from SRS resource set 1 will be used to transmit the two PUSCH layers. Since these two resources only have UL PT-RS port n0 configured, the number of UL PT-RS ports transmitted toward TRP1 is determined to be 1 (i.e., N1 = 1). Then, the second SRI set indicates two SRS resources (0 and 2) from the second SRS resource set such that the number of UL PT-RS ports configured in these two resources is also 1 (i.e., N2 = N1 = 2). Figure 9 As shown, the two SRS resources indicated by the second SRI set are configured with UL PT-RS port n0, therefore, UL PT-RS port n0 will transmit to TRP2.

[0133] In another embodiment, when the PUSCH for two TRPs is repeatedly scheduled by the network (i.e., via the configuration of two SRS resource sets, whose usage is set to 'non-codebook' and the indication of the two SRI sets), only a single UL PT-RS port (e.g., a UL PT-RS port with index n0) is allowed to be transmitted to both TRP1 and TRP2. This is advantageous when the UE is only using a single panel to transmit to one TRP, in which case it is sufficient for the UE to transmit a single UL PT-RS port on which phase tracking can be performed. One option is to... Figure 11 The same UL PT-RS port index is configured in all SRS resources of the SRS resource set shown. As shown in the figure, UL PT-RS port index n0 is configured in all SRS resources of SRS resource set 1, while UL PT-RS port index n1 is configured in all SRS resources of SRS resource set 2. In this example, UL PT-RS port index n0 will transmit to TRP1, and UL PT-RS port index n1 will transmit to TRP2.

[0134] In an alternative embodiment, only the UL PT-RS port index n0 can be associated with all SRS resources configured in both SRS resource sets. That is, the UL PT-RS port index n0 is associated with all SRS resources in SRS resource set 1, and the 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 the UL PT-RS port index n0 for each SRS resource. Therefore, in this alternative embodiment, when the PUSCH for both TRPs is repeatedly scheduled by the network (i.e., via the configuration of both SRS resource sets, using an indication set to 'non-codebook' and both SRI sets), the UL PT-RS port index is not explicitly configured for each SRS resource, and the UE uses the UL PT-RS port index n0 for both TRP1 and TRP2. This alternative embodiment can save some configuration overhead because it is no longer necessary to configure the RRC parameters of the PT-RS port index for each SRS resource.

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

[0136] Example 2: Independently determine the number of UL PT-RS ports for different TRPs

[0137] In this embodiment, the number of UL PT-RS ports corresponding to the PUSCH repetitions transmitted to TRP 1 is first determined based on the first SRI set indicated from the first SRS resource set, wherein the "use" of the first SRS resource set is set to "non-codebook".

[0138] • When the SRS resources indicated in the first SRI set from the first SRS resource set are all configured with the same PT-RS port index (e.g., n0 or n1), then the single UL PT-RS port N1=1 is determined to be transmitted to TRP1.

[0139] • When the SRS resources indicated from the first SRI set of the first SRS resource set are configured with different 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), then the two UL PT-RS ports N1 = 2 are determined to be transmitted to TRP1.

[0140] Once the number N1 of UL PT-RS ports used for transmission to TRP1 is determined as above, the number N2 of UL PT-RS ports used for transmission of PUSCH repeats to TRP2 is determined based on the second SRI set indicated from the second SRS resource set, whose "use" is set to "non-codebook".

[0141] • When the SRS resources indicated in the second SRI set from the second SRS resource set are all configured with the same PT-RS port index (e.g., n0 or n1), then the single UL PT-RS port N2=1 is determined to be transmitted to TRP2.

[0142] • When the SRS resources indicated in the second SRI set from the second SRS resource set are configured with different PT-RS port indices (e.g., some indicated SRS resources have PT-RS port index n0 while others have PT-RS port index n1), then the two UL PT-RS ports N2 = 2 are determined to be transmitted to TRP2.

[0143] Note that in this embodiment, the number N1 (corresponding to TRP1) and the number N2 (corresponding to TRP2) of UL PT-RS ports are determined independently based on the indicated first SRI set and the indicated second SRI set, respectively. In some cases, the number N1 of UL PT-RS ports determined based on the indicated first SRI set may differ from the number N2 of UL PT-RS ports determined based on the indicated second SRI set. This embodiment is advantageous for UEs equipped with multiple antenna panels, wherein the UE uses N1 panels to transmit PUSCH to the first TRP and uses N2 panels to transmit PUSCH to the second TRP, where N1 may differ from N2.

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

[0145] Example 3: Determining the number of UL PT-RS ports during dynamic switching between single TRP PUSCH repeat and multiple TRP PUSCH repeat.

[0146] In this embodiment, the UE can indicate this through two SRI fields in the DCI, where only one SRI field in the DCI is enabled when scheduling PUSCH repetition transmission and disabling the second SRI field in the DCI. This corresponds to PUSCH repetition to a single TRP. That is, PUSCH repetition is transmitted using SRS resources from one SRS resource set corresponding to the enabled SRI field. It should be noted that in this case, the UE is still configured with two SRS resource sets, whose "Use" is set to "Non-Codebook," and the two SRI fields in the DCI correspond to two SRS resource sets. This setting can be used to dynamically switch between single-TRP PUSCH transmission and multi-TRP PUSCH transmission.

[0147] To schedule PUSCH repeats only toward TRP1, the SRS resources from the first SRS resource set can be indicated to the UE via the first SRI field in the DCI. The second SRI field is disabled (e.g., the second SRI field may not indicate any SRS resources and may point to a reserved code point). The UE determines the number N1 of UL PT-RS ports from the SRI set indicated by the first SRI field in the DCI. The UE then transmits all PUSCH repeats and N1 UL PT-RS ports to 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).

[0148] To schedule PUSCH repeats only toward TRP2, the SRS resources from the second SRS resource set can be indicated to the UE via the second SRI field in the DCI. The first SRI field is disabled (e.g., the first SRI field may not indicate any SRS resources and may point to a reserved code point). The UE determines the number N2 of UL PT-RS ports from an SRI set indicated by the second SRI field in the DCI. The UE then transmits all PUSCH repeats and N2 UL PT-RS ports to TRP2. If the indicated SRS resources are associated with the same UL PT-RS port, a single UL PT-SRS 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).

[0149] • Implement the scheduling of PUSCH repetitions toward TRP1 and TRP2 according to the embodiments described in Examples 1 and 2.

[0150] Figure 14This is a schematic block diagram of a radio access node 1400 according to some embodiments of the present disclosure. Optional features are indicated by dashed boxes. The radio access node 1400 may be, for example, a base station 402 or 406 described herein, or a network node implementing all or part of the functions of a base station 402 or gNB 406. As shown, the radio access node 1400 includes a control system 1402, which includes one or more processors 1404 (e.g., a central processing unit (CPU), application-specific integrated circuit (ASIC), 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 circuitry. Furthermore, the radio access node 1400 may include one or more radio units 1410 coupled to one or more antennas 1416, each radio unit 1410 including one or more transmitters 1412 and one or more receivers 1414. The radio unit 1410 may be referred to as radio interface circuitry or part of radio interface circuitry. In some embodiments, the radio units 1410 are external to the control system 1402 and connected to the control system 1402 via, for example, a wired connection (e.g., fiber optic cable). However, in some other embodiments, the radio units 1410 and potentially the antennas 1416 are integrated with the control system 1402. One or more processors 1404 operate to provide one or more functions of the radio access node 1400 as described herein, which are implemented in software stored, for example, in memory 1406 and executed by the one or more processors 1404.

[0151] Figure 15 This is a schematic block diagram illustrating a virtualized embodiment of a radio access node 1400 according to some embodiments of this disclosure. This discussion is equally applicable to other types of network nodes. Furthermore, other types of network nodes may have similar virtualization architectures. Additionally, optional functions are indicated by dashed boxes.

[0152] As used herein, a “virtualized” radio access node is a radio access node 1400 in which at least a portion of the functionality of radio access node 1400 is implemented as a virtual component (e.g., via virtual machines executed on physical processing nodes in multiple networks). As illustrated, in this example, as described above, radio access node 1400 may include a control system 1402 and / or one or more radio units 1410. Control system 1402 may be connected to radio units 1410 via, for example, fiber optic cables. Radio access node 1400 includes one or more processing nodes 1500 that are coupled to or included as part of networks 1502. If present, control system 1402 or radio units 1500 are connected to processing nodes 1500 via network 1502. Each processing node 1500 includes one or more processors 1504 (e.g., CPU, ASIC, FPGA, and / or the like), memory 1506, and network interface 1508.

[0153] In this example, the functionality 1510 of the radio access node 1400 described herein is distributed across one or more processing nodes 1500 and control system 1402 and / or (multiple) radio units 1410 in any anticipated manner or implemented at one or more processing nodes 1500. In some specific embodiments, some or all of the functionality 1510 of the radio access node 1400 described herein is implemented as virtual components executed by one or more virtual machines implemented in (multiple) virtual environments hosted by (multiple) processing nodes 1500. As will be understood by those skilled in the art, additional signaling or communication is provided between (multiple) processing nodes 1500 and the control system 1402 used to perform at least some of the intended functionality 1510. Notably, in some embodiments, the control system 1402 may not be included, in which case (multiple) radio units 1410 communicate directly with (multiple) processing nodes 1500 via suitable (multiple) network interfaces.

[0154] In some embodiments, a computer program containing instructions is provided that, when executed by at least one processor, causes at least one processor to perform the functionality of radio access node 1400 or a node (e.g., processing node 1500) implementing one or more functions 1510 of radio access node 1400 in a virtual environment, according to any embodiment described herein. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of electronic signals, optical signals, radio signals, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as memory).

[0155] Figure 16This is a schematic block diagram of a radio access node 1400 according to some other embodiments of the present disclosure. The radio access node 1400 includes one or more modules 1600, each module 1600 being implemented in software. The modules(multiple) Modules 1600 provide the functionality of the radio access node 1400 described herein. This discussion also applies to... Figure 15 The processing node 1500, wherein the module 1600 may be implemented in one of the processing nodes 1500 or distributed across multiple processing nodes 1500 and / or across (multiple) processing nodes 1500 and the control system 1402.

[0156] Figure 17 This 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., CPU, ASIC, FPGA, etc.), a memory 1704, and one or more transceivers 1706. Each transceiver 1706 includes one or more transmitters 1708 and one or more receivers 1710 coupled to one or more antennas 1712. As understood by those skilled in the art, the transceivers 1706 include radio front-end circuitry connected to the antennas 1712, configured to modulate signals communicating between the antennas 1712 and the processors 1702. The processor 1702 is also referred to herein as processing circuitry. The transceiver 1706 is also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 1700 described above may be implemented entirely or partially in software, which may be stored, for example, in the memory 1704 and executed by the processors 1702. Note that the wireless communication device 1700 may include... Figure 17 Additional components not shown, such as one or more user interface components (e.g., including a display, buttons, touch screen, microphone, speakers, etc. and / or any other components that allow information to be input to and / or output from the wireless communication device 1700, power supply (e.g., battery and associated power circuitry), etc.

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

[0158] Figure 18This 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 module 1800 being implemented in software. The modules(multiple) 1800 provide the functionality of the wireless communication device 1700 described herein.

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

[0160] Telecommunication network 1900 is itself connected to host 1916, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. Host 1916 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. Connections 1918 and 1920 between telecommunication network 1900 and host 1916 may extend directly from core network 1904 to host 1916, or via an optional intermediate network 1922. Intermediate network 1922 may be one or more of the following: a public, private, or hosted network; intermediate network 1922 may be a backbone network or the Internet, if any; specifically, intermediate network 1922 may include two or more subnetworks (not shown).

[0161] Figure 19The communication system as a whole enables connectivity between connected UEs 1912, 1914 and host 1916. This connectivity can be described as an over-the-top (OTT) connection 1924. Host 1916 and connected UEs 1912, 1914 are configured to use access network 1902, core network 1904, any intermediate network 1922 and other possible infrastructure (not shown) as intermediaries to transmit data and / or signaling via OTT connection 1924. OTT connection 1924 can be transparent because the participating communication devices traversed by OTT connection 1924 are unaware of the routes of uplink and downlink communications. For example, base station 1906 may not be informed or need not be informed of the past routes of incoming downlink communications carrying data from host 1916 to be forwarded (e.g., handed over) to connected UE 1912. Similarly, base station 1906 does not need to be aware of the future routes of outgoing uplink communications originating from UE 1912 to host 1916.

[0162] Now refer to Figure 20 Example implementations of the UE, base station, and host discussed in the preceding paragraphs are described according to embodiments. In communication system 2000, host computer 2002 includes hardware 2004, which includes a communication interface 2006 configured to establish and maintain wired or wireless connections to an interface of a communication device different from communication system 2000. Host computer 2002 also includes processing circuitry 2008, which may have storage and / or processing capabilities. Specifically, processing circuitry 2008 may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. Host computer 2002 also includes software 2010, which is stored in or accessible by host computer 2002 and executable by processing circuitry 2008. Software 2010 includes host application 2012. Host application 2012 can be used to provide services to remote users such as UE 2014 connected via OTT connection 2016 terminated at UE 2014 and host computer 2002. When providing services to remote users, Host Application 2012 can provide user data transmitted using OTT connection 2016.

[0163] The communication system 2000 also includes a base station 2018 provided in the telecommunications system. The base station 2018 includes hardware 2020 that enables it to communicate with the host computer 2002 and the UE 2014. The hardware 2020 may include: a communication interface 2022 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 2000; and a radio interface 2024 for establishing and maintaining connections with at least the coverage area served by the base station 2018. Figure 20The wireless connection 2026 of UE2014 (not shown in the diagram). Communication interface 2022 can be configured to facilitate connection 2028 to host computer 2002. Connection 2028 can be direct, or it can pass through the core network of the telecommunications system (…). Figure 20 (not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 2020 of the base station 2018 also includes processing circuitry 2030, which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) suitable for executing instructions. The base station 2018 also has software 2032 stored internally or accessible via an external connection.

[0164] The communication system 2000 also includes the previously mentioned UE 2014. The hardware 2034 of UE 2014 may include a radio interface 2036 configured to establish and maintain a wireless connection 2026 with a base station serving the coverage area currently occupied by UE 2014. The hardware 2034 of UE 2014 also includes processing circuitry 2038, which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) suitable for executing instructions. UE 2014 also includes software 2040, which is stored in or accessible by UE 2014 and executable by processing circuitry 2038. Software 2040 includes a client application 2042. Client application 2042 is operable to provide services to human or non-human users via UE 2014 with the support of host computer 2002. In host computer 2002, host application 2012 can communicate with client application 2042 via OTT connection 2016 terminated at UE 2014 and host computer 2002. When providing services to a user, client application 2042 can receive request data from host application 2012 and provide user data in response to the request data. OTT connection 2016 can transmit both request data and user data. Client application 2012 can interact with the user to generate the user data it provides.

[0165] Notice, Figure 18 The host computer 2002, base station 2018, and UE 2014 shown can be respectively connected to... Figure 19 The host computer 1916, base stations 1906A, 1906B, and 1906C are identical to one of the UEs 1912 and 1914. That is to say, the internal workings of these entities can be as follows: Figure 20 As shown, and independently, the surrounding network topology can be Figure 19 The network topology.

[0166] exist Figure 20The OTT connection 2016 has been abstractly depicted to illustrate communication between host computer 2002 and UE 2014 via base station 2018, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine this route, which can be configured to be hidden from UE 2014, from the service provider operating host computer 2002, or from both. During OTT connection 2016 activity, the network infrastructure can also make decisions to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0167] The wireless connection 2026 between UE 2014 and base station 2018 is based on the teachings of the embodiments described throughout this disclosure. One or more embodiments in the various embodiments improve the performance of OTT services provided to UE 2014 using OTT connection 2016, wherein wireless connection 2026 forms the final segment of OTT connection 2016. More precisely, the teachings of these embodiments can improve, for example, data rates, latency, power consumption, etc., thereby providing benefits such as reduced user wait time, relaxed file size limits, better responsiveness, and extended battery life.

[0168] For the purpose of monitoring data rates, latency, and other factors improved in one or more embodiments, a measurement process may be provided. Optional network functions may also be available for reconfiguring the OTT connection 2016 between the host computer 2002 and the UE 2014 in response to changes in measurement results. The measurement process and / or network functions for reconfiguring the OTT connection 2016 may be implemented using software 2010 and hardware 2004 of the host computer 2002, or software 2040 and hardware 2034 of the UE 2014, or both. In some embodiments, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 2016 passes; the sensor may participate in the measurement process by providing values ​​of the monitored quantities illustrated above or by providing values ​​of other physical quantities that the software 2010, 2040 may use to calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 2016 may include message formatting, retransmission settings, preferred routing, etc.; this reconfiguration does not need to affect the base station 2018, and it may be unknown or imperceptible to the base station 2018. Such processes and functions may be known and practiced in the art. In a particular embodiment, measurement may involve proprietary UE signaling that facilitates the host computer 2002 to measure throughput, propagation time, latency, etc. This measurement may be implemented as follows: software 2010 and 2040 enable the OTT connection 2016 to send messages, specifically empty messages or "fake" messages, while monitoring propagation time, errors, etc.

[0169] Figure 21 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may be a reference... Figure 19 and Figure 20 Those described include host computers, base stations, and UEs. For the sake of brevity, this section will only include descriptions of... Figure 21 The diagram is referenced. In step 2100, the host computer provides user data. In sub-step 2102 of step 2100 (which may be optional), the host computer provides user data by executing a host application. In step 2104, the host computer initiates a transmission carrying user data to the UE. In step 2106 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 2108 (which may be optional), the UE executes a client application associated with the host application executed by the host computer.

[0170] Figure 22 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may be a reference... Figure 19 and Figure 20 Those described include host computers, base stations, and UEs. For the sake of brevity, this section will only include descriptions of... Figure 22 The diagram is referenced. In step 2200 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 2202, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, this transmission may be via a base station. In step 2204 (which may be optional), the UE receives the user data carried in the transmission.

[0171] Figure 23 This is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes: a host computer, a base station, and a UE, which may be referenced... Figure 19 and Figure 20 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include... Figure 23Reference numerals are used in the accompanying drawings. In step 2300 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2302 (which may be optional), the UE provides user data. In sub-step 2304 of step 2300 (which may be optional), the UE provides user data by executing a client application. In sub-step 2306 of step 2302 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates the transmission of 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 sent from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0172] Figure 24 This is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes: a host computer, a base station, and a UE, which may be referenced... Figure 19 and Figure 20 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section will only include... Figure 24 Reference numerals are used in the accompanying drawings. 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 a transmission of user data to the host computer. In step 2404 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0173] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such 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), application-specific digital logic, etc. 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, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In some implementations, the processing circuitry may be used to cause various functional units to perform corresponding functions according to one or more embodiments of this disclosure.

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

[0175] Example

[0176] Group A Examples

[0177] Example 1: A method performed by a wireless device for transmitting a non-codebook-based Physical Uplink Shared Channel (PUSCH), the method comprising one or more of the following: receiving (500) a configuration of a first or second Uplink UL Phase Tracking Reference Signal (PT-RS) port index according to SRS resources in at most two Probe Reference Signal (SRS) resource sets; receiving (502) an indication of at least one of the following: a first SRS Resource Indicator (SRI) set from a first SRS resource set; and a second SRI set from a second SRS resource set; determining (504) at least one of the following: i. a first number of UL PT-RS ports to be transmitted according to the SRS resources indicated in the first SRI set; and ii. a second number of UL PT-RS ports to be transmitted according to the SRS resources indicated in the second SRI set; and transmitting (506) the number of UL PT-RS ports determined together with a plurality of PUSCH repetitions.

[0178] Example 2: According to the method of Example 1, the first PUSCH repeat subset is transmitted according to the SRS resources indicated in the first SRI set, and the first PUSCH repeat subset includes the transmission of a first number of UL PT-RS ports.

[0179] Example 3: According to the method of Example 1, a second PUSCH repeat subset detached from the first PUSCH repeat subset is transmitted according to the SRS resources indicated in the second SRI set, and the second PUSCH repeat subset includes the transmission of a second number of UL PT-RS ports.

[0180] Example 4: According to the method of Example 1, all PUSCH repeats are transmitted according to the SRS resources indicated in the first SRI set, and the PUSCH repeats include the transmission of a first number of UL PT-RS ports.

[0181] Example 5: According to the method of Example 1, all PUSCH repeats are transmitted according to the SRS resources indicated in the second SRI set, and the PUSCH repeats include the transmission of a second number of UL PT-RS ports.

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

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

[0184] Example 8: According to the method of any one of Examples 1 to 7, wherein when the SRS resources indicated in the first SRI set all have the same configured PT-RS port index, the first number of UL PT-RS ports is determined to be 1.

[0185] Example 9: According to the method of any one of Examples 1 to 7, wherein when the SRS resources indicated in the second SRI set all have the same configured PT-RS port index, the second number of UL PT-RS ports is determined to be 1.

[0186] Example 10: According to the method of any one of Examples 1 to 7, wherein when the SRS resource indicated in the first SRI set has two different configured PT-RS port index values, the first number of UL PT-RS ports is determined to be 2.

[0187] Example 11: According to the method of any one of Examples 1 to 7, wherein when the SRS resource indicated in the second SRI set has two different configured PT-RS port index values, the second number of UL PT-RS ports is determined to be 2.

[0188] Example 12: According to any one of Examples 1 to 11, the first SRI set and the second SRI set are indicated by the first SRI field and the second SRI field in the downlink control indicator DCI that is repeated by the scheduling PUSCH, respectively.

[0189] Example 13: The method according to any one of Examples 1 to 11, wherein the first SRI set and the second SRI set are indicated via a first index and a second index, respectively, and the first index and the second index are configured as part of the configured authorized PUSCH configuration.

[0190] Example 14: The method according to any one of Examples 1 to 13, wherein the first SRS resource set corresponds to the first transmitting and receiving point (TRP), and the second SRS resource set corresponds to the second TRP.

[0191] Example 15: The method according to any of the preceding embodiments further includes: providing user data; and forwarding the user data to a host computer via transmission to a base station.

[0192] Group B Implementation Examples

[0193] Example 16: A method for receiving a non-codebook-based Physical Uplink Shared Channel (PUSCH) performed by a base station, the method comprising: transmitting (600) a configuration of a first or second uplink UL phase tracking reference signal (PT-RS) port index according to SRS resources in at most two probe reference signal (SRS) resource sets; transmitting (602) an indication of at least one of the following: a first SRS resource indicator (SRI) set from a first SRS resource set; and a second SRI set from a second SRS resource set; determining (604) at least one of the following: i. a first number of UL PT-RS ports to be received according to the SRS resources indicated in the first SRI set; and ii. a second number of UL PT-RS ports to be received according to the SRS resources indicated in the second SRI set; and receiving (606) the number of UL PT-RS ports determined together with a plurality of PUSCH repetitions.

[0194] Example 17: According to the method of Example 16, wherein a first PUSCH repeat subset is received according to the SRS resources indicated in the first SRI set, and the first PUSCH repeat subset includes the reception of a first number of UL PT-RS ports.

[0195] Example 18: According to the method of Example 16, a second PUSCH repeat subset detached from the first PUSCH repeat subset is received according to the SRS resources indicated in the second SRI set, and the second PUSCH repeat subset includes the reception of a second number of UL PT-RS ports.

[0196] Example 19: According to the method of Example 16, all PUSCH repeats are received according to the SRS resources indicated in the first SRI set, and the PUSCH repeats include the reception of a first number of UL PT-RS ports.

[0197] Example 20: According to the method of Example 16, all PUSCH repeats are transmitted according to the SRS resources indicated in the second SRI set, and the PUSCH repeats include the transmission of a second number of UL PT-RS ports.

[0198] Example 21: The method according to any one of Examples 16 to 18, wherein the first number of UL PT-RS ports is the same as the second number of UL PT-RS ports.

[0199] Example 22: The method according to any one of Examples 16 to 18, wherein the first number of UL PT-RS ports is different from the second number of UL PT-RS ports.

[0200] Example 23: According to the method of any one of Examples 16 to 22, wherein when the SRS resources indicated in the first SRI set all have the same configured PT-RS port index, the first number of UL PT-RS ports is determined to be 1.

[0201] Example 24: According to the method of any one of Examples 16 to 22, wherein when the SRS resource indicated in the second SRI set has two different configured PT-RS port index values, the second number of UL PT-RS ports is determined to be 2.

[0202] Example 25: According to any one of Examples 16 to 24, the first SRI set and the second SRI set are indicated by the first SRI field and the second SRI field in the downlink control indicator DCI repeated by the scheduling PUSCH, respectively.

[0203] Example 26: The method according to any one of Examples 16 to 24, wherein the first SRI set and the second SRI set are indicated via a first index and a second index, respectively, and the first index and the second index are configured as part of the configured authorized PUSCH configuration.

[0204] Example 27: The method according to any one of Examples 16 to 26, wherein the first SRS resource set corresponds to the first transmitting and receiving point (TRP), and the second SRS resource set corresponds to the second TRP.

[0205] Example 28: The method according to any of the previous embodiments further includes: acquiring user data; and forwarding the user data to a host computer or a wireless device.

[0206] Group C Implementation Examples

[0207] Example 29: A wireless device for non-codebook-based Physical Uplink Shared Channel (PUSCH) transmission, the wireless device comprising: processing circuitry configured to perform any step of any of the Group A embodiments; and power supply circuitry configured to supply power to the wireless device.

[0208] Example 30: A base station for receiving a non-codebook-based Physical Uplink Shared Channel (PUSCH), the base station comprising: processing circuitry configured to perform the steps of any one of the Group B examples; and power supply circuitry configured to supply power to the base station.

[0209] Example 31: A user equipment (UE) for non-codebook-based Physical Uplink Shared Channel (PUSCH) transmission, the UE comprising: an antenna configured to transmit and receive radio signals; a radio front-end circuit connected to the antenna and the processing circuit, configured to modulate signals communicating between the antenna and the processing circuit; a processing circuit configured to perform any one of the steps in any of the Group A embodiments; an input interface connected to the processing circuit, configured to allow information to be input to the UE to be processed by the processing circuit; an output interface connected to the processing circuit, configured to output information already processed by the processing circuit from the UE; and a battery connected to the processing circuit, configured to power the UE.

[0210] Example 32: A communication system including a host computer includes: processing circuitry configured to provide user data; and a communication interface configured to forward 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 processing circuitry, the processing circuitry of the base station being configured to perform any one of the steps in any of the Group B examples.

[0211] Example 33: The communication system according to the previous embodiment also includes a base station.

[0212] Example 34: The communication system according to the previous two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.

[0213] Example 35: A communication system according to the previous three embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application to provide user data; and the UE includes processing circuitry configured to execute a client application associated with the host application.

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

[0215] Example 37: The method according to the previous embodiment further includes transmitting user data at the base station.

[0216] Example 38: According to the method of the previous two embodiments, wherein user data is provided by executing a host application at a host computer, the method further includes executing a client application associated with the host application at the UE.

[0217] Example 39: A user equipment (UE) configured to communicate with a base station, the UE including a radio interface and processing circuitry configured to perform the methods of the preceding three embodiments.

[0218] Example 40: A communication system including a host computer includes: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE); wherein the UE includes a radio interface and processing circuitry, and the components of the UE are configured to perform any one of the steps in any of the Group A examples.

[0219] Example 41: A communication system according to a previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

[0220] Example 42: A communication system according to the previous two embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application to provide user data; and the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0221] Example 43: A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at the host computer; and initiating a transmission carrying the user data to the UE via a cellular network including the base station at the host computer, wherein the UE performs any one of the steps in any of the Group A examples.

[0222] Example 44: The method according to the previous embodiment further includes receiving user data from the base station at the UE.

[0223] Example 45: A communication system including a host computer includes: a communication interface configured to receive user data transmitted from a user equipment (UE) to a base station; wherein the UE includes a radio interface and processing circuitry, the processing circuitry of the UE being configured to perform any one of the steps in any of the Group A examples.

[0224] Example 46: The communication system according to the previous embodiment also includes a UE.

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

[0226] Example 48: A communication system according to the previous 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.

[0227] Example 49: A communication system according to the previous four embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application to provide requested data; and the processing circuitry of the UE is configured to execute a client application associated with the host application to provide user data in response to the requested data.

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

[0229] Example 51: The method according to the previous embodiment further includes providing user data to the base station at U.

[0230] Example 52: The method according to the previous two embodiments further includes: at the UE, executing a client application to provide user data to be transmitted; and at the host computer, executing a client application associated with a host application.

[0231] Example 53: The method according to the previous three embodiments further includes: executing a client application at the UE; and receiving input data to the client application at the UE, the input data being provided by executing a host application associated with the client application at a host computer; wherein user data to be transmitted is provided by the client application in response to the input data.

[0232] Example 54: A communication system including a host computer, including a communication interface configured to receive user data transmitted from a user equipment (UE) to a base station, wherein the base station includes a radio interface and processing circuitry configured to perform any one of the steps in any of the Group B examples.

[0233] Example 55: The communication system according to the previous embodiment further includes a base station.

[0234] Example 56: The communication system according to the previous two embodiments further includes a UE, wherein the UE is configured to communicate with a base station.

[0235] Example 57: A communication system according to the previous 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 to be received by the host computer.

[0236] Example 58: A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: at the host computer, receiving from the base station user data transmitted from the base station that has already been received from the UE, wherein the UE performs any one of the steps in any of the Group A examples.

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

[0238] Example 60: The method according to the previous two embodiments further includes, at the base station, initiating the transmission of the received user data to the host computer.

[0239] In this disclosure, at least some of the following abbreviations may be used. In the event of inconsistencies between abbreviations, the abbreviation used above shall prevail. If abbreviations are listed multiple times below, the first list shall prevail over any subsequent list(s).

[0240] ·3GPP Third Generation Partnership Program

[0241] 5G (Fifth Generation)

[0242] ·5GC fifth-generation core

[0243] ·5GS Fifth Generation System

[0244] ·AF Application Functions

[0245] • AMF Access and Mobility Functions

[0246] ·AN access network

[0247] AP access point

[0248] Application-Specific Integrated Circuits (ASICs)

[0249] • AUSF Authentication Server Functionality

[0250] CPU (Central Processing Unit)

[0251] DN Data Network

[0252] DSP (Digital Signal Processor)

[0253] • eNB Enhanced or Evolved Node B

[0254] • EPS Evolution of Grouping System

[0255] E-UTRA evolved universal terrestrial radio access

[0256] FPGA (Field Programmable Gate Array)

[0257] gNB New Radio Base Station

[0258] gNB-DU New Type of Distributed Radio Base Station Unit

[0259] HSS (Home Server)

[0260] IoT (Internet of Things)

[0261] Protocols for interconnecting IP networks

[0262] LTE Long Term Evolution

[0263] •MME (Mobility Management Entity)

[0264] • MTC Machine Type Communication

[0265] • NEF Network Open Functionality

[0266] NF Network Functions

[0267] NR New Radio

[0268] • NRF Network Functions Repository Functionality

[0269] NSSF Network Slice Selection Function

[0270] • OTT over-the-top

[0271] PC (Personal Computer)

[0272] PCF policy control function

[0273] P-GW Packet Data Network Gateway

[0274] QoS (Quality of Service)

[0275] RAM (Random Access Memory)

[0276] RAN (Radio Access Network)

[0277] ROM (Read-Only Memory)

[0278] ·RRH Remote Wireless Head

[0279] ·RTT Round Trip Time

[0280] • SCEF service capability opening function

[0281] • SMF Session Management Function

[0282] UDM (Unified Data Management)

[0283] UE (User Equipment)

[0284] UPF User Plane Function

[0285] Those skilled in the art will recognize improvements and modifications to embodiments of this disclosure, all of which are considered to be within the scope of the concepts disclosed herein.

Claims

1. A method performed by a wireless device (1700) for non-codebook-based Physical Uplink Shared Channel (PUSCH) transmission, the method comprising: According to the configuration of the first or second uplink UL phase tracking reference signal PT-RS port index, the SRS resources in the multiple SRS resources configured in the two probe reference signal SRS resource sets for non-codebook-based PUSCH are received (500). Receive (502) an instruction of at least one of the following: a first SRS resource indicator (SRI) set indicating SRS resources from a first SRS resource set; and a second SRI set indicating SRS resources from a second SRS resource set; Determine (504) at least one of the following: The first number of ULPT-RS ports to be transmitted according to the SRS resources indicated in the first SRI set; and The second number of ULPT-RS ports to be transmitted according to the SRS resources indicated in the second SRI set; and The number of UL PT-RS ports determined by transmission (506) are repeated along with multiple PUSCHs.

2. The method of claim 1, wherein a first subset of the plurality of PUSCH repeats is transmitted according to the SRS resource indicated in the first SRI set, and the first subset of PUSCH repeats includes transmissions of the first number of UL PT-RS ports.

3. The method of claim 1, wherein a second PUSCH repeat subset detached from the first PUSCH repeat subset is transmitted according to the SRS resource indicated in the second SRI set, and the second PUSCH repeat subset includes the transmission of the second number of UL PT-RS ports.

4. The method of claim 1, wherein the plurality of PUSCH repeats are transmitted according to the SRS resources indicated in the first SRI set, and the plurality of PUSCH repeats include transmissions of the first number of UL PT-RS ports.

5. The method of claim 1, wherein the plurality of PUSCH repeats are transmitted according to the SRS resources indicated in the second SRI set, and the plurality of PUSCH repeats include transmissions of the second number of UL PT-RS ports.

6. The method according to any one of claims 1 to 3, wherein the first number of UL PT-RS ports is the same as the second number of UL PT-RS ports.

7. The method according to any one of claims 1 to 3, wherein the first number of UL PT-RS ports is different from the second number of UL PT-RS ports.

8. The method according to any one of claims 1 to 7, wherein the first number of UL PT-RS ports is determined to be 1 when the SRS resources indicated in the first SRI set all have the same configured PT-RS port index.

9. The method according to any one of claims 1 to 7, wherein when the SRS resources indicated in the second SRI set all have the same configured PT-RS port index, the second number of UL PT-RS ports is determined to be 1.

10. The method according to any one of claims 1 to 7, wherein when the SRS resource indicated in the first SRI set has two different configured PT-RS port index values, the first number of UL PT-RS ports is determined to be 2.

11. The method according to any one of claims 1 to 7, wherein when the SRS resource indicated in the second SRI set has two different configured PT-RS port index values, the second number of UL PT-RS ports is determined to be 2.

12. The method according to any one of claims 1 to 11, wherein the first SRI set and the second SRI set are indicated via a first SRI field and a second SRI field in a downlink control indicator (DCI) that schedules the PUSCH repetition.

13. The method according to any one of claims 1 to 11, wherein the first SRI set and the second SRI set are indicated via a first index and a second index, respectively, the first index and the second index being configured as part of a configured authorized PUSCH configuration.

14. The method according to any one of claims 1 to 13, wherein the first SRS resource set corresponds to a first transmit and receive point (TRP), and the second SRS resource set corresponds to a second TRP.

15. The method according to any one of claims 1 to 14, wherein the wireless device (1700) operates in a fifth-generation 5G new radio (NR) network.

16. A method for receiving a non-codebook-based Physical Uplink Shared Channel (PUSCH) performed by a base station (1400), the method comprising: According to the SRS resources configured in the multiple SRS resources of the two probe reference signal SRS resource sets for non-codebook-based PUSCH, transmit (600) the configuration of the first or second uplink UL phase tracking reference signal PT-RS port index; Transmit (602) an indication of at least one of the following: a first SRS Resource Indicator (SRI) set indicating an SRS resource from a first SRS resource set; and a second SRI set indicating an SRS resource from a second SRS resource set; Determine (604) at least one of the following: The first number of ULPT-RS ports to be received according to the SRS resources indicated in the first SRI set; and The second number of ULPT-RS ports to be received according to the SRS resources indicated in the second SRI set; as well as The number of UL PT-RS ports determined by (606) are repeated along with multiple PUSCHs.

17. The method of claim 16, wherein a first subset of the plurality of PUSCH repeats is received according to the SRS resource indicated in the first SRI set, and the first subset of PUSCH repeats includes reception of the first number of UL PT-RS ports.

18. The method of claim 16, wherein a second subset of PUSCH repeats, which is separated from the first subset of PUSCH repeats, is received according to the SRS resource indicated in the second SRI set, and the second subset of PUSCH repeats includes reception of the second number of UL PT-RS ports.

19. The method of claim 16, wherein the plurality of PUSCH repeats are received according to the SRS resources indicated in the first SRI set, and the plurality of PUSCH repeats include reception of the first number of UL PT-RS ports.

20. The method of claim 16, wherein the plurality of PUSCH repeats are transmitted according to the SRS resources indicated in the second SRI set, and the plurality of PUSCH repeats include transmissions of the second number of UL PT-RS ports.

21. The method according to any one of claims 16 to 18, wherein the first number of UL PT-RS ports is the same as the second number of UL PT-RS ports.

22. The method according to any one of claims 16 to 18, wherein the first number of UL PT-RS ports is different from the second number of UL PT-RS ports.

23. The method according to any one of claims 16 to 22, wherein the first number of UL PT-RS ports is determined to be 1 when the SRS resources indicated in the first SRI set all have the same configured PT-RS port index.

24. The method according to any one of claims 16 to 22, wherein when the SRS resource indicated in the second SRI set has two different configured PT-RS port index values, the second number of UL PT-RS ports is determined to be 2.

25. The method of any one of claims 16 to 24, wherein the first SRI set and the second SRI set are indicated via a first SRI field and a second SRI field in a downlink control indicator (DCI) that schedules the PUSCH repetition.

26. The method of any one of claims 16 to 24, wherein the first SRI set and the second SRI set are indicated via a first index and a second index, respectively, the first index and the second index being configured as part of a configured authorized PUSCH configuration.

27. The method according to any one of claims 16 to 26, wherein the first SRS resource set corresponds to a first transmit and receive point (TRP), and the second SRS resource set corresponds to a second TRP.

28. A wireless device (1700) comprising one or more processors (1702), said one or more processors (1702) being configured to cause the wireless device (1700) to: The configuration of receiving the first or second uplink UL phase tracking reference signal PT-RS port index is based on the SRS resources configured in the two probe reference signal SRS resource sets for non-codebook-based PUSCH. Receive an instruction of at least one of the following: a first SRS Resource Indicator (SRI) set indicating SRS resources from a first SRS resource set; and a second SRI set indicating SRS resources from a second SRS resource set; Determine at least one of the following: The first number of ULPT-RS ports to be transmitted according to the SRS resources indicated in the first SRI set; as well as The second number of ULPT-RS ports to be transmitted according to the SRS resources indicated in the second SRI set; as well as The transmission uses a defined number of UL PT-RS ports along with multiple PUSCH repeats.

29. The wireless device (1700) of claim 28, wherein the one or more processors (1702) are further configured to cause the wireless device (1700) to perform any one of the steps of any one of claims 2 to 15.

30. A base station (1400) comprising one or more processors (1402), said one or more processors (1402) being configured to cause the base station (1400) to: The configuration of transmitting the first or second uplink UL phase tracking reference signal PT-RS port index according to the SRS resources in the multiple SRS resources configured in the two probe reference signal SRS resource sets for non-codebook-based PUSCH; Transmit an indication of at least one of the following: a first SRS Resource Indicator (SRI) set indicating an SRS resource from a first SRS resource set; and a second SRI set indicating an SRS resource from a second SRS resource set; Determine at least one of the following: The first number of ULPT-RS ports to be received according to the SRS resources indicated in the first SRI set; as well as The second number of ULPT-RS ports to be received according to the SRS resources indicated in the second SRI set; as well as The determined number of UL PT-RS ports are received along with multiple PUSCH repeats.

31. The base station (1400) according to claim 30, wherein the one or more processors (1402) are further configured to cause the base station (1400) to perform any step of any of claims 17 to 27.

Images