Attorney Docket No.: AF4861-PCT (31517-3237) ENHANCED UPLINK TRANSMISSIONS FOR WIRELESS COMMUNICATIONS USING MORE THAN FOUR LAYERS CROSS-REFERENCE TO RELATED PATENT APPLICATION(S) This application claims the benefit of PCT Provisional Application No. PCT/CN2022/112038, filed August 12, 2022, PCT Provisional Application No. PCT/CN2022/123283, filed September 30, 2022, and PCT Provisional Application No. PCT/CN2022/123232, filed September 30, 2022, the disclosures of which are incorporated herein by reference as if set forth in full. TECHNICAL FIELD This disclosure generally relates to systems and methods for wireless communications and, more particularly, to uplink transmissions using more than four layers. BACKGROUND Wireless devices are becoming widely prevalent and are increasingly using wireless channels. The 3 ^rd Generation Partnership Program (3GPP) is developing one or more standards for wireless communications. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a network diagram illustrating an example network environment, in accordance with one or more example embodiments of the present disclosure. FIG. 2 illustrates an example portion of downlink control information (DCI) signaling used for precoding uplink transmissions, in accordance with one or more example embodiments of the present disclosure. FIG. 3 illustrates a flow diagram of illustrative process for DCI signaling used for precoding uplink transmissions, in accordance with one or more example embodiments of the present disclosure. FIG 4. illustrates a network, in accordance with one or more example embodiments of the present disclosure. FIG. 5 schematically illustrates a wireless network, in accordance with one or more example embodiments of the present disclosure. FIG. 6 is a block diagram illustrating components, in accordance with one or more example embodiments of the present disclosure. Attorney Docket No.: AF4861-PCT (31517-3237) DETAILED DESCRIPTION The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, algorithm, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims. Wireless devices may operate as defined by technical standards. For cellular telecommunications, the 3 ^rd Generation Partnership Program (3GPP) define communication techniques, including precoders (e.g., transmit precoding matrix indices (TPMIs)) for uplink communications. Currently, 3GPP defines up to four layers for physical uplink shared channel (PUSCH) transmissions. The precoders for PUSCH transmissions are defined in 3GPP TS 38.211, depending on the rank value (e.g., number of layers), number of antenna ports and waveform (e.g., cyclic prefix orthogonal frequency division multiplexing or discrete Fourier transform spread orthogonal frequency division multiplexing). Table 1 shows the precoding matrix W for a single-layer transmission using two antenna ports. Table 1: Precoding Matrix W for Single-Layer Transmission (Rank 1) Using Two Antenna Ports Table 2 shows the precoding matrix W for a two-layer transmission using two antenna ports with transform precoding disabled. Table 2: Precoding Matrix W for Two-Layer Transmission (Rank 2) Using Two Antenna Ports (cyclic prefix orthogonal frequency division multiplexing) Table 3 shows a precoding matrix W for single-layer transmission using four antenna ports with transform precoding enabled. Attorney Docket No.: AF4861-PCT (31517-3237) Table 3: Precoding Matrix W for Single-Layer Transmission (Rank 1) Using Four Antenna Ports (discrete Fourier transform spread orthogonal frequency division multiplexing) Table 4 shows a precoding matrix W for single-layer transmission using four antenna ports with transform precoding disabled.

Attorney Docket No.: AF4861-PCT (31517-3237) Table 4: Precoding Matrix W for Single-Layer Transmission (Rank 1) Using Four Antenna Ports (cyclic prefix orthogonal frequency division multiplexing) Table 5 shows a precoding matrix W for two-layer transmission using four antenna ports with transform precoding disabled.

Attorney Docket No.: AF4861-PCT (31517-3237) Table 5: Precoding Matrix W for Two-Layer Transmission (Rank 2) Using Four Antenna Ports (cyclic prefix orthogonal frequency division multiplexing) Table 6 shows a precoding matrix W for three-layer transmission using four antenna ports with transform precoding disabled.

Attorney Docket No.: AF4861-PCT (31517-3237) Table 6: Precoding Matrix W for Three-Layer Transmission (Rank 3) Using Four Antenna Ports (cyclic prefix orthogonal frequency division multiplexing) Table 7 shows a precoding matrix W for four-layer transmission using four antenna ports with transform precoding disabled. Table 7: Precoding Matrix W for Four-Layer Transmission (Rank 4) Using Four Antenna Ports (cyclic prefix orthogonal frequency division multiplexing): In the DCI scheduling PUSCH (e.g., DCI format 0_1/0_2), TPMI could be indicated via the “Precoding information and number of layers” field, which can indicate the rank and precoder used for PUSCH transmission, i.e., the rank indicator and precoder indicator are jointly encoded. In 3GPP Rel-18, up to eight layers will be supported for PUSCH transmission. The codebook should be enhanced to support up to eight layers with eight antenna ports. The codebook design could be based on Rel-15 uplink 2Tx/4Tx precoders. Or the codebook design could be based on Rel-15 downlink Type I codebook. For Rel-15 DL Type I codebook, it is based on the antenna structure and configuration, such as ( _^^ , _^ ), and ( _^^ ,^ _ଶ ), where _^^ , _^ are the number of antenna elements in horizontal and vertical direction, respectively, and are the oversampling factor in horizontal and Attorney Docket No.: AF4861-PCT (31517-3237) vertical direction, respectively. For Type I codebook, the precoder could be constructed according to the rank value and parameter ^ _^,ଶ , ^ _^,ଷ , and ^ _ଶ reported by the UE. However, the number of precoders could be large leading to overhead in DCI. The overhead should be addressed in the codebook design. The TPMIs could be categorized into full coherent TPMI, partial coherent TPMI and non-coherent TPMI, depending on whether relative phase can be maintained among all (full coherent), or a subset (partial coherent), or none (non-coherent) of the antenna ports. Table 8 shows the non-coherent, partial coherent and full coherent TPMIs 4-ports with rank-1 and rank-2. Table 8: Example of Non-Coherent, Partial Coherent, and Full Coherent Precoding Matrix In Rel-18, the uplink transmission will be extended to eight Tx layers. Therefore, the codebook with eight ports should be defined. For full coherent UE, the codebook could be based on Rel-15 Type I codebook. However, the partial coherent codebook may be used. In addition, for Rel-18, up to eight layers could be used for uplink transmission, and multiple codewords could be used. The switching between single codeword and multiple codewords should be supported. The current 3GPP codebook is only for up to four transmission layers and four ports for uplink transmissions, including PUSCH transmissions. In one or more embodiments, an enhanced method of signaling the TPMI indication may support more than four layers of transmission for PUSCH and other uplink transmissions, and may result in reduced DCI overhead. An enhanced codebook may support up to eight transmission layers and antenna ports, and dynamic switching between a single codeword and multiple codewords. In one or more embodiments, there may be a joint encoding of the rank indicator and precoder indicator. For example, for PUSCH transmission with 8 Tx, the rank indicator and precoder indicator are jointly encoded in one field(s) in the DCI, i.e., in the TPMI table, the precoders for each rank (depending on the maximum rank configuration) are included. Attorney Docket No.: AF4861-PCT (31517-3237) Alternatively, an equation is specified to determine PMI index based on bitfield for RI and CQI or vice-versa, e.g., Equation (1) can be used: (Equation 1), where I is the bitfield value, RI is maximum rank value, N(r) – total number of PMIs for a rank r = 1,2,…RI, N(0) = 0, PMI – the PMI numbering for rank RI. It could be applied for the codebook based on Rel-15 DL Type I codebook, and the codebook based on Rel-15 UL 2Tx/4Tx precoders. In one or more embodiments, there may be separate encodings of the rank indicator and for the precoder indicator, such as via the DCI. For example, for PUSCH transmission with 8 ports, separate rank indication and precoder indication could be used in the DCI scheduling PUSCH transmission. It could be applied for the codebook based on Rel-15 DL Type I codebook, and the codebook based on Rel-15 UL 2Tx/4Tx precoders. In the DCI scheduling PUSCH, a new field(s) could be added to indicate the rank used for the PUSCH transmission, i.e., for rank indication. Alternatively, some existing field(s) could be reused/repurposed to indicate the rank. The field length depends on the configured maximum rank. In the DCI scheduling PUSCH, another new field(s) is used to indicate the precoder used for PUSCH transmission (alternatively, some existing field(s) could be reused/repurposed). The field length is determined by: assuming _^ is the number of precoders for rank- x, where x is smaller than or equal to the configured maximum rank. In another example, if the codebook is based on Rel-15 DL Type I codebook, the ^{precoder indication in DCI could indicate the parameters for the codebook construction, e.g.,} _{^^,^, ^^,ଶ, ^^,ଷ, and ^ଶ (^^,^, ^^,ଶ, ^^,ଷ, and ^ଶ could be indicated via one field or separate fields, the} field(s) could be newly added or some existing field(s) could be reused/repurposed). In such ^{case, the field length of the precoder indication is: where:} of ^ _^,ଷ for rank-x; Attorney Docket No.: AF4861-PCT (31517-3237) ^{is the length to indicate ^ଶ, and ^^ଶ,௫ is the number of values of} _{^ଶ for rank-x.} If the number of values for is only one, then the corresponding length is zero bits. For multi-TRP operation, two TPMIs with 8Tx could be indicated. For joint encoding, two fields could be included to indicate two TPMIs with 8Tx. For separate encoding, in order to indicate two TPMIs with 8Tx, two fields could be included for rank indication to indicate two ranks (or one field if the same rank is applied), and two fields could be included for precoder indication to indicate two precoders (or two fields could be included to indicate two set of parameters ^ _^,^ , ^ _^,ଶ , ^ _^,ଷ , and ^ _ଶ ). In one or more embodiments, a codebook subset configuration may be provided. For example, for PUSCH transmission with 8 Tx, the codebook subsets include full coherent codebook subset, partial coherent codebook subset, and non-coherent codebook subset. The full coherent codebook subset could contain full coherent precoders, partial coherent precoders, and non-coherent precoders. The partial coherent codebook subset could contain partial coherent precoders and non-coherent precoders. The non-coherent codebook subset could contain non-coherent precoders. In one or more embodiments, for PUSCH transmission with 8 Tx, the full coherent codebook subset only contains full coherent precoders. The partial coherent codebook subset only contains partial coherent precoders (or the partial coherent codebook subset contains partial coherent and non-coherent precoders). The non-coherent codebook subset only contains non-coherent precoders. The codebook subset could be configured by RRC or updated by MAC-CE or DCI. The DCI field configuration for TPMI indication could be determined according to the configured/updated codebook subset. In one example, the same TPMI indication scheme (whether joint encoding of rank indicator and precoder indicator, or separate rank indication and precoder indication) are used for all the codebook subsets. In another example, different TPMI indication scheme (whether joint encoding of rank indicator and precoder indicator, or separate rank indication and precoder indication) could be used for different codebook subset. For example, for full coherent codebook subset, separate rank indication and precoder indication is used, and for partial coherent/non-coherent codebook subset, joint encoding of rank indicator and precoder indicator is used. Attorney Docket No.: AF4861-PCT (31517-3237) In another example, if the codebook subset is indicated by DCI, the indication for codebook subset could be based on new fields or some existing fields could be reused/repurposed. ACK should be provided for the DCI indicating codebook subset. And application time should be defined between the receiving of the DCI and the application of indicated codebook subset. The embodiments for the coodbook subset configuration could be applied for the codebook based on Rel-15 DL Type I codebook, and the codebook based on Rel-15 UL 2Tx/4Tx precoders. In one or more embodiments, the enhanced codebook may have low overhead based on a DL Type 1 codebook. For example, for PUSCH transmission with 8Tx, if the codebook is based on Rel-15 DL Type I codebook, then RRC or MAC-CE or DCI could be used to configure/update some parameters for the Type I codebook, such as ^ _^,^ , ^ _^,ଶ , ^ _^,ଷ , and ^ _ଶ . In one example, the parameter ^ _ଶ which represents the co-phasing factor could be configured/reconfigured by RRC. Or it could be configured by RRC and updated by MAC-CE. In the DCI scheduling PUSCH, only are indicated. The indicated precoder is constructed according to the ^ _^,^ /^ _^,ଶ /^ _^,ଷ indicated by DCI and ^ _ଶ configured/updated by RRC/MAC-CE. In another example, RRC could configure/reconfigure the values (or subset of the ^{values) of one or several or all the parameters: ^^,^, ^^,ଶ, ^^,ଷ, and ^ଶ (different values of} _{^^,^/^^,ଶ/^^,ଷ/^ଶ could be configured for different rank). Or MAC-CE could be used to} ^{configure/select some the values (or subset of the values) of one or several or all the parameters:} _{^^,^, ^^,ଶ, ^^,ଷ, and ^ଶ (different values of could be configured for different rank).} In the DCI, the size of the field for TPMI indication is determined according to the subset of the values of ^ _^,^ , ^ _^,ଶ , ^ _^,ଷ , and ^ _ଶ configured by RRC/MAC-CE (or the DCI field size is pre- defined if the values of ^ _^,^ , ^ _^,ଶ , ^ _^,ଷ , and ^ _ଶ is configured by MAC-CE). In one or more embodiments, for PUSCH transmission with 8Tx, if the codebook is based on Rel-15 DL Type I codebook, there could be some restriction to reduce the number of precoders. For example, the value of the oversampling factor ( _^^ ,^ _ଶ ) could be set to be (2,1) or (1,1). In another example, only a subset of the values are used for the codebook generation and precoder indication. In another example, the values (or the subset of the values) for ^ _^,^ /^ _^,ଶ /^ _^,ଷ /^ _ଶ could be reported by the UE, i.e., subject to UE capability. In one or more embodiments, for PUSCH transmission with 8Tx, rank restriction could be introduced. The rank restriction could be configured/updated by RRC/MAC-CE. In the DCI, Attorney Docket No.: AF4861-PCT (31517-3237) only the precoders for the ranks allowed by the rank restriction can be indicated. And the DCI field size is determined according to the number of precoders for the allowed ranks. In one or more embodiments, for PUSCH transmission with 8Tx, if the codebook is based on Rel-15 DL Type I codebook, subset of PMI index(es) may be considered for precoder generation and indication. For index parameter can be configured by the network or specified, where precoding matrix index ^ _^,^ is determined based on index െ 1} indicated in the For index ^ _^,ଶ , parameter ^ _ଶ can be configured by the network or specified, where precoding matrix index ^ _^,ଶ is determined based on index ^^ _^,ଶ = {0,1, … , െ 1} indicated in the DCI, where ^ _^,ଶ = ^ _ଶ ή ^^ _^,ଶ (e.g. ^ _ଶ = ^ _ଶ ). For index ^ _^,ଷ , a subset of index values is indicated in DCI or index ^ _^,ଷ is not indicated in the DCI and fixed to 0. For index ^ _ଶ , parameter ^ can be configured by the network or specified, where ^{precoding matrix index ^ଶ is determined based on index ^^ଶ indicated in the DCI, where ^ଶ =} _{rank > 1.} In another example, the values ^ _ଶ , and ^ could be reported by the UE, subject to UE capability. In one or more embodiments, for PUSCH transmission with 8Tx, if the codebook is based on Rel-15 DL Type I codebook, the codebook is based on structure ^ = × _^ . In this case, multiple DCIs could be used for the TPMI indication. For example, one DCI is used to indicate the parameters for W1 (i.e., ^ _^,^ , ^ _^,ଶ , ^ _^,ଷ ), and the other DCI is used to indicate the parameters for W2 (i.e., ^ _ଶ ). In one option, the DCI for W1 could be transmitted less frequently and the DCI for W2 could be transmitted more frequently. Regarding the DCI for W1, the indication for W1 parameters could be based on new fields or some existing fields could be reused/repurposed. ACK should be provided for the DCI indicating W1. And application time should be defined between the receiving of the DCI and the application of indicated W1. In another option, the DCI for W2 could be transmitted less frequently and the DCI for W1 could be transmitted more frequently. Regarding the DCI for W2, the indication for W2 parameters could be based on new fields or some existing fields could be reused/repurposed. ACK should be provided for the DCI indicating W2. And application time should be defined between the receiving of the DCI and the application of indicated W2. Attorney Docket No.: AF4861-PCT (31517-3237) In one or more embodiments, the TPMI indication for the codebook may be based on Rel-15 UL 2Tx/4Tx precoders. For example, for PUSCH transmission with 8Tx, if the codebook is based on Rel-15 UL 2Tx/4Tx precoders, the codebook could be generated according to Equation (2) or Equation (3): (Equation 2), ^ _்௫ = _^,ସ்௫ ^ _^^,ଶ்௫ (Equation 3), w ^{herein ^^,ଶ்௫ is a Rel-15 UL 2Tx precoder, ^,ସ்௫ is a Rel-15 UL 4Tx precoder, and} _{^ represents Kronecker product operation. For full coherent precoders with 8Tx, both ^^,ଶ்௫} and _^,ସ்௫ should be full coherent. For partial coherent precoders with 8Tx, _^^,ଶ்௫ should be non-coherent and _^,ସ்௫ should be full coherent/partial coherent; Or _^^,ଶ்௫ should be full coherent and^ _{ଶ,ସ்௫} should be non-coherent/partial coherent. For non-coherent precoders with 8Tx, both _^^,ଶ்௫ and _^,ସ்௫ should be non-coherent. For rank value of {5, 7}, the precoders with 8Tx could be generated by dropping one column of the precoder with rank {6, 8}. In one example for the precoder generation, _^^,ଶ்௫ and _^,ସ்௫ could include all the non-coherent/partial-coherent/full coherent precoders for certain rank. For example, _^^,ଶ்௫ could be TPMI {#2, #3, #4, #5} as shown in Figure 1. In another option, _^^,ଶ்௫ and _^,ସ்௫ could include a subset of all the non-coherent/partial-coherent/full coherent precoders for certain rank. For example, _^^,ଶ்௫ could be just TPMI {#2, #3} as shown in Figure 1. Alternatively, the supported _^^,ଶ்௫ and _^,ସ்௫ could be reported by the UE, i.e., subject to UE capability. For TPMI indication, in the first option, the rank indicator and precoder indicator are jointly encoded in one field(s) in the DCI, i.e., in the TPMI table, the precoders for each rank (depending on the maximum rank configuration) are included. In the second option for TPMI indication, separate rank indication and precoder indication could be used in the DCI scheduling PUSCH transmission. In the DCI scheduling PUSCH, a new field(s) could be added to indicate the rank used for the PUSCH transmission, i.e., for rank indication. Alternatively, some existing field(s) could be reused/repurposed to indicate the rank. The field length depends on the configured maximum rank. In the DCI scheduling PUSCH, another new field(s) is used to indicate the precoder used for PUSCH transmission (alternatively, some existing field(s) could be reused/repurposed). The field length is determined by: assuming _^ is the number of precoders for rank- x, where x is smaller than or equal to the configured maximum rank. Attorney Docket No.: AF4861-PCT (31517-3237) In the third option for TPMI indication, _^^,ଶ்௫ and _^,ସ்௫ could be indicated in the DCI scheduling PUSCH. New field(s) could be added to indicate _^^,ଶ்௫ and _^,ସ்௫ (alternatively, some existing field(s) could be reused/repurposed). When or _^,ସ்௫ is non-coherent, then it can represent the antenna port group selection. In the fourth option for TPMI indication, RRC could be used to configure the values (or select a subset) of _^^,ଶ்௫ and/or _^,ସ்௫ , i.e., the UL 2Tx/4Tx precoders (different and/or _^,ସ்௫ could be configured for different rank). Alternatively, MAC-CE could be used to configure the values (or select a subset) of _^^,ଶ்௫ and/or _^,ସ்௫ , i.e., the UL 2Tx/4Tx precoders (different _^^,ଶ்௫ and/or _^,ସ்௫ could be configured for different rank). It could be applied to the first option to the third option. And the DCI field size in the first option to the third option is determined according to the subset of _^^,ଶ்௫ and/or _^,ସ்௫ configured by RRC/MAC-CE (or the DCI field size could be pre-defined if^ and/or^ _{ଶ,ସ்௫} is configured ^{by MAC-CE). In another example, the values (or the subset of the values) for ^^,ଶ்௫ and/or} ^ _{,ସ்௫ could be reported by the UE, i.e., subject to UE capability.} In the fifth option for TPMI indication, multiple DCIs could be used for the TPMI indication. For example, one DCI is used to indicate _^^,ଶ்௫ , and the other DCI is used to indicate _^,ସ்௫ . In one example, the DCI for _^^,ଶ்௫ could be transmitted less frequently and the DCI for _^,ସ்௫ could be transmitted more frequently. Regarding the DCI for _^^,ଶ்௫ , the indication for _^^,ଶ்௫ could be based on new fields or some existing fields could be reused/repurposed. ACK should be provided for the DCI indicating _^^,ଶ்௫ . And application ^{time should be defined between the receiving of the DCI and the application of indicated} ^ _{^,ଶ்௫. In another example, the DCI for ^,ସ்௫ could be transmitted less frequently and the} DCI for _^^,ଶ்௫ could be transmitted more frequently. Regarding the DCI for the indication for _^,ସ்௫ could be based on new fields or some existing fields could be reused/repurposed. ACK should be provided for the DCI indicating _^,ସ்௫ . And application ^{time should be defined between the receiving of the DCI and the application of indicated} ^ _,ସ்௫. For multi-TRP operation, two TPMIs with 8Tx could be indicated. For joint encoding (the first option), two fields could be included to indicate two TPMIs with 8Tx. For separate encoding (the second option), in order to indicate two TPMIs with 8Tx, two fields could be included for rank indication to indicate two ranks (or one field if the same rank is applied), and two fields could be included for precoder indication to indicate two precoders. For the third Attorney Docket No.: AF4861-PCT (31517-3237) and the fourth option, in order two indicate two TPMIs with 8Tx, two fields could be included for two and two fields could be included for two _^,ସ்௫ . This embodiment could be applied to one or multiple or all the following UE coherence: non-coherent, partial coherent, full coherent. In one or more embodiments, the TPMI indication for the codebook may be based on Rel-15 DL Type I codebook and Rel-15 UL 2Tx/4Tx precoders. For example, for PUSCH transmission with 8Tx, the full coherent precoders could be based on Rel-15 DL Type I codebook, and the non-coherent/partial coherent precoders could be based on Rel-15 UL 2Tx/4Tx precoders. In the first option, the full coherent codebook subset contains the precoders for all the coherence. In such case, for full coherent codebook subset, joint encoding between rank indictor and precoder indicator, or separate rank indication and precoder indication (as shown in Figure 8) could be used (or the options in Section D could be used). For partial coherent and non-coherent codebook subset, either option (from the first option to the fifth option) in Section E could be used. In the second option, the full coherent codebook subset only contains the full coherent precoders. In such case, for full coherent codebook subset, joint encoding between rank indictor and precoder indicator, or separate rank indication and precoder indication (as shown in Figure 8 or Figure 9), or the options in Section D could be used. For partial coherent and non-coherent codebook subset, either option (from the first option to the fifth option) could be used. In one or more embodiments, the uplink codebook with 8 Tx could be based on Rel-15 ^{Type I codebook. For full coherent UE, the precoding matrix for rank-^ could be denoted as} ^ _{^ and is generated according to Rel-15 Type I codebook, where the size of ^^ is 8 × ^.} For partial coherent UE, the precoding matrix _^^^ for rank-^ could be generated based on the 8-port full coherent codebook _^^ . The partial coherent precoding matrix _^^^ for rank-^ could be generated according to Equation (4). ^ ^{^ 0 ڮ 0} ^ _{^^ = ^ × ^^ = ൦} ^{0 ^} ڭ _ڭ ^{ଶ ڮ 0} ڰ _ڭ ^{൪ × ^^ (Equation 4).} 0 _{0 ڮ ^଼} The matrix ^ (the size of ^ is 8 × 8) is a diagonal matrix and represents antenna/port selection. The value of the diagonal elements ^ _^ (1 ^ ^ ^ 8) could be either zero or non-zero values. For the non-zero values of it means the corresponding antenna port ^ are co-phasing Attorney Docket No.: AF4861-PCT (31517-3237) ports. The number of non-zero values of ^ _^ depends on the number of co-phasing ports. For the partial coherent UE with two antenna groups, each group contains four co-phasing antenna ports, the number of non-zero values of^ _^ is four. For the partial coherent UE with four antenna ^{groups, each group contains two co-phasing antenna ports, the number of non-zero values of} _{^^ is two.} For example, for the partial coherent UE with two antenna groups, each group contains four co-phasing antenna ports, i.e., antenna port group {#1, #2, #3, #4} and antenna port group {#5, #6, #7, #8}. When generating the partial coherent precoders, either the group of {^ _^ , ^ _ଶ , ^ _ଷ , ^ _ସ } or the group of {^ _ହ , ^ _^ , ^ _^ , ^ _଼ } could be non-zero value. For example, either {^ _^ , ^ _ଶ , ^ _ଷ , ^ _ସ }=1 and {^ _ହ , ^ _^ , ^ _^ , ^ _଼ }=0, or {^ _^ , ^ _ଶ , ^ _ଷ , ^ _ସ }=0 and {^ _ହ , ^ _^ , ^ _^ , ^ _଼ }=1. One example of the partial coherent precoding matrix for rank-1 is: One example of the partial coherent precoding matrix for rank-2 is: In this manner, for the generated partial coherent precoders, the transmission from multi-layers is always transmitted from the same antenna/port group. In another embodiment, the partial coherent precoding matrix _^^^ for rank-^ could be expressed by column vector. ^ _^^ = ^[ ^^^,^ ^^^,ଶ ^ڮ ^^^,௫ ^] (Equation 5) The size of one column vector _^^^,^ is 8 × 1, where 1 ^ ^ ^ ^. The 8-port full coherent codebook _^^ for rank-^ could also be expressed by column vector. ^ _^ = [ _{^^,^ ^^,ଶ} ^ڮ _^^,௫ ] (Equation 6) The size of one column vector _^^,^ is 8 × 1, where 1 ^ ^ ^ ^. Attorney Docket No.: AF4861-PCT (31517-3237) The column vector of the partial coherent precoding matrix could be generated according to Equation (7). The matrix ^ (the size of ^ is 8 × 8) is a diagonal matrix and represents antenna/port selection. The value of the diagonal elements ^ _^ (1 ^ ^ ^ 8) could be either zero or non-zero values. For the non-zero values of ^ _^ , it means the corresponding antenna port ^ are co-phasing ports. For different layers, the non-zero values of ^ _^ could be over different antenna ports. In this way, for the generated partial coherent precoders, the transmission from different layers could be transmitted over different antenna/port group. For example, for the partial coherent UE with two antenna groups, each group contains four co-phasing antenna ports, i.e., antenna port group {#1, #3, #5, #7} and antenna port group {#2, #4, #6, #8}. For Rank-2 precoders, for the first layer (^ = 1), {^ _^ , ^ _ଷ , ^ _ହ , ^ _^ }=1 and {^ _ଶ , ^ _ସ , ^ _^ , ^ _଼ }=0. For the second layer (^ = 2), {^ _^ , ^ _ଷ , ^ _ହ , ^ _^ }=0 and {^ _ଶ , ^ _ସ , ^ _^ , ^ _଼ }=1. One example of the partial coherent precoding matrix for rank-2 is: In another embodiment, the UE should report the UE antenna structure/layout, such as number of antenna/port groups (including in the vertical/horizontal direction), number of antennas/ports per group (including in the vertical/horizontal direction), total number of antennas/ports (including in the vertical/horizontal direction). In another example, the UE should report the coherence type (full coherence/partial coherence/non-coherence). For partial coherent UE, the UE could also report the coherence port number, for example, port {#1, #3, #5, #7} or port {#1, #2, #3, #4}. In one or more embodiments, multiple codewords could be used for uplink transmission with 8Tx, e.g., two codewords. And multiple MCS/RV/NDI fields could be configured in the DCI scheduling PUSCH, e.g., two MCS/RV/NDI fields, one for each codeword. Attorney Docket No.: AF4861-PCT (31517-3237) In one example, whether one codeword or multiple codewords are used could be configured by RRC. In another example, if the maximum number of layers is 4 (the maximum number of layers is configured by RRC maxRank or maxMIMO-Layers), then single codeword is used. If the maximum number of layers is larger than 4, then multiple (e.g., two) codewords are used. In another example, whether single codeword or multiple codewords are used could depends on the number of layers indicated by DCI. If the number of layers indicated by DCI is larger than 4, then multiple (e.g., two) codewords are used, otherwise single codeword is used. In another example, a new field could be added to the DCI (or some existing field could be repurposed) to indicate whether single codeword or multiple codewords are used. For example, a new field is added to indicate whether the second codeword is enabled or not. If the second codeword is disabled, then the corresponding MCS/RV/NDI fields for the second codeword should be ignored by the UE. In another example, multiple maxRank or maxMIMO-Layers values could be configured, one for each codeword. Whether single codeword or multiple codewords is used could be configured/indicated by RRC/DCI. In another embodiment, the maximum number of codewords, e.g., 1 or 2, could be configured by RRC. If the maximum number of layers of PUSCH configured by RRC is smaller than or equal to 4, then the maximum number of codewords should be 1. If the maximum number of layers of PUSCH configured by RRC is larger than 4, then the maximum number of codewords could be 2. If different MCS/RV/NDI field are used for two codewords, then the two MCS fields/two RV fields/two NDI fields should be included in the DCI when the maximum number of codewords is configured as 2 by RRC. When the maximum number of codewords is configured as 1 by RRC, only the first MCS field/the first RV field/the first NDI field is included in the DCI. When the maximum number of codewords is configured as 2 by RRC, in the first option, whether one or two codewords is used for PUSCH could be indicated by the number of layers of PUSCH via the DCI. If the number of layers of PUSCH indicated by the DCI is smaller than or equal to 4, then only one codeword is used, e.g., only the first codeword is used (the second MCS field/the second RV field/the second NDI field could be set to all zeros, or it should be ignored by the UE). If the number of layers of PUSCH indicated by the DCI is larger than 4, then both codewords are used. Attorney Docket No.: AF4861-PCT (31517-3237) When the maximum number of codewords is configured as 2 by RRC, in the second option, whether one or two codewords is used for PUSCH could be indicated by some specific value(s) of one or several fields in the DCI. For example, if the second MCS field and/or the second RV field is set to specific value(s), then it means only the first codeword is used and the second MCS field/the second RV field/the second NDI field should be ignored by the UE. In another embodiment, if the current active BWP is configured with maximum of one codeword for PUSCH, and BWP switching is triggered to another BWP which is configured with maximum of two codewords for PSUCH, then MCS/RV/NDI field for the second codeword should be zero padded. And the MCS/RC/NDI field for the second codeword should be ignored by the UE for the new BWP. The above descriptions are for purposes of illustration and are not meant to be limiting. Numerous other examples, configurations, processes, algorithms, etc., may exist, some of which are described in greater detail below. Example embodiments will now be described with reference to the accompanying figures. FIG. 1 is a network diagram illustrating an example network environment 100, in accordance with one or more example embodiments of the present disclosure. Wireless network 100 may include one or more UEs 120 and one or more RANs 102 (e.g., gNBs), which may communicate in accordance with 3GPP communication standards. The UE(s) 120 may be mobile devices that are non-stationary (e.g., not having fixed locations) or may be stationary devices. In some embodiments, the UEs 120 and the RANs 102 may include one or more computer systems similar to that of FIGs. 3-5. One or more illustrative UE(s) 120 and/or RAN(s) 102 may be operable by one or more user(s) 110. A UE may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable UE, a quality-of-service (QoS) UE, a dependent UE, and a hidden UE. The UE(s) 120 (e.g., 124, 126, or 128) and/or RAN(s) 102 may include any suitable processor-driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static device. For example, UE(s) 120 may include, a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabookTM computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (IoT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA Attorney Docket No.: AF4861-PCT (31517-3237) device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a “carry small live large” (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID), an “origami” device or computing device, a device that supports dynamically composable computing (DCC), a context-aware device, a video device, an audio device, an A/V device, a set-top-box (STB), a blu-ray disc (BD) player, a BD recorder, a digital video disc (DVD) player, a high definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a personal video recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, a music player, or the like. Other devices, including smart devices such as lamps, climate control, car components, household components, appliances, etc. may also be included in this list. As used herein, the term “Internet of Things (IoT) device” is used to refer to any object (e.g., an appliance, a sensor, etc.) that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID), a near-field communication (NFC) ID, etc.) and can transmit information to one or more other devices over a wired or wireless connection. An IoT device may have a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like. An IoT device can have a particular set of attributes (e.g., a device state or status, such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light- emitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an IoT network such as a local ad-hoc network or the Internet. For example, IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the IoT network. IoT devices may also Attorney Docket No.: AF4861-PCT (31517-3237) include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Accordingly, the IoT network may be comprised of a combination of “legacy” Internet-accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.). Any of the UE(s) 120 (e.g., UEs 124, 126, 128), and UE(s) 120 may be configured to communicate with each other via one or more communications networks 130 and/or 135 wirelessly or wired. The UE(s) 120 may also communicate peer-to-peer or directly with each other with or without the RAN(s) 102. Any of the communications networks 130 and/or 135 may include, but not limited to, any one of a combination of different types of suitable communications networks such as, for example, broadcasting networks, cable networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and/or public networks. Further, any of the communications networks 130 and/or 135 may have any suitable communication range associated therewith and may include, for example, cellular networks. In addition, any of the communications networks 130 and/or 135 may include any type of medium over which network traffic may be carried including, but not limited to, coaxial cable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC) medium, microwave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof. Any of the UE(s) 120 (e.g., UE 124, 126, 128) and RAN(s) 102 may include one or more communications antennas. The one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the UE(s) 120 (e.g., UEs 124, 126 and 128), and RAN(s) 102. Some non-limiting examples of suitable communications antennas include cellular antennas, 3GPP family of standards compatible antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi-omnidirectional antennas, or the like. The one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the UEs 120 and/or RAN(s) 102. Any of the UE(s) 120 (e.g., UE 124, 126, 128), and RAN(s) 102 may be configured to perform directional transmission and/or directional reception in conjunction with wirelessly communicating in a wireless network. Any of the UE(s) 120 (e.g., UE 124, 126, 128), and RAN(s) 102 may be configured to perform such directional transmission and/or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays or the like). Each of the multiple Attorney Docket No.: AF4861-PCT (31517-3237) antenna arrays may be used for transmission and/or reception in a particular respective direction or range of directions. Any of the UE(s) 120 (e.g., UE 124, 126, 128), and RAN(s) 102 may be configured to perform any given directional transmission towards one or more defined transmit sectors. Any of the UE(s) 120 (e.g., UE 124, 126, 128), and RAN(s) 102 may be configured to perform any given directional reception from one or more defined receive sectors. MIMO beamforming in a wireless network may be accomplished using RF beamforming and/or digital beamforming. In some embodiments, in performing a given MIMO transmission, UE 120 and/or RAN(s) 102 may be configured to use all or a subset of its one or more communications antennas to perform MIMO beamforming. Any of the UE 120 (e.g., UE 124, 126, 128), and RAN(s) 102 may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by any of the UE(s) 120 and RAN(s) 102 to communicate with each other. The radio components may include hardware and/or software to modulate and/or demodulate communications signals according to pre-established transmission protocols. The radio components may further have hardware and/or software instructions to communicate via one or more 3GPP protocols and using 3GPP bandwidths. The radio component may include any known receiver and baseband suitable for communicating via the communications protocols. The radio component may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, and digital baseband. In one or more embodiments, and with reference to FIG.1, one or more of the UEs 120 may exchange frames 140 with the RANs 102. The frames 140 may include UL and DL frames, TMPI signaling, codewords, PUSCH transmissions, DCI transmissions, and the like as described herein. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting. FIG. 2 illustrates an example portion 200 of downlink control information (DCI) signaling used for precoding uplink transmissions, in accordance with one or more example embodiments of the present disclosure. Referring to FIG.2, the DCI portion 200 (e.g., for DCI 0_1/0_2) for precoder signaling may include a rank indicator 202 (e.g., to indicate the rank used for an uplink transmission such as PUSCH) and a precoder indicator 204 (e.g., to indicate the precoder used for the uplink transmission). Attorney Docket No.: AF4861-PCT (31517-3237) In an embodiment, for PUSCH transmission with 8 ports, the rank indicator 202 and the precoder indicator 204 may be separate in the DCI scheduling PUSCH transmission. It could be applied for the codebook based on Rel-15 DL Type I codebook, and the codebook based on Rel-15 UL 2Tx/4Tx precoders. The rank indicator 202 may be a new DCI field. Alternatively, some existing field(s) could be reused/repurposed to indicate the rank. The field length depends on the configured maximum rank. In the DCI scheduling PUSCH, the precoder indicator 204 may be new (alternatively, some existing field(s) could be reused/repurposed). The precoder indicator 204 field length is determined by: assuming _^ is the number of precoders for rank-x, where x is smaller than or equal to the configured maximum rank. In another example, if the codebook is based on Rel-15 DL Type I codebook, the precoder indicator 204 in DCI could indicate the parameters for the codebook construction, e.g.,^ _^,^ ,^ _^,ଶ ,^ _^,ଷ , and^ _ଶ (^ _^,^ ,^ _^,ଶ ,^ _^,ଷ , and^ _ଶ could be indicated via one field or separate fields, the field(s) could be newly added or some existing field(s) could be reused/repurposed). In ^{such case, the field length of the precoder indication is:} _{^^^^ଶ ^^^^൫ ^^^^,௫൯^^+^^^^ଶ ^^^^൫ ^^^ଶ,௫൯^^+^^^^ଶ ^^^^൫ ^^^ଷ,௫൯^^+^^^^ଶ ^^^^൫ ^^ଶ,௫൯^^,} ^where: ^ _{^^^ଶ ^^^^൫ ^^^^,௫൯^^: is the length to indicate ^^,^, and ^^^^,௫ is the number of values} ^{of ^^,ଷ for rank-x;} ^^^^ _ଶ ^^^^൫ _^^ଶ,௫ ൯^^: is the length to indicate ^ _ଶ , and _^^ଶ,௫ is the number of values of _{^ଶ for rank-x.} If the number of values for ^ _^,^ /^ _^,ଶ /^ _^,ଷ /^ _ଶ is only one, then the corresponding length of the precoder indicator 204 is zero bits. For multi-TRP operation, two TPMIs with 8Tx could be indicated. For joint encoding, two fields could be included to indicate two TPMIs with 8Tx. For separate encoding, in order to indicate two TPMIs with 8Tx, two fields could be included for rank indicator 202 to indicate two ranks (or one field if the same rank is applied), and two fields could be included for Attorney Docket No.: AF4861-PCT (31517-3237) precoder indicator 204 to indicate two precoders (or two fields could be included to indicate two set of parameters ^ _^,^ , ^ _^,ଶ , ^ _^,ଷ , and ^ _ଶ ). FIG. 3 illustrates a flow diagram of illustrative process 300 for DCI signaling used for precoding uplink transmissions, in accordance with one or more example embodiments of the present disclosure. At block 302, a device (e.g., a RANs 102 of FIG. 1, the LTE RAN 410 of FIG. 4, the NG-RAN 414 of FIG. 4) may encode a precoder rank indicator (e.g., the precoder rank indicator 202 of FIG. 2) for use by a UE (e.g., the UE 120 of FIG. 1, the UE 402 of FIG. 4) in an eight-transmitter uplink transmission to the device. At block 304, the device may encode a precoder indicator (e.g., the precoder indicator 204 of FIG. 2), indicative of a precoder type for use by the UE in the eight-transmitter uplink transmission. The precoder rank indicator and the precoder indicator may be encoded jointly into a same field or separately encoded into different fields. At block 306, the device may encode downlink control information (DCI) including the precoder rank indicator and the precoder indicator for transmission to the UE to configure the UE for the uplink transmission. These embodiments are not meant to be limiting. FIG.4 illustrates a network 400 in accordance with various embodiments. The network 400 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like. The network 400 may include a UE 402, which may include any mobile or non-mobile computing device designed to communicate with a RAN 404 via an over-the-air connection. The UE 402 may be communicatively coupled with the RAN 404 by a Uu interface. The UE 402 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc. In some embodiments, the network 400 may include a plurality of UEs coupled directly Attorney Docket No.: AF4861-PCT (31517-3237) with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. In some embodiments, the UE 402 may additionally communicate with an AP 406 via an over-the-air connection. The AP 406 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 404. The connection between the UE 402 and the AP 406 may be consistent with any IEEE 802.11 protocol, wherein the AP 406 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 402, RAN 404, and AP 406 may utilize cellular-WLAN aggregation (for example, LWA/LWIP). Cellular-WLAN aggregation may involve the UE 402 being configured by the RAN 404 to utilize both cellular radio resources and WLAN resources. The RAN 404 may include one or more access nodes, for example, AN 408. AN 408 may terminate air-interface protocols for the UE 402 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 408 may enable data/voice connectivity between CN 420 and the UE 402. In some embodiments, the AN 408 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 408 be referred to as a BS, gNB, RAN node, eNB, ng- eNB, NodeB, RSU, TRxP, TRP, etc. The AN 408 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. In embodiments in which the RAN 404 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 404 is an LTE RAN) or an Xn interface (if the RAN 404 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc. The ANs of the RAN 404 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 402 with an air interface for network access. The UE 402 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 404. For example, the UE 402 and RAN 404 may use carrier aggregation to allow the UE 402 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be Attorney Docket No.: AF4861-PCT (31517-3237) any combination of eNB, gNB, ng-eNB, etc. The RAN 404 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol. In V2X scenarios the UE 402 or AN 408 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network. In some embodiments, the RAN 404 may be an LTE RAN 410 with eNBs, for example, eNB 412. The LTE RAN 410 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI- RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands. In some embodiments, the RAN 404 may be an NG-RAN 414 with gNBs, for example, gNB 416, or ng-eNBs, for example, ng-eNB 418. The gNB 416 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 416 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 418 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air Attorney Docket No.: AF4861-PCT (31517-3237) interface. The gNB 416 and the ng-eNB 418 may connect with each other over an Xn interface. In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 414 and a UPF 448 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 414 and an AMF 444 (e.g., N2 interface). The NG-RAN 414 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G- NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH. In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 402 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 402, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 402 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 402 and in some cases at the gNB 416. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load. The RAN 404 is communicatively coupled to CN 420 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 402). The components of the CN 420 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 420 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 420 may be referred to as a network slice, and a logical instantiation of a portion of the CN 420 may be referred to as a network sub-slice. In some embodiments, the CN 420 may be an LTE CN 422, which may also be referred to as an EPC. The LTE CN 422 may include MME 424, SGW 426, SGSN 428, HSS 430, PGW Attorney Docket No.: AF4861-PCT (31517-3237) 432, and PCRF 434 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 422 may be briefly introduced as follows. The MME 424 may implement mobility management functions to track a current location of the UE 402 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc. The SGW 426 may terminate an S1 interface toward the RAN and route data packets between the RAN and the LTE CN 422. The SGW 426 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. The SGSN 428 may track a location of the UE 402 and perform security functions and access control. In addition, the SGSN 428 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 424; MME selection for handovers; etc. The S3 reference point between the MME 424 and the SGSN 428 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states. The HSS 430 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 430 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 430 and the MME 424 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 420. The PGW 432 may terminate an SGi interface toward a data network (DN) 436 that may include an application/content server 438. The PGW 432 may route data packets between the LTE CN 422 and the data network 436. The PGW 432 may be coupled with the SGW 426 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 432 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 432 and the data network 436 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 432 may be coupled with a PCRF 434 via a Gx reference point. The PCRF 434 is the policy and charging control element of the LTE CN 422. The PCRF 434 may be communicatively coupled to the app/content server 438 to determine appropriate QoS and charging parameters for service flows. The PCRF 432 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI. Attorney Docket No.: AF4861-PCT (31517-3237) In some embodiments, the CN 420 may be a 5GC 440. The 5GC 440 may include an AUSF 442, AMF 444, SMF 446, UPF 448, NSSF 450, NEF 452, NRF 454, PCF 456, UDM 458, and AF 460 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 440 may be briefly introduced as follows. The AUSF 442 may store data for authentication of UE 402 and handle authentication- related functionality. The AUSF 442 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 440 over reference points as shown, the AUSF 442 may exhibit an Nausf service-based interface. The AMF 444 may allow other functions of the 5GC 440 to communicate with the UE 402 and the RAN 404 and to subscribe to notifications about mobility events with respect to the UE 402. The AMF 444 may be responsible for registration management (for example, for registering UE 402), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 444 may provide transport for SM messages between the UE 402 and the SMF 446, and act as a transparent proxy for routing SM messages. AMF 444 may also provide transport for SMS messages between UE 402 and an SMSF. AMF 444 may interact with the AUSF 442 and the UE 402 to perform various security anchor and context management functions. Furthermore, AMF 444 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 404 and the AMF 444; and the AMF 444 may be a termination point of NAS (N1) signaling, and perform NAS ciphering and integrity protection. AMF 444 may also support NAS signaling with the UE 402 over an N3 IWF interface. The SMF 446 may be responsible for SM (for example, session establishment, tunnel management between UPF 448 and AN 408); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 448 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 444 over N2 to AN 408; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 402 and the data network 436. The UPF 448 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 436, and a branching point to Attorney Docket No.: AF4861-PCT (31517-3237) support multi-homed PDU session. The UPF 448 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 448 may include an uplink classifier to support routing traffic flows to a data network. The NSSF 450 may select a set of network slice instances serving the UE 402. The NSSF 450 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 450 may also determine the AMF set to be used to serve the UE 402, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 454. The selection of a set of network slice instances for the UE 402 may be triggered by the AMF 444 with which the UE 402 is registered by interacting with the NSSF 550, which may lead to a change of AMF. The NSSF 450 may interact with the AMF 444 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 450 may exhibit an Nnssf service-based interface. The NEF 452 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 460), edge computing or fog computing systems, etc. In such embodiments, the NEF 452 may authenticate, authorize, or throttle the AFs. NEF 452 may also translate information exchanged with the AF 460 and information exchanged with internal network functions. For example, the NEF 452 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 452 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 452 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 452 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 452 may exhibit an Nnef service-based interface. The NRF 454 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 454 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 454 may exhibit the Nnrf service-based interface. Attorney Docket No.: AF4861-PCT (31517-3237) The PCF 456 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 456 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 458. In addition to communicating with functions over reference points as shown, the PCF 456 exhibit an Npcf service-based interface. The UDM 458 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 402. For example, subscription data may be communicated via an N8 reference point between the UDM 458 and the AMF 444. The UDM 458 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 458 and the PCF 456, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 402) for the NEF 452. The Nudr service-based interface may be exhibited by the UDR to allow the UDM 458, PCF 456, and NEF 452 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 458 may exhibit the Nudm service-based interface. The AF 460 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control. In some embodiments, the 5GC 440 may enable edge computing by selecting operator/3 ^rd party services to be geographically close to a point that the UE 402 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 440 may select a UPF 448 close to the UE 402 and execute traffic steering from the UPF 448 to data network 436 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 460. In this way, the AF 460 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 460 is considered to be a trusted entity, the network operator may permit AF 460 to interact directly with relevant NFs. Additionally, the AF 460 may exhibit an Naf service-based interface. Attorney Docket No.: AF4861-PCT (31517-3237) The data network 436 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 438. FIG. 5 schematically illustrates a wireless network 500 in accordance with various embodiments. The wireless network 500 may include a UE 502 in wireless communication with an AN 504. The UE 502 and AN 504 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein. The UE 502 may be communicatively coupled with the AN 504 via connection 506. The connection 506 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies. The UE 502 may include a host platform 508 coupled with a modem platform 510. The host platform 508 may include application processing circuitry 512, which may be coupled with protocol processing circuitry 514 of the modem platform 510. The application processing circuitry 512 may run various applications for the UE 502 that source/sink application data. The application processing circuitry 512 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations The protocol processing circuitry 514 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 506. The layer operations implemented by the protocol processing circuitry 514 may include, for example, MAC, RLC, PDCP, RRC and NAS operations. The modem platform 510 may further include digital baseband circuitry 516 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 514 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions. The modem platform 510 may further include transmit circuitry 518, receive circuitry 520, RF circuitry 522, and RF front end (RFFE) 524, which may include or connect to one or Attorney Docket No.: AF4861-PCT (31517-3237) more antenna panels 526. Briefly, the transmit circuitry 518 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 520 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 522 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 524 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 518, receive circuitry 520, RF circuitry 522, RFFE 524, and antenna panels 526 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc. In some embodiments, the protocol processing circuitry 514 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components. A UE reception may be established by and via the antenna panels 526, RFFE 524, RF circuitry 522, receive circuitry 520, digital baseband circuitry 516, and protocol processing circuitry 514. In some embodiments, the antenna panels 526 may receive a transmission from the AN 504 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 526. A UE transmission may be established by and via the protocol processing circuitry 514, digital baseband circuitry 516, transmit circuitry 518, RF circuitry 522, RFFE 524, and antenna panels 526. In some embodiments, the transmit components of the UE 504 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 526. Similar to the UE 502, the AN 504 may include a host platform 528 coupled with a modem platform 530. The host platform 528 may include application processing circuitry 532 coupled with protocol processing circuitry 534 of the modem platform 530. The modem platform may further include digital baseband circuitry 536, transmit circuitry 538, receive circuitry 540, RF circuitry 542, RFFE circuitry 544, and antenna panels 546. The components of the AN 504 may be similar to and substantially interchangeable with like-named components of the UE 502. In addition to performing data transmission/reception as described above, the components of the AN 508 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource Attorney Docket No.: AF4861-PCT (31517-3237) management, and data packet scheduling. FIG. 6 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 6 shows a diagrammatic representation of hardware resources 600 including one or more processors (or processor cores) 610, one or more memory/storage devices 620, and one or more communication resources 630, each of which may be communicatively coupled via a bus 640 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 602 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 600. The processors 610 may include, for example, a processor 612 and a processor 614. The processors 610 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof. The memory/storage devices 620 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 620 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc. The communication resources 630 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 604 or one or more databases 606 or other network elements via a network 608. For example, the communication resources 630 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components. Instructions 650 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 610 to perform any one or more of the methodologies discussed herein. The instructions 650 may reside, completely or partially, within at least one of the processors 610 (e.g., within the processor’s cache memory), Attorney Docket No.: AF4861-PCT (31517-3237) the memory/storage devices 620, or any suitable combination thereof. Furthermore, any portion of the instructions 650 may be transferred to the hardware resources 600 from any combination of the peripheral devices 604 or the databases 606. Accordingly, the memory of processors 610, the memory/storage devices 620, the peripheral devices 604, and the databases 606 are examples of computer-readable and machine-readable media. The following examples pertain to further embodiments. Example 1 may include an apparatus of a network device for configuring an uplink transmission for a user equipment device (UE) using eight transmitters, the apparatus comprising processing circuitry coupled to storage for storing information associated with the configuring, the processing circuitry configured to: encode a precoder rank indicator for use in an eight-transmitter uplink transmission by a UE device; encode a precoder indicator, indicative of a precoder type, for use in the eight-transmitter uplink transmission by the UE device; and encode downlink control information (DCI) for transmission to the UE device, the DCI comprising the precoder rank and the precoder indicator. The network device may include a gNB, a base station, or an enodeB, for example. Example 2 may include the apparatus of example 1 and/or any other example herein, wherein the precoder rank indicator and the precoder indicator are indicative of a fully coherent codebook subset of only fully coherent precoders, a partially coherent codebook subset of only partially coherent precoders, or a non-coherent codebook subset of only non-coherent precoders. Example 3 may include the apparatus of example 1 and/or any other example herein, wherein the precoder rank indicator and the precoder indicator are indicative of two codewords to be used by the UE device in the uplink transmission, and wherein the uplink transmission is a physical uplink shared control channel (PUSCH) transmission. Example 4 may include the apparatus of example 1 and/or any other example herein, wherein the precoder rank indicator and the precoder indicator are jointly encoded in one field of the DCI. Example 5 may include the apparatus of example 1 and/or any other example herein, wherein the precoder rank indicator and the precoder indicator are jointly encoded in one field of the DCI and are indicative of precoder matrix index. Example 6 may include the apparatus of example 1 and/or any other example herein, wherein the precoder rank indicator and the precoder indicator are separately encoded into two different fields of the DCI. Example 7 may include the apparatus of example 1 and/or any other example herein, Attorney Docket No.: AF4861-PCT (31517-3237) wherein the precoder indicator is indicative of parameters for codebook construction. Example 8 may include the apparatus of example 1 and/or any other example herein, wherein the precoder rank indicator and the precoder indicator are indicative of a fully coherent codebook subset comprising fully coherent precoders, partially coherent precoders, and non- coherent precoders, further indicative of a partially coherent codebook subset comprising partially coherent precoders and non-coherent precoders, and further indicative of a non- coherent codebook subset of only non-coherent precoders. Example 9 may include the apparatus of example 1 and/or any other example herein, wherein the processing circuitry is further configured to: encode radio resource control (RRC) information for transmission to the UE device, the RRC information comprising an indication of a codebook subset for use by the UE device in the uplink transmission. Example 10 may include the apparatus of example 1 and/or any other example herein, wherein the processing circuitry is further configured to: encode a medium access control (MAC) control element (MAC-CE) for transmission to the UE device, the MAC-CE indicative of codebook parameters for use by the UE device in the uplink transmission. Example 11 may include the apparatus of example 1 and/or any other example herein, wherein the processing circuitry is further configured to: encode a second DCI for transmission to the UE device, wherein the DCI is indicative of a first precoder matrix for use by the UE device in the uplink transmission, and wherein the second DCI is indicative of a second precoder matrix for use by the UE device in the uplink transmission. Example 12 may include the apparatus of example 1 and/or any other example herein, wherein a size of a precoder matrix indicated by the DCI is eight multiplied by a rank indicated by the precoder rank indicator. Example 13 may include the apparatus of example 1 and/or any other example herein, wherein a partial precoding matrix for use by the UE in the uplink transmission may be based on a rank indicated by the precoder rank indicator, and an 8x8 diagonal matrix multiplied by a partial precoding matrix, wherein the 8x8 diagonal matrix represents an antenna selection for the uplink transmission. Example 14 may include the apparatus of example 1 and/or any other example herein, wherein the processing circuitry is further configured to: decode an antenna structure of the UE, received from the UE, indicative of a number of antenna groups, a number of antennas per antenna group, and a total number of antennas of the UE. Example 15 may include the apparatus of example 1 and/or any other example herein, wherein the processing circuitry is further configured to: decode an indication of full Attorney Docket No.: AF4861-PCT (31517-3237) coherence, partial coherence, or non-coherence, received from the UE device. Example 16 may include the apparatus of example 1 and/or any other example herein, wherein the DCI indicates that a first codeword in the uplink transmission by the UE is to be based on a first maximum rank or first maximum multiple input multiple output layers, and that a second codeword in the uplink transmission by the UE is to be based on a second maximum rank or second maximum multiple input multiple output layers. Example 17 may include a computer-readable storage medium comprising instructions to cause processing circuitry of a network device for configuring an uplink transmission for a user equipment device (UE) using eight transmitters, upon execution of the instructions by the processing circuitry, to: encode a precoder rank indicator for use in an eight-transmitter uplink transmission by a UE device; encode a precoder indicator, indicative of a precoder type, for use in the eight-transmitter uplink transmission by the UE device; and encode downlink control information (DCI) for transmission to the UE device, the DCI comprising the precoder rank and the precoder indicator. Example 19 may include a method for configuring an uplink transmission for a user equipment device (UE) using eight transmitters, the method comprising: encoding, by processing circuitry of a network device, a precoder rank indicator for use in an eight- transmitter uplink transmission by a UE device; encoding, by the processing circuitry, a precoder indicator, indicative of a precoder type, for use in the eight-transmitter uplink transmission by the UE device; and encoding, by the processing circuitry, downlink control information (DCI) for transmission to the UE device, the DCI comprising the precoder rank and the precoder indicator. Example 20 may include an apparatus comprising means for: encoding, by a network device, a precoder rank indicator for use in an eight-transmitter uplink transmission by a UE device; encoding a precoder indicator, indicative of a precoder type, for use in the eight- transmitter uplink transmission by the UE device; and encoding downlink control information (DCI) for transmission to the UE device, the DCI comprising the precoder rank and the precoder indicator. Example 21 may 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 a method described in or related to any of examples 1-20, or any other method or process described herein. Example 22 may include an apparatus comprising logic, modules, and/or circuitry to Attorney Docket No.: AF4861-PCT (31517-3237) perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein. Example 23 may include a method, technique, or process as described in or related to any of examples 1-20, or portions or parts thereof. Example 24 may 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 the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof. Example 25 may include a method of communicating in a wireless network as shown and described herein. Example 26 may include a system for providing wireless communication as shown and described herein. Example 27 may include a device for providing wireless communication as shown and described herein. 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 in the example section below. For example, the baseband circuitry 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 below. 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 below in the example section. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. The terms “computing device,” “user device,” “communication station,” “station,” “handheld device,” “mobile device,” “wireless device” and “user equipment” (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device. The device may be either mobile or stationary. As used within this document, the term “communicate” is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and Attorney Docket No.: AF4861-PCT (31517-3237) received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as “communicating,” when only the functionality of one of those devices is being claimed. The term “communicating” as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless communication unit, which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit. As used herein, unless otherwise specified, the use of the ordinal adjectives “first,” “second,” “third,” etc., to describe a common object, merely indicates that different instances of like objects are being referred to and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner. The term “access point” (AP) as used herein may be a fixed station. An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), or some other similar terminology known in the art. An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art. Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards. Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an on- board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN), and the like. Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a Attorney Docket No.: AF4861-PCT (31517-3237) cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple input multiple output (MIMO) transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multi- standard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like. Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi- tone (DMT), Bluetooth^, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra- wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3GPP, long term evolution (LTE), LTE advanced, enhanced data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems, and/or networks. Various embodiments are described below. Embodiments according to the disclosure are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well. The dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims. The subject- matter which can be claimed comprises not only the combinations of features as set out in the attached claims but also any other combination of features in the claims, wherein each feature mentioned in the claims can be combined with any other feature or combination of other Attorney Docket No.: AF4861-PCT (31517-3237) features in the claims. Furthermore, any of the embodiments and features described or depicted herein can be claimed in a separate claim and/or in any combination with any embodiment or feature described or depicted herein or with any of the features of the attached claims. 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. Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some implementations. These computer-executable program instructions may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks. These computer program instructions may also be stored in a computer-readable storage media or memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks. As an example, certain implementations may provide for a computer program product, comprising a computer- readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks. Attorney Docket No.: AF4861-PCT (31517-3237) Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions. Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation. Many modifications and other implementations of the disclosure set forth herein will be apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein. The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware Attorney Docket No.: AF4861-PCT (31517-3237) elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry. The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.” The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like. The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface. The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, Attorney Docket No.: AF4861-PCT (31517-3237) bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like. The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources. The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource. The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable. The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications Attorney Docket No.: AF4861-PCT (31517-3237) channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information. The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code. The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like. The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 v16.0.0 (2019-06) and/or any other 3GPP standard. For the purposes of the present document, the following abbreviations (shown in Table 9) may apply to the examples and embodiments discussed herein.

Attorney Docket No. AE4861-PCT (31517-3237) Table 9: Abbreviations Attorney Docket No. AE4861-PCT (31517-3237) Attorney Docket No. AE4861-PCT (31517-3237) Attorney Docket No. AE4861-PCT (31517-3237) Attorney Docket No. AE4861-PCT (31517-3237) Attorney Docket No. AE4861-PCT (31517-3237) Attorney Docket No. AE4861-PCT (31517-3237) Attorney Docket No. AE4861-PCT (31517-3237) Attorney Docket No. AE4861-PCT (31517-3237)