PUCCH REPORTING OF RECIPROCITY-BASED TYPE-II CODEBOOK CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This application claims the benefit of United States Provisional Patent Application Number 63/182,591, entitled “PUCCH REPORTING OF RECIPROCITY-BASED TYPE-II CODEBOOK” and filed on April 30, 2021, for Ahmed Hindy, et al., which is incorporated herein by reference. FIELD [0002] The subject matter disclosed herein relates generally to wireless communications and more particularly relates to physical uplink control channel (“PUCCH”) reporting of reciprocity-based type-II codebook. BACKGROUND [0003] For new radio (“NR”) Rel.16 Type-II codebook, the number of Precoding Matrix Indicator (“PMI”) bits fed back from the User Equipment (“UE”) in the next-generation node-B (gNB) via Uplink Control Information (“UCI”) can be very large (>1000 bits at large bandwidth). In addition, the number of Channel State Information Reference Signals (“CSI-RS”) ports sent in the downlink channel to enable channel estimation at the user equipment can be large as well, leading to higher system complexity and loss of resources and higher system overhead for reference signaling. Thereby, further reduction of the PMI feedback bits and/or a reduction in the number of CSI-RS ports utilized is needed to improve efficiency. [0004] A special case of the NR Rel.16 Type-II codebook (dubbed port-selection codebook) has been discussed, in which the number of CSI-RS ports is reduced via applying an underlying spatial beamforming process. In addition, it has been discussed that the channel correlation between uplink and downlink channels can be exploited to reduce CSI feedback overhead, even in the Frequency-Division Duplexing (“FDD”) mode where the Uplink (“UL”)- Downlink (“DL”) carrier frequency spacing is not too large. Also, two issues may arise under DL channel estimation based on partial UL channel reciprocity under FDD mode. First, the UL channel estimated at the gNB may not be accurate due to conventional channel estimation issues that are well-known in the field of wireless communications, e.g., channel quantization and hardware impairments. Second, the channel may vary within the time between the transmission of the Sounding Reference Signals (“SRS”) for UL CSI acquisition and the transmission of the beamformed CSI-RSs. BRIEF SUMMARY [0005] In one embodiment, a first apparatus includes a transceiver that receives, from a network entity, a channel state information (“CSI”) reporting configuration comprising a codebook type associated with a precoding matrix. In one embodiment, the transceiver receives, from the network entity, CSI reference signals (“CSI-RS”) over a set of CSI-RS resources based on the CSI reporting configuration. In one embodiment, the apparatus includes a processor that identifies a set of coefficients associated with the codebook based on the received set of CSI-RS resources. In one embodiment, the transceiver transmits, to the network entity, a CSI report on a physical uplink control channel (“PUCCH”) or a physical uplink shared channel (“PUSCH”) and based on the codebook type, the CSI report comprising CSI and the set of coefficients, wherein to transmit the CSI report on the PUCCH is based on a value of a sub-configuration of the CSI reporting configuration. [0006] In one embodiment, a first method includes receiving, from a network entity, a channel state information (“CSI”) reporting configuration comprising a codebook type associated with a precoding matrix. In one embodiment, the first method includes receiving, from the network entity, CSI reference signals (“CSI-RS”) over a set of CSI-RS resources based on the CSI reporting configuration. In one embodiment, the first method includes identifying a set of coefficients associated with the codebook based on the received set of CSI-RS resources. In one embodiment, the first method includes transmitting, to the network entity, a CSI report on a physical uplink control channel (“PUCCH”) or a physical uplink shared channel (“PUSCH”) and based on the codebook type, the CSI report comprising CSI and the set of coefficients, wherein to transmit the CSI report on the PUCCH is based on a value of a sub-configuration of the CSI reporting configuration. [0007] In one embodiment, a second apparatus includes a transceiver that transmits, to a user equipment (“UE”), a channel state information (“CSI”) reporting configuration comprising a codebook type associated with a precoding matrix. In one embodiment, the transceiver transmits, to the UE, CSI reference signals (“CSI-RS”) over a set of CSI-RS resources based on the CSI reporting configuration. In one embodiment, the transceiver receives, from the UE, a CSI report on a physical uplink control channel (“PUCCH”) or a physical uplink shared channel (“PUSCH”) and based on the codebook type, the CSI report comprising CSI and a set of coefficients associated with the codebook, wherein to receive the CSI report on the PUCCH is based on a value of a sub-configuration of the CSI reporting configuration. [0008] In one embodiment, a second method transmits, to a user equipment (“UE”), a channel state information (“CSI”) reporting configuration comprising a codebook type associated with a precoding matrix. In one embodiment, the second method transmits, to the UE, CSI reference signals (“CSI-RS”) over a set of CSI-RS resources based on the CSI reporting configuration. In one embodiment, the second method receives, from the UE, a CSI report on a physical uplink control channel (“PUCCH”) or a physical uplink shared channel (“PUSCH”) and based on the codebook type, the CSI report comprising CSI and a set of coefficients associated with the codebook, wherein to receive the CSI report on the PUCCH is based on a value of a sub-configuration of the CSI reporting configuration. BRIEF DESCRIPTION OF THE DRAWINGS [0009] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which: [0010] Figure 1 is a block diagram illustrating one embodiment of a wireless communication system for PUCCH reporting of reciprocity-based Type-II codebook; [0011] Figure 2 is a diagram illustrating one embodiment of Aperiodic Trigger State defining a list of CSI Report Settings; [0012] Figure 3 is a diagram illustrating one embodiment of Aperiodic trigger state indicates the resource set and QCL information; [0013] Figure 4 is a diagram illustrating one embodiment of RRC configuration for NZP- CSI-RS Resource; [0014] Figure 5 is a diagram illustrating one embodiment of RRC configuration for CSI- IM Resource; [0015] Figure 6 is a diagram illustrating one embodiment of Partial CSI omission for PUSCH-Based CSI; [0016] Figure 7 is a diagram illustrating one embodiment of ASN.1 code for configuring the UE with a PUCCH reporting of reciprocity-based Type-II codebook; [0017] Figure 8 is a diagram illustrating a second embodiment of ASN.1 code for configuring the UE with a PUCCH reporting of reciprocity-based Type-II codebook; [0018] Figure 9 is a diagram illustrating a third embodiment of ASN.1 code for configuring the UE with a PUCCH reporting of reciprocity-based Type-II codebook; [0019] Figure 10 is a diagram illustrating an example embodiment of ASN.1 code for CSI-RS-ResoureMapping CSI-RS resource mapping IE; [0020] Figure 11 is a block diagram illustrating one embodiment of a user equipment apparatus that may be used for codebook structure for PUCCH reporting of reciprocity-based Type-II codebook; [0021] Figure 12 is a block diagram illustrating one embodiment of a network apparatus that may be used for codebook structure for PUCCH reporting of reciprocity-based Type-II codebook; [0022] Figure 13 is a flowchart diagram illustrating one embodiment of a method for codebook structure for PUCCH reporting of reciprocity-based Type-II codebook; and [0023] Figure 14 is a flowchart diagram illustrating one embodiment of a method for codebook structure for PUCCH reporting of reciprocity-based Type-II codebook. DETAILED DESCRIPTION [0024] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects. [0025] For example, the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the- shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. [0026] Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code. [0027] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. [0028] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. [0029] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user’s computer, partly on the user’s computer, as a stand-alone software package, partly on the user’s computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user’s computer through any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider (“ISP”)). [0030] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment. [0031] Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise. [0032] As used herein, a list with a conjunction of “and/or” includes any single item in the list or a combination of items in the list. For example, a list of A, B and/or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one or more of” includes any single item in the list or a combination of items in the list. For example, one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one of” includes one and only one of any single item in the list. For example, “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C. As used herein, “a member selected from the group consisting of A, B, and C,” includes one and only one of A, B, or C, and excludes combinations of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof” includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. [0033] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams. [0034] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the flowchart diagrams and/or block diagrams. [0035] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams. [0036] The flowchart diagrams and/or block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart diagrams and/or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s). [0037] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures. [0038] Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code. [0039] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements. [0040] Generally, the present disclosure describes systems, methods, and apparatus for codebook structure for PUCCH reporting of reciprocity-based Type-II codebook. For Third Generation Partnership Project (“3GPP”) New Radio (“NR”) Release 16 (“Rel-16”) Type-II codebook the number of Precoding Matrix Indicator (“PMI”) bits fed back from the User Equipment (“UE”) in the next-generation node-B (“gNB”) via Uplink Control Information (“UCI”) can be very large (>1000 bits at large bandwidth). In addition, the number of Channel State Information Reference Signals (“CSI-RS”) ports sent in the downlink channel to enable channel estimation at the user equipment can be large as well, leading to higher system complexity and loss of resources over reference signaling. Thereby, further reduction of the PMI feedback bits and/or a reduction in the number of CSI-RS ports utilized is needed to improve efficiency. [0041] A special case of the NR Rel-16 Type-II codebook (dubbed port-selection codebook) was proposed, in which the number of CSI-RS ports was reduced via applying an underlying spatial beamforming process. No insight onto how to design this beamforming process was provided. In addition, it has been recently discussed in the literature that the channel correlation between uplink and downlink channels can be exploited to reduce Channel State Information (“CSI”) feedback overhead, even in the Frequency-Division Duplexing (“FDD”) mode where the Uplink-Downlink carrier frequency spacing is not too large. Also, two issues are expected to arise under Downlink (“DL”) channel estimation based on partial Uplink (“UL”) channel reciprocity under FDD mode. First, the UL channel estimated at the gNB (i.e., a 5G/NR Node B) may not be accurate due to conventional channel estimation issues that are well-known in the field of wireless communications, e.g., channel quantization and hardware impairments. Second, the channel may vary within the time between the transmission of the Sounding Reference Signals (“SRS”) for UL CSI acquisition and the transmission of the beamformed CSI- RSs. [0042] In one embodiment, this disclosure provides details on the setup, conditions, and signaling variants under which Rel.17 Type-II port-selection codebook. More specifically, the uplink channels that support transmission of Rel.17 Type-II port selection are discussed, as well as the corresponding variants of the codebook for each channel. Moreover, the time-domain behavior of the Rel.17 Type-II port selection codebook is also discussed. [0043] Figure 1 depicts a wireless communication system 100 supporting PUCCH reporting of reciprocity-based Type-II codebook, according to embodiments of the disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 110 (e.g., a 5G RAN), and a mobile core network 130. The RAN 110 and the mobile core network 130 form a mobile communication network. The RAN 110 may be composed of a base unit 121. Even though a specific number of remote units 105, RANs 110, and mobile core networks 130 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 105, RANs 110, and mobile core networks 130 may be included in the wireless communication system 100. [0044] The 5G-(R)AN 110 may be composed of a Third Generation Partnership Project (“3GPP”) access network 120 containing at least one cellular base unit 121 and/or a non-3GPP access network 111 containing at least one access point 112. Here, the RAN 110 is an intermediate network that provides the remote units 105 with access to the mobile core network 130. [0045] In one implementation, the 3GPP access network 120 that is compliant with the Fifth-Generation (“5G”) system specified in the 3GPP specifications. For example, the 3GPP access network 120 may be a New Generation Radio Access Network (“NG-RAN”), implementing NR Radio Access Technology (“RAT”) and/or 3GPP Long-Term Evolution (“LTE”) RAT. In another example, the 3GPP access network 120 may include non-3GPP RAT (e.g., Wi-Fi® or Institute of Electrical and Electronics Engineers (“IEEE”) 802.11-family compliant WLAN). In another implementation, the 3GPP access network 120 is compliant with the LTE system specified in the 3GPP specifications. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication network, for example Worldwide Interoperability for Microwave Access (“WiMAX”) or IEEE 802.16-family standards, among other networks. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. [0046] In one embodiment, the remote units 105 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. In some embodiments, the remote units 105 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 105 may be referred to as the UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit (“WTRU”), a device, or by other terminology used in the art. In various embodiments, the remote unit 105 includes a subscriber identity and/or identification module (“SIM”) and the mobile equipment (“ME”) providing mobile termination functions (e.g., radio transmission, handover, speech encoding and decoding, error detection and correction, signaling and access to the SIM). In certain embodiments, the remote unit 105 may include a terminal equipment (“TE”) and/or be embedded in an appliance or device (e.g., a computing device, as described above). [0047] The remote units 105 may communicate directly with the base units 121 in the 3GPP access network 120 via uplink (“UL”) and/or downlink (“DL”) communication signals. Furthermore, the UL and DL communication signals may be carried over the 3GPP wireless communication links 123. Additionally (or alternatively), the remote units 105 may communicate directly with the access points 112 in the non-3GPP access network 111 via UL and/or DL communication signals, which may be carried over the non-3GPP communication links 113. [0048] In some embodiments, the remote units 105 communicate with an application server 151 via a network connection with the mobile core network 130. For example, an application 107 (e.g., web browser, media client, email client, telephone and/or Voice-over- Internet-Protocol (“VoIP”) application) in a remote unit 105 may trigger the remote unit 105 to establish a protocol data unit (“PDU”) session (or other data connection) with the mobile core network 130 via the RAN 110. The mobile core network 130 then relays traffic between the remote unit 105 and the application server 151 (e.g., a content server in the packet data network 150) using the PDU session. The PDU session represents a logical connection between the remote unit 105 and the User Plane Function (“UPF”) 131. [0049] In order to establish the PDU session (or PDN connection), the remote unit 105 must be registered with the mobile core network 130 (also referred to as ‘“attached to the mobile core network” in the context of a Fourth Generation (“4G”) system). Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 130. As such, the remote unit 105 may have at least one PDU session for communicating with the packet data network 150, e.g., representative of the Internet. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and/or other communication peers. [0050] In the context of a 5G system (“5GS”), the term “PDU Session” a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between the remote unit 105 and a specific Data Network (“DN”) through the UPF 131. A PDU Session supports one or more Quality of Service (“QoS”) Flows. In certain embodiments, there may be a one-to-one mapping between a QoS Flow and a QoS profile, such that all packets belonging to a specific QoS Flow have the same 5G QoS Identifier (“5QI”). [0051] In the context of a 4G/LTE system, such as the Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also referred to as EPS session) provides E2E UP connectivity between the remote unit and a PDN. The PDN connectivity procedure establishes an EPS Bearer, i.e., a tunnel between the remote unit 105 and a Packet Gateway (“PGW”, not shown) in the mobile core network 130. In certain embodiments, there is a one-to-one mapping between an EPS Bearer and a QoS profile, such that all packets belonging to a specific EPS Bearer have the same QoS Class Identifier (“QCI”). [0052] The base units 121 may be distributed over a geographic region. In certain embodiments, a base unit 121 may also be referred to as an access terminal, an access point, a base, a base station, a Node-B (“NB”), an Evolved Node B (abbreviated as eNodeB or “eNB,” also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node B), a 5G/NR Node B (“gNB”), a Home Node-B, a relay node, a RAN node, or by any other terminology used in the art. The base units 121 are generally part of a RAN, such as the RAN 120, that may include one or more controllers communicably coupled to one or more corresponding base units 121. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art. The base units 121 connect to the mobile core network 130 via the RAN 120. [0053] The base units 121 may serve a number of remote units 105 within a serving area, for example, a cell or a cell sector, via a wireless communication link 123. The base units 121 may communicate directly with one or more of the remote units 105 via communication signals. Generally, the base units 121 transmit DL communication signals to serve the remote units 105 in the time, frequency, and/or spatial domain. Furthermore, the DL communication signals may be carried over the wireless communication links 123. The wireless communication links 123 may be any suitable carrier in licensed or unlicensed radio spectrum. The wireless communication links 123 facilitate communication between one or more of the remote units 105 and/or one or more of the base units 121. Note that during NR in Unlicensed Spectrum (“NR- U”) operation, the base unit 121 and the remote unit 105 communicate over unlicensed radio spectrum. [0054] The non-3GPP access networks 111 may be distributed over a geographic region. Each non-3GPP access network 111 may serve a number of remote units 105 with a serving area. Typically, a serving area of the non-3GPP access network 111 is smaller than the serving area of a cellular base unit 121. An access point 112 in a non-3GPP access network 111 may communicate directly with one or more remote units 105 by receiving UL communication signals and transmitting DL communication signals to serve the remote units 105 in the time, frequency, and/or spatial domain. Both DL and UL communication signals are carried over the non-3GPP communication links 133. The 3GPP communication links 123 and non-3GPP communication links 133 may employ different frequencies and/or different communication protocols. In various embodiments, an access point 112 may communicate using unlicensed radio spectrum. The mobile core network 140 may provide services to a remote unit 105 via the non-3GPP access networks 111, as described in greater detail herein. [0055] In some embodiments, a non-3GPP access network 111 connects to the mobile core network 140 via an interworking function 115. The interworking function 115 provides interworking between the remote unit 105 and the mobile core network 140. In some embodiments, the interworking function 115 is a Non-3GPP Interworking Function (“N3IWF”) and, in other embodiments, it is a Trusted Non-3GPP Gateway Function (“TNGF”). The N3IWF supports the connection of “untrusted” non-3GPP access networks to the mobile core network (e.g., 5GC), whereas the TNGF supports the connection of “trusted” non-3GPP access networks to the mobile core network. The interworking function 115 supports connectivity to the mobile core network 140 via the “N2” and “N3” interfaces, and it relays “N1” signaling between the remote unit 105 and the AMF 143. As depicted, both the 3GPP access network 120 and the interworking function 115 communicate with the AMF 143 using a “N2” interface. The interworking function 115 also communicates with the UPF 141 using a “N3” interface. [0056] In certain embodiments, a non-3GPP access network 111 may be controlled by an MNO of the mobile core network 140 and may have direct access to the mobile core network 140. Such a non-3GPP AN deployment is referred to as a “trusted non-3GPP access network.” A non-3GPP access network 111 is considered as “trusted” when it is operated by the MNO, or a trusted partner, and supports certain security features, such as strong air-interface encryption. In contrast, a non-3GPP AN deployment that is not controlled by an operator (or trusted partner) of the mobile core network 140, does not have direct access to the mobile core network 140, or does not support the certain security features is referred to as a “non-trusted” non-3GPP access network. [0057] In one embodiment, the mobile core network 130 is a 5G Core network (“5GC”) or an Evolved Packet Core network (“EPC”), which may be coupled to a packet data network 150, like the Internet and private data networks, among other data networks. A remote unit 105 may have a subscription or other account with the mobile core network 130. Each mobile core network 130 belongs to a single public land mobile network (“PLMN”). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. [0058] The mobile core network 130 includes several network functions (“NFs”). As depicted, the mobile core network 130 includes at least one UPF 131. The mobile core network 130 also includes multiple control plane (“CP”) functions including, but not limited to, an Access and Mobility Management Function (“AMF”) 133 that serves the RAN 120, a Session Management Function (“SMF”) 135, a Policy Control Function (“PCF”) 137, a Unified Data Management function (“UDM”) and a User Data Repository (“UDR”). [0059] The UPF(s) 131 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU session for interconnecting Data Network (DN), in the 5G architecture. The AMF 133 is responsible for termination of NAS signaling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The SMF 135 is responsible for session management (i.e., session establishment, modification, release), remote unit (i.e., UE) IP address allocation & management, DL data notification, and traffic steering configuration for UPF for proper traffic routing. [0060] The PCF 137 is responsible for unified policy framework, providing policy rules to CP functions, access subscription information for policy decisions in UDR. The UDM is responsible for generation of Authentication and Key Agreement (“AKA”) credentials, user identification handling, access authorization, subscription management. The UDR is a repository of subscriber information and can be used to service a number of network functions. For example, the UDR may store subscription data, policy-related data, subscriber-related data that is permitted to be exposed to third party applications, and the like. In some embodiments, the UDM is co-located with the UDR, depicted as combined entity “UDM/UDR” 139. [0061] In various embodiments, the mobile core network 130 may also include an Authentication Server Function (“AUSF”) (which acts as an authentication server), a Network Repository Function (“NRF”) (which provides NF service registration and discovery, enabling NFs to identify appropriate services in one another and communicate with each other over Application Programming Interfaces (“APIs”)), a Network Exposure Function (“NEF”) (which is responsible for making network data and resources easily accessible to customers and network partners), or other NFs defined for the 5GC. In certain embodiments, the mobile core network 130 may include an authentication, authorization, and accounting (“AAA”) server. [0062] In various embodiments, the mobile core network 130 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a “network slice” refers to a portion of the mobile core network 130 optimized for a certain traffic type or communication service. A network instance may be identified by a single-network slice selection assistance information (“S-NSSAI,”) while a set of network slices for which the remote unit 105 is authorized to use is identified by network slice selection assistance information (“NSSAI”). [0063] Here, “NSSAI” refers to a vector value including one or more S-NSSAI values. In certain embodiments, the various network slices may include separate instances of network functions, such as the SMF 135 and UPF 131. In some embodiments, the different network slices may share some common network functions, such as the AMF 133. The different network slices are not shown in Figure 1 for ease of illustration, but their support is assumed. Where different network slices are deployed, the mobile core network 130 may include a Network Slice Selection Function (“NSSF”) which is responsible for selecting of the Network Slice instances to serve the remote unit 105, determining the allowed NSSAI, determining the AMF set to be used to serve the remote unit 105. [0064] Although specific numbers and types of network functions are depicted in Figure 1, one of skill in the art will recognize that any number and type of network functions may be included in the mobile core network 130. Moreover, in an LTE variant where the mobile core network 130 comprises an EPC, the depicted network functions may be replaced with appropriate EPC entities, such as a Mobility Management Entity (“MME”), a Serving Gateway (“SGW”), a PGW, a Home Subscriber Server (“HSS”), and the like. For example, the AMF 133 may be mapped to an MME, the SMF 135 may be mapped to a control plane portion of a PGW and/or to an MME, the UPF 131 may be mapped to an SGW and a user plane portion of the PGW, the UDM/UDR 139 may be mapped to an HSS, etc. [0065] The Operations, Administration and Maintenance (“OAM”) plane 140 is involved with the operating, administering, managing and maintaining of the system 100. “Operations” encompass automatic monitoring of environment, detecting and determining faults and alerting admins. “Administration” involves collecting performance stats, accounting data for the purpose of billing, capacity planning using Usage data and maintaining system reliability. Administration can also involve maintaining the service databases which are used to determine periodic billing. “Maintenance” involves upgrades, fixes, new feature enablement, backup and restore and monitoring the media health. In certain embodiments, the OAM plane 140 may also be involved with provisioning, i.e., the setting up of the user accounts, devices and services. [0066] While Figure 1 depicts components of a 5G RAN and a 5G core network, the described embodiments apply to other types of communication networks and RATs, including IEEE 802.11 variants, Global System for Mobile Communications (“GSM,” i.e., a 2G digital cellular network), General Packet Radio Service (“GPRS”), UMTS, LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, and the like. [0067] In the following descriptions, the term “gNB” is used for the base station but it is replaceable by any other radio access node, e.g., RAN node, eNB, Base Station (“BS”), Access Point (“AP”), NR/5G BS, etc. Further the operations are described mainly in the context of 5G NR. However, the described solutions/methods are also equally applicable to other mobile communication systems supporting PUCCH reporting of reciprocity-based Type-II codebook. [0068] Regarding the 3GPP NR Rel-15 Type-II Codebook, it is assumed that the gNB is equipped with a two-dimensional (“2D”) antenna array with N ₁ , N ₂ antenna ports per polarization placed horizontally and vertically and communication occurs over N ₃ PMI sub-bands. A PMI sub-band consists of a set of resource blocks, each resource block consisting of a set of subcarriers. In such case, 2N ₁ N ₂ CSI-RS ports are utilized to enable DL channel estimation with high resolution for NR Rel-15 Type-II codebook. In order to reduce the UL feedback overhead, a Discrete Fourier transform (“DFT”)-based CSI compression of the spatial domain is applied to L dimensions per polarization, where L<N ₁ N ₂ . In the sequel the indices of the 2L dimensions are referred as the Spatial Domain (“SD”) basis indices. The magnitude and phase values of the linear combination coefficients for each sub-band are fed back to the gNB as part of the CSI report. The 2N ₁ N ₂ ×N ₃ codebook per layer takes on the form W = W ₁ W ₂ where W ₁ is a 2N ₁ N ₂ ×2L block-diagonal matrix (L<N ₁ N ₂ ) with two identical diagonal blocks, i.e., and B is an N ₁ N ₂ ×L matrix with columns drawn from a 2D oversampled DFT matrix, as follows: where the superscript ^T denotes a matrix transposition operation. Note that O ₁ , O ₂ oversampling factors are assumed for the 2D DFT matrix from which matrix B is drawn. Note that W ₁ is common across all layers. W ₂ is a 2L×N ₃ matrix, where the i ^th column corresponds to the linear combination coefficients of the 2L beams in the i ^th sub-band. Only the indices of the L selected columns of B are reported, along with the oversampling index taking on O ₁ O ₂ values. Note that W ₂ are independent for different layers. [0069] In more detail, the specification for the NR Rel.15 Type-II Codebook is as follows (e.g., refer to 3GPP NR TS 38.214): [0070] For 4 antenna ports {3000, 3001, …, 3003}, 8 antenna ports {3000, 3001, …, 3007}, 12 antenna ports {3000, 3001, …, 3011}, 16 antenna ports {3000, 3001, …, 3015}, 24 antenna ports {3000, 3001, …, 3023}, and 32 antenna ports {3000, 3001, …, 3031}, and the UE configured with higher layer parameter codebookType set to 'typeII' ● The values of N ₁ and N ₂ are configured with the higher layer parameter n1-n2- codebookSubsetRestriction. The supported configurations of (N ₁ , N ₂ ) for a given number of CSI-RS ports and the corresponding values of (O ₁ , O ₂ ) are given in Table 5.2.2.2.1-2 of TS 38.214. The number of CSI-RS ports, P _CSI-RS , is 2N ₁ N ₂ . ● The value of L is configured with the higher layer parameter numberOfBeams, where L=2 when P _CSI-RS =4 and L∈{2,3,4} when P _CSI-RS >4. ● The value of NPSK is configured with the higher layer parameter phaseAlphabetSize, where N _PSK ∈{4,8}. ● The UE is configured with the higher layer parameter subbandAmplitude set to 'true' or 'false'. ● The UE shall not report RI > 2. [0071] When v≤2, where v is the associated RI value, each PMI value corresponds to the codebook indices i1 and i2 where [0072] The L vectors combined by the codebook are identified by the indices i _1,1 and i _1,2 , where [0073] Let and where the values of C(x,y) are given in Table 1 below. [0074] Then the elements of n1 and n2 are found from i1,2 using the algorithm: s-1=0 for i=0,…., L-1 Find the largest x*∈{L-1-i,…,N ₁ N ₂ -1-i} in Table 1 such that i1,2-si-1 ≥ C(x*,L-i) [0075] When n ₁ and n ₂ are known, i _1,2 is found using: n _(i) = N ₁ n ₂ (i) + n ₁ (i) where the indices i=0,1,…, L-1 are assigned such that n ⁽ⁱ⁾ increases as i increases where C(x,y) is given in Table 1. ● If N ₂ =1, q ₂ =0 and n ₂ ⁽ⁱ⁾ =0 for i=0,1,…, L-1, and q ₂ is not reported. ● When (N ₁ , N ₂ )=(2,1), n ₁ =[0,1] and n ₂ =[0,0], and i _1,2 is not reported. ● When (N ₁ , N ₂ )=(4,1) and L=4, n ₁ =[0,1,2,3] and n ₂ =[0,0,0,0], and i _1,2 is not reported. ● When (N ₁ , N ₂ )=(2,2) and L=4, n ₁ =[0,1,0,1] and n ₂ =[0,0,1,1], and i _1,2 is not reported. Table 1: Combinatorial coefficients C(x,y) [0076] The strongest coefficient on layer l=1,…,v is identified by i _1,3,l ∈{0,1,…,2L-1}. The amplitude coefficient indicators i _1,4,l and i _2,2,l are: for l=1,…,v. The mapping from to the amplitude coefficient is given in Table 2 and the mapping from to the amplitude coefficient is given in Table 3. The amplitude coefficients are represented by for l=1,…,v. Table 2: Mapping of elements of Table 3: Mapping of elements of [0077] The phase coefficient indicators are for l=1,…,v. [0078] The amplitude and phase coefficient indicators are reported as follows: ● The indicators are not reported for l=1,…,v. ● The remaining 2L-1 elements of are reported, where Let M _l (l=1,…,v) be the number of elements of i _1,4,l that satisfy [0079] The remaining 2L-1 elements of i _2,1,l and i _2,2,l (l=1,…,v) are reported as follows: ● When subbandAmplitude is set to 'false', o for l=1,…,v, and i=0,1,…,2L-1. i _2,2,l is not reported for l=1,…,v. o For l=1,…,v, the elements of i _2,1,l corresponding to the coefficients that satisfy i≠i _1,3,l , as determined by the reported elements of i _1,4,l , are reported, where c _l,i ∈{0,1,…,N _PSK -1} and the remaining 2L-M _l elements of i _2,1,l are not reported and are set to ● When subbandAmplitude is set to 'true', o For l=1,…,v, the elements of i _2,2,l and i _2,1,l corresponding to the min(M _l , K ⁽²⁾ )-1 strongest coefficients (excluding the strongest coefficient indicated by i _1,3,l ), as determined by the corresponding reported elements of i _1,4,l , are reported, where and The values of K ⁽²⁾ are given in Table 4. The remaining 2L- min(M _l , K ⁽²⁾ ) elements of i _2,2,l are not reported and are set to The elements of i _2,1,l corresponding to the M _l - min(M _l , K ⁽²⁾ ) weakest non-zero coefficients are reported, where The remaining 2L-M _l elements of i _2,1,l are not reported and are set to c _l, i=0. o When two elements, of the reported elements of i _1,4,l are identical then element min(x,y) is prioritized to be included in the set of the min(M _l , K ⁽²⁾ )-1 strongest coefficients for i _2,1,l and i _2,2,l (l=1,…,v) reporting. Table 4: Full resolution sub-band coefficients when subbandAmplitude is set to 'true' [0080] The codebooks for 1-2 layers are given in Table 5, where the indices m1 ⁽ⁱ⁾ and are given by: [0081] For i=0,1,…,L-1, and the quantities φ _l,i , u _m , and v _l,m are given by

Table 5: Codebook for 1-layer and 2-layer CSI reporting using antenna ports 3000 to 2999+PCSI-RS [0082] When the UE is configured with higher layer parameter codebookType set to 'typeII', the bitmap parameter typeII-RI‑Restriction forms the bit sequence r ₁ , r ₀ where r ₀ is the LSB and r1 is the MSB. When ri is zero, i∈{0,1}, PMI and RI reporting are not allowed to correspond to any precoder associated with v=i+1 layers. The bitmap parameter n1- n2‑codebookSubsetRestriction forms the bit sequence B=B1B2 where bit sequences B1, and B2 are concatenated to form B. To define B ₁ and B ₂ , first define the O ₁ O ₂ vector groups G(r ₁ ,r ₂ ) as for [0083] The UE shall be configured with restrictions for 4 vector groups indicated by for k=0,1,2,3 and identified by the group indices [0084] For k=0,1,…,3, where the indices are assigned such that g ^(k) increases as k increases. The remaining vector groups are not restricted. ● If N ₂ =1, g ^(k) =k for k=0,1,…,3, and B ₁ is empty. ● If N ₂ >1, B ₁ =b ₁ ⁽¹⁰⁾ …b ₁ ⁽⁰⁾ is the binary representation of the integer β1 where b1 ⁽¹⁰⁾ is the MSB and b ₁ ⁽⁰⁾ is the LSB. β ₁ is found using: where C(x,y) is defined in Table 1. [0085] The group indices g(k) and indicators for k=0,1,2,3 may be found from β1 using the algorithm: for k=0,…,3. Find the largest T∗ ∈ {3 − k, … , O ₁ O ₂ − 1 − k} such that β ₁ − s _k-1 ≥ [0086] The bit sequence is the concatenation of the bit sequences 2 ⁽ B ^k) for k=0,1,…,3, corresponding to the group indices g ^(k) . The bit sequence B2 ^(k) is defined as [0087] Bits indicate the maximum allowed amplitude coefficient p _l,i ⁽¹⁾ for the vector in group g ^(k) indexed by x ₁ ,x ₂ , where the maximum amplitude coefficients are given in Table 6. A UE that does not report parameter amplitudeSubsetRestriction = 'supported' in its capability signaling is not expected to be configured with Table 6: Maximum allowed amplitude coefficients for restricted vectors [0088] Regarding 3GPP NR Rel-15, for Type-II Port Selection codebook, only K (where K ≤ 2N ₁ N ₂ ) beamformed CSI-RS ports are utilized in DL transmission, in order to reduce complexity. The. The KxN ₃ codebook matrix per layer takes on the form: [0089] Here, W ₂ follows the same structure as the conventional NR Rel-15 Type-II Codebook, and are layer specific. is a K×2L block-diagonal matrix with two identical diagonal blocks, e.g., and E is an K/2×L matrix whose columns are standard unit vectors, as follows: where is a standard unit vector with a 1 at the i ^th location. Here d _PS is an RRC parameter which takes on the values {1,2,3,4} under the condition d _PS ≤ min(K/2, L), whereas m _PS takes on the values and is reported as part of the UL CSI feedback overhead. W ₁ is common a cross all layers. [0090] For K=16, L=4 and d _PS =1, the 8 possible realizations of E corresponding to m _PS = {0,1,…,7} are as follows

[0091] When d _PS =2, the 4 possible realizations of E corresponding to m _PS ={0,1,2,3} are as follows [0092] When d _PS =3, the 3 possible realizations of E corresponding of m _PS ={0,1,2} are as follows [0093] When d _PS =4, the 2 possible realizations of E corresponding of m _PS ={0,1} are as follows

[0094] To summarize, m _PS parametrizes the location of the first 1 in the first column of E, whereas d _PS represents the row shift corresponding to different values of m _PS . [0095] In more detail, the specification for the NR Rel.15 Type-II Port Selection Codebook is as follows (see, e.g., 3GPP NR TS 38.214): [0096] For 4 antenna ports {3000, 3001, …, 3003}, 8 antenna ports {3000, 3001, …, 3007}, 12 antenna ports {3000, 3001, …, 3011}, 16 antenna ports {3000, 3001, …, 3015}, 24 antenna ports {3000, 3001, …, 3023}, and 32 antenna ports {3000, 3001, …, 3031}, and the UE configured with higher layer parameter codebookType set to 'typeII-PortSelection' ● The number of CSI-RS ports is given by P _CSI-RS ∈ {4,8,12,16,24,32}as configured by higher layer parameter nrofPorts. ● The value of L is configured with the higher layer parameter numberOfBeams , where L=2 when P _CSI-RS =4 and L∈{2,3,4} when P _CSI-RS >4. ● The value of d is configured with the higher layer parameter ● The value of N _PSK is configured with the higher layer parameter phaseAlphabetSize, where N _PSK ∈{4,8}. ● The UE is configured with the higher layer parameter subbandAmplitude set to 'true' or 'false'. ● The UE shall not report RI > 2. [0097] The UE is also configured with the higher layer parameter typeII- PortSelectionRI-Restriction. The bitmap parameter typeII-PortSelectionRI-Restriction forms the bit sequence r ₁ ,r ₀ where r ₀ is the LSB and r ₁ is the MSB. When r _i is zero, i∈{0,1}, PMI and RI reporting are not allowed to correspond to any precoder associated with v=i+1 layers. [0098] When v≤2, where v is the associated RI value, each PMI value corresponds to the codebook indices i1 and i2 where [0099] The L antenna ports per polarization are selected by the index i _1,1 , where [0100] The strongest coefficient on layer l, l=1,…,v is identified by i _1,3,l ∈{0,1,…,2L-1}. [0101] The amplitude coefficient indicators i _1,4,l and i _2,2,l are for l=1,…,v. The mapping from k _l,i ⁽¹⁾ to the amplitude coefficient p _l,i ⁽¹⁾ is given in Table 2 and the mapping from k _l,i ⁽²⁾ to the amplitude coefficient p _l,i ⁽²⁾ is given in Table 3. The amplitude coefficients are represented by for l=1,…,v. [0102] The phase coefficient indicators are for l=1,…,v. [0103] The amplitude and phase coefficient indicators are reported as follows: ● The indicators and are not reported for l=1,…,v. ● The remaining 2L-1 elements of i _1,4,l (l=1,…,v) are reported, where Let M _l (l=1,…,v) be the number of elements of i _1,4,l that satisfy ● The remaining 2L-1 elements of i _2,1,l and i _2,2,l (l=1,…,v) are reported as follows: o When subbandAmplitude is set to 'false', ■ for l = 1, … , v, and i=0,1,…,2L-1. i _2,2,l is not reported for l=1,…,v. ■ For l=1,…,v, the M _l -1 elements of i _2,1,l corresponding to the coefficients that satisfy as determined by the reported elements of i _1,4,l , are reported, where c _l,i ∈ {0,1,…,N _PSK -1} and the remaining 2L-M _l elements of i _2,1,l are not reported and are set to cl,i=0. o When subbandAmplitude is set to 'true', ■ For l=1,…,v, the elements of i _2,2,l and i _2,1,l corresponding to the min(M _l ,K ⁽²⁾ )-1 strongest coefficients (excluding the strongest coefficient indicated by i _1,3,l ), as determined by the corresponding reported elements of i _1,4,l , are reported, where and c _l,i ∈ ,…,N _PSK -1}. The values of K ⁽² {0,1 ⁾ are given in Table 4. The remaining 2L- min(M _l ,K ⁽²⁾ ) elements of i _2,2,l are not reported and are set to = 1. The elements of i _2,1,l corresponding to the M _l - min(M _l ,K ⁽²⁾ ) weakest non-zero coefficients are reported, where c _l,i ∈{0,1,2,3}. The remaining 2L-M _l elements of i _2,1,l are not reported and are set to c _l,i =0. ■ When two elements, of the reported elements of i _1,4,l are identical , then element min(x,y) is prioritized to be included in the set of the min(M _l ,K ⁽²⁾ )-1 strongest coefficients for i _2,1,l and i _2,2,l (l=1,…,v) reporting. [0104] The codebooks for 1-2 layers are given in Table 7, where the quantity φ _l,i is given by [0105] and v _m is a P _CSI-RS /2-element column vector containing a value of 1 in element (m mod P _CSI-RS /2) and zeros elsewhere (where the first element is element 0). Table 7: Codebook for 1-layer and 2-layer CSI reporting using antenna ports 3000 to 2999+PCSI-RS [0106] Regarding 3GPP NR Rel-15, the Type-I codebook is the baseline codebook for NR, with a variety of configurations. The most common utility of Rel.15 Type-I codebook is a special case of NR Rel. 15 Type-II codebook with L=1 for RI=1,2, wherein a phase coupling value is reported for each sub-band, i.e., is 2xN , with the first row equal to [1, 1, …, 1] and the second row equal to Under specific configurations, ϕ ₀ = ϕ ₁ …= ϕ, i.e., wideband reporting. For RI>2 different beams are used for each pair of layers. Obviously, NR Rel.15 Type- I codebook can be depicted as a low-resolution version of NR Rel. 15 Type-II codebook with spatial beam selection per layer-pair and phase combining only. [0107] Regarding the 3GPP NR Rel-16 Type-II Codebook, it is assumed that the gNB is equipped with a two-dimensional (2D) antenna array with N , N antenna ports per polarization placed horizontally and vertically and communication occurs over N ₃ PMI sub-bands. A PMI sub- band consists of a set of resource blocks, each resource block consisting of a set of subcarriers. In such case, 2N ₁ N ₂ N ₃ CSI-RS ports are utilized to enable DL channel estimation with high resolution for NR Rel.16 Type-II codebook. In order to reduce the UL feedback overhead, a Discrete Fourier transform (DFT)-based CSI compression of the spatial domain is applied to L dimensions per polarization, where L<N N . Similarly, additional compression in the frequency domain is applied, where each beam of the frequency-domain precoding vectors is transformed using an inverse DFT matrix to the delay domain, and the magnitude and phase values of a subset of the delay-domain coefficients are selected and fed back to the gNB as part of the CSI report. The 2N ₁ N ₂ xN ₃ codebook per layer takes on the form: where W ₁ is a 2N ₁ N ₂ x2L block-diagonal matrix (L<N ₁ N ₂ ) with two identical diagonal blocks, i.e., and B is an N ₁ N ₂ xL matrix with columns drawn from a 2D oversampled DFT matrix, as follows: where the superscript ^T denotes a matrix transposition operation. Note that O ₁ , O ₂ oversampling factors are assumed for the 2D DFT matrix from which matrix B is drawn. Note that W ₁ is common across all layers. In various embodiments, the above parameters comply with 3GPP TS 38.214 definitions and procedures. W _f is an N ₃ ×M matrix (where M < N ₃ ) with columns selected from a critically-sampled size-N ₃ DFT matrix, as follows: [0108] Only the indices of the L selected columns of B are reported, along with the oversampling index taking on O ₁ O ₂ values. Similarly for W _F , only the indices of the M selected columns out of the predefined size-N ₃ DFT matrix are reported. In the sequel the indices of the M dimensions are referred as the selected Frequency Domain (“FD”) basis indices. Hence, L, M represent the equivalent spatial and frequency dimensions after compression, respectively. Finally, the 2LxM matrix represents the linear combination coefficients (“LCCs”) of the spatial and frequency DFT-basis vectors. Both W _f are selected independent for different layers. Magnitude and phase values of an appr oximately β fraction of the 2LM available coefficients are reported to the gNB (β<1) as part of the CSI report. Coefficients with zero magnitude are indicated via a per-layer bitmap. Since all coefficients reported within a layer are normalized with respect to the coefficient with the largest magnitude (strongest coefficient), the relative value of that coefficient is set to unity, and no magnitude or phase information is explicitly reported for this coefficient. Only an indication of the index of the strongest coefficient per layer is reported. Hence, for a single-layer transmission, magnitude and phase values of a maximum of (2βLM)-1 coefficients (along with the indices of selected L, M DFT vectors) are reported per layer, leading to significant reduction in CSI report size, compared with reporting 2N ₁ N ₂ xN ₃ -1 coefficients’ information. [0109] In more detail, the specification for the NR Rel.16 Type-II Codebook is as follows (e.g., see 3GPP NR TS 38.214): [0110] For 4 antenna ports {3000, 3001, …, 3003}, 8 antenna ports {3000, 3001, …, 3007}, 12 antenna ports {3000, 3001, …, 3011}, 16 antenna ports {3000, 3001, …, 3015}, 24 antenna ports {3000, 3001, …, 3023}, and 32 antenna ports {3000, 3001, …, 3031}, and UE configured with higher layer parameter codebookType set to ' typeII-r16' ● The values of N ₁ and N ₂ are configured with the higher layer parameter n1-n2- codebookSubsetRestriction-r16. The supported configurations of (N ₁ , N ₂ ) for a given number of CSI-RS ports and the corresponding values of (O ₁ , O ₂ ) are given in Table 5.2.2.2.1-2 of TS 38.214. The number of CSI-RS ports, P _CSI-RS , is 2N ₁ N ₂ . ● The values of L, β and p _ν are determined by the higher layer parameter paramCombination-r16, where the mapping is given in Table 8. ● The UE is not expected to be configured with paramCombination-r16 equal to o 3, 4, 5, 6, 7, or 8 when P _CSI-RS = 4, o 7 or 8 when P _CSI-RS < 32 o 7 or 8 when higher layer parameter typeII-RI-Restriction-r16 is configured with r _i = 1 for any / > 1. o 7 or 8 when À = 2. [0111] The parameter À is configured with the higher-layer parameter numberOfPMISubbandsPerCQISubband-r16. This parameter controls the total number of precoding matrices N ₃ indicated by the PMI as a function of the number of configured subbands in csi-ReportingBand, the subband size configured by the higher-level parameter subbandSize and of the total number of PRBs in the bandwidth part according to Table 5.2.1.4-2 of TS 38.214, as follows: ^ When À = 1: o One precoding matrix is indicated by the PMI for each sub-band in csi- ReportingBand. ● When R = 2: o For each sub-band in csi-ReportingBand that is not the first or last sub-band of a BWP, two precoding matrices are indicated by the PMI: the first precoding matrix corresponds to the first PRBs of the subband and the second precoding matrix corresponds to the last PRBs of the subband. o For each sub-band in csi-ReportingBand that is the first or last sub-band of a BWP. ■ one precoding matrix is indicated by the PMI corresponding to the first sub-band. If two precoding matrices are indicated by the PMI corresponding to the first sub-band: the first precoding matrix corresponds to the first PRBs of the first subband and the second precoding matrix corresponds to the last PRBs of the first subband. ■ If one precoding matrix is indicated by the PMI corresponding to the last sub-band. If 1 + two precoding matrices are indicated by the PMI corresponding to the last sub-band: the first precoding matrix corresponds to the first PRBs of the last subband and the second precoding matrix corresponds to the last 1 + the last subband. Table 8: Codebook parameter configurations for L, β and p _v ● The UE shall report the RI value 3 according to the configured higher layer parameter typeII-RI-Restriction-r16. The UE shall not report 3 > 4. [0112] The PMI value corresponds to the codebook indices of i ₁ and i ₂ where [0113] The precoding matrices indicated by the PMI are determined from L + M _v vectors. [0114] P vectors − 1 , are identified by the indices q ₁ , q ₂ , n ₁ , n ₂ , indicated by i _1,1 , i _1,2 , where the values of C(x, y) are given in Table 11. are identified by M _initial (for N ₃ > 19) and n _3,l (l = 1, … , v) where which are indicated by means of the indices i _1,5 (for N ₃ > 19) and i _1,6,l (for M _v > 1 and l = 1, … , v), where [0116] The amplitude coefficient indicators i _2,3,l and i _2,4,l are for l = 1, … , v. [0117] The phase coefficient indicator i _2,5,l is for l = 1, … , v. [0118] Let K ₀ = (β2LM ₁ ). The bitmap whose nonzero bits identify which coefficients in i _2,4,l and i _2,5,l are reported, is indicated by i _1,7,l for l = 1, … , v, such that is the number of nonzero coefficients for layer l = 1, … , v and he total number of nonzero coefficients. [0119] The indic es of i _2,4,l , i _2,5,l and i _1,7,l are associated to the M _v codebook indices in n _3,l . [0120] The mapping from to the amplitude coefficient is given in Table 5.2.2.2.5-2 and the mapping from to the amplitude coefficient s given in Table 10. The amplitude coefficients are repres ented by for l = 1, … , 3. [0121] Le the index of i _2,4,l and / the index of which identify the strongest coefficient of layer l, i.e., the element of i _2,4,l , for l = 1, … , v . The codebook indices of n _3,l are remapped with respect to after remapping. The index Ñ is remapped with respect to such that the index of the strongest coefficient is ( l = 1, … , v), after remapping. The indices of i _2,4,l , i _2,5,l and i _1,7,l indicate amplitude coefficients, phase coefficients and bitmap after remapping. [0122] The strongest coefficient of layer " is identified by i _1,8,l ∈ {0,1, … ,2L − 1}, which is obtained as follows for l = 1, … , v. [0123] The amplitude and phase coefficient indicators are reported as follows:

[0124] The elements f n ₁ an d n ₂ are found from i _1,2 using the algorithm below, where the values of C(x, y) are given in Table 11. [0125] For N ₃ > 19, M _initial is identified by i _1,5 . [0126] For all values of +1, the nonzero elements of identified by nd from

end if end if Table 11: Combinatorial coefficients C(x, y) [0127] [0128] When n _3,l and M _initial are known, i _1,5 and i _1,6,l (l = 1, … , v) are found as follows: ● If N ₃ ≤ 19, i _1,5 = 0 and is not reported. If M _v = 1, i _1,6,l = 0, for l = 1, … , v, and is not reported. given in Table 11 and where the indices f = 1, … , M _v − 1 are assigned such th increases as f increases. ● If N ₃ > 19, M _initial is indicated by i _1,5 , which is reported and given by [0129] Only the nonzero indices , Table 12: Codebook for 1-layer.2-layer, 3-layer and 4-layer CSI reporting using antenna ports 3000 to 2999+PCSI-RS [0131] For coefficients with amplitude and phase are set to zero, i.e. and [0132] The bitmap parameter typeII-RI-Restriction-r16 forms the bit sequence ere r is the LSB and is the MSB. When r is zero, i ∈ 0,1, … ,3 , PMI and RI reporting are not allowed to correspond to any precoder associated with 3 = i + 1 layers. [0133] The bitmap parameter n1-n2-codebookSubsetRestriction-r16 forms the bit 0,1), with i ∈ {0,1, … , P − 1}, of the coefficients associated with the vector in group ^ indexed by x ₁ , x ₂ , where the maximum amplitudes are given in Table 13 and the average coefficient amplitude is restricted as follows for l = 1, … , v , and p = 0,1 . A UE that does not report the parameter amplitudeSubsetRestriction='supported' in its capability signaling is not expected to be configured Table 13: Maximum allowed average coefficient amplitudes for restricted vectors [0134] Regarding 3GPP NR Rel-16, for Type-II Port Selection codebook, only K (where K ≤ 2N ₁ N ₂ ) beamformed CSI-RS ports are utilized in DL transmission, in order to reduce complexity. The K×N ³ codebook matrix per layer takes on the form: [0135] Here, follow the same structure as the conventional NR Rel-16 Type- II Codebook, where both are layer specific. The matrix block-diagonal matrix with the same structure as that in the NR Rel-15 Type-II Port Selection Codebook. [0136] In more detail, the specification for the NR Rel. 16 Type-II Port Selection Codebook is as follows (see 3GPP NR TS 38.214): [0137] For 4 antenna ports {3000, 3001, …, 3003}, 8 antenna ports {3000, 3001, …, 3007}, 12 antenna ports {3000, 3001, …, 3011}, 16 antenna ports {3000, 3001, …, 3015}, 24 antenna ports {3000, 3001, …, 3023}, and 32 antenna ports {3000, 3001, …, 3031}, and the UE configured with higher layer parameter codebookType set to ' typeII-PortSelection-r16 ' ● The number of CSI-RS ports is configured as in Clause 5.2.2.2.4 of TS 38.214 ● The value of d is configured with the higher layer parameter portSelectionSamplingSize-r16, where d ∈ {1,2,3,4} and d ≤ L. ● The values l, β and p _v are configured as in Clause 5.2.2.2.5 of TS 38.214, where the supported configurations are given in Table 14. Table 14: Codebook parameter configurations for Î, ^ andb _Ð ^ The UE shall report the RI value 3 according to the configured higher layer parameter typeII-PortSelectionRI-Restriction-r16. The UE shall not report 3 > 4. ^ The values of À is configured as in Clause 5.2.2.2.5 of TS 38.214. [0138] The UE is also configured with the higher layer bitmap parameter typeII- PortSelectionRI-Restriction-r16, which forms the bit sequence r ₁ , r ₂ , r ₁ , r ₀ , where r ₀ is the LSB and r ₁ is the MSB. When r _i is zero, i ∈ {0,1, … , 3}, PMI and RI reporting are not allowed to correspond to any precoder associated with 3 = i + 1 layers. [0139] The PMI value corresponds to the codebook indices i ₁ and i ₂ where [0140] The 2P antenna ports are selected by the index i _1,1 as in clause 5.2.2.2.4 of TS 38.214. [0141] Parameters N ₃ , M _v , M _initial (for N ₃ > 19) and K ₀ are defined as in clause 5.2.2.2.5 of TS 38.214. the strongest coefficient i _1,8,l , the amplitude coefficient indicators i _2,3,l and i _2,4,l , the phase coefficient indicator i _2,5,l and the bitmap indicator i _1,7,l are defined and indicated as in clause 5.2.2.2.5, where the mapping from to the amplitude coefficient is given in Table 9 and the mapping from to the amplitude coefficient is given in Table 10. [0143] The number of nonzero coefficients for layer l , and the total number of nonzero coefficients K ^NZ are defined as in Clause 5.2.2.2.5 of TS 38.214. [0144] The amplitude coefficients are represented as in clause 5.2.2.2.5. [0145] The amplitude and phase coefficient indicators are reported as in clause 5.2.2.2.5 of TS 38.214. [0146] Codebook indicators i and i (l = 1, … , v) are found as in clause 5.2.2.2.5 of TS 38.214. [0147] The codebooks for 1-4 layers are given in Table 15, where v _m is a P _CSI-RS /2 - element column vector containing a value of 1 in element (m mod P _CSI-RS /2 ) and zeros elsewhere (where the first element is element 0), and the quantities are defined as in clause 5.2.2.2.5 of TS 38.214. Table 15: Codebook for 1-layer.2-layer, 3-layer and 4-layer CSI reporting using antenna ports 3000 to 2999+PCSI-RS [0148] For coefficients with , amplitude and phase are set to zero, i.e., an [0149] Regarding UE SRS configuration, as discussed in 3GPP TS 38.214, the UE may be configured with one or more SRS resource sets as configured by the higher-layer parameter SRS- ResourceSet, wherein each SRS resource set is associated with K ≥ 1 SRS resources (higher-layer parameter SRS-Resource), where the maximum value of K is indicated by UE capability. The SRS resource set applicability is configured by the higher-layer parameter usage in SRS-ResourceSet. The higher-layer parameter SRS-Resource configures some SRS parameters, including the SRS resource configuration identity (srs-ResourceId), the number of SRS ports (nrofSRS-Ports) with default value of one, and the time-domain behavior of SRS resource configuration (resourceType). [0150] The UE may be configured by the higher-layer parameter resourceMapping in SRS- Resource with an SRS resource occupying Ns∈{1,2,4} adjacent symbols within the last 6 symbols of the slot, where all antenna ports of the SRS resources are mapped to each symbol of the resource. [0151] For a UE configured with one or more SRS resource configuration(s), and when the higher-layer parameter resourceType in SRS-Resource is set to 'aperiodic': ● The UE receives a configuration of SRS resource sets, ● The UE receives a downlink downlink control information (“DCI”), a group common DCI, or an uplink DCI based command where a codepoint of the DCI may trigger one or more SRS resource set(s). For SRS in a resource set with usage set to 'codebook' or 'antennaSwitching', the minimal time interval between the last symbol of the physical downlink control channel (“PDCCH”) triggering the aperiodic SRS transmission and the first symbol of SRS resource is N ₂ . Otherwise, the minimal time interval between the last symbol of the PDCCH triggering the aperiodic SRS transmission and the first symbol of SRS resource is N ₂ + 14. The minimal time interval in units of orthogonal frequency division multiplexing (“OFDM”) symbols is counted based on the minimum subcarrier spacing between the PDCCH and the aperiodic SRS. ● If the UE is configured with the higher-layer parameter spatialRelationInfo containing the ID of a reference 'ssb-Index', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference synchronization signal (“SS”)/physical broadcast channel (“PBCH”) block, if the higher-layer parameter spatialRelationInfo contains the ID of a reference 'csi- RS-Index', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the reception of the reference periodic CSI-RS or of the reference semi-persistent CSI-RS, or of the latest reference aperiodic CSI-RS. If the higher-layer parameter spatialRelationInfo contains the ID of a reference 'srs', the UE shall transmit the target SRS resource with the same spatial domain transmission filter used for the transmission of the reference periodic SRS or of the reference semi-persistent SRS or of the reference aperiodic SRS. ● The update command contains spatial relation assumptions provided by a list of references to reference signal IDs, one per element of the updated SRS resource set. Each ID in the list refers to a reference SS/PBCH block, non-zero power (“NZP”) CSI-RS resource configured on serving cell indicated by Resource Serving Cell ID field in the update command if present, same serving cell as the SRS resource set otherwise, or SRS resource configured on serving cell and uplink bandwidth part indicated by Resource Serving Cell ID field and Resource BWP ID field in the update command if present, same serving cell and bandwidth part as the SRS resource set otherwise. ● When the UE is configured with the higher-layer parameter usage in SRS- ResourceSet set to 'antennaSwitching', the UE shall not expect to be configured with different spatial relations for SRS resources in the same SRS resource set. [0152] For physical uplink control channel (“PUCCH”) and SRS on the same carrier, a UE shall not transmit SRS when semi-persistent and periodic SRS are configured in the same symbol(s) with PUCCH carrying only CSI report(s), or only L1-RSRP report(s), or only L1-SINR report(s). A UE shall not transmit SRS when semi-persistent or periodic SRS is configured or aperiodic SRS is triggered to be transmitted in the same symbol(s) with PUCCH carrying HARQ- ACK, link recovery request and/or SR. In the case that SRS is not transmitted due to overlap with PUCCH, only the SRS symbol(s) that overlap with PUCCH symbol(s) are dropped. PUCCH shall not be transmitted when aperiodic SRS is triggered to be transmitted to overlap in the same symbol with PUCCH carrying semi-persistent/periodic CSI report(s) or semi-persistent/periodic L1-RSRP report(s) only, or only L1-SINR report(s). [0153] When the UE is configured with the higher-layer parameter usage in SRS- ResourceSet set to 'antennaSwitching', and a guard period of Y symbols is configured, the UE shall use the same priority rules as defined above during the guard period as if SRS was configured. [0154] Regarding UE sounding procedure for DL CSI acquisition, when the UE is configured with the higher-layer parameter usage in SRS-ResourceSet set as 'antennaSwitching', the UE may be configured with one configuration depending on the indicated UE capability supportedSRS-TxPortSwitch, which takes on the values {'t1r2', 't1r1-t1r2', 't2r4', 't1r4', 't1r1-t1r2- t1r4', 't1r4-t2r4', 't1r1-t1r2-t2r2-t2r4', 't1r1-t1r2-t2r2-t1r4-t2r4', 't1r1', 't2r2', 't1r1-t2r2', 't4r4', 't1r1- t2r2-t4r4'} ● For 1T2R, up to two SRS resource sets configured with a different value for the higher-layer parameter resourceType in SRS-ResourceSet set, where each set has two SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of the second resource in the set is associated with a different UE antenna port than the SRS port of the first resource in the same set, or ● For 2T4R, up to two SRS resource sets configured with a different value for the higher-layer parameter resourceType in SRS-ResourceSet set, where each SRS resource set has two SRS resources transmitted in different symbols, each SRS resource in a given set consisting of two SRS ports, and the SRS port pair of the second resource is associated with a different UE antenna port pair than the SRS port pair of the first resource, or ● For 1T4R, zero or one SRS resource set configured with higher-layer parameter resourceType in SRS-ResourceSet set to 'periodic' or 'semi-persistent' with four SRS resources transmitted in different symbols, each SRS resource in a given set consisting of a single SRS port, and the SRS port of each resource is associated with a different UE antenna port, and ● For 1T4R, zero or two SRS resource sets each configured with higher-layer parameter resourceType in SRS-ResourceSet set to 'aperiodic' and with a total of four SRS resources transmitted in different symbols of two different slots, and where the SRS port of each SRS resource in the given two sets is associated with a different UE antenna port. The two sets are each configured with two SRS resources, or one set is configured with one SRS resource and the other set is configured with three SRS resources. ● For 1T=1R, or 2T=2R, or 4T=4R, up to two SRS resource sets each with one SRS resource, where the number of SRS ports for each resource is equal to 1, 2, or 4. [0155] The UE is configured with a guard period of Y symbols, in which the UE does not transmit any other signal, in the case the SRS resources of a set are transmitted in the same slot. The guard period is in-between the SRS resources of the set. The value of Y is 2 when the OFDM sub-carrier spacing is 120 kHz, otherwise Y=1. [0156] For 1T2R, 1T4R or 2T4R, the UE shall not expect to be configured or triggered with more than one SRS resource set with higher-layer parameter usage set as 'antennaSwitching' in the same slot. For 1T=1R, 2T=2R or 4T=4R, the UE shall not expect to be configured or triggered with more than one SRS resource set with higher-layer parameter usage set as 'antennaSwitching' in the same symbol. [0157] Regarding CSI reporting, the codebook report is partitioned into two parts based on the priority of information reported. Each part is encoded separately (Part 1 has a possibly higher code rate). Below we list the parameters for NR Rel.16 Type-II codebook only. More details can be found in TS38.214 Sec5.2.3-4. [0158] Note that multiple CSI reports may be transmitted, where the CSI reports would be reported via the priority reporting levels of CSI Part 2 in the table below:

^ Table - Priority reporting levels for Part 2 CSI [0159] Note that the priority of the N _Rep CSI reports are based on the following a. A CSI report corresponding to one CSI reporting configuration for one cell may have higher priority compared with another CSI report corresponding to one other CSI reporting configuration for the same cell b. CSI reports intended to one cell may have higher priority compared with other CSI reports intended to another cell c. CSI reports may have higher priority based on the CSI report content, e.g., CSI reports carrying L1-RSRP information have higher priority d. CSI reports may have higher priority based on their type, e.g., whether the CSI report is aperiodic, semi-persistent or periodic, and whether the report is sent via PUSCH or PUCCH, may impact the priority of the CSI report [0160] In light of that, CSI reports may be prioritized as follows, where CSI reports with ^{lower IDs have higher priority} [0161] s: CSI reporting configuration index, and Ms: Maximum number of CSI reporting configurations [0162] c: Cell index, and N _cells : Number of serving cells [0163] k: 0 for CSI reports carrying L1-RSRP or L1-SINR, 1 otherwise [0164] y: 0 for aperiodic reports, 1 for semi-persistent reports on PUSCH, 2 for semi- persistent reports on PUCCH, 3 for periodic reports. [0165] Regarding triggering priority for CSI reporting, the UE needs to report the needed CSI information for the network using the CSI framework in NR Release 15. From a UE perspective, CSI reporting is independent of what NCJT scheme is used on the downlink. The triggering mechanism between a report setting and a resource setting can be summarized in below. Table - Triggering mechanism between a report setting and a resource setting [0166] Moreover, a. All associated Resource Settings for a CSI Report Setting need to have same time domain behavior. b. Periodic CSI-RS/ IM resource and CSI reports are always assumed to be present and active once configured by RRC c. Aperiodic and semi-persistent CSI-RS/ IM resources and CSI reports needs to be explicitly triggered or activated. d. Aperiodic CSI-RS/ IM resources and aperiodic CSI reports, the triggering is done jointly by transmitting a DCI Format 0-1. e. Semi-persistent CSI-RS/ IM resources and semi-persistent CSI reports are independently activated. [0167] For multi-TRP NCJT, aperiodic CSI reporting is likely to be triggered to inform the network about the channel conditions for every transmission hypothesis, since using periodic CSI- RS for the TRPs in the coordination cluster constitutes a large overhead. As mentioned earlier, for aperiodic CSI-RS/IM resources and aperiodic CSI reports, the triggering is done jointly by transmitting a DCI Format 0-1. The DCI Format 0_1 contains a CSI request field (0 to 6 bits). A non-zero request field points to a so-called aperiodic trigger state configured by RRC (see Figure 2). [0168] Figure 2 depicts a diagram 200 illustrating one embodiment of an aperiodic trigger state defining a list of CSI report settings. Specifically, the diagram 200 includes a DCI format 0_1 202, a CSI request codepoint 204, and an aperiodic trigger state 2 206. Moreover, the aperiodic trigger state 2 includes a ReportConfigID x 208, a ReportConfigID y 210, and a ReportConfigID z 212. For aperiodic CSI-RS/IM resources and aperiodic CSI reports, the triggering is done jointly by transmitting a DCI Format 0-1. The DCI Format 0_1 contains a CSI request field (0 to 6 bits). A non-zero request field points to a so-called aperiodic trigger state configured by RRC. An aperiodic trigger state in turn is defined as a list of up to 16 aperiodic CSI Report Settings, identified by a CSI Report Setting ID for which the UE calculates simultaneously CSI and transmits it on the scheduled PUSCH transmission. [0169] Figure 3 depicts aperiodic trigger state that indicates the resource set 302 and QCL information 304. When the CSI Report Setting is linked with aperiodic Resource Setting (can comprise multiple Resource Sets), the aperiodic NZP-CSI-RS Resource Set for channel measurement, the aperiodic CSI-IM Resource Set (if used) and the aperiodic NZP CSI-RS Resource Set for IM (if used) to use for a given CSI Report Setting are also included in the aperiodic trigger state definition. For aperiodic NZP-CSI-RS, the QCL source to use is also configured in the aperiodic trigger state. The UE assumes that the resources used for the computation of the channel and interference can be processed with the same spatial filter i.e., quasi‐co‐located with respect to “QCL‐TypeD.” [0170] Figure 4 is a code sample 402 illustrating one embodiment of the process by which an aperiodic trigger state indicates a resource set and QCL information. [0171] Figure 5 is a code sample 502 illustrating one embodiment of an RRC configuration including a NZP-CSI-RS resource and a CSI-IM-resource. [0172] The table below summarizes the type of uplink channels used for CSI reporting as a function of the CSI codebook type.

Table - uplink channels used for CSI reporting as a function of the CSI codebook type [0173] For aperiodic CSI reporting, PUSCH-based reports are divided into two CSI parts: CSI Part1 and CSI Part 2. The reason for this is that the size of CSI payload varies significantly, and therefore a worst-case UCI payload size design would result in large overhead. [0174] CSI Part 1 has a fixed payload size (and can be decoded by the gNB without prior information) and contains the following: a. RI (if reported), CRI (if reported) and CQI for the first codeword, b. number of non-zero wideband amplitude coefficients per layer for Type II CSI feedback on PUSCH. [0175] CSI Part 2 has a variable payload size that can be derived from the CSI parameters in CSI Part 1, and contains PMI and the CQI for the second codeword when RI > 4. [0176] For example, if the aperiodic trigger state indicated by DCI format 0_1 defines 3 report settings x, y, and z, then the aperiodic CSI reporting for CSI part 2 will be ordered as indicated in Figure 6. [0177] Figure 6 is a schematic block diagram 600 illustrating one embodiment of a partial CSI omission for PUSCH-based CSI. The diagram 600 includes a ReportConfigID x 602, a ReportConfigID y 604, and a ReportConfigID z 606. Moreover, the diagram 600 includes a first report 608 (e.g., requested quantities to be reported) corresponding to the ReportConfigID x 602, a second report 610 (e.g., requested quantities to be reported) corresponding to the ReportConfigID y 604, and a third report 612 (e.g., requested quantities to be reported) corresponding to the ReportConfigID z 606. Each of the first report 608, the second report 610, and the third report 612 includes a CSI part 1620, and a CSI part 2622. An ordering 623 of CSI part 2 across reports is CSI part 2 of the first report 624, CSI part 2 of the second report 626, and CSI part 2 of the third report 628. Moreover, the CSI part 2 reports may produce a report 1 WB CSI 634, a report 2 WB CSI 636, a report 3 WB CSI 638, a report 1 even SB CSI 640, a report 1 odd SB CSI 642, a report 2 even SB CSI 644, a report 2 odd SB CSI 646, a report 3 even SB CSI 648, and a report 3 odd SB CSI 650. [0178] As mentioned earlier, CSI reports are prioritized according to: a. Time-domain behavior and physical channel, where more dynamic reports are given precedence over less dynamic reports and PUSCH has precedence over PUCCH. b. CSI content, where beam reports (i.e. L1-RSRP reporting) has priority over regular CSI reports. c. Serving cell to which the CSI corresponds (in case of CA operation). CSI corresponding to the PCell has priority over CSI corresponding to Scells. d. The ID of the CSI Report Configuration reportConfigID. [0179] In general, a UE is configured by higher-layers with one or more CSI-ReportConfig Reporting Settings, wherein each Reporting Setting may configure at least one CodebookConfig Codebook Configuration or one reportQuantity Reporting Quantity, or both, for CSI Reporting. Each Codebook Configuration represents at least one codebookType Codebook type, which includes indicators representing at least one or more of a CSI-RS Resource Indicator (“CRI”), a Synchronization-Signal Block Resource Indicator (“SSBRI”), a Rank Indicator (“RI”), a Precoding Matrix Indicator (“PMI”), a Channel Quality Indicator (“CQI”), a Layer Indicator (“LI”), a Layer-1 Reference Signal Received Power “(L1-RSRP”) and a Layer-1 Signal-to- Interference-plus-Noise Ratio (“L1-SINR”). Several embodiments are described below. According to a possible embodiment, one or more elements or features from one or more of the described embodiments may be combined. [0180] Regarding indication of reciprocity-based codebook, the network may configure a UE with a reciprocity-based codebook as part of CSI feedback reporting, via one or more of the indications discussed below with reference to Figures 7-9. [0181] Figure 7 depicts an example of Abstract Syntax Notation One (“ASN.1”) code for configuring the UE with a reciprocity-based codebook, according to a first alternative. According to the first alternative, the network introduces one or more additional values to the higher-layer parameter CodebookType. In one embodiment, the parameter CodebookType may be part of one or more Codebook Configuration Information Elements (“IE”) that were introduced in Rel-15 and Rel-16, i.e., CodebookConfig, or CodebookConfig-r16, respectively. In another embodiment, a new Codebook Configuration is introduced in Rel. 17, i.e.,CodebookConfig-r17 702. All the Codebook Configuration IEs are part of the CSI-ReportConfig Reporting Setting IE. Examples of the additional values of the CodebookType parameter are ‘typeII-PortSelection-r17’, or ‘typeII- Reciprocity’. An example of the ASN.1 code that corresponds to the latter embodiment is provided in Figure 2 for the Codebook Configuration IE. [0182] Figure 8 depicts an example of ASN.1 code for configuring the UE with a reciprocity-based codebook, according to a second alternative. According to the second alternative, the network introduces an additional higher-layer parameter, e.g., channelReciprocity 802, within the CSI-ReportConfig Reporting Setting IE that configures the UE with CSI feedback reporting based on channel reciprocity. The Channel Reciprocity parameter may appear in different sub-elements of the Reporting Setting IE. An Example of the ASN.1 code that corresponds to this embodiment is provided in Figure 3 for the CSI-ReportConfig Reporting Setting IE. [0183] Figure 9 depicts an example of ASN.1 code for configuring the UE with a reciprocity-based codebook, according to a third alternative. According to the third alternative, the network introduces an additional higher-layer parameter, e.g., channelReciprocity, within the Codebook Configuration CodebookConfig IE. In one embodiment, the new parameter is under the Codebook Configuration IE, e.g., CodebookConfig, CodebookConfig-r16. In another embodiment, the new parameter is under a new configuration such as CodebookConfig-r17902. In yet another embodiment, the new parameter is a sub-parameter within the higher-layer parameter codebookType, whenever the Codebook Type is set to ‘typeII-PortSelection,’ ‘typeII- PortSelection-r16’ or another Type-II Port Selection Codebook, e.g., ‘typeII-PortSelection-r17.’ An Example of the ASN.1 code that corresponds to the last embodiment is provided in Figure 4 for the CodebookConfig Codebook Configuration IE. [0184] Due to the exploitation of the FDD reciprocity of the channel, a gNB may transmit beamformed CSI-RSs, where the CSI-RS beamforming is based on the UL channel estimated via SRS transmission. The beamforming can then flatten the channel in the frequency domain, i.e., a fewer number of significant channel taps, i.e., taps with relatively large power, are observed at the UE, compared with non-beamformed CSI-RS transmission. Such beamforming may result in a fewer number of coefficients, corresponding to fewer FD basis indices, being fed back in the CSI report. [0185] In one embodiment, different codebook configurations related to the time-domain behavior of CSI reporting of reciprocity-based codebook, as well as the supporting uplink channels may be implemented. In addition, CSI-RS configurations that are associated with the aforementioned CSI reports corresponding to different time-domain behaviors and supporting uplink channels may be implemented. Different embodiments of this concept are provided below. Note that a combination of one or more features or elements of one embodiment with another is not precluded. [0186] Regarding time-domain behavior of CSI reporting for reciprocity-based codebook, a UE is configured with a CSI Reporting Setting that triggers the UE to feed back a CSI report on an uplink channel with a specific time-domain behavior. In this section, different time-domain behaviors of CSI reporting for reciprocity-based codebook and supporting channels for the corresponding CSI reports are discussed. Different embodiments of this concept are provided below. Note that a combination of one or more features or elements of one embodiment with another is not precluded. [0187] In a first embodiment, an aperiodic CSI report carried on the PUSCH supports wideband, and sub-band frequency granularities, wherein the aperiodic CSI report carried on the PUSCH supports or can be configured for/with Further Enhanced Type II CSI, e.g., Rel.17 Type- II port selection codebook. [0188] In a second embodiment, semi-persistent CSI reporting on the PUSCH supports Further Enhanced Type II CSI, e.g., Rel. 17 Type-II port selection codebook. In a first example, semi-persistent CSI reporting on the PUSCH supports Further Enhanced Type II CSI with codebook-based specific configuration. [0189] In a third embodiment, periodic CSI reporting on PUCCH supports Further Enhanced Type II CSI, e.g., Rel. 17 Type-II port selection codebook. In a first example, periodic CSI reporting on PUCCH supports Further Enhanced Type II CSI with codebook-based specific configuration. In a second example, Further Enhanced Type II CSI is supported on periodic CSI reporting on/using PUCCH formats 3, 4. [0190] In a fourth embodiment, semi-persistent CSI reporting on the PUCCH supports Further Enhanced Type II CSI, e.g., Rel. 17 Type-II port selection codebook. In a first example, semi-persistent CSI reporting on PUCCH supports Further Enhanced Type II CSI with codebook- based specific configuration. In a second example, Further Enhanced Type II CSI is supported on semi-persistent CSI reporting on PUCCH formats 3, 4. [0191] In a fifth embodiment, Further Enhanced Type II CSI with codebook-based specific configuration corresponds to a codebook with at least one of the following configurations: wideband frequency granularity, and a PMI format indicator set to wideband, and a CQI format indicator set to wideband, and a number of PMI sub-bands per CQI sub-band set to a value below a certain threshold, e.g., 2, and a number of CSI-RS ports below a certain threshold, e.g., 16, and a number of beams below a certain threshold, e.g., 4, and a rank (number of layers) restricted to a specific value, e.g., 1, 2, and parameter corresponding to a number of selected frequency basis indices, e.g., M, set to one. [0192] Regarding CSI-RS configuration for reciprocity-based codebook, a UE is configured with a CSI Reporting Setting that configures the UE to receive one or more NZP CSI- RS resources within a CSI-RS resource set for channel measurement. In this section we discuss the CSI resource setting corresponding to Rel. 17 Type-II port selection codebook. Different embodiments of this concept are provided below. Note that a combination of one or more features or elements of one embodiment with another is not precluded. [0193] In a first embodiment, a UE configured with a higher-layer parameter for codebook type codebooktype set to a Further Enhanced Type II CSI, e.g., ‘typeII-PortSelection-r17’ for a CSI Reporting Setting CSI-ReportConfig, is also expected to be configured with one or more NZP CSI-RS Resources with a CSI-RS frequency density in CSI-RS Resource mapping set to 0.25, e.g., ‘dot25’, within the same CSI Reporting Setting CSI-ReportConfig. [0194] In a second embodiment, a CSI Reporting Setting with one or more NZP CSI-RS resources with a CSI-RS frequency density in CSI-RS Resource mapping configured with set to 0.25, e.g., ‘dot25’ 1002, includes a two-bit indication for RB level comb offset indicating whether the offset value is one of {0,1,2,3}. An example of the ASN.1 code the corresponds to the CSI- ReportConfig Reporting Setting IE is provided in Figure 10. [0195] In a third embodiment, a UE is expected to be configured with one or more NZP CSI-RS Resources with a CSI-RS frequency density in CSI-RS Resource mapping set to 0.25, e.g., ‘dot25’, only if it is configured with a codebook configuration codebookConfig with a Further Enhanced Type II CSI codebook, e.g., ‘typeII-PortSelection-r17’. [0196] In a fourth embodiment, a UE is not expected to be configured with more than X CSI-RS resources in a CSI-RS resource set for channel measurement for a CSI-ReportConfig with the higher layer parameter codebookType set to a Further Enhanced Type II CSI codebook, e.g., ‘typeII-PortSelection-r17’. In one example, X=2. [0197] In a fifth embodiment, a UE that is expected to send a CSI report corresponding to Further Enhanced Type II CSI, e.g., Rel.17 Type-II port selection codebook, via one of periodic or semi-persistent reporting on PUCCH is also expected to be configured with an NZP CSI-RS Resource with a CSI-RS frequency density in CSI-RS Resource mapping set to 0.25, e.g., ‘dot25’. [0198] In a sixth embodiment, a UE that is expected to send a CSI report corresponding to Further Enhanced Type II CSI, e.g., Rel.17 Type-II port selection codebook, via one of periodic or semi-persistent reporting on PUCCH is also expected to be configured with two or more NZP CSI-RS Resources in a CSI-RS resource set for channel measurement for a CSI-ReportConfig Reporting Setting. [0199] Regarding Antenna Panel/Port, Quasi-collocation, Transmission Configuration Indicator (“TCI”) state, and Spatial Relation, in some embodiments, the terms antenna, panel, and antenna panel are used interchangeably. An antenna panel may be a hardware that is used for transmitting and/or receiving radio signals at frequencies lower than 6GHz, e.g., frequency range 1 (FR1), or higher than 6GHz, e.g., frequency range 2 (FR2) or millimeter wave (mmWave). In some embodiments, an antenna panel may comprise an array of antenna elements, wherein each antenna element is connected to hardware such as a phase shifter that allows a control module to apply spatial parameters for transmission and/or reception of signals. The resulting radiation pattern may be called a beam, which may or may not be unimodal and may allow the device to amplify signals that are transmitted or received from spatial directions. [0200] In some embodiments, an antenna panel may or may not be virtualized as an antenna port in the specifications. An antenna panel may be connected to a baseband processing module through a radio frequency (“RF”) chain for each of transmission (egress) and reception (ingress) directions. A capability of a device in terms of the number of antenna panels, their duplexing capabilities, their beamforming capabilities, and so on, may or may not be transparent to other devices. In some embodiments, capability information may be communicated via signaling or, in some embodiments, capability information may be provided to devices without a need for signaling. In the case that such information is available to other devices, it can be used for signaling or local decision making. [0201] In some embodiments, a device (e.g., UE, node) antenna panel may be a physical or logical antenna array comprising a set of antenna elements or antenna ports that share a common or a significant portion of an RF chain (e.g., in-phase/quadrature (“I/Q”) modulator, analog to digital (“A/D”) converter, local oscillator, phase shift network). The device antenna panel or “device panel” may be a logical entity with physical device antennas mapped to the logical entity. The mapping of physical device antennas to the logical entity may be up to device implementation. Communicating (receiving or transmitting) on at least a subset of antenna elements or antenna ports active for radiating energy (also referred to herein as active elements) of an antenna panel requires biasing or powering on of the RF chain which results in current drain or power consumption in the device associated with the antenna panel (including power amplifier/low noise amplifier (“LNA”) power consumption associated with the antenna elements or antenna ports). The phrase "active for radiating energy," as used herein, is not meant to be limited to a transmit function but also encompasses a receive function. Accordingly, an antenna element that is active for radiating energy may be coupled to a transmitter to transmit radio frequency energy or to a receiver to receive radio frequency energy, either simultaneously or sequentially, or may be coupled to a transceiver in general, for performing its intended functionality. Communicating on the active elements of an antenna panel enables generation of radiation patterns or beams. [0202] In some embodiments, depending on device’s own implementation, a “device panel” can have at least one of the following functionalities as an operational role of Unit of antenna group to control its Tx beam independently, Unit of antenna group to control its transmission power independently, Unit of antenna group to control its transmission timing independently. The “device panel” may be transparent to gNB. For certain condition(s), gNB or network can assume the mapping between device’s physical antennas to the logical entity “device panel” may not be changed. For example, the condition may include until the next update or report from device or comprise a duration of time over which the gNB assumes there will be no change to the mapping. A Device may report its capability with respect to the “device panel” to the gNB or network. The device capability may include at least the number of “device panels.” In one implementation, the device may support UL transmission from one beam within a panel; with multiple panels, more than one beam (one beam per panel) may be used for UL transmission. In another implementation, more than one beam per panel may be supported/used for UL transmission. [0203] In some of the embodiments described, an antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. [0204] Two antenna ports are said to be quasi co-located (“QCL”) if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. Two antenna ports may be quasi-located with respect to a subset of the large-scale properties and different subset of large-scale properties may be indicated by a QCL Type. The QCL Type can indicate which channel properties are the same between the two reference signals (e.g., on the two antenna ports). Thus, the reference signals can be linked to each other with respect to what the UE can assume about their channel statistics or QCL properties. For example, qcl-Type may take one of the following values: ● 'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread} ● 'QCL-TypeB': {Doppler shift, Doppler spread} ● 'QCL-TypeC': {Doppler shift, average delay} ● 'QCL-TypeD': {Spatial Rx parameter} [0205] Spatial Rx parameters may include one or more of: angle of arrival (“AoA”), Dominant AoA, average AoA, angular spread, Power Angular Spectrum (“PAS”) of AoA, average angle of departure (“AoD”), PAS of AoD, transmit/receive channel correlation, transmit/receive beamforming, spatial channel correlation etc. [0206] The QCL-TypeA, QCL-TypeB and QCL-TypeC may be applicable for all carrier frequencies, but the QCL-TypeD may be applicable only in higher carrier frequencies (e.g., mmWave, FR2 and beyond), where essentially the UE may not be able to perform omni-directional transmission, i.e., the UE would need to form beams for directional transmission. A QCL-TypeD between two reference signals A and B, the reference signal A is considered to be spatially co- located with reference signal B and the UE may assume that the reference signals A and B can be received with the same spatial filter (e.g., with the same RX beamforming weights). [0207] An “antenna port” according to an embodiment may be a logical port that may correspond to a beam (resulting from beamforming) or may correspond to a physical antenna on a device. In some embodiments, a physical antenna may map directly to a single antenna port, in which an antenna port corresponds to an actual physical antenna. Alternately, a set or subset of physical antennas, or antenna set or antenna array or antenna sub-array, may be mapped to one or more antenna ports after applying complex weights, a cyclic delay, or both to the signal on each physical antenna. The physical antenna set may have antennas from a single module or panel or from multiple modules or panels. The weights may be fixed as in an antenna virtualization scheme, such as cyclic delay diversity (CDD). The procedure used to derive antenna ports from physical antennas may be specific to a device implementation and transparent to other devices. [0208] In some of the embodiments described, a TCI-state (Transmission Configuration Indication) associated with a target transmission can indicate parameters for configuring a quasi- collocation relationship between the target transmission (e.g., target RS of DM-RS ports of the target transmission during a transmission occasion) and a source reference signal(s) (e.g., SSB/CSI-RS/SRS) with respect to quasi co-location type parameter(s) indicated in the corresponding TCI state. The TCI describes which reference signals are used as QCL source, and what QCL properties can be derived from each reference signal. A device can receive a configuration of a plurality of transmission configuration indicator states for a serving cell for transmissions on the serving cell. In some of the embodiments described, a TCI state comprises at least one source RS to provide a reference (UE assumption) for determining QCL and/or spatial filter. [0209] In some of the embodiments described, a spatial relation information associated with a target transmission can indicate parameters for configuring a spatial setting between the target transmission and a reference RS (e.g., SSB/CSI-RS/SRS). For example, the device may transmit the target transmission with the same spatial domain filter used for reception the reference RS (e.g., DL RS such as SSB/CSI-RS). In another example, the device may transmit the target transmission with the same spatial domain transmission filter used for the transmission of the reference RS (e.g., UL RS such as SRS). A device can receive a configuration of a plurality of spatial relation information configurations for a serving cell for transmissions on the serving cell. [0210] Figure 11 depicts a user equipment apparatus 1100 that may be used for PUCCH reporting of reciprocity-based Type-II codebook, according to embodiments of the disclosure. In various embodiments, the user equipment apparatus 1100 is used to implement one or more of the solutions described above. The user equipment apparatus 1100 may be one embodiment of a UE, such as the remote unit 105 and/or the UE 205, as described above. Furthermore, the user equipment apparatus 1100 may include a processor 1105, a memory 1110, an input device 1115, an output device 1120, and a transceiver 1125. In some embodiments, the input device 1115 and the output device 1120 are combined into a single device, such as a touchscreen. In certain embodiments, the user equipment apparatus 1100 may not include any input device 1115 and/or output device 1120. In various embodiments, the user equipment apparatus 1100 may include one or more of: the processor 1105, the memory 1110, and the transceiver 1125, and may not include the input device 1115 and/or the output device 1120. [0211] As depicted, the transceiver 1125 includes at least one transmitter 1130 and at least one receiver 1135. Here, the transceiver 1125 communicates with one or more base units 121. Additionally, the transceiver 1125 may support at least one network interface 1140 and/or application interface 1145. The application interface(s) 1145 may support one or more APIs. The network interface(s) 1140 may support 3GPP reference points, such as Uu and PC5. Other network interfaces 1140 may be supported, as understood by one of ordinary skill in the art. [0212] The processor 1105, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 1105 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), a digital signal processor (“DSP”), a co-processor, an application-specific processor, or similar programmable controller. In some embodiments, the processor 1105 executes instructions stored in the memory 1110 to perform the methods and routines described herein. [0213] The processor 1105 is communicatively coupled to the memory 1110, the input device 1115, the output device 1120, and the transceiver 1125. In certain embodiments, the processor 1105 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions. In various embodiments, the processor 1105 controls the user equipment apparatus 1100 to implement the above described UE behaviors for PUCCH reporting of reciprocity-based Type-II codebook. [0214] The memory 1110, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 1110 includes volatile computer storage media. For example, the memory 1110 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 1110 includes non-volatile computer storage media. For example, the memory 1110 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 1110 includes both volatile and non-volatile computer storage media. [0215] In some embodiments, the memory 1110 stores data related to PUCCH reporting of reciprocity-based Type-II codebook. For example, the memory 1110 may store parameters, configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory 1110 also stores program code and related data, such as an operating system or other controller algorithms operating on the user equipment apparatus 1100, and one or more software applications. [0216] The input device 1115, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 1115 may be integrated with the output device 1120, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 1115 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 1115 includes two or more different devices, such as a keyboard and a touch panel. [0217] The output device 1120, in one embodiment, is designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 1120 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 1120 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 1120 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 1100, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 1120 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like. [0218] In certain embodiments, the output device 1120 includes one or more speakers for producing sound. For example, the output device 1120 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 1120 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the output device 1120 may be integrated with the input device 1115. For example, the input device 1115 and output device 1120 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 1120 may be located near the input device 1115. [0219] The transceiver 1125 includes at least transmitter 1130 and at least one receiver 1135. The transceiver 1125 may be used to provide UL communication signals to a base unit 121 and to receive DL communication signals from the base unit 121, as described herein. Similarly, the transceiver 1125 may be used to transmit and receive sidelink (“SL”) signals (e.g., V2X communication). Although only one transmitter 1130 and one receiver 1135 are illustrated, the user equipment apparatus 1100 may have any suitable number of transmitters 1130 and receivers 1135. Further, the transmitter(s) 1130 and the receiver(s) 1135 may be any suitable type of transmitters and receivers. In one embodiment, the transceiver 1125 includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum. [0220] In certain embodiments, the first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components. For example, certain transceivers 1125, transmitters 1130, and receivers 1135 may be implemented as physically separate components that access a shared hardware resource and/or software resource, such as for example, the network interface 1140. [0221] In various embodiments, one or more transmitters 1130 and/or one or more receivers 1135 may be implemented and/or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an ASIC, or other type of hardware component. In certain embodiments, one or more transmitters 1130 and/or one or more receivers 1135 may be implemented and/or integrated into a multi-chip module. In some embodiments, other components such as the network interface 1140 or other hardware components/circuits may be integrated with any number of transmitters 1130 and/or receivers 1135 into a single chip. In such embodiment, the transmitters 1130 and receivers 1135 may be logically configured as a transceiver 1125 that uses one more common control signals or as modular transmitters 1130 and receivers 1135 implemented in the same hardware chip or in a multi-chip module. [0222] In one embodiment, the transceiver 1125 receives, from a network entity, a channel state information (“CSI”) reporting configuration comprising a codebook type associated with a precoding matrix. In one embodiment, the transceiver 1125 receives, from the network entity, CSI reference signals (“CSI-RS”) over a set of CSI-RS resources based on the CSI reporting configuration. In one embodiment, the processor 1105 identifies a set of coefficients associated with the codebook based on the received set of CSI-RS resources. In one embodiment, the transceiver 1225 transmits, to the network entity, a CSI report on a physical uplink control channel (“PUCCH”) or a physical uplink shared channel (“PUSCH”) and based on the codebook type, the CSI report comprising CSI and the set of coefficients, wherein to transmit the CSI report on the PUCCH is based on a value of a sub-configuration of the CSI reporting configuration. [0223] In one embodiment, the codebook type is indicated using a higher-layer parameter of a codebook configuration within the CSI reporting configuration. [0224] In one embodiment, the CSI report is configured to be reported over the PUCCH. [0225] In one embodiment, the transceiver 1125 transmits the CSI report based on one of periodic reporting and semi-persistent reporting. [0226] In one embodiment, the CSI report is associated with one or more of a precoding matrix indicator (“PMI”) format indicator that is restricted to a value corresponding to a wideband format and a channel quality indicator (“CQI”) that is restricted to a value corresponding to a wideband format. [0227] In one embodiment, a maximum configured value of a number of PMI sub-bands per CQI sub-band corresponding to the CSI report is less than a maximum configured value of a number of PMI sub-bands per CQI sub-band corresponding to a CSI report configured to be reported over the PUSCH. [0228] In one embodiment, a maximum configured value of a rank of the codebook corresponding to the CSI report is less than a maximum configured value of a rank of the codebook corresponding to a CSI report configured to be reported over the PUSCH. [0229] In one embodiment, the CSI report comprises PMI-based coefficients corresponding to at least one dimension corresponding to one or more frequency-domain basis indices. [0230] In one embodiment, a maximum configured value of a number of frequency- domain basis indices corresponding to the CSI report is less than a maximum configured value of a number of frequency-domain basis indices corresponding to a CSI report configured to be reported over the PUSCH. [0231] In one embodiment, the set of one or more non-zero power (“NZP”) CSI-RS resources for channel measurement is configured with frequency density of a value equal to one quarter. [0232] In one embodiment, a CSI-RS resource mapping corresponding to the set of one or more NZP CSI-RS resources comprises an indication of a resource-block level offset, the resource- block level offset taking on values of 0, 1, 2, or 3. [0233] In one embodiment, the set of one or more NZP CSI-RS resources for channel measurement configured with frequency density of a value equal to one quarter corresponds to CSI reporting on the PUCCH. [0234] In one embodiment, the codebook type is a port-selection codebook. [0235] Figure 12 depicts one embodiment of a network apparatus 1200 that may be used for PUCCH reporting of reciprocity-based Type-II codebook, according to embodiments of the disclosure. In some embodiments, the network apparatus 1200 may be one embodiment of a RAN node and its supporting hardware, such as the base unit 121 and/or the gNB 210, described above. Additionally, the network apparatus 1200 may include a processor 1205, a memory 1210, an input device 1215, an output device 1220, and a transceiver 1225. In certain embodiments, the network apparatus 1200 does not include any input device 1215 and/or output device 1220. [0236] As depicted, the transceiver 1225 includes at least one transmitter 1230 and at least one receiver 1235. Here, the transceiver 1225 communicates with one or more remote units 65. Additionally, the transceiver 1225 may support at least one network interface 1240 and/or application interface 1245. The application interface(s) 1245 may support one or more APIs. The network interface(s) 1240 may support 3GPP reference points, such as Uu, S1, N1, N2, and/or N3 interfaces. Other network interfaces 1240 may be supported, as understood by one of ordinary skill in the art. [0237] The processor 1205, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 1205 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), a digital signal processor (“DSP”), a co-processor, an application-specific processor, or similar programmable controller. In some embodiments, the processor 1205 executes instructions stored in the memory 1210 to perform the methods and routines described herein. [0238] The processor 1205 is communicatively coupled to the memory 1210, the input device 1215, the output device 1220, and the transceiver 1225. In certain embodiments, the processor 1205 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio function. In various embodiments, the processor 1205 controls the network apparatus 1200 to implement the above described network entity behaviors for PUCCH reporting of reciprocity-based Type-II codebook. [0239] The memory 1210, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 1210 includes volatile computer storage media. For example, the memory 1210 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 1210 includes non-volatile computer storage media. For example, the memory 1210 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 1210 includes both volatile and non-volatile computer storage media. [0240] In some embodiments, the memory 1210 stores data relating to PUCCH reporting of reciprocity-based Type-II codebook. For example, the memory 1210 may store parameters, configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory 1210 also stores program code and related data, such as an operating system (“OS”) or other controller algorithms operating on the network apparatus 1200, and one or more software applications. [0241] The input device 1215, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 1215 may be integrated with the output device 1220, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 1215 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 1215 includes two or more different devices, such as a keyboard and a touch panel. [0242] The output device 1220, in one embodiment, may include any known electronically controllable display or display device. The output device 1220 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 1220 includes an electronic display capable of outputting visual data to a user. Further, the output device 1220 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like. [0243] In certain embodiments, the output device 1220 includes one or more speakers for producing sound. For example, the output device 1220 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 1220 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the output device 1220 may be integrated with the input device 1215. For example, the input device 1215 and output device 1220 may form a touchscreen or similar touch-sensitive display. In other embodiments, all or portions of the output device 1220 may be located near the input device 1215. [0244] As discussed above, the transceiver 1225 may communicate with one or more remote units and/or with one or more interworking functions that provide access to one or more PLMNs. The transceiver 1225 may also communicate with one or more network functions (e.g., in the mobile core network 130). The transceiver 1225 operates under the control of the processor 1205 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor 1205 may selectively activate the transceiver (or portions thereof) at particular times in order to send and receive messages. [0245] The transceiver 1225 may include one or more transmitters 1230 and one or more receivers 1235. In certain embodiments, the one or more transmitters 1230 and/or the one or more receivers 1235 may share transceiver hardware and/or circuitry. For example, the one or more transmitters 1230 and/or the one or more receivers 1235 may share antenna(s), antenna tuner(s), amplifier(s), filter(s), oscillator(s), mixer(s), modulator/demodulator(s), power supply, and the like. In one embodiment, the transceiver 1225 implements multiple logical transceivers using different communication protocols or protocol stacks, while using common physical hardware. [0246] In one embodiment, the transceiver 1225 transmits, to a UE, a CSI reporting configuration comprising a codebook type associated with a precoding matrix. In one embodiment, the transceiver 1225 transmits, to the UE, CSI reference signals (“CSI-RS”) over a set of CSI-RS resources based on the CSI reporting configuration. In one embodiment, the transceiver 1225 receives, from the UE, a CSI report on a physical uplink control channel (“PUCCH”) or a physical uplink shared channel (“PUSCH”) and based on the codebook type, the CSI report comprising CSI and a set of coefficients associated with the codebook, wherein to receive the CSI report on the PUCCH is based on a value of a sub-configuration of the CSI reporting configuration. [0247] Figure 13 is a flowchart diagram of a method 1300 for PUCCH reporting of reciprocity-based type-II codebook. The method 1300 may be performed by a user equipment device operating in a communication network, for example, the remote unit 105 and/or the user equipment apparatus 1100, described above. In some embodiments, the method 1300 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0248] In one embodiment, the method 1300 includes receiving 1305, from a network entity, a channel state information (“CSI”) reporting configuration comprising a codebook type associated with a precoding matrix. In one embodiment, the method 1300 includes receiving 1310, from the network entity, CSI reference signals (“CSI-RS”) over a set of CSI-RS resources based on the CSI reporting configuration. In one embodiment, the method 1300 includes identifying 1315 a set of coefficients associated with the codebook based on the received set of CSI-RS resources. In one embodiment, the method 1300 includes transmitting 1320, to the network entity, a CSI report on a physical uplink control channel (“PUCCH”) or a physical uplink shared channel (“PUSCH”) and based on the codebook type, the CSI report comprising CSI and the set of coefficients, wherein to transmit the CSI report on the PUCCH is based on a value of a sub- configuration of the CSI reporting configuration, and the method 1300 ends. [0249] Figure 14 is a flowchart diagram of a method 1300 for PUCCH reporting of reciprocity-based type-II codebook. The method 1400 may be performed a network equipment device operating in a communication network, for example, the access point 112, base unit 121, a gNB, and/or the network equipment apparatus 1200, described above. In some embodiments, the method 1400 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0250] In one embodiment, the method 1400 transmits 1405, to a user equipment (“UE”), a channel state information (“CSI”) reporting configuration comprising a codebook type associated with a precoding matrix. In one embodiment, the method 1400 transmits 1410, to the UE, CSI reference signals (“CSI-RS”) over a set of CSI-RS resources based on the CSI reporting configuration. In one embodiment, the method 1400 receives 1415, from the UE, a CSI report on a physical uplink control channel (“PUCCH”) or a physical uplink shared channel (“PUSCH”) and based on the codebook type, the CSI report comprising CSI and a set of coefficients associated with the codebook, wherein to receive the CSI report on the PUCCH is based on a value of a sub- configuration of the CSI reporting configuration, and the method 1400 ends. [0251] A first apparatus is disclosed for PUCCH reporting of reciprocity-based type-II codebook. The first apparatus may include a user equipment device operating in a communication network, for example, the remote unit 105 and/or the user equipment apparatus 1100, described above. In some embodiments, the first apparatus may include a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0252] In one embodiment, the first apparatus includes a transceiver that receives, from a network entity, a channel state information (“CSI”) reporting configuration comprising a codebook type associated with a precoding matrix. In one embodiment, the transceiver receives, from the network entity, CSI reference signals (“CSI-RS”) over a set of CSI-RS resources based on the CSI reporting configuration. In one embodiment, the apparatus includes a processor that identifies a set of coefficients associated with the codebook based on the received set of CSI-RS resources. In one embodiment, the transceiver transmits, to the network entity, a CSI report on a physical uplink control channel (“PUCCH”) or a physical uplink shared channel (“PUSCH”) and based on the codebook type, the CSI report comprising CSI and the set of coefficients, wherein to transmit the CSI report on the PUCCH is based on a value of a sub-configuration of the CSI reporting configuration. [0253] In one embodiment, the codebook type is indicated using a higher-layer parameter of a codebook configuration within the CSI reporting configuration. [0254] In one embodiment, the CSI report is configured to be reported over the PUCCH. [0255] In one embodiment, the transceiver transmits the CSI report based on one of periodic reporting and semi-persistent reporting. [0256] In one embodiment, the CSI report is associated with one or more of a precoding matrix indicator (“PMI”) format indicator that is restricted to a value corresponding to a wideband format and a channel quality indicator (“CQI”) that is restricted to a value corresponding to a wideband format. [0257] In one embodiment, a maximum configured value of a number of PMI sub-bands per CQI sub-band corresponding to the CSI report is less than a maximum configured value of a number of PMI sub-bands per CQI sub-band corresponding to a CSI report configured to be reported over the PUSCH. [0258] In one embodiment, a maximum configured value of a rank of the codebook corresponding to the CSI report is less than a maximum configured value of a rank of the codebook corresponding to a CSI report configured to be reported over the PUSCH. [0259] In one embodiment, the CSI report comprises PMI-based coefficients corresponding to at least one dimension corresponding to one or more frequency-domain basis indices. [0260] In one embodiment, a maximum configured value of a number of frequency- domain basis indices corresponding to the CSI report is less than a maximum configured value of a number of frequency-domain basis indices corresponding to a CSI report configured to be reported over the PUSCH. [0261] In one embodiment, the set of one or more non-zero power (“NZP”) CSI-RS resources for channel measurement is configured with frequency density of a value equal to one quarter. [0262] In one embodiment, a CSI-RS resource mapping corresponding to the set of one or more NZP CSI-RS resources comprises an indication of a resource-block level offset, the resource- block level offset taking on values of 0, 1, 2, or 3. [0263] In one embodiment, the set of one or more NZP CSI-RS resources for channel measurement configured with frequency density of a value equal to one quarter corresponds to CSI reporting on the PUCCH. [0264] In one embodiment, the codebook type is a port-selection codebook. [0265] A first method is disclosed for PUCCH reporting of reciprocity-based type-II codebook. The first method may be performed by a user equipment device operating in a communication network, for example, the remote unit 105 and/or the user equipment apparatus 1100, described above. In some embodiments, the first method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0266] In one embodiment, the first method includes receiving, from a network entity, a channel state information (“CSI”) reporting configuration comprising a codebook type associated with a precoding matrix. In one embodiment, the first method includes receiving, from the network entity, CSI reference signals (“CSI-RS”) over a set of CSI-RS resources based on the CSI reporting configuration. In one embodiment, the first method includes identifying a set of coefficients associated with the codebook based on the received set of CSI-RS resources. In one embodiment, the first method includes transmitting, to the network entity, a CSI report on a physical uplink control channel (“PUCCH”) or a physical uplink shared channel (“PUSCH”) and based on the codebook type, the CSI report comprising CSI and the set of coefficients, wherein to transmit the CSI report on the PUCCH is based on a value of a sub-configuration of the CSI reporting configuration. [0267] In one embodiment, the codebook type is indicated using a higher-layer parameter of a codebook configuration within the CSI reporting configuration. [0268] In one embodiment, the CSI report is configured to be reported over the PUCCH. [0269] In one embodiment, the first method transmits the CSI report based on one of periodic reporting and semi-persistent reporting. [0270] In one embodiment, the CSI report is associated with one or more of a precoding matrix indicator (“PMI”) format indicator that is restricted to a value corresponding to a wideband format and a channel quality indicator (“CQI”) that is restricted to a value corresponding to a wideband format. [0271] In one embodiment, a maximum configured value of a number of PMI sub-bands per CQI sub-band corresponding to the CSI report is less than a maximum configured value of a number of PMI sub-bands per CQI sub-band corresponding to a CSI report configured to be reported over the PUSCH. [0272] In one embodiment, a maximum configured value of a rank of the codebook corresponding to the CSI report is less than a maximum configured value of a rank of the codebook corresponding to a CSI report configured to be reported over the PUSCH. [0273] In one embodiment, the CSI report comprises PMI-based coefficients corresponding to at least one dimension corresponding to one or more frequency-domain basis indices. [0274] In one embodiment, a maximum configured value of a number of frequency- domain basis indices corresponding to the CSI report is less than a maximum configured value of a number of frequency-domain basis indices corresponding to a CSI report configured to be reported over the PUSCH. [0275] In one embodiment, the set of one or more non-zero power (“NZP”) CSI-RS resources for channel measurement is configured with frequency density of a value equal to one quarter. [0276] In one embodiment, a CSI-RS resource mapping corresponding to the set of one or more NZP CSI-RS resources comprises an indication of a resource-block level offset, the resource- block level offset taking on values of 0, 1, 2, or 3. [0277] In one embodiment, the set of one or more NZP CSI-RS resources for channel measurement configured with frequency density of a value equal to one quarter corresponds to CSI reporting on the PUCCH. [0278] In one embodiment, the codebook type is a port-selection codebook. [0279] A second apparatus is disclosed for PUCCH reporting of reciprocity-based type-II codebook. The second apparatus may include a network equipment device operating in a communication network, for example, the access point 112, base unit 121, a gNB, and/or the network equipment apparatus 1200, described above. In some embodiments, the second apparatus may include a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0280] In one embodiment, the second apparatus includes a transceiver that transmits, to a user equipment (“UE”), a channel state information (“CSI”) reporting configuration comprising a codebook type associated with a precoding matrix. In one embodiment, the transceiver transmits, to the UE, CSI reference signals (“CSI-RS”) over a set of CSI-RS resources based on the CSI reporting configuration. In one embodiment, the transceiver receives, from the UE, a CSI report on a physical uplink control channel (“PUCCH”) or a physical uplink shared channel (“PUSCH”) and based on the codebook type, the CSI report comprising CSI and a set of coefficients associated with the codebook, wherein to receive the CSI report on the PUCCH is based on a value of a sub- configuration of the CSI reporting configuration. [0281] A second method is disclosed for PUCCH reporting of reciprocity-based type-II codebook. The second method may be performed a network equipment device operating in a communication network, for example, the access point 112, base unit 121, a gNB, and/or the network equipment apparatus 1200, described above. In some embodiments, the second method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0282] In one embodiment, the second method transmits, to a user equipment (“UE”), a channel state information (“CSI”) reporting configuration comprising a codebook type associated with a precoding matrix. In one embodiment, the second method transmits, to the UE, CSI reference signals (“CSI-RS”) over a set of CSI-RS resources based on the CSI reporting configuration. In one embodiment, the second method receives, from the UE, a CSI report on a physical uplink control channel (“PUCCH”) or a physical uplink shared channel (“PUSCH”) and based on the codebook type, the CSI report comprising CSI and a set of coefficients associated with the codebook, wherein to receive the CSI report on the PUCCH is based on a value of a sub- configuration of the CSI reporting configuration. [0283] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.