Methods, systems, and apparatus for 3TX uplink operation

Abstract

Some embodiments herein include enhancements for 3Tx uplink operation. In some embodiments, a UE may send, to a network node, a capability report indicating support for 3 Transmit Antennas (3Tx) Physical Uplink Shared Channel (PUSCH) operation. The UE may receive a sounding reference signal (SRS) configuration for the 3Tx PUSCH operation, and transmit SRS resources in the SRS Resource Set with one or more SRS ports. The UE may receive a PUSCH configuration that schedules the 3Tx PUSCH operation based on the transmitted one or more SRS resources.

Description

METHODS, SYSTEMS, AND APPARATUS FOR 3TX UPLINK OPERATION TECHNICAL FIELD

[0001] This application relates generally to wireless communication systems, including the implementation of 3Tx based operation. BACKGROUND

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wireless Local Area Networks (WLAN) (commonly known to industry groups as Wi-Fi®).

[0003] As contemplated by the 3GPP, different wireless communication systems' standards and protocols can use various radio access networks (RANs) for communicating between a base station of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE). 3GPP RANs can include, for example, Global System for Mobile communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next-Generation Radio Access Network (NG-RAN).

[0004] Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements Universal Mobile Telecommunication System (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR). In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.

[0005] A base station used by a RAN may correspond to that RAN. One example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-1 4924-5092-6383\1 P66895WO2UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB). One example of an NG-RAN base station is a next generation Node B (also sometimes referred to as a g Node B or gNB).

[0006] A RAN provides its communication services with external entities through its connection to a core network (CN). For example, E-UTRAN may utilize an Evolved Packet Core (EPC) while NG-RAN may utilize a 5G Core Network (5GC). BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0007] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0008] FIG. 1 illustrates a table for interpreting a value of a precoding information and number of layers field in accordance with some embodiments.

[0009] FIG. 2 illustrates an example table for interpreting a precoding information and number of layers field, for 3 antenna ports, if transform precoder is disabled and maxRank equal to 2 or 3 in accordance with some embodiments.

[0010] FIG. 3 illustrates an example of a sounding reference signal (SRS) sequence in accordance with some embodiments.

[0011] FIG. 4 illustrates example port configurations in accordance with some embodiments.

[0012] FIG. 5 illustrates a table for interpreting a value of the “PTRS-DMRS association” field in accordance with some embodiments.

[0013] FIG. 6 illustrates a table for interpreting a value of the “PTRS-DMRS association” field in accordance with some embodiments.

[0014] FIG. 7 illustrates a method performed by a UE, according to embodiments herein.

[0015] FIG. 8 illustrates a method performed by a network node, according to embodiments herein.

[0016] FIG. 9 illustrates a method performed by a UE, according to embodiments herein.

[0017] FIG. 10 illustrates a method performed by a network node, according to embodiments herein.2 4924-5092-6383\1 P66895WO2

[0018] FIG. 11 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.

[0019] FIG. 12 illustrates a system for performing signaling between a wireless device and a network device, according to embodiments disclosed herein. DETAILED DESCRIPTION

[0020] Some wireless communication devices may include multiple antennas. Wireless communication systems may support uplink transmission modes that are classified by how many antennas are used for the transmission (e.g., 1Tx, 2Tx, and 4Tx). It may be desirable to support 3Tx uplink operation. Accordingly, embodiments herein provide sounding reference signals (SRS) and phase tracking reference signal (PTRS) enhancement for 3Tx codebook based physical uplink shared channel (PUSCH) operation. Some embodiments, provide methods, systems, and apparatuses for 3Tx uplink operation.

[0021] Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.

[0022] In some wireless communication systems, new radio (NR) uplink (UL) physical uplink shared channel (PUSCH) operation supports two multiple input multiple output (MIMO) operation modes: Codebook and nonCodebook. In codebook based PUSCH operation, the network may configure a sounding reference signal (SRS) resource set (SRS-ResourceSet) with usage = “codebook”. The UE may then transmit one or more SRS resources (SRS-Resource) in the SRS-ResourceSet with usage = “codebook” with one or multiple SRS ports. The network may schedule the PUSCH by indicating the SRS resource for the codebook based PUSCH transmission reference in, for example, an “SRS resource indicator (SRI)” field where one SRS resource is indicated for codebook based PUSCH transmission. The network may also schedule the PUSCH by indicating the precoder including the number of layers to be applied for the PUSCH in, for example3 4924-5092-6383\1 P66895WO2a “precoding information and number of layers” (transmit precoding matrix indicator (TPMI)) field.

[0023] The second MIMO operation mode supported includes nonCodebook based PUSCH operation. The network may configure an SRS resource set (SRS-ResourceSet) with usage = “nonCodebook”. The UE may then transmit one or multiple SRS resources (SRS-Resource) in the SRS-ResourceSet with usage = “nonCodebook” with a single SRS port. The network schedules the PUSCH by indicating the precoder including the number of layers to be applied for the PUSCH in, for example, a “SRS resource indicator (SRI)” field where one or more SRS resources may be indicated for nonCodebook based PUSCH transmission.

[0024] The number of transmit antennas (Tx) supported for PUSCH operation may be different based on the wireless communication system. In Rel-15, 1Tx, 2Tx and 4Tx are supported. For 1Tx codebook based PUSCH operation, a non-coherent codebook may be used. For 2Tx codebook based PUSCH operation, a non-coherent and a full-coherent codebook may be used. For 4Tx codebook based PUSCH operation, a non-coherent, a partial-coherent and a full-coherent codebook may be used. In Rel-18, 8Tx may be supported. For 8Tx codebook based PUSCH operations, (1) codebook1, i.e., full- coherent codebook, (2) codebook2, i.e., partial-coherent codebook with 2 coherent antenna port groups, (3) codebook3, i.e., partial-coherent codebook with 4 coherent antenna port groups, (4) codebook4, i.e., non-coherent codebook are used.

[0025] Embodiments herein discuss the support of and details of 3Tx UL PUSCH operation. For example, details discussed herein include support of codebook based PUSCH, support of nonCodebook based PUSCH, and support of SRS antenna switching.

[0026] Support of codebook based PUSCH

[0027] In some embodiments, for non-coherent codebook based 3Tx PUSCH operation, one or multiple of the following precoding matrices may be supported. For example, for 10 0rank set equal to 1 the following precoding matrices may be supported:൭0^ ,൭1^ ,൭0^.0 0 1For rank set equal to 2 the following precoding matrices may be4 4924-5092-6383\1 P66895WO21 0 1 0 0 0supported: ൭0 1^ ,൭0 0^ ,൭1 0^. For rank set equal to 3 the following precoding0 0 0 1 0 11 0 0matrices may be supported: ൭0 1 0^.0 0 1

[0028] In some embodiments, when the UE reports that the UE supports codebook based 3Tx PUSCH operation, the UE may report that the UE supports a maximum of three layers. It may be noted that before Rel-19, for 1Tx, 2Tx, and 4Tx operation, the UE may not be allowed to report that the UE supports a maximum of three layers. An example report, transmitted by the UE, that the UE supports a maximum of three layers is given as follows: maxNumberMIMO-LayersCB-PUSCH MIMO-LayersUL MIMO-LayersUL-r19 ::= ENUMERATED {oneLayer, twoLayers, threeLayers, fourLayers}

[0029] This report may allow the UE to report that it supports maximum one layer, two layers, three layers, or four layers.

[0030] In some embodiments, when the UE reports that the UE supports codebook based 3Tx PUSCH operation, various examples may be used regarding the coherency mode when the network configures the UE to operate with codebook based 2Tx PUSCH operation. In some examples, the UE may further report the coherency mode when the UE is downgraded from a codebook based 3Tx PUSCH to a codebook based 2Tx PUSCH. The candidate coherency mode may take the form of: {nonCoherent, fullCoherent}. In some other examples, the UE may be configured for non-coherent codebook based 2Tx PUSCH operation.

[0031] In some embodiments, when the UE is configured with the codebook based 3Tx PUSCH operation, for the “precoding information and number of layers” field, when a maxRank field is equal to one, the bitwidth of the “precoding information and number of layers” field is two bits in length with an interpretation according to the table 102 shown in FIG. 1. Table 102, shows Precoding Information and Number of Layers, for Three Antenna Ports, if Transform Precoder is Disabled and maxRank =1.5 4924-5092-6383\1 P66895WO2

[0032] FIG. 1 also shows matrices that may be configured for various rank and TPMI 10 0values. For rank = 1 TPMI=0൭0^, TPMI=1൭1^, TPMI=2൭0^. For rank = 200 11 0 1 0 0 0TPMI=0൭0 1^, TPMI=1൭0 0^, TPMI=2൭1 0^, and for rank = 30 0 0 1 0 11 0 0TPMI=0 ൭0 1 0^.0 0 1

[0033] Note that the maxRank field may be configured in the PUSCH-Config.

[0034] As shown in the table 102, in some embodiments, when the bit field of the precoding information and number of layers field is set to zero and the max rank is equal to one, it may indicate that the UE is to use 1 layer and TPMI=0. In some embodiments, when the bit field is set to one and the max rank is equal to one, it may indicate that the UE is to use 1 layer and TPMI=1. In some embodiments, when the bit field is set to two and the max rank is equal to one, it may indicate that the UE is to use 1 layer and TPMI=2. A value of three may be reserved.

[0035] FIG. 2 illustrates an example table 202 for interpreting a precoding information and number of layers field, for 3 antenna ports, if transform precoder is disabled and maxRank equal to 2 or 3 in accordance with some embodiments.

[0036] In some embodiments, when the UE is configured with codebook based 3Tx PUSCH operation, for the “precoding information and number of layers” field, when the maxRank is equal to 2 or 3, the bitwidth of the “precoding information and number of layers” field is 3 bits and the bits may be interpreted according to the table 202 in FIG. 2.

[0037] Additionally, the following matrices may be configured for various rank and 10 0TPMI values. For rank = 1 TPMI=0൭0^, TPMI=1 ൭1^, TPMI=2 ൭0^, For rank = 200 11 0 1 0 0 0TPMI=0 ൭0 1^, TPMI=1൭0 0^, TPMI=2൭1 0^, and for rank = 30 0 0 1 0 11 0 0TPMI=0 ൭0 1 0^.0 0 1

[0038] As shown in the table 202, in some embodiments, when the bit field of the precoding information and number of layers field is set to zero, it may indicate that the UE is to use 1 layer and TPMI=0. In some embodiments, when the bit field is set to one,6 4924-5092-6383\1 P66895WO2it may indicate that the UE is to use 1 layer and TPMI=1. In some embodiments, when the bit field is set to two, it may indicate that the UE is to use 1 layer and TPMI=2. In some embodiments, when the bit field is set to three, it may indicate that the UE is to use 2 layer and TPMI=0. In some embodiments, when the bit field is set to four, it may indicate that the UE is to use 2 layer and TPMI=1. In some embodiments, when the bit field is set to five, it may indicate that the UE is to use 2 layer and TPMI=2. In some embodiments, when the bit field is set to six, it may indicate that the UE is to use 3 layer and TPMI=0. A value of seven may be reserved.

[0039] In some embodiments, for codebook based 3Tx PUSCH operation, full power transmission mode 0 may be supported. For example, full power transmission mode 0 performs power scaling with the factor s=1 for UL precoders (i.e., TPMI) with 3Tx codebook based PUSCH operation. Additionally, the network is allowed to configure either no full power transmission or full power transmission mode 0, where the full power transmission mode is configured in the PUSCH-Config. An example may be given as: ul-FullPowerTransmission-r19 ENUMERATED {fullpower} OPTIONAL, -- Need R

[0040] In some cases, when the UE reports that the UE supports 3Tx codebook based PUSCH operation, the UE may further report whether the UE supports full power transmission mode 0. In some examples, the full power transmission mode 0 for 3Tx codebook based PUSCH operation is reported independently as a Rel-19 UE capability. In some other examples, the full power transmission mode 0 for 3Tx codebook based PUSCH operation is reported reusing current UE capabilities (i.e., either using a Rel-16 or a Rel-18 UE capability).

[0041] Support of nonCodebook based PUSCH

[0042] In some embodiments, when the UE reports that the UE supports nonCodebook based 3Tx PUSCH operation, the UE may report that the UE supports a maximum of three layers. Note that before Rel-19, for 1Tx, 2Tx, and 4Tx operation, the UE was not allowed to report that the UE supports a maximum of three layers. An example of reporting may be given as: maxNumberMIMO-LayersNonCB-PUSCH MIMO-LayersUL OPTIONAL,7 4924-5092-6383\1 P66895WO2MIMO-LayersUL-r19 ::= ENUMERATED {oneLayer, twoLayers, threeLayers, fourLayers}

[0043] In some embodiments, when the UE reports that the UE supports nonCodebook based 3Tx PUSCH operation, the UE may report various capabilities including the maximum number of SRS resources that can be configured in the same SRS-ResourceSet with usage = “nonCodebook” and the maximum number of simultaneous transmitted SRS resources at one symbol. These capabilities may be reported independently from the previously used reporting (i.e., as a Rel-19 UE feature). In some examples, there is no candidate value, (i.e., “support” or “not support”). If the UE reports the capability, the UE supports three SRS resources. In some other examples, the candidate values may be {1, 2, 3}.

[0044] Support of SRS antenna switching

[0045] In some embodiments, for 3Tx operation, a 3T6R operation may be supported as well as a basic 3T6R configuration may be supported. For example, the UE may be configured with up to two SRS-ResourceSets with usage = “antennaSwitching”. Each SRS-ResourceSet may include two SRS resources transmitted in different symbols and each SRS resource may include three SRS ports for transmission. Additionally, the SRS ports of the second SRS resource may be associated with different UE antenna ports than the SRS ports of the first SRS resource. However, when two SRS-ResourceSets are configured, they may be configured with a different resourceType including, for example, aperiodic, semi-persistent, and periodic resourceTypes.

[0046] In some embodiments, for 3Tx operation, 3T6R operation may be supported including an advanced 3T6R configuration in addition to the basic 3T6R configuration. Up to two SRS-ResourceSets with resourceType in SRS-ResourceSet set to 'semi- persistent' and up to one SRS-ResourceSet with resourceType in SRS-ResourceSet set to 'periodic' may be configured. The two SRS-ResourceSet with resourceType in SRS- ResourceSet set to ‘semi-persistent' may not be activated simultaneously. Whether the UE supports this feature or not may be reported independently as a Rel-19 UE capability.

[0047] In some embodiments, for 3Tx operation, 3T6R operation may be supported, including an advanced 3T6R configuration that is in addition to the basic 3T6R configuration. Additionally, up to two SRS-ResourceSet with resourceType in SRS- ResourceSet set to 'aperiodic' and up to one SRS-ResourceSet with resourceType in SRS-ResourceSet set to 'periodic' or 'semi-persistent' may be configured. In some8 4924-5092-6383\1 P66895WO2embodiments, when two resource sets with resourceType in SRS-ResourceSet set to ‘aperiodic' are configured: each SRS-ResourceSet includes one SRS resource; each SRS resource includes three SRS ports for transmission; the total of two SRS resources are transmitted in different symbols of two different slots; and the SRS ports of the second SRS resource are associated with different UE antenna ports than the SRS ports of the first SRS resource.

[0048] Whether the UE supports this feature or not may be reported independently as a Rel-19 UE capability.

[0049] SRS and PTRS enhancements for 3Tx codebook based PUSCH operation are now discussed.

[0050] Many wireless communication standards provide for the use of known signals (e.g., reference signals) for a variety of purposes, such as synchronization, measurements, equalization, control, etc. For example, in cellular wireless communications, SRS may be used to estimate uplink channel quality. A wireless communication device or mobile device (i.e., UE) can transmit an SRS to a base station (e.g., eNB for LTE and gNB for NR). SRS may provide information about the combined effect of multipath fading, scattering, Doppler and power loss of transmitted signal.

[0051] Using the SRS, the base station may estimate the channel quality and manage resources accordingly. For example, since the reference signals include data known to both the transmitter and the receiver, the receiver may use the reference signal to determine / identify various characteristics of the communication channel. This may be referred to as channel estimation. Known channel properties of a communication link in wireless communications are referred to as channel state information (CSI), which provides information indicative of the combined effects of, for example, scattering, fading, and power decay with distance. The CSI makes it possible to adapt transmissions to current channel conditions, which is useful for achieving reliable communications with high data rates in multi-antenna systems.

[0052] Multi-antenna systems may use precoding for improved communications. Precoding is an extension of beamforming to support multi-stream (or multi-layer) transmissions for multi-antenna wireless communications and is used to control the differences in signal properties between the respective signals transmitted from multiple antennas by modifying the signal transmitted from each antenna according to a precoding matrix. The precoding matrix may be selected from a codebook that defines9 4924-5092-6383\1 P66895WO2multiple precoding matrix candidates, wherein a precoding matrix candidate is typically selected according to a desired performance level based on any of a number of different factors such as current system configuration, communication environment, and / or feedback information from the receiver receiving the transmitted signal(s).

[0053] The feedback information may be used in selecting a precoding matrix candidate by defining the same codebook at both the transmitter and the receiver, and using the feedback information from the receiver as an indication of a preferred precoding matrix. Similarly, the feedback information may be used in selecting preferred ports for UE transmission.

[0054] In some wireless communication systems (e.g., Rel-15), for new radio (NR) SRS design, the SRS may be transmitted in the last six symbols of a slot and the SRS may be repeated up to four symbols, and the SRS supports Comb 2 / 4. In other wireless systems (e.g., Rel-16), for NR SRS design, the SRS may be transmitted in any symbol of a slot, and SRS repetition with 8 / 12 symbols is supported. The SRS also supports Comb 8 with 1 / 2 SRS ports. Further, NR Rel-17 enhanced the SRS coverage and capability. For example, RB-level Partial Frequency Sounding (RPFS) may be supported. For RPFS, a start physical resource block (PRB) location hopping may be supported. SRS repetition with 10 / 14 symbols may also be supported. For Comb 8, a maximum 6 cyclic shifts (CS) and 4 SRS ports may be supported. Rel-18 NR further enhanced SRS. For example, comb offset hopping and cyclic shift hopping for interference randomization may be supported. TDM SRS ports may also be used to increase capacity and an eight port SRS is supported.

[0055] In some systems, a PTRS may be used to facilitate the receiver to estimate the phase noise in NR. For uplink (UL) (e.g., in a PUSCH), the PTRS may be configured with a maximum of two ports. The PTRS is associated with a demodulation reference signal (DMRS) port indicated by a network indication. The PTRS is transmitted in the same pattern as the DMRS. For UL, DMRS to PTRS port association is indicated by a “PTRS-DMRS association” field in DCI format 0_1 / 0_2. The “PTRS-DMRS association” field is either 0 or 2 bits in length.

[0056] Additionally, in Rel-19, 3Tx UL operation may be supported including the 3Tx codebook based PUSCH operation. In view of this, a three port SRS may need to be supported. Also, PTRS for 3Tx codebook based PUSCH operation may need to be supported. Embodiments herein discuss SRS and PTRS enhancement to support 3Tx10 4924-5092-6383\1 P66895WO2codebook based PUSCH operation including details on SRS enhancement and PTRS enhancement.

[0057] FIG. 3 illustrates an example of an SRS sequence 302 in accordance with some embodiments. As shown, a transmission of the SRS sequence 302 may include a number of resource elements (REs) (e.g., first RE 304, second RE 306, third RE 308, and fourth RE 310). A RE is a frequency-time unit to which an SRS sequence 302 is mapped. The transmission further comprises multiple physical resource blocks (PRBs) (e.g., PRB1 312 and PRB2314) comprising a plurality of contiguous REs.

[0058] In some wireless communication systems, an SRS sequence 302 may support the following lengths {6, 12, 18, 24, any sequence >= 36}. The SRS sequence 302 is mapped to frequency domain resource (i.e., a resource element (RE) with a comb structure). The NR SRS supports Comb 2 / 4 / 8 and Comb N (N=2 / 4 / 8) subsamples the RE with a factor N, different Comb are orthogonal since they are non-overlapping in frequency.

[0059] Additionally, multiple cyclic shift sequences can be applied on top of the same SRS sequence. A length M cyclic shift sequence can have M orthogonal sequences. This may create M orthogonal SRS sequence using the same SRS comb offset. The cyclic shift sequence length M is a function of Comb size N as provided in, for example, Table 1 provided below. Comb 2 may have a maximum of 8 cyclic shifts. Comb 4 may have a maximum of 12 cyclic shifts and comb 8 may have a maximum of 6 cyclic shifts. Table 1: Maximum number of cyclic shifts ^^^^,^^௫ௌோௌas a function of ^^்^^^ ^்^ ^^ ^,^^௫ௌோௌ2

[0061] In some embodiments, for 3Tx codebook based PUSCH operation, a three port SRS may be supported (i.e., a single SRS-Resource (SRS resource) transmitted with three ports). In some examples, the three port SRS may be based on the existing four port SRS resource. For example, four port SRS resource may be configured with one of the ports being disabled. In some other examples, the three port SRS may be based on the existing four port SRS resource and / or eight port SRS resource. In yet some other examples, the three port SRS may be based on the existing eight port SRS resource.11 4924-5092-6383\1 P66895WO2

[0062] In some embodiments, for 3Tx codebook based PUSCH operation, when a three port SRS is supported based on the existing four port SRS resource, the network may configure an SRS-Resource with four SRS ports. One of the four configured SRS ports may not be used by the UE for transmission of the SRS for 3Tx. In some embodiments, the network further selects three out of the four SRS ports for UE SRS transmission.

[0063] In some embodiments, for 3Tx codebook based PUSCH operation, when a three port SRS is supported based on the existing eight port SRS resource, the network may configure an SRS-Resource with eight SRS ports. The network may further select three out of the eight SRS ports for UE SRS transmission.

[0064] In some embodiments, for 3Tx codebook based PUSCH operation, when a three port SRS is supported based on the existing four port SRS resource, regarding the configuration of SRS port selection, selection of three out of four SRS ports for UE SRS transmission may be configured by a radio resource control (RRC) in the SRS-Resource, according to various examples. In some examples, consecutive SRS ports may be selected with one bit to configure the index of starting SRS port. A value of “0” may correspond to, SRS ports {0, 1, 2} being selected. A value of “1” may correspond to SRS ports {1, 2, 3} being selected. Accordingly, in some embodiments, SRS ports {0, 1, 2, 3} may be configured and the first three SRS ports (e.g., SRS ports {0, 1, 2} may be used for the SRS transmission, and the last SRS port may not be used.

[0065] In some other examples, non-consecutive SRS ports may be selected, with two bits to configure the index of SRS port that is not selected. A value of “0” may correspond to, SRS ports {1, 2, 3} being selected. A value of “1” may correspond to SRS ports {0, 2, 3} being selected. A value of “2” may correspond to SRS ports {0, 1, 3} being selected. A value of “3” may correspond to SRS ports {0, 1, 2} being selected.

[0066] In yet some other examples, non-consecutive SRS ports can be selected with a four bit bitmap. Each bit in the bitmap indicates whether the corresponding SRS port is selected or not. Three bits and only three bits out of four bit bitmap may be indicated as a value of “1”.

[0067] In some embodiments, for 3Tx codebook based PUSCH operation, when a three port SRS is supported based on the existing eight port SRS resource, regarding the configuration of SRS port selection, the selection of three out of eight SRS ports for UE SRS transmission is configured by RRC in SRS-Resource, according to various examples.12 4924-5092-6383\1 P66895WO2

[0068] In some examples, consecutive SRS ports may be selected with three bits to configure the index of starting SRS port. A value of “0” may correspond to SRS ports {0, 1, 2} being selected. A value of “1” may correspond to SRS ports {1, 2, 3} being selected. A value of “2” may correspond to SRS ports {2, 3, 4} being selected. A value of “3” may correspond to SRS ports {3, 4, 5} being selected. A value of “4” may correspond to SRS ports {4, 5, 6} being selected. A value of “5” may correspond to SRS ports {5, 6, 7} being selected.

[0069] In some other examples, non-consecutive SRS ports may be selected with six bits to configure the index of SRS port that is not selected. The first 56 values of the 6- bits (“0” to “55”) map to the 56 possible selection of the three ports out of the eight ports, respectively.

[0070] In yet some other examples, non-consecutive SRS ports may be selected with an eight bit bitmap. Each bit in the bitmap indicates whether the corresponding SRS port is selected or not. Three bits and only three bits out of eight bit bitmap may be indicated as a value of “1”.

[0071] In some embodiments, for 3Tx codebook based PUSCH operation, when a three port SRS is supported based on the existing 4 / 8 port SRS resource, regarding the number of comb offsets, various alternatives may be used according to the number of port SRS resources. For example, for a 4 port SRS resource, in some cases only 1 comb offset is supported. In some other cases, both 1 and 2 comb offsets are supported. Note that, for 1 comb offset, each comb offset includes four SRS ports with enough for the selection of three ports and for 2 comb offset and each comb offset includes two SRS ports and more than 1 comb offset is needed

[0072] In some other examples, for eight port SRS resource, in some cases only 1 comb offset is supported. In some other cases, both 1 and 2 comb offsets are supported. In yet some other cases, only 2 comb offsets are supported. In still yet some other cases, 1, 2 and 4 comb offsets are supported. Note that, for 1 comb offset, each comb offset includes eight SRS ports with enough for the selection of three ports. For 2 comb offset, each comb offset includes four SRS ports with enough for the selection of three ports. For a 4 comb offset, each comb offset includes two SRS ports and more than 1 comb offset may be needed.

[0073] In some embodiments, for 3Tx codebook based PUSCH operation, when a three port SRS is supported based on the existing eight port SRS resource with 2 comb offset,13 4924-5092-6383\1 P66895WO2regarding the number of comb offsets that is used for port selection, three ports may be selected in the same comb offset, or 3 ports may be selected in different comb offsets.

[0074] In some embodiments, for 3Tx codebook based PUSCH operation, when a three port SRS is supported based on the existing 8 port SRS resource, whether time-division multiplexing (TDM) SRS ports is supported may be decided according to various alternatives. In some examples, a TDM SRS port is not supported. In some other examples, a TDM SRS port is supported with one or both of the following options illustrated in FIG. 4.

[0075] FIG. 4 illustrates example port configurations in accordance with some embodiments. In some such examples, two ports are transmitted in one SRS symbol, and the remaining one port is transmitted in the other SRS symbol (referred to as “option 2.1" 402) or 3 ports are transmitted in one SRS symbol, and no SRS transmission in the other SRS symbol (referred to as “option 2.2” 404).

[0076] In some embodiments, for 3Tx codebook based PUSCH operation, a three port SRS is supported based on the existing eight port SRS resource, a TDM SRS port is supported that two ports are transmitted in one SRS symbol, and the remaining one port is transmitted in the other SRS symbol. In some embodiments, all three SRS ports are transmitted with the same transmit power. Additionally, the transmission power may be determined by the SRS symbols that comprises two ports, denoted as ^^ௌோௌ. For the SRS symbol with two ports, each SRS port may be transmitted with ^^ௌோௌ / 2. For the SRS symbol with one port, the SRS port may be transmitted with ^^ௌோௌ / 2.The SRS symbol with one port may be transmitted with 50% less transmit power compared to the SRS symbol with two ports.

[0077] PTRS enhancement

[0078] In some embodiments, for 3Tx codebook based PUSCH operation, when the network configures a one port UL PTRS, a “PTRS-DMRS association” field in DCI format 0_1 and DCI format 0_2 has two bits, denoted as {b1, b0}, where ‘b1’ is the most significant bit (MSB), and ‘b0’ is the least significant bit (LSB). Note that a one port UL PTRS may be configured as a higher layer parameter maxNrofPorts in the PTRS- UplinkConfig that may be set to ‘n1’.

[0079] For example, FIG. 5 illustrates a table 502 for interpreting a value of the “PTRS-DMRS association” field in accordance with some embodiments. In the illustrated embodiment, a “PTRS-DMRS association” field value of zero may correspond14 4924-5092-6383\1 P66895WO2with a first scheduled DMRS port, a value of one may correspond with a second scheduled DMRS port, a value of two may correspond with a third scheduled DMRS port, and a value of three may be reserved. Thus, the network node may indicate the PTRS DMRS association.

[0080] In some embodiments, for 3Tx codebook based PUSCH operation, when the network configures a 2 port UL PTRS, a “PTRS-DMRS association” field in DCI format 0_1 and DCI format 0_2 has 2 bits, denoted as {b1, b0}, with ‘b1’ as the MSB, and ‘b0’ as the LSB. Note that a 2 port UL PTRS is configured as a higher layer parameter maxNrofPorts in the PTRS-UplinkConfig may be set to ‘n2’. The interpretation of “PTRS-DMRS association” field may be as shown in table 602 of FIG. 6.

[0081] In some examples, PUSCH antenna port 1000 and 1002 in an indicated TPMI share PT-RS port 0 and PUSCH antenna port 1001 in an indicated TPMI share PT-RS port 1. In some other examples, a PUSCH antenna port 1000 and 1001 in an indicated TPMI share PT-RS port 0 and a PUSCH antenna port 1002 in an indicated TPMI share PT-RS port 1.

[0082] For example, FIG. 6 illustrates a table 602 for interpreting a value of the “PTRS-DMRS association” field in accordance with some embodiments. As shown, in some embodiments, when the value of MSB is zero, the first DMRS port which shares PTRS port 0 may be indicated as associated with the PTRS. When the value of MSB is one, the second DMRS port which shares PTRS port 0 may be indicated as associated with the PTRS.

[0083] In some embodiments, for 3Tx nonCodebook based PUSCH operation, a PTRS to DMRS association may follow a codebook based PUSCH operation as discussed herein for PTRS enhancement. For a two port UL PTRS (for the PTRS-UplinkConfig set to ‘n2’ discussed herein), the SRS resource in nonCodebook based PUSCH operation may map to PUSCH antenna port in the codebook based PUSCH. In some examples, the SRS resource may be configured with smaller index maps to PUSCH antenna port with a smaller index. In some other examples, the SRS resource may be configured earlier in the SRS-ResourceSet and maps to the PUSCH antenna port with a smaller index.

[0084] In some embodiments, for 3Tx nonCodebook based PUSCH operation, a UE may be configured with the PTRS port index for each configured SRS resource by the higher layer parameter ptrs-PortIndex configured by the SRS-Config. If the PT-RS port15 4924-5092-6383\1 P66895WO2index associated with different SRIs are the same, the corresponding UL DMRS ports may be associated to the one UL PTRS port.

[0085] FIG. 7 illustrates a method 700 performed by a UE, according to embodiments herein. The illustrated method 700 includes sending 702, to a network node, a capability report indicating support for 3Tx PUSCH operation. The method 700 further includes receiving 704, from the network node, an SRS configuration for the 3Tx PUSCH operation, the SRS configuration comprising an SRS resource set. The method 700 further includes transmitting 706 one or more SRS resources in the SRS Resource Set with one or more SRS ports. The method 700 further includes receiving 708, from the network node, a PUSCH configuration that schedules the 3Tx PUSCH operation based on the transmitted one or more SRS resources.

[0086] In some embodiments of the method 700, the 3Tx PUSCH operation is non- coherent codebook based 3Tx PUSCH operation, and wherein the UE supports one or multiple of precoding matrices based on a rank variable including: 10 0for rank = 1 TPMI=0൭0^, TPMI=1൭1^, TPMI=2൭0^;0 0for 0^; andfor

[0087] the method 700, the capability report indicating the support for the 3Tx PUSCH operation comprises: a first indication of support for codebook based 3Tx PUSCH operation, and a second indication that the UE supports a maximum 3 layers.

[0088] In some embodiments of the method 700, the PUSCH configuration comprises a max rank field, wherein when the max rank field is set equal to one, a bit width of a precoding information and number of layers field is two bits.

[0089] In some embodiments of the method 700, the PUSCH configuration comprises a max rank field, wherein when the max rank field is set equal to two or three, a bit width of a precoding information and number of layers field is three bits.16 4924-5092-6383\1 P66895WO2

[0090] In some embodiments, the method 700 further comprises reporting, to the network node support for full power transmission mode 0 when the 3TX PUSCH operation is codebook based.

[0091] In some embodiments of the method 700, the capability report indicating support for 3Tx PUSCH operation comprises: a first indication of support for nonCodebook based 3Tx PUSCH operation, and a second indication that the UE supports a maximum 3 layers. In some such embodiments, the capability report further comprises a maximum number of SRS resources that can be configured in a same SRS-ResourceSet with usage equal to nonCodebook, and a maximum number of simultaneous transmitted SRS resources at one symbol. In some other such embodiments, the SRS configuration comprises: two SRS-ResourceSets with usage set equal to antennaSwitching, wherein each of the two SRS-ResourceSets includes two SRS resources that the UE transmits in different symbols, where each of the two SRS resources includes three SRS ports for transmission, wherein the three SRS ports of a second SRS resource are associated with different UE antenna ports than the SRS ports of a first SRS resource, and wherein each of the two SRS-ResourceSets are configured with a different resource type. In yet some other such embodiments, the SRS configuration comprises: two SRS-ResourceSets with resourceType in SRS-ResourceSet set to semi-persistent, and one SRS-ResourceSet with resourceType in SRS-ResourceSet set to periodic.

[0092] FIG. 8 illustrates a method 800 performed by a network node, according to embodiments herein. The illustrated method 800 includes receiving 802, from a UE, a capability report indicating support for 3Tx PUSCH operation. The method 800 further includes sending 804, to the UE, an SRS configuration for the 3Tx PUSCH operation, the SRS configuration comprising an SRS resource set. The method 800 further includes receiving 806, from the UE, one or more SRS resources in the SRS Resource Set with one or more SRS ports. The method 800 further includes sending 808, to the UE, a PUSCH configuration that schedules the 3Tx PUSCH operation based on the transmitted one or more SRS resources.

[0093] In some embodiments of the method 800, the 3Tx PUSCH operation is non- coherent codebook based 3Tx PUSCH operation, and wherein the UE supports one or multiple of precoding matrices based on a rank variable including: 10 0for17 4924-5092-6383\1 P66895WO21 0 1 0 0 0for rank = 2 TPMI=0 ൭0 1^, TPMI=1 ൭0 0^, TPMI=2 ൭1 0^; andfor

[0094] the method 800, the capability report indicating thesupport comprises: a first indication of support for codebook based 3Tx PUSCH operation, and a second indication that the UE supports a maximum 3 layers.

[0095] In some embodiments of the method 800, the PUSCH configuration comprises a max rank field, wherein when the max rank field is set equal to one, a bit width of a precoding information and number of layers field is two bits.

[0096] In some embodiments of the method 800, the PUSCH configuration comprises a max rank field, wherein when the max rank field is set equal to two or three, a bit width of a precoding information and number of layers field is three bits.

[0097] In some embodiments, the method 800 further comprises receiving, from the UE, an indication of support for full power transmission mode 0 when the 3TX PUSCH operation is codebook based.

[0098] In some embodiments of the method 800, the capability report indicating support for 3Tx PUSCH operation comprises: a first indication of support for nonCodebook based 3Tx PUSCH operation, and a second indication that the UE supports a maximum 3 layers. In some such embodiments, the capability report further comprises a maximum number of SRS resources that can be configured in a same SRS-ResourceSet with usage equal to nonCodebook, and a maximum number of simultaneous transmitted SRS resources at one symbol. In some other such embodiments, the SRS configuration comprises: two SRS-ResourceSets with usage set equal to antennaSwitching, wherein each of the two SRS-ResourceSets includes two SRS resources that the UE transmits in different symbols, where each of the two SRS resources includes three SRS ports for transmission, wherein the three SRS ports of a second SRS resource are associated with different UE antenna ports than the SRS ports of a first SRS resource, and wherein each of the two SRS-ResourceSets are configured with a different resource type. In yet some other such embodiments, the SRS configuration comprises: two SRS-ResourceSets with18 4924-5092-6383\1 P66895WO2resourceType in SRS-ResourceSet set to semi-persistent, and one SRS-ResourceSet with resourceType in SRS-ResourceSet set to periodic.

[0099] FIG. 9 illustrates a method 900 performed by a UE, according to embodiments herein. The illustrated method 900 includes receiving 902, from a network node, an SRS- Resource configuration for three port SRS, wherein the SRS-Resource configuration configures four SRS ports. The method 900 further includes determining 904 which three SRS ports of the four SRS ports included in the SRS-Resource configuration to use to send an SRS transmission. The method 900 further includes sending 906, to the network node, the SRS transmission using the three SRS ports that are determined. The method 900 further includes receiving 908, from the network node, a signal indicating a 3Tx codebook for PUSCH operation based on the SRS transmission sent on the three SRS ports.

[0100] In some embodiments of the method 900, the three SRS ports used to send the SRS transmission are ports {0, 1, 2}.

[0101] In some embodiments of the method 900, the three SRS ports are transmitted with a same transmit power.

[0102] In some embodiments, the method 900 further comprises receiving, from the network node, a configuration for 1 port UL PTRS, receiving a DCI comprising a PTRS- DMRS association field, wherein the field comprises two bits that indicates which DMRS port the 1 port UL PTRS is associated with, wherein when a value of the two bits is zero, the 1 port UL PTRS is associated with a first scheduled DMRS port, when the value of the two bits is one, the 1 port UL PTRS is associated with a second scheduled DMRS port, and when the value of the two bits is two, the 1 port UL PTRS is associated with a third scheduled DMRS port.

[0103] In some embodiments, the method 900 further comprises receiving, from the network node, a configuration for 2 port UL PTRS and receiving a DCI comprising a PTRS-DMRS association field indicating which of two DMRS port in indicated TPMI that share with PT-RS port 0 is associated with the 2 port UL PTRS, and wherein a PUSCH antenna port in the indicated TPMI is shared with PTRS port 1 and is also used for the 2 port UL PTRS.

[0104] In some embodiments of the method 900, for 3Tx nonCodebook based PUSCH operation, PTRS to DMRS association follows codebook based PUSCH operation. In some such embodiments, SRS resource in the 3Tx nonCodebook based PUSCH19 4924-5092-6383\1 P66895WO2operation maps to a PUSCH antenna port in codebook based PUSCH. In certain such embodiments, a first SRS resource configured with smaller index maps to the PUSCH antenna port with a smaller index, or a second SRS resource configured earlier in SRS- ResourceSet maps to the PUSCH antenna port with the smaller index.

[0105] FIG. 10 illustrates a method 1000 performed by a network node, according to embodiments herein. The illustrated method 1000 includes generating 1002 an SRS- Resource configuration for three port SRS, wherein the SRS-Resource configuration configures four SRS ports where only three ports of the four SRS ports are applicable to the three port SRS. The method 1000 further includes sending 1004, to a UE, the SRS- Resource configuration for the three port SRS. The method 1000 further includes receiving 1006, from the UE, an SRS transmission via the three SRS ports. The method 1000 further includes sending 1008, to the UE, a signal indicating a 3Tx codebook for PUSCH operation based on the SRS transmission sent on the three SRS ports.

[0106] In some embodiments of the method 1000, the three SRS ports used to send the SRS transmission are ports {0, 1, 2}.

[0107] In some embodiments of the method 1000, the three SRS ports are transmitted by the UE with a same transmit power.

[0108] In some embodiments, the method 1000 further comprises sending, to the UE, a configuration for 1 port UL PTRS, sending a DCI comprising a PTRS-DMRS association field, wherein the field comprises two bits that indicates which DMRS port the 1 port UL PTRS is associated with, wherein when a value of the two bits is zero, the 1 port UL PTRS is associated with a first scheduled DMRS port, when the value of the two bits is one, the 1 port UL PTRS is associated with a second scheduled DMRS port, and when the value of the two bits is two, the 1 port UL PTRS is associated with a third scheduled DMRS port.

[0109] In some embodiments, the method 1000 further comprises sending, to the UE, a configuration for 2 port UL PTRS, and sending a DCI comprising a PTRS-DMRS association field indicating which of two DMRS port in indicated TPMI that share with PT-RS port 0 is associated with the 2 port UL PTRS, and wherein a PUSCH antenna port in the indicated TPMI is shared with PTRS port 1 and is also used for the 2 port UL PTRS.

[0110] In some embodiments of the method 1000, for 3Tx nonCodebook based PUSCH operation, PTRS to DMRS association follows codebook based PUSCH operation. In20 4924-5092-6383\1 P66895WO2some such embodiments, SRS resource in the 3Tx nonCodebook based PUSCH operation maps to a PUSCH antenna port in codebook based PUSCH. In certain such embodiments, a first SRS resource configured with smaller index maps to the PUSCH antenna port with a smaller index, or a second SRS resource configured earlier in SRS- ResourceSet maps to the PUSCH antenna port with the smaller index.

[0111] FIG. 11 illustrates an example architecture of a wireless communication system 1100, according to embodiments disclosed herein. The following description is provided for an example wireless communication system 1100 that operates in conjunction with the LTE system standards and / or 5G or NR system standards as provided by 3GPP technical specifications.

[0112] As shown by FIG. 11, the wireless communication system 1100 includes UE 1102 and UE 1104 (although any number of UEs may be used). In this example, the UE 1102 and the UE 1104 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device configured for wireless communication.

[0113] The UE 1102 and UE 1104 may be configured to communicatively couple with a RAN 1106. In embodiments, the RAN 1106 may be NG-RAN, E-UTRAN, etc. The UE 1102 and UE 1104 utilize connections (or channels) (shown as connection 1108 and connection 1110, respectively) with the RAN 1106, each of which comprises a physical communications interface. The RAN 1106 can include one or more base stations (such as base station 1112 and base station 1114) that enable the connection 1108 and connection 1110.

[0114] In this example, the connection 1108 and connection 1110 are air interfaces to enable such communicative coupling, and may be consistent with RAT(s) used by the RAN 1106, such as, for example, an LTE and / or NR.

[0115] In some embodiments, the UE 1102 and UE 1104 may also directly exchange communication data via a sidelink interface 1116. The UE 1104 is shown to be configured to access an access point (shown as AP 1118) via connection 1120. By way of example, the connection 1120 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 1118 may comprise a Wi-Fi®router. In this example, the AP 1118 may be connected to another network (for example, the Internet) without going through a CN 1124.21 4924-5092-6383\1 P66895WO2

[0116] In embodiments, the UE 1102 and UE 1104 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 1112 and / or the base station 1114 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0117] In some embodiments, all or parts of the base station 1112 or base station 1114 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 1112 or base station 1114 may be configured to communicate with one another via interface 1122. In embodiments where the wireless communication system 1100 is an LTE system (e.g., when the CN 1124 is an EPC), the interface 1122 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and / or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 1100 is an NR system (e.g., when CN 1124 is a 5GC), the interface 1122 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 1112 (e.g., a gNB) connecting to 5GC and an eNB, and / or between two eNBs connecting to 5GC (e.g., CN 1124).

[0118] The RAN 1106 is shown to be communicatively coupled to the CN 1124. The CN 1124 may comprise one or more network elements 1126, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UE 1102 and UE 1104) who are connected to the CN 1124 via the RAN 1106. The components of the CN 1124 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine- readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0119] In embodiments, the CN 1124 may be an EPC, and the RAN 1106 may be connected with the CN 1124 via an S1 interface 1128. In embodiments, the S1 interface22 4924-5092-6383\1 P66895WO21128 may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the base station 1112 or base station 1114 and a serving gateway (S-GW), and the S1-MME interface, which is a signaling interface between the base station 1112 or base station 1114 and mobility management entities (MMEs).

[0120] In embodiments, the CN 1124 may be a 5GC, and the RAN 1106 may be connected with the CN 1124 via an NG interface 1128. In embodiments, the NG interface 1128 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 1112 or base station 1114 and a user plane function (UPF), and the S1 control plane (NG-C) interface, which is a signaling interface between the base station 1112 or base station 1114 and access and mobility management functions (AMFs).

[0121] Generally, an application server 1130 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 1124 (e.g., packet switched data services). The application server 1130 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 1102 and UE 1104 via the CN 1124. The application server 1130 may communicate with the CN 1124 through an IP communications interface 1132.

[0122] FIG. 12 illustrates a system 1200 for performing signaling 1234 between a wireless device 1202 and a network device 1218, according to embodiments disclosed herein. The system 1200 may be a portion of a wireless communications system as herein described. The wireless device 1202 may be, for example, a UE of a wireless communication system. The network device 1218 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.

[0123] The wireless device 1202 may include one or more processor(s) 1204. The processor(s) 1204 may execute instructions such that various operations of the wireless device 1202 are performed, as described herein. The processor(s) 1204 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0124] The wireless device 1202 may include a memory 1206. The memory 1206 may be a non-transitory computer-readable storage medium that stores instructions 120823 4924-5092-6383\1 P66895WO2(which may include, for example, the instructions being executed by the processor(s) 1204). The instructions 1208 may also be referred to as program code or a computer program. The memory 1206 may also store data used by, and results computed by, the processor(s) 1204.

[0125] The wireless device 1202 may include one or more transceiver(s) 1210 that may include radio frequency (RF) transmitter circuitry and / or receiver circuitry that use the antenna(s) 1212 of the wireless device 1202 to facilitate signaling (e.g., the signaling 1234) to and / or from the wireless device 1202 with other devices (e.g., the network device 1218) according to corresponding RATs.

[0126] The wireless device 1202 may include one or more antenna(s) 1212 (e.g., one, two, four, or more). For embodiments with multiple antenna(s) 1212, the wireless device 1202 may leverage the spatial diversity of such multiple antenna(s) 1212 to send and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect). MIMO transmissions by the wireless device 1202 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 1202 that multiplexes the data streams across the antenna(s) 1212 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream). Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).

[0127] In certain embodiments having multiple antennas, the wireless device 1202 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s) 1212 are relatively adjusted such that the (joint) transmission of the antenna(s) 1212 can be directed (this is sometimes referred to as beam steering).

[0128] The wireless device 1202 may include one or more interface(s) 1214. The interface(s) 1214 may be used to provide input to or output from the wireless device 1202. For example, a wireless device 1202 that is a UE may include interface(s) 1214 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for24 4924-5092-6383\1 P66895WO2input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 1210 / antenna(s) 1212 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

[0129] The wireless device 1202 may include a 3Tx codebook module 1216. The 3Tx codebook module 1216 may be implemented via hardware, software, or combinations thereof. For example, the 3Tx codebook module 1216 may be implemented as a processor, circuit, and / or instructions 1208 stored in the memory 1206 and executed by the processor(s) 1204. In some examples, the 3Tx codebook module 1216 may be integrated within the processor(s) 1204 and / or the transceiver(s) 1210. For example, the 3Tx codebook module 1216 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 1204 or the transceiver(s) 1210.

[0130] The 3Tx codebook module 1216 may be used for various aspects of the present disclosure, for example, aspects of FIG. 1, FIG. 2, FIG. 3, FIG. 4, FIG. 5, FIG. 6 and FIG. 7. The 3Tx codebook module 1216 is configured to cause the wireless device 1202 to send, to a network device 1218, a capability report indicating support for 3Tx PUSCH operation. The 3Tx codebook module 1216 is further configured to cause the wireless device 1202 to receive, from the network device 1218, an SRS configuration for the 3Tx PUSCH operation, the SRS configuration comprising an SRS resource set. The 3Tx codebook module 1216 is further configured to cause the wireless device 1202 to transmit one or more SRS resources in the SRS Resource Set with one or more SRS ports. The 3Tx codebook module 1216 is further configured to cause the wireless device 1202 to receive, from the network device 1218, a PUSCH configuration that schedules the 3Tx PUSCH operation based on the transmitted one or more SRS resources.

[0131] The network device 1218 may include one or more processor(s) 1220. The processor(s) 1220 may execute instructions such that various operations of the network device 1218 are performed, as described herein. The processor(s) 1220 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.25 4924-5092-6383\1 P66895WO2

[0132] The network device 1218 may include a memory 1222. The memory 1222 may be a non-transitory computer-readable storage medium that stores instructions 1224 (which may include, for example, the instructions being executed by the processor(s) 1220). The instructions 1224 may also be referred to as program code or a computer program. The memory 1222 may also store data used by, and results computed by, the processor(s) 1220.

[0133] The network device 1218 may include one or more transceiver(s) 1226 that may include RF transmitter circuitry and / or receiver circuitry that use the antenna(s) 1228 of the network device 1218 to facilitate signaling (e.g., the signaling 1234) to and / or from the network device 1218 with other devices (e.g., the wireless device 1202) according to corresponding RATs.

[0134] The network device 1218 may include one or more antenna(s) 1228 (e.g., one, two, four, or more). In embodiments having multiple antenna(s) 1228, the network device 1218 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.

[0135] The network device 1218 may include one or more interface(s) 1230. The interface(s) 1230 may be used to provide input to or output from the network device 1218. For example, a network device 1218 that is a base station may include interface(s) 1230 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 1226 / antenna(s) 1228 already described) that enables the base station to communicate with other equipment in a core network, and / or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.

[0136] The network device 1218 may include a 3Tx codebook module 1232. The 3Tx codebook module 1232 may be implemented via hardware, software, or combinations thereof. For example, the 3Tx codebook module 1232 may be implemented as a processor, circuit, and / or instructions 1224 stored in the memory 1222 and executed by the processor(s) 1220. In some examples, the 3Tx codebook module 1232 may be integrated within the processor(s) 1220 and / or the transceiver(s) 1226. For example, the 3Tx codebook module 1232 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 1220 or the transceiver(s) 1226.26 4924-5092-6383\1 P66895WO2

[0137] The 3Tx codebook module 1232 may be used for various aspects of the present disclosure, for example, aspects of FIG. 1, FIG. 2, FIG. 3, FIG. 4, FIG. 5, FIG. 6 and FIG. 8. The 3Tx codebook module 1232 is configured to cause the network device 1218 to receive, from a UE, a capability report indicating support for 3Tx PUSCH operation. The 3Tx codebook module 1232 is further configured to cause the network device 1218 to send, to the wireless device 1202, an SRS configuration for the 3Tx PUSCH operation, the SRS configuration comprising an SRS resource set. The 3Tx codebook module 1232 is further configured to cause the network device 1218 to receive, from the wireless device 1202, one or more SRS resources in the SRS Resource Set with one or more SRS ports. The 3Tx codebook module 1232 is further configured to cause the network device 1218 to send, to the wireless device 1202, a PUSCH configuration that schedules the 3Tx PUSCH operation based on the transmitted one or more SRS resources.

[0138] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 700. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1202 that is a UE, as described herein).

[0139] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 700. This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 1206 of a wireless device 1202 that is a UE, as described herein).

[0140] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 700. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1202 that is a UE, as described herein).

[0141] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 700. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1202 that is a UE, as described herein).

[0142] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 700.27 4924-5092-6383\1 P66895WO2

[0143] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method 700. The processor may be a processor of a UE (such as a processor(s) 1204 of a wireless device 1202 that is a UE, as described herein). These instructions may be, for example, located in the processor and / or on a memory of the UE (such as a memory 1206 of a wireless device 1202 that is a UE, as described herein).

[0144] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 800. This apparatus may be, for example, an apparatus of a base station (such as a network device 1218 that is a base station, as described herein).

[0145] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 800. This non-transitory computer-readable media may be, for example, a memory of a base station (such as a memory 1222 of a network device 1218 that is a base station, as described herein).

[0146] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 800. This apparatus may be, for example, an apparatus of a base station (such as a network device 1218 that is a base station, as described herein).

[0147] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 800. This apparatus may be, for example, an apparatus of a base station (such as a network device 1218 that is a base station, as described herein).

[0148] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 800.

[0149] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of the method 800. The processor may be a processor of a base station (such as a28 4924-5092-6383\1 P66895WO2processor(s) 1220 of a network device 1218 that is a base station, as described herein). These instructions may be, for example, located in the processor and / or on a memory of the base station (such as a memory 1222 of a network device 1218 that is a base station, as described herein).

[0150] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.

[0151] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0152] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.

[0153] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for29 4924-5092-6383\1 P66895WO2parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.

[0154] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[0155] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.30 4924-5092-6383\1 P66895WO2

Claims

CLAIMS 1. A method performed by a user equipment (UE), the method comprising: sending, to a network node, a capability report indicating support for 3 Transmit Antennas (3Tx) Physical Uplink Shared Channel (PUSCH) operation; receiving, from the network node, a sounding reference signal (SRS) configuration for the 3Tx PUSCH operation, the SRS configuration comprising an SRS resource set; transmitting one or more SRS resources in the SRS Resource Set with one or more SRS ports; and receiving, from the network node, a PUSCH configuration that schedules the 3Tx PUSCH operation based on the transmitted one or more SRS resources.

2. The method of claim 1, wherein the 3Tx PUSCH operation is non-coherent codebook based 3Tx PUSCH operation, and wherein the UE supports one or multiple of precoding matrices based on a rank variable including: 10 0for rank = 1 TPMI=0൭0^, TPMI=1൭1^, TPMI=2൭0^; 3. Thefor the 3Tx PUSCH operation comprises: a first indication of support for codebook based 3Tx PUSCH operation, and a second indication that the UE supports a maximum 3 layers.

4. The method of claim 1, wherein the PUSCH configuration comprises a max rank field, wherein when the max rank field is set equal to one, a bit width of a precoding information and number of layers field is two bits.

5. The method of claim 1, wherein the PUSCH configuration comprises a max rank field, wherein when the max rank field is set equal to two or three, a bit width of a precoding information and number of layers field is three bits.31 4924-5092-6383\1 P66895WO26. The method of claim 1, further comprising reporting, to the network node support for full power transmission mode 0 when the 3TX PUSCH operation is codebook based.

7. The method of claim 1, wherein the capability report indicating support for 3Tx PUSCH operation comprises: a first indication of support for nonCodebook based 3Tx PUSCH operation, and a second indication that the UE supports a maximum 3 layers.

8. The method of claim 7, wherein the capability report further comprises a maximum number of SRS resources that can be configured in a same SRS-ResourceSet with usage equal to nonCodebook, and a maximum number of simultaneous transmitted SRS resources at one symbol.

9. The method of claim 7, wherein the SRS configuration comprises: two SRS-ResourceSets with usage set equal to antennaSwitching, wherein each of the two SRS-ResourceSets includes two SRS resources that the UE transmits in different symbols, where each of the two SRS resources includes three SRS ports for transmission, wherein the three SRS ports of a second SRS resource are associated with different UE antenna ports than the SRS ports of a first SRS resource, and wherein each of the two SRS-ResourceSets are configured with a different resource type.

10. The method of claim 7, wherein the SRS configuration comprises: two SRS-ResourceSets with resourceType in SRS-ResourceSet set to semi- persistent, and one SRS-ResourceSet with resourceType in SRS-ResourceSet set to periodic.

11. A method performed by a network node, the method comprising: receiving, from a user equipment (UE), a capability report indicating support for 3 Transmit Antennas (3Tx) Physical Uplink Shared Channel (PUSCH) operation; sending, to the UE, a sounding reference signal (SRS) configuration for the 3Tx PUSCH operation, the SRS configuration comprising an SRS resource set; receiving, from the UE, one or more SRS resources in the SRS Resource Set with one or more SRS ports; and32 4924-5092-6383\1 P66895WO2sending, to the UE, a PUSCH configuration that schedules the 3Tx PUSCH operation based on the transmitted one or more SRS resources.

12. The method of claim 11, wherein the 3Tx PUSCH operation is non-coherent codebook based 3Tx PUSCH operation, and wherein the UE supports one or multiple of precoding matrices based on a rank variable including: 10 0for rank = 1 TPMI=0൭0^, TPMI=1 ൭1^, TPMI=2൭0^;13.for the 3Tx PUSCH operation comprises: a first indication of support for codebook based 3Tx PUSCH operation, and a second indication that the UE supports a maximum 3 layers.

14. The method of claim 11, wherein the PUSCH configuration comprises a max rank field, wherein when the max rank field is set equal to one, a bit width of a precoding information and number of layers field is two bits.

15. The method of claim 11, wherein the PUSCH configuration comprises a max rank field, wherein when the max rank field is set equal to two or three, a bit width of a precoding information and number of layers field is three bits.

16. The method of claim 11, further comprising receiving, from the UE, an indication of support for full power transmission mode 0 when the 3TX PUSCH operation is codebook based.

17. The method of claim 11, wherein the capability report indicating support for 3Tx PUSCH operation comprises: a first indication of support for nonCodebook based 3Tx PUSCH operation, and a second indication that the UE supports a maximum 3 layers.33 4924-5092-6383\1 P66895WO218. The method of claim 17, wherein the capability report further comprises a maximum number of SRS resources that can be configured in a same SRS-ResourceSet with usage equal to nonCodebook, and a maximum number of simultaneous transmitted SRS resources at one symbol.

19. The method of claim 17, wherein the SRS configuration comprises: two SRS-ResourceSets with usage set equal to antennaSwitching, wherein each of the two SRS-ResourceSets includes two SRS resources that the UE transmits in different symbols, where each of the two SRS resources includes three SRS ports for transmission, wherein the three SRS ports of a second SRS resource are associated with different UE antenna ports than the SRS ports of a first SRS resource, and wherein each of the two SRS-ResourceSets are configured with a different resource type.

20. The method of claim 17, wherein the SRS configuration comprises: two SRS-ResourceSets with resourceType in SRS-ResourceSet set to semi- persistent, and one SRS-ResourceSet with resourceType in SRS-ResourceSet set to periodic.

21. An apparatus comprising means to perform the method of any of claim 1 to claim 20.

22. A computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform the method of any of claim 1 to claim 20.

23. An apparatus comprising logic, modules, or circuitry to perform the method of any of claim 1 to claim 20.

24. A baseband processor for a user equipment (UE) that is configured to cause the UE to perform one or more elements of any one of claim 1 to claim 10.

25. A baseband processor for a base station that is configured to cause the base station to perform one or more elements of any one of claim 11 to claim 20.34 4924-5092-6383\1 P66895WO2

Images