SRS CONFIGURATION AND INDICATION FOR CODEBOOK AND NON-CODEBOOK BASED UL TRANSMISSIONS IN A NETWORK

Abstract

The embodiments herein relate to a method performed by a network node and a network node. The method comprises setting a higher-layer parameter usage in at least one sounding reference signal, SRS, resource set configuration to nonCodebook or Codebook, wherein each configured SRS resource set comprises one or more SRS resources, and scheduling a physical uplink shared channel (PUSCH) transmission via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set; and receiving from the user equipment a physical uplink shared channel that is transmitted using the ports associated with the indicated SRS resources.

Claims

1-22. (canceled)

23. A method performed by a user equipment (UE), the method comprising: receiving a configuration from a network node via a higher layer, the configuration comprising at least two sounding reference signal (SRS) resource sets wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to Codebook (CB); receiving a scheduling of at least one physical uplink shared channel (PUSCH) transmission from the network node via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set; mapping a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and transmitting a PUSCH using antenna ports associated with the indicated SRS resources.

24. The method according to claim 23, wherein the DCI indicates as many transmitted precoding matrix index (TPMI) values as the number of SRS resources indicated via the SRI field of the DCI in which a first TPMI value indicates the precoder for the antenna ports corresponding to a first SRS resource and a second TPMI value indicates the precoder for the antenna ports corresponding to a second SRS resource and so on.

25. The method according to claim 23, wherein any two SRS resources configured for two different SRS resource sets, having the same time domain behavior which includes one of the following: aperiodic, semi-persistent or periodic, can be transmitted simultaneously by the UE.

26. The method according to claim 23, wherein the maximum number of SRS resource sets supported by the UE for codebook-based uplink transmission, is a UE capability that is reported to said network node by said UE via a higher-layer message, for radio resource control (RRC) and wherein the value of the UE capability is identical to the number of either all of UE panels/Tx-Rx RF chains, or a subset of UE panels/Tx-Rx RF chains.

27. The method according to claim 23, wherein in the case of aperiodic SRS transmission by the UE, reference SRS resource sets are the SRS resource sets transmitted after the most recent downlink control information (DCI) carrying a SRS request triggering the aperiodic resource sets, wherein the reference SRS resource sets with respect to an SRI field are defined as the SRS resource sets from which the SRS resources are indicated by the SRI field.

28. The method according to claim 23, wherein in the case of semi-persistent SRS transmission by the UE, reference SRS resource sets for a SRI of the PUSCH-scheduling DCI in transmission slot n are all the semi-persistent SRS resource sets that were not deactivated by a medium access control (MAC) control element command before n−k slots, where k is a constant value, wherein the reference SRS resource sets with respect to an SRI field are defined as the SRS resource sets from which the SRS resources are indicated by the SRI field.

29. The method according to claim 23, wherein, only the SRS resources that belong to reference SRS resource sets are indicated in the SRI field of the PUSCH-scheduling DCI, wherein the reference SRS resource sets with respect to an SRI field are defined as the SRS resource sets from which the SRS resources are indicated by the SRI field.

30. The method according to claim 23, wherein said mapping is performed using the following table: TABLE-US-00007 SRI Bit SRS resource(s) SRI Bit SRS resource(s) field indicated for CB field indicated for CB mapped to UL mapped to UL index (N.sub.max, SRSres.sup.(CB) = 1) index (N.sub.max, SRSres.sup.(CB) = 2) 0 s.sub.0.sup.0 0 s.sub.0.sup.0 1 s.sub.0.sup.1 1 s.sub.0.sup.1 2 s.sub.0.sup.0, s.sub.0.sup.1 3 reserved wherein the notation s.sub.i.sup.j denotes the i-th SRS resource of the j-th reference SRS resource set, the values of i and j are given by i=0, . . . , N.sub.SRSres.sup.(CB)−1 and j=0, . . . , N.sub.SRSset,Tx.sup.(CB)−1, respectively, wherein N.sub.SRSset,Tx.sup.(CB) is the number of reference SRS resource sets.

31. The method according to claim 23, wherein said mapping is performed using the following table: TABLE-US-00008 SRI Bit field SRS resource(s) SRI Bit field SRS resource(s) mapped to indicated for CB UL mapped to indicated for CB UL index (N.sub.max, SRSres.sup.(CB) = 1) index (N.sub.max, SRSres.sup.(CB) = 2) 0 s.sub.0.sup.0 0 s.sub.0.sup.0 1 s.sub.1.sup.0 1 s.sub.1.sup.0 2 s.sub.0.sup.1 2 s.sub.0.sup.1 3 s.sub.1.sup.1 3 s.sub.1.sup.1 4 s.sub.0.sup.0, s.sub.0.sup.1 5 s.sub.0.sup.0, s.sub.1.sup.1 6 s.sub.1.sup.0, s.sub.0.sup.1 7 s.sub.1.sup.0, s.sub.1.sup.1 wherein the notation s.sub.i.sup.j denotes the i-th SRS resource of the j-th reference SRS resource set, the values of i and j are given by i=0, . . . , N.sub.SRSres.sup.(CB)−1 and j=0, . . . , N.sub.SRSset,Tx.sup.(CB)−1, respectively, wherein N.sub.SRSset,Tx.sup.(CB) is the number of reference SRS resource sets.

32. The method according to claim 23, wherein said mapping is performed using the following table: TABLE-US-00009 SRI Bit SRS resource(s) SRI Bit SRS resource(s) SRI Bit SRS resource(s) field indicated for field indicated for field indicated for mapped CB UL mapped CB UL mapped CB UL to index (N.sub.max, SRSres.sup.(CB) = 1) to index (N.sub.max, SRSres.sup.(CB) = 2) to index (N.sub.max, SRSres.sup.(CB) = 3) 0 s.sub.0.sup.0 0 s.sub.0.sup.0 0 s.sub.0.sup.0 1 s.sub.0.sup.1 1 s.sub.0.sup.1 1 s.sub.0.sup.1 2 s.sub.0.sup.2 2 s.sub.0.sup.2 2 s.sub.0.sup.2 3 reserved 3 s.sub.0.sup.0, s.sub.0.sup.1 3 s.sub.0.sup.0, s.sub.0.sup.1 4 s.sub.0.sup.0, s.sub.0.sup.2 4 s.sub.0.sup.0, s.sub.0.sup.2 5 s.sub.0.sup.1, s.sub.0.sup.2 5 s.sub.0.sup.1, s.sub.0.sup.2 6-7 reserved 6 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.2 7 reserved wherein the notation s.sub.i.sup.j denotes the i-th SRS resource of the j-th reference SRS resource set, the values of i and j are given by i=0, . . . , N.sub.SRSres.sup.(CB)−1 and j=0, . . . , N.sub.SRSset,Tx.sup.(CB)−1, respectively, wherein N.sub.SRSset,Tx.sup.(CB) is the number of reference SRS resource sets.

33. The method according to claim 23, wherein the number of bits of the SRI field are required to indicate: a maximum of N.sub.max,SRSres.sup.(CB) resources from N.sub.SRSset,Tx.sup.(CB) codebook-based SRS resource sets is $.Math.{\log }_2\left({.Math.}_{n=1}^{N_{\max ,\mathrm{SRSres}}^{\left(\mathrm{CB}\right)}}\left(\begin{array}{c}{N}_{\mathrm{SRSset},\mathrm{Tx}}^{\left(\mathrm{CB}\right)}\\ n\end{array}\right).Math.{\left(N_{\mathrm{SRSres}}^{\left(\mathrm{CB}\right)}\right)}^n\right)],$ wherein N.sub.SRSres.sup.(CB) is the number of SRS resources configured per SRS resource set whose higher-layer parameter usage set to ‘codebook’.

34. A network node comprising a processor and a memory, the memory containing instructions executable by the processor whereby the network node is configured to: configure at least two sounding reference signal (SRS) resource sets for a user equipment (UE) via a higher layer, wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to Codebook (CB); schedule at least one physical uplink shared channel (PUSCH) transmission for said user equipment via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set; map a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and receive from the user equipment a PUSCH that is transmitted using antenna ports associated with the indicated SRS resources.

35. A user equipment (UE) comprising a processor and a memory, said memory containing instructions executable by said processor whereby said UE is configured to: receive a configuration from a network node via a higher layer, the configuration comprising at least two sounding reference signal (SRS) resource sets wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to Codebook (CB); receive a scheduling of at least one physical uplink shared channel (PUSCH) transmission from the network node via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set; map a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and transmit a PUSCH using the antenna ports associated with the indicated SRS resources.

36. A method performed by a network node, the method comprising: configuring at least two sounding reference signal (SRS) resource sets for a user equipment (UE) via a higher layer, wherein each SRS resource set comprises at least one SRS resource, and wherein the higher layer configuration of the SRS comprises a parameter usage and the value of the parameter is set to Codebook (CB); scheduling at least one physical uplink shared channel (PUSCH) transmission for said user equipment via a downlink control information (DCI) wherein at least two SRS resources are indicated via a sounding reference signal resource indicator (SRI) field of the DCI, wherein each SRS resource is associated with a different SRS resource set; mapping a given SRI bit field of the SRI field to the SRS resources indicated from associated SRS resource sets; and receiving from the user equipment a PUSCH that is transmitted using antenna ports associated with the indicated SRS resources.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Examples of embodiments and additional advantages of the embodiments herein are described in more detail with reference to attached drawings in which:

[0038] FIG. 1 shows reference SRS resource sets in the case of aperiodic SRS resource sets.

[0039] FIG. 2 is an illustration of the indication of SRS resources in the SRI field of the PUSCH-scheduling DCI.

[0040] FIG. 3 illustrates a flowchart of a method performed by a network node according to some exemplary embodiments herein.

DETAILED DESCRIPTION

[0041] In the following, is presented a detailed description of the exemplary embodiments in conjunction with the drawings, in several scenarios, to enable easier understanding of the solution(s) described herein.

[0042] The following embodiments propose a modification of the SRS resource set configuration of the 3GPP Rel. 15 specification [2] for non-codebook- and codebook-based uplink transmissions for UEs equipped with multiple panels/Tx-Rx RF chains in order to facilitate multi-panel-based uplink transmissions employing panel-specific power control.

[0043] In accordance with some exemplary embodiments, the higher-layer parameter usage in the SRS resource set configuration is set to ‘nonCodebook’ or ‘Codebook’. The number of SRS resource sets that can be configured per cell, BWP, and time-domain behavior is given by N.sub.SRSset.sup.(NCB) and N.sub.SRSset.sup.(CB), respectively. The number of configured SRS resource sets is identical to the number of either all of UE panels/Tx-Rx RF chains, or a subset of UE panels/Tx-Rx RF chains.

[0044] For example, a UE may be equipped with three panels/Tx-Rx RF chains and shall be configured with three SRS resource sets for non-codebook/codebook usage in a particular BWP with a specific time-domain behavior, such that the first SRS resource set having SRS resource set ID ‘100’ is associated with the first panel/Tx-Rx RF chain, the second SRS resource set having SRS resource set ID ‘101’ is associated with the second panel/Tx-Rx RF chain, and the third SRS resource set having SRS resource set ID ‘102’ is associated with the third panel/Tx-Rx RF chain.

[0045] In another example, the UE may be equipped with three panels/Tx-RX RF chains and is configured with only two SRS resource sets for non-codebook/codebook usage in a particular BWP with a specific time-domain behavior, such that the first SRS resource set having SRS resource set ID ‘100’ is associated with the first panel/Tx-Rx RF chain, and the second SRS resource set having SRS resource set ID ‘101’ is associated with the second panel/Tx-Rx RF chain.

[0046] In accordance with some exemplary embodiments, any two SRS resources from two different SRS resource sets, both the SRS resource sets configured with higher-layer parameter usage set to ‘nonCodebook’ or ‘Codebook’, the same time-domain behavior and the same BWP, can be transmitted simultaneously by the UE using multiple panels/Tx-Rx RF chains. For example, an SRS resource set with SRS resource set ID ‘100’ is configured with higher-layer parameter usage set to ‘codebook’ or ‘nonCodebook’ for a particular BWP in a cell and a particular time-domain behavior. Another SRS resource set with SRS resource set ID ‘101’ is configured with the same value for the higher-layer parameter usage as the SRS resource set ‘100’ and configured for the identical BWP in the same cell and the same time-domain behaviour as SRS resource set ‘100’. Any SRS resource from the SRS resource set ‘100’ can be transmitted simultaneously with any SRS resource from SRS resource set ‘101’. This essentially means that an SRS resource set consists of SRS resources that are transmitted from a particular panel/Tx-Rx RF chain at the UE.

[0047] In accordance with some exemplary embodiments, the maximum number of SRS resource sets supported by the UE per BWP, per cell and time-domain behavior, for codebook and non-codebook-based uplink transmission, is a UE capability and defined by higher layer (RRC) parameters, e.g., “maxNumberOfSRSResourceSetsCB” (N.sub.SRSset.sup.(CB)) and “maxNumberOfSRSResourceSetsNCB” (N.sub.STSset.sup.(NCB)). The UE capability parameters denote the maximum number of UE panels/Tx-Rx RF chains the UE supports for a particular SRS usage.

[0048] In accordance with some exemplary embodiments, each SRS resource in the SRS resource set configuration with the higher-layer parameter usage set to ‘nonCodebook’ is configured with only one SRS port. Each SRS port in this case has a one-to-one mapping with a demodulation reference signal (DMRS) port over which each data layer is transmitted. Hence, the number of SRS resources indicated in the PUSCH-scheduling DCI for non-codebook-based UL transmission automatically determines the maximum number of MIMO layers to be transmitted by the UE in the physical uplink shared channel (PUSCH).

[0049] In the following, indication of SRS resources for PUSCH (physical uplink shared channel) transmission is presented in according with some embodiments herein.

[0050] In accordance with some exemplary embodiments, for non-codebook-based PUSCH transmission, the PUSCH-scheduling DCI indicates up to L.sub.max.sup.(NCB) SRS resources for PUSCH transmission in the SRS resource indicator (SRI) field.

[0051] In accordance with some exemplary embodiments, for codebook-based PUSCH transmission, the PUSCH-scheduling DCI indicates up to N.sub.max,SRSres.sup.(CB) SRS resources in the SRI field. The value of N.sub.max,SRSres.sup.(CB) is a UE capability and defined by a higher-layer (RRC) parameter, e.g., “maxSimultSRSResourcesTxCBUL”.

[0052] In accordance with some exemplary embodiments, each SRS resource indicated in the SRI field of the PUSCH-scheduling-DCI for codebook or non-codebook-based PUSCH transmission is chosen from different SRS resource sets. For example, the SRI in the PUSCH-scheduling DCI indicates 3 SRS resources for PUSCH transmission. The first SRS resource indicated in the SRI belongs to the SRS resource set with SRS resource set ID ‘100’ configured with higher-layer parameter usage set to ‘codebook’ or ‘nonCodebook’ for a particular BWP in a cell and a particular time-domain behavior. The second SRS resource indicated in the SRI belongs to the SRS resource set having SRS resource set ID ‘101’ configured with the same value for the higher-layer parameter usage, identical BWP in the same cell and the same time-domain behavior as SRS resource set ‘100’. The third SRS resource indicated in the SRI belongs to the SRS resource set having SRS resource set ID ‘102’ configured with the same value for the higher-layer parameter usage, identical BWP in the same cell and the same time-domain behavior as SRS resource set ‘100’.

[0053] In accordance with some exemplary embodiments, the SRS resource sets from which the SRI field in the PUSCH-scheduling DCI indicates the SRS resources for PUSCH transmission are called reference SRS resource sets.

[0054] In accordance with embodiments, in the case of aperiodic SRS transmission, the reference SRS resource sets are the SRS resource sets transmitted after the most recent DCI carrying the SRS request triggering the aperiodic resource sets, see FIG. 1.

[0055] FIG. 1 illustrates the downlink (DL) and uplink (UL) transmission slots. FIG. 1 also shows the DCI (downlink control information) containing SRI that indicates SRS resources for PUSCH transmission from the SRS resources transmitted by the UE (grey coloured slots). The SRS resource sets mapped to an aperiodic trigger state ‘01’ transmitted are in the grey coloured slots. The DCI carrying SRS ‘01’ is also shown.

[0056] In accordance with some exemplary embodiments, in the case of semi-persistent SRS transmission, the reference SRS resource sets for the SRI of the PUSCH-scheduling DCI in transmission slot n are all the semi-persistent SRS resource sets that were not deactivated by a MAC control element command before n-k slots, where k is a constant value.

[0057] In accordance with embodiments, in the case of periodic SRS transmission, the indicated SRS resources in the SRI (SRS resource indicator (SRI)) field of the PUSCH-scheduling DCI are the periodic SRS resource sets configured by the higher-layer for the BWP (bandwidth-part) associated with the DCI.

[0058] In accordance with the embodiments, only the SRS resources that belong to the reference SRS resource set(s) is/are indicated in the SRI field of the PUSCH-scheduling DCI.

[0059] Let the number of reference SRS resource sets be N.sub.SRSset,Tx.sup.(NCB) for non-codebook-based SRS and N.sub.SRSset,Tx.sup.(CB) for codebook-based SRS. The values of N.sub.SRSset,Tx.sup.(CB) and N.sub.SRSset,Tx.sup.(NCB) satisfy the following inequalities: N.sub.SRSset,Tx.sup.(CB)≤N.sub.SRSset.sup.(CB) and N.sub.SRSset,Tx.sup.(NCB)≤N.sub.SRSset.sup.(NCB).

[0060] In accordance with some exemplary embodiments, Tables 1-6 below provide a mapping of a given SRI bit field to the SRS resources indicated from the associated SRS resource sets.

TABLE-US-00001 TABLE 1 SRI indices and indicated SRS resource(s) for when N.sub.SRSset, Tx.sup.(NCB) = 2, N.sub.SRSres.sup.(NCB) = 1 for NCB UL transmissions and N.sub.SRSset, Tx.sup.(CB) = 2, N.sub.SRSres.sup.(CB) = 1 for CB UL transmissions. SRS resource(s) SRS resource(s) SRI Bit indicated for NCB SRI Bit indicated for NCB field (L.sub.max.sup.(NCB) = 1) and field (L.sub.max.sup.(NCB) = 2) and mapped to CB UL mapped to CB UL index (N.sub.max, SRSres.sup.(CB) = 1) index (N.sub.max, SRSres.sup.(CB) = 2) 0 s.sub.0.sup.0 0 s.sub.0.sup.0 1 s.sub.0.sup.1 1 s.sub.0.sup.1 2 s.sub.0.sup.0, s.sub.0.sup.1 3 reserved

TABLE-US-00002 TABLE 2 SRI indices and indicated SRS resource(s) for when N.sub.SRSset, Tx.sup.(NCB) = 2, N.sub.SRSres.sup.(NCB) = 2 for NCB UL transmissions and N.sub.SRSset, Tx.sup.(CB) = 2, N.sub.SRSres.sup.(CB) = 2 for CB UL transmissions. SRS SRS resource(s) resource(s) SRI Bit indicated for indicated for field NCB (L.sub.max.sup.(NCB) = SRI Bit field NCB (L.sub.max.sup.(NCB) = mapped to 1) and CB UL mapped to 2) and CB UL index (N.sub.max, SRSres.sup.(CB) = 1) index (N.sub.max, SRSres.sup.(CB) = 2) 0 s.sub.0.sup.0 0 s.sub.0.sup.0 1 s.sub.1.sup.0 1 s.sub.1.sup.0 2 s.sub.0.sup.1 2 s.sub.0.sup.1 3 s.sub.1.sup.1 3 s.sub.1.sup.1 4 s.sub.0.sup.0, s.sub.0.sup.1 5 s.sub.0.sup.0, s.sub.1.sup.1 6 s.sub.1.sup.0, s.sub.0.sup.1 7 s.sub.1.sup.0, s.sub.1.sup.1

TABLE-US-00003 TABLE 3 SRI indices and indicated SRS resource(s) for when N.sub.SRSset, Tx.sup.(NCB) = 3, N.sub.SRSres.sup.(NCB) = 1 for NCB UL transmissions and N.sub.SRSset, Tx.sup.(CB) = 3, N.sub.SRSres.sup.(CB) = 1 for CB UL transmissions. SRS resource(s) SRS resource(s) SRS resource(s) SRI Bit indicated for NCB SRI Bit indicated for NCB SRI Bit indicated for NCB field (L.sub.max.sup.(NCB) = 1) and field (L.sub.max.sup.(NCB) = 2) and field (L.sub.max.sup.(NCB) = 3) and mapped CB UL mapped CB UL mapped CB UL to index (N.sub.max, SRSres.sup.(CB) = 1) to index (N.sub.max, SRSres.sup.(CB) = 2) to index (N.sub.max, SRSres.sup.(CB) = 3) 0 s.sub.0.sup.0 0 s.sub.0.sup.0 0 s.sub.0.sup.0 1 s.sub.0.sup.1 1 s.sub.0.sup.1 1 s.sub.0.sup.1 2 s.sub.0.sup.2 2 s.sub.0.sup.2 2 s.sub.0.sup.2 3 reserved 3 s.sub.0.sup.0, s.sub.0.sup.1 3 s.sub.0.sup.0, s.sub.0.sup.1 4 s.sub.0.sup.0, s.sub.0.sup.2 4 s.sub.0.sup.0, s.sub.0.sup.2 5 s.sub.0.sup.1, s.sub.0.sup.2 5 s.sub.0.sup.1, s.sub.0.sup.2 6-7 reserved 6 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.2 7 reserved

TABLE-US-00004 TABLE 4 SRI indices and indicated SRS resource(s) for when N.sub.SRSset, Tx.sup.(NCB) = 3, N.sub.SRSres.sup.(NCB) = 2 for NCB UL transmissions and N.sub.SRSset, Tx.sup.(CB) = 3, N.sub.SRSres.sup.(CB) = 2 for CB UL transmissions. SRS resource(s) SRS resource(s) SRS resource(s) SRI Bit indicated for NCB SRI Bit indicated for NCB SRI Bit indicated for NCB field (L.sub.max.sup.(NCB) = 1) and field (L.sub.max.sup.(NCB) = 2) and field (L.sub.max.sup.(NCB) = 3) and mapped CB UL mapped CB UL mapped CB UL to index (N.sub.max, SRSres.sup.(CB) = 1) to index (N.sub.max, SRSres.sup.(CB) = 2) to index (N.sub.max, SRSres.sup.(CB) = 3) 0 s.sub.0.sup.0 0 s.sub.0.sup.0 0 s.sub.0.sup.0 1 s.sub.0.sup.1 1 s.sub.0.sup.1 1 s.sub.0.sup.1 2 s.sub.0.sup.2 2 s.sub.0.sup.2 2 s.sub.0.sup.2 3 s.sub.1.sup.0 3 s.sub.1.sup.0 3 s.sub.1.sup.0 4 s.sub.1.sup.1 4 s.sub.1.sup.1 4 s.sub.1.sup.1 5 s.sub.1.sup.2 5 s.sub.1.sup.2 5 s.sub.1.sup.2 6-7 reserved 6 s.sub.0.sup.0, s.sub.0.sup.1 6 s.sub.0.sup.0, s.sub.0.sup.1 7 s.sub.0.sup.0, s.sub.0.sup.2 7 s.sub.0.sup.0, s.sub.0.sup.2 8 s.sub.0.sup.1, s.sub.0.sup.2 8 s.sub.0.sup.1, s.sub.0.sup.2 9 s.sub.0.sup.0, s.sub.1.sup.1 9 s.sub.0.sup.0, s.sub.1.sup.1 10 s.sub.0.sup.0, s.sub.1.sup.2 10 s.sub.0.sup.0, s.sub.1.sup.2 11 s.sub.0.sup.1, s.sub.1.sup.2 11 s.sub.0.sup.1, s.sub.1.sup.2 12 s.sub.1.sup.1, s.sub.1.sup.2 12 s.sub.1.sup.1, s.sub.1.sup.2 13-15 reserved 13 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.2 14 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.1.sup.2 15 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.0.sup.2 16 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.1.sup.2 17 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.0.sup.2 18 s.sub.0.sup.1, s.sub.0.sup.1, s.sub.1.sup.2 19 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.0.sup.2 20 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.1.sup.2 21-32 reserved

TABLE-US-00005 TABLE 5 SRI indices and indicated SRS resource(s) for when N.sub.SRSset, Tx.sup.(NCB) = 4, N.sub.SRSres.sup.(NCB) = 1 for NCB UL transmissions and N.sub.SRSset, Tx.sup.(CB) = 4, N.sub.SRSres.sup.(CB) = 1 for CB UL transmissions. SRS resource(s) SRS resource(s) SRS resource(s) SRS resource(s) SRI Bit indicated for NCB SRI Bit indicated for NCB SRI Bit indicated for NCB SRI Bit indicated for NCB field (L.sub.max.sup.(NCB) = 1) field (L.sub.max.sup.(NCB) = 2) field (L.sub.max.sup.(NCB) = 3) field (L.sub.max.sup.(NCB) = 4) mapped and CB UL mapped and CB UL mapped and CB UL mapped and CB UL to index (N.sub.max, SRSres.sup.(CB) = 1) to index (N.sub.max, SRSres.sup.(CB) = 2) to index (N.sub.max, SRSres.sup.(CB) = 3) to index (N.sub.max, SRSres.sup.(CB) = 4) 0 s.sub.0.sup.0 0 s.sub.0.sup.0 0 s.sub.0.sup.0 0 s.sub.0.sup.0 1 s.sub.0.sup.1 1 s.sub.0.sup.1 1 s.sub.0.sup.1 1 s.sub.0.sup.1 2 s.sub.0.sup.2 2 s.sub.0.sup.2 2 s.sub.0.sup.2 2 s.sub.0.sup.2 3 s.sub.0.sup.3 3 s.sub.0.sup.3 3 s.sub.0.sup.3 3 s.sub.0.sup.3 4 s.sub.0.sup.0, s.sub.0.sup.1 4 s.sub.0.sup.0, s.sub.0.sup.1 4 s.sub.0.sup.0, s.sub.0.sup.1 5 s.sub.0.sup.0, s.sub.0.sup.2 5 s.sub.0.sup.0, s.sub.0.sup.2 5 s.sub.0.sup.0, s.sub.0.sup.2 6 s.sub.0.sup.0, s.sub.0.sup.3 6 s.sub.0.sup.0, s.sub.0.sup.3 6 s.sub.0.sup.0, s.sub.0.sup.3 7 s.sub.0.sup.1, s.sub.0.sup.2 7 s.sub.0.sup.1, s.sub.0.sup.2 7 s.sub.0.sup.1, s.sub.0.sup.2 8 s.sub.0.sup.1, s.sub.0.sup.3 8 s.sub.0.sup.1, s.sub.0.sup.3 8 s.sub.0.sup.1, s.sub.0.sup.3 9 s.sub.0.sup.2, s.sub.0.sup.3 9 s.sub.0.sup.2, s.sub.0.sup.3 9 s.sub.0.sup.2, s.sub.0.sup.3 10-15 reserved 10 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.2 10 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.2 11 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.3 11 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.3 12 s.sub.0.sup.0, s.sub.0.sup.2, s.sub.0.sup.3 12 s.sub.0.sup.0, s.sub.0.sup.2, s.sub.0.sup.3 13 s.sub.0.sup.1, s.sub.0.sup.2, s.sub.0.sup.3 13 s.sub.0.sup.1, s.sub.0.sup.2, s.sub.0.sup.3 14-15 reserved 14 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.2, s.sub.0.sup.3 15 reserved

TABLE-US-00006 TABLE 6 SRI indices and indicated SRS resource(s) for when N.sub.SRSset, Tx.sup.(NCB) = 4, N.sub.SRSres.sup.(NCB) = 2 for NCB UL transmissions and N.sub.SRSset, Tx.sup.(CB) = 4, N.sub.SRSres.sup.(CB) = 2 for CB UL transmissions. SRS resource(s) SRS resource(s) SRS resource(s) SRS resource(s) SRI Bit indicated for NCB SRI Bit indicated for NCB SRI Bit indicated for NCB SRI Bit indicated for NCB field (L.sub.max.sup.(NCB) = 1) field (L.sub.max.sup.(NCB) = 2) field (L.sub.max.sup.(NCB) = 3) field (L.sub.max.sup.(NCB) = 4) mapped and CB UL mapped and CB UL mapped and CB UL mapped and CB UL to index (N.sub.max, SRSres.sup.(CB) = 1) to index (N.sub.max, SRSres.sup.(CB) = 2) to index (N.sub.max, SRSres.sup.(CB) = 3) to index (N.sub.max, SRSres.sup.(CB) = 4) 0 s.sub.0.sup.0 0 s.sub.0.sup.0 0 s.sub.0.sup.0 0 s.sub.0.sup.0 1 s.sub.0.sup.1 1 s.sub.0.sup.1 1 s.sub.0.sup.1 1 s.sub.0.sup.1 2 s.sub.0.sup.2 2 s.sub.0.sup.2 2 s.sub.0.sup.2 2 s.sub.0.sup.2 3 s.sub.0.sup.3 3 s.sub.0.sup.3 3 s.sub.0.sup.3 3 s.sub.0.sup.3 4 s.sub.1.sup.0 4 s.sub.1.sup.0 4 s.sub.1.sup.0 4 s.sub.1.sup.0 5 s.sub.1.sup.1 5 s.sub.1.sup.1 5 s.sub.1.sup.1 5 s.sub.1.sup.1 6 s.sub.1.sup.2 6 s.sub.1.sup.2 6 s.sub.1.sup.2 6 s.sub.1.sup.2 7 s.sub.1.sup.3 7 s.sub.1.sup.3 7 s.sub.1.sup.3 7 s.sub.1.sup.3 8 s.sub.0.sup.0, s.sub.0.sup.1 8 s.sub.0.sup.0, s.sub.0.sup.1 8 s.sub.0.sup.0, s.sub.0.sup.1 9 s.sub.0.sup.0, s.sub.1.sup.1 9 s.sub.0.sup.0, s.sub.1.sup.1 9 s.sub.0.sup.0, s.sub.1.sup.1 10 s.sub.1.sup.0, s.sub.0.sup.1 10 s.sub.1.sup.0, s.sub.0.sup.1 10 s.sub.1.sup.0, s.sub.0.sup.1 11 s.sub.1.sup.0, s.sub.1.sup.1 11 s.sub.1.sup.0, s.sub.1.sup.1 11 s.sub.1.sup.0, s.sub.1.sup.1 12 s.sub.0.sup.0, s.sub.0.sup.2 12 s.sub.0.sup.0, s.sub.0.sup.2 12 s.sub.0.sup.0, s.sub.0.sup.2 13 s.sub.0.sup.0, s.sub.1.sup.2 13 s.sub.0.sup.0, s.sub.1.sup.2 13 s.sub.0.sup.0, s.sub.1.sup.2 14 s.sub.1.sup.0, s.sub.0.sup.2 14 s.sub.1.sup.0, s.sub.0.sup.2 14 s.sub.1.sup.0, s.sub.0.sup.2 15 s.sub.2.sup.0, s.sub.1.sup.2 15 s.sub.2.sup.0, s.sub.1.sup.2 15 s.sub.2.sup.0, s.sub.1.sup.2 16 s.sub.0.sup.0, s.sub.0.sup.3 16 s.sub.0.sup.0, s.sub.0.sup.3 16 s.sub.0.sup.0, s.sub.0.sup.3 17 s.sub.0.sup.0, s.sub.1.sup.3 17 s.sub.0.sup.0, s.sub.1.sup.3 17 s.sub.0.sup.0, s.sub.1.sup.3 18 s.sub.1.sup.0, s.sub.0.sup.3 18 s.sub.1.sup.0, s.sub.0.sup.3 18 s.sub.1.sup.0, s.sub.0.sup.3 19 s.sub.1.sup.0, s.sub.1.sup.3 19 s.sub.1.sup.0, s.sub.1.sup.3 19 s.sub.1.sup.0, s.sub.1.sup.3 20 s.sub.0.sup.1, s.sub.0.sup.2 20 s.sub.0.sup.1, s.sub.0.sup.2 20 s.sub.0.sup.1, s.sub.0.sup.2 21 s.sub.0.sup.1, s.sub.1.sup.2 21 s.sub.0.sup.1, s.sub.0.sup.2 21 s.sub.0.sup.1, s.sub.0.sup.2 22 s.sub.1.sup.1, s.sub.0.sup.2 22 s.sub.1.sup.1, s.sub.0.sup.2 22 s.sub.1.sup.1, s.sub.0.sup.2 23 s.sub.1.sup.1, s.sub.1.sup.2 23 s.sub.1.sup.1, s.sub.1.sup.2 23 s.sub.1.sup.1, s.sub.1.sup.2 24 s.sub.0.sup.1, s.sub.0.sup.3 24 s.sub.0.sup.1, s.sub.0.sup.3 24 s.sub.0.sup.1, s.sub.0.sup.3 25 s.sub.0.sup.1, s.sub.1.sup.3 25 s.sub.0.sup.1, s.sub.1.sup.3 25 s.sub.0.sup.1, s.sub.1.sup.3 26 s.sub.1.sup.1, s.sub.0.sup.3 26 s.sub.1.sup.1, s.sub.0.sup.3 26 s.sub.1.sup.1, s.sub.0.sup.3 27 s.sub.1.sup.1, s.sub.1.sup.3 27 s.sub.1.sup.1, s.sub.1.sup.3 27 s.sub.1.sup.1, s.sub.1.sup.3 28 s.sub.0.sup.2, s.sub.0.sup.3 28 s.sub.0.sup.2, s.sub.0.sup.3 28 s.sub.0.sup.2, s.sub.0.sup.3 29 s.sub.0.sup.2, s.sub.1.sup.3 29 s.sub.0.sup.2, s.sub.1.sup.3 29 s.sub.0.sup.2, s.sub.1.sup.3 30 s.sub.1.sup.2, s.sub.0.sup.3 30 s.sub.1.sup.2, s.sub.0.sup.3 30 s.sub.1.sup.2, s.sub.0.sup.3 31 s.sub.1.sup.2, s.sub.1.sup.3 31 s.sub.1.sup.2, s.sub.1.sup.3 31 s.sub.1.sup.2, s.sub.1.sup.3 32 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.2 32 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.2 33 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.1.sup.2 33 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.1.sup.2 34 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.0.sup.2 34 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.0.sup.2 35 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.1.sup.2 35 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.1.sup.2 36 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.0.sup.2 36 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.0.sup.2 37 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.1.sup.2 37 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.1.sup.2 38 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.0.sup.2 38 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.0.sup.2 39 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.1.sup.2 39 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.1.sup.2 40 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.3 40 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.3 41 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.1.sup.3 41 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.1.sup.3 42 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.0.sup.3 42 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.0.sup.3 43 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.1.sup.3 43 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.1.sup.3 44 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.0.sup.3 44 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.0.sup.3 45 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.1.sup.3 45 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.1.sup.3 46 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.0.sup.3 46 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.0.sup.3 47 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.1.sup.3 47 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.1.sup.3 48 s.sub.0.sup.0, s.sub.0.sup.2, s.sub.0.sup.3 48 s.sub.0.sup.0, s.sub.0.sup.2, s.sub.0.sup.3 49 s.sub.0.sup.0, s.sub.0.sup.2, s.sub.1.sup.3 49 s.sub.0.sup.0, s.sub.0.sup.2, s.sub.1.sup.3 50 s.sub.0.sup.0, s.sub.1.sup.2, s.sub.0.sup.3 50 s.sub.0.sup.0, s.sub.1.sup.2, s.sub.0.sup.3 51 s.sub.0.sup.0, s.sub.1.sup.2, s.sub.1.sup.3 51 s.sub.0.sup.0, s.sub.1.sup.2, s.sub.1.sup.3 52 s.sub.1.sup.0, s.sub.0.sup.2, s.sub.0.sup.3 52 s.sub.1.sup.0, s.sub.0.sup.2, s.sub.0.sup.3 53 s.sub.1.sup.0, s.sub.0.sup.2, s.sub.1.sup.3 53 s.sub.1.sup.0, s.sub.0.sup.2, s.sub.1.sup.3 54 s.sub.1.sup.0, s.sub.1.sup.2, s.sub.0.sup.3 54 s.sub.1.sup.0, s.sub.1.sup.2, s.sub.0.sup.3 55 s.sub.1.sup.0, s.sub.1.sup.2, s.sub.1.sup.3 55 s.sub.1.sup.0, s.sub.1.sup.2, s.sub.1.sup.3 56 s.sub.0.sup.1, s.sub.0.sup.2, s.sub.0.sup.3 56 s.sub.0.sup.1, s.sub.0.sup.2, s.sub.0.sup.3 57 s.sub.0.sup.1, s.sub.0.sup.2, s.sub.1.sup.3 57 s.sub.0.sup.1, s.sub.0.sup.2, s.sub.1.sup.3 58 s.sub.0.sup.1, s.sub.1.sup.2, s.sub.0.sup.3 58 s.sub.0.sup.1, s.sub.1.sup.2, s.sub.0.sup.3 59 s.sub.0.sup.1, s.sub.1.sup.2, s.sub.1.sup.3 59 s.sub.0.sup.1, s.sub.1.sup.2, s.sub.1.sup.3 60 s.sub.1.sup.1, s.sub.0.sup.2, s.sub.0.sup.3 60 s.sub.1.sup.1, s.sub.0.sup.2, s.sub.0.sup.3 61 s.sub.1.sup.1, s.sub.0.sup.2, s.sub.1.sup.3 61 s.sub.1.sup.1, s.sub.0.sup.2, s.sub.1.sup.3 62 s.sub.1.sup.1, s.sub.1.sup.2, s.sub.0.sup.3 62 s.sub.1.sup.1, s.sub.1.sup.2, s.sub.0.sup.3 63 s.sub.1.sup.1, s.sub.1.sup.2, s.sub.1.sup.3 63 s.sub.1.sup.1, s.sub.1.sup.2, s.sub.1.sup.3 64 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.2, s.sub.0.sup.3 65 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.0.sup.2, s.sub.1.sup.3 66 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.1.sup.2, s.sub.0.sup.3 67 s.sub.0.sup.0, s.sub.0.sup.1, s.sub.1.sup.2, s.sub.1.sup.3 68 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.0.sup.2, s.sub.0.sup.3 69 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.0.sup.2, s.sub.1.sup.3 70 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.1.sup.2, s.sub.0.sup.3 71 s.sub.0.sup.0, s.sub.1.sup.1, s.sub.1.sup.2, s.sub.1.sup.3 72 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.0.sup.2, s.sub.0.sup.3 73 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.0.sup.2, s.sub.1.sup.3 74 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.1.sup.2, s.sub.0.sup.3 75 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.0.sup.2, s.sub.0.sup.3 76 s.sub.1.sup.0, s.sub.0.sup.1, s.sub.1.sup.2, s.sub.1.sup.3 77 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.1.sup.2, s.sub.0.sup.3 78 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.1.sup.2, s.sub.0.sup.3 79 s.sub.1.sup.0, s.sub.1.sup.1, s.sub.1.sup.2, s.sub.1.sup.3 80-127 reserved

[0061] In the Tables above, the notation s.sub.i.sup.j denotes the i-th SRS resource of the j-th reference SRS resource set. For non-codebook based SRS, the values of i and j are given by i=0, . . . , N.sub.SRSres.sup.(NCB)−1 and j=0, . . . , N.sub.SRSset,Tx.sup.(NCB)−1, respectively. For codebook-based SRS, the values of i and j are given by i=0, . . . , N.sub.SRSres.sup.(CB)−1 and j=0, . . . , N.sub.SRSset,Tx.sup.(CB)−1, respectively. For the purpose of indication with the SRI as shown in Tables 1-6, the SRS resource sets in the reference SRS resource sets are ordered in ascending order based on the SRS resource set ID and are indexed from 0, . . . , N.sub.SRSset,Tx.sup.(NCB)−1 and 0, . . . , N.sub.SRSset,Tx.sup.(CB)−1 for non-codebook based SRS and codebook based SRS, respectively. Similarly, the SRS resources in each SRS resource set are ordered in ascending order based on the SRS resource ID and are indexed from 0, . . . , N.sub.SRSres.sup.(NCB)−1 and 0, . . . , N.sub.SRSres.sup.(CB)−1 for non-codebook based SRS and codebook based SRS, respectively. For example, there are 3 SRS resource sets that act as reference SRS resource sets with SRS resource set ID values ‘100’, ‘102’ and ‘103’. The notation s.sub.i.sup.0 denotes the i-th resource in SRS resource set ‘100’, s.sub.i.sup.1 denotes the i-th resource in SRS resource set ‘102’, and s.sub.i.sup.2 denotes the i-th resource in SRS resource set ‘103’.

[0062] Hence, the notation s.sub.i.sup.j denotes the i-th SRS resource of the j-th reference SRS resource set, wherein L.sub.max.sup.(NCB) is the value of the UE capability parameter ‘maxNumberMIMO-LayersNonCB-PUSCH’ defined in 3GPP Rel. 15, and for non-codebook based SRS, the values of i and j are given by i=0, . . . , N.sub.SRSres.sup.(NCB)−1 and j=0, . . . , N.sub.SRSset,Tx.sup.(NCB)−1, respectively, wherein N.sub.SRSset,Tx.sup.(NCB) is the number of reference SRS resource sets. For codebook-based SRS, the values of i and j are given by i=0, . . . , N.sub.SRSres.sup.(CB)−1 and j=0, . . . , N.sub.SRSset,Tx.sup.(CB)−1, respectively, wherein N.sub.SRSset,Tx.sup.(CB) is the number of reference SRS resource sets.

[0063] In accordance with exemplary embodiments, the number of bits of the SRI field required to indicate [0064] a maximum of L.sub.max.sup.(NCB) resources from N.sub.SRSset,Tx.sup.(NCB) non-codebook-based SRS resource sets is

[00001]$.Math.{\log }_2\left({.Math.}_{n=1}^{L_{\max }^{\left(\mathrm{NCB}\right)}}\left(\begin{array}{c}{N}_{\mathrm{SRSset},\mathrm{Tx}}^{\left(\mathrm{NCB}\right)}\\ n\end{array}\right).Math.{\left(N_{\mathrm{SRSres}}^{\left(\mathrm{NCB}\right)}\right)}^n\right)],$

and [0065] a maximum of N.sub.max,SRSres.sup.(CB) resources from N.sub.SRSset,Tx.sup.(CB) codebook-based SRS resource sets is

[00002]$.Math.{\log }_2\left({.Math.}_{n=1}^{N_{\max ,\mathrm{SRSres}}^{\left(\mathrm{CB}\right)}}\left(\begin{array}{c}{N}_{\mathrm{SRSset},\mathrm{Tx}}^{\left(\mathrm{CB}\right)}\\ n\end{array}\right).Math.{\left(N_{\mathrm{SRSres}}^{\left(\mathrm{CB}\right)}\right)}^n\right)].$

[0066] An illustration of the indication of SRS resources in the SRI field of the PUSCH-scheduling DCI is provided in FIG. 2 for four reference SRS resource sets and two SRS resources per set, i.e., N.sub.SRSset,Tx.sup.(CB) or N.sub.SRSset,Tx.sup.(NCB)=4 and N.sub.SRSres.sup.(NCB) or N.sub.SRSres.sup.(NCB)=2. In SRI examples 1 and 2, 3 and 2 SRS resources are indicated respectively, each one from a different SRS resource set. The arrows indicate the SRS resource set the indicated SRS resource belongs to. The SRI bit field that shall be used to indicate the chosen set of resources is obtained from Table 6. Each table lists the possible combinations of SRS resources that the gNB may report and the corresponding SRI bit field that shall be used for the same.

[0067] FIG. 1 shows a scenario where N.sub.SRSset,Tx.sup.(CB) or N.sub.SRSset,Tx.sup.(NCB)=4 and N.sub.SRSres.sup.(NCB) or N.sub.SRSres.sup.(NCB)=2 is illustrated in the figure (refer to Table 6 for SRI bit field mapping for the same). Two examples of SRI indication are shown where each indicated SRS resource is from a different SRS resource set (arrows indicate the SRS resource set the indicate resource is configured in).

[0068] In accordance with embodiments, for codebook-based PUSCH transmission, for a DCI indicating N.sub.SRSres,ind.sup.(CB) SRS resources in the SRI, N.sub.SRSres,ind.sup.(CB) associated transmitted precoding matrix indicators (TPMIs) are indicated by the DCI, such that the k-th precoding matrix indicated by the k-th TPMI is used to precode the antenna ports (used for PUSCH transmission) associated with the k-th SRS resource indicated by the SRI (k=1, . . . , N.sub.SRSres,ind.sup.(CB)).

[0069] In accordance with embodiments, the UE expects to be indicated with TPMI values for PUSCH transmission such that the sum of the transmission rank values of the indicated precoders does not exceed L.sub.max.sup.(CB).

[0070] Referring to FIG. 3, there is illustrated a method performed by a network node according to previously described embodiments. The method comprises [0071] (301) setting a higher-layer parameter usage in at least one sounding reference signal, SRS, resource set configuration to nonCodebook or Codebook, wherein each configured SRS resource set comprises one or more SRS resources, and wherein any two SRS resources configured for two different SRS resource sets having the same time domain behavior can be transmitted simultaneously by a user equipment, UE. Hence step (301) comprises configuring at least two SRS resource sets for a UE via the higher layer parameter usage; and the value of the parameter is set to nonCodebook or Codebook. The method further comprises scheduling at least one PUSCH transmission for the UE via a DCI, wherein at least two SRS resources are indicated via the SRI field in the SRI and each SRS resource is associated with a different SRS resource set; and [0072] (302) configuring said UE accordingly, so the network node receives from the UE a PUSCH that is transmitted using the ports associated with the indicated SRS resources.

[0073] According to an embodiment each configured SRS resource set is associated with the UE's, panel or group of antenna ports or a Tx-Rx RF chain, and wherein the number of configured SRS resource sets is identical to the maximum number of UE panels or antenna ports, or to a subset of said UE panels or antenna ports, or to the maximum number of UE transmission-reception, Tx-Rx, radio frequency chains or to a subset of said Tx-Rx radio frequency, RF, chains.

[0074] According to an embodiment the maximum number of SRS resource sets supported by the UE for codebook and non-codebook-based uplink transmission, is a UE capability that is reported to said network node by said UE via a higher-layer message, for e.g., radio resource control, RRC, and wherein the value of the UE capability is equal to the total number of UE panel(s)/group of antenna port(s)/Tx-Rx RF chains or a subset of UE panel(s)/group of antenna port(s)/Tx-Rx RF chains

[0075] According to an embodiment the UE capability denotes the maximum number of UE panels/Tx-Rx RF chains the UE supports for a particular SRS usage.

[0076] According to an embodiment each SRS resource in the SRS resource set configuration with the higher-layer parameter usage set to ‘nonCodebook’ is configured with only one SRS port.

[0077] According to an embodiment each SRS resource indicated in a sounding resource indicator, SRI, field of a physical uplink shared channel, PUSCH-scheduling-downlink control information, DCI, for codebook or non-codebook-based PUSCH transmission is chosen from different SRS resource sets.

[0078] According to an embodiment, in the case of aperiodic SRS transmission, the reference SRS resource sets are the SRS resource sets transmitted after the most recent downlink control information, DCI, carrying a SRS request triggering the aperiodic resource sets.

[0079] According to an embodiment, in the case of semi-persistent SRS transmission, the reference SRS resource sets for a SRI of the PUSCH-scheduling DCI in transmission slot n are all the semi-persistent SRS resource sets that were not deactivated by a medium access control, MAC, control element command before n-k slots, where k is a constant value.

[0080] According to an embodiment, in the case of periodic SRS transmission, the reference SRS resource sets are the periodic SRS resource sets configured by the higher-layer for the BWP, bandwidth-part, associated with the DCI.

[0081] According to an embodiment, only the SRS resources that belong to the reference SRS resource set(s) is/are indicated in the SRI field of the PUSCH-scheduling DCI.

[0082] According to an embodiment, the method further comprises mapping a given SRI bit field to the SRS resources indicated from associated SRS resources sets. The mapping may be performed using any of tables 1-6 previously described.

[0083] The embodiments herein also provide a network node comprising a processor and a memory, said memory containing instructions executable by said processor whereby said network node is operative to perform any of method claims 1-12. Further, there is provided a user equipment comprising a processor and a memory, said memory containing instructions executable by said processor whereby said user equipment is operative to be configured by said network node according to claim 13, and a method performed by a user equipment, the method comprising, receiving a configuration from a network node according to claim 13 and operate according to said received configuration.

[0084] There is also provided a computer program comprising instructions which when executed on at least one processor of the network according to claim 13 cause at least said one processor to carry out the method according to anyone of claim 1-12.

[0085] There is also provided a carrier containing the computer program, wherein the carrier is one of a computer readable storage medium; an electronic signal, optical signal or a radio signal.

[0086] Throughout this disclosure, the word “comprise” or “comprising” has been used in a non-limiting sense, i.e. meaning “consist at least of”. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. The embodiments herein may be applied in any wireless systems including GSM, 3G or WCDMA, LTE or 4G, LTE-A (or LTE-Advanced), 5G, WiMAX, WiFi, Bluetooth, satellite communications, TV broadcasting etc. wherein SRS configuration and indication for codebook and non-codebook based UL transmissions in a network is employed.

REFERENCES

[0087] [1] 3GPP TS 38.214, “Physical layer procedures for data (Release 15),” 3rd Generation Partnership Project; Technical Specification Group Radio Access Network, Version 15.4.0, January 2019. [0088] [2] 3GPP TS 38.331, “Radio Resource Control (RRC) protocol specification (Release 15),” 3rd Generation Partnership Project; Technical Specification Group Radio Access Network, Version 15.1.0, March 2018. [0089] [3] 3GPP TS 38.211, “Physical channels and modulation (Release 15),” 3rd Generation Partnership Project; Technical Specification Group Radio Access Network, Version 15.4.0, January 2019. [0090] [4] R1-1901348, “Feature lead summary of Enhancements on Multi-beam Operations,” LG Electronics, Taipei, Taiwan, January 2019.