Channel state information (CSI) measurements for large antenna arrays

Abstract

Various embodiments herein provide techniques related to transmission of channel state information (CSI)-reference signal (RS) information transmitted by a base station on greater than 32 CSI-RS ports. A user equipment (UE) may perform one or more CSI measurements on CSI-RS information received from a subset of the greater than 32 CSI-RS ports, where the subset includes 32 or fewer CSI-RS ports. The UE may then generate, based on the CSI measurements, a CSI report that includes a CSI value related to the greater than 32 CSI-RS ports. Other embodiments may be described and / or claimed.

Description

[0001] CHANNEL STATE INFORMATION (CSI) MEASUREMENTS FOR LARGE ANTENNA ARRAYS CROSS REFERENCE TO RELATED APPLICATION The present application claims priority to U.S. Provisional Patent Application No. 63 / 550,526, which was filed February 6th, 2024; and to U.S. Provisional Patent Application No. 63 / 554.818, which was filed February 16th, 2024. BACKGROUND Various embodiments generally may relate to the field of wireless communications. BRIEF DESCRIPTION OF THE DRAWINGS Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings. Figure 1 depicts examples of a channel state informtion (CSI)-reference signal (RS) block, in accordance with various embodiments. Figures 2a and 2b (collectively, Figure 2) depict examples of a CSI-RS, in accordance with various embodiments. Figures 3a, 3b, 3c, 3d, 3e, and 3f (collectively, Figure 3) depict examples of different CSI-RS resource element (RE) mapping options, in accordance with various embodiments. Figure 4 schematically illustrates a wireless network in accordance with various embodiments. Figure 5 schematically illustrates components of a wireless network in accordance with various embodiments. Figure 6 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Figure 7 illustrates a network in accordance with various embodiments. Figure 8 depicts an example procedure for practicing the various embodiments discussed herein. Figure 9 depicts another example procedure for practicing the various embodiments discussed herein. Figure 10 depicts another example procedure for practicing the various embodiments discussed herein. Figure 11 depicts another example procedure for practicing the various embodiments herein. DETAILED DESCRIPTION The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A / B” mean (A), (B), or (A and B). Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 v16.0.0 (2019-06).

[0002] Performance of physical downlink shared channel (PDSCH) transmission in fifth generation (5G) new radio (NR) cellular communication systems may depend on the availability of CSI at a base station such as a gNodeB (gNB). CSI feedback, for example as may be reported by a user equipment (UE) may be used by a gNB to derive CSI. Progress in active antenna arrays technology may allow the production of antenna arrays with a large number of antenna ports for digital beamforming and spatial multiplexing of data streams. Legacy commercial gNB antenna arrays may support at least 64 antenna ports for transmission and reception. However, CSI in legacy 5G NR physical layer third genereation partnership (3GPP) specifications may be optimized for smaller numbers of antenna ports. Specifically, optimized CSI-RS configuration and Precoding Matrix Indicator (PMI) codebooks may not be available in legacy specifications for gNBs with more than 32 antenna ports. Various embodiments herein provide techniques for CSI-RS configurations for precoding with more than 32 CSI-RS ports, and may further relate to UE CSI processing aspects for such configurations. Aspects of various embodiments may be incorporated into 5G NR and / or future physical layer specifications, e.g., 3GPP Technical Standard (TS) 38.214, 38.213, and / or another standard. Embodiments may include configuration of CSI-RS resources, CSI processing unit (CPU) occupancy rules, and active CSI-RS resource counting for Enhanced Type II precoding matrix indicator (PMI) codebooks for coherent joint transmission (CJT). More generally, embodiments may provide enhancements for 5G NR physical layer specifications that support or describe CSI-RS configuration targeting at support of CSI Reference Signals (CSI-RS) configuration and resource mapping for precoding with more than 32 CSI-RS ports. Embodiments may further relate to UE CSI processing aspects for such configuration including CSI processing units (CPU) occupancy and active CSI-RS resource counting. 1.1 Channel state information feedback CSI feedback may be used in 5G NR (New Radio) systems to assist scheduling, link adaptation, precoding and spatial multiplexing operations for PDSCH transmission(s). CSI reports may be transmitted from a UE to a gNB via the physical uplink control channel (PUCCH) and / or the physical uplink shared channel (PUSCH). The following are three example components of a CSI report: • CSI-RS resource indicator (CRI): indicates CSI-RS resource(s) that are selected by the UE and used for computation of other CSI components in the CSI report; • Rank indicator (RI): contains information on the number of spatial layers (rank) recommended by the UE for PDSCH; • PMI: contains information on the precoding matrix recommended by the UE for PDSCH; • Channel quality indicator (CQI): contains information on the modulation and coding scheme recommended by the UE for PDSCH. For a given CSI report, a UE is configured with K≥1 CSI-RS resources each corresponding to P≥1 CSI-RS ports in each CSI-RS resource. To determine CRI / RI / PMI / CQI for the CSI report, UE measures channel on the configured CSI-RS resources and CSI-RS ports. For the PMI codebooks supported for NR, except PMI codebook for CJT (Coherent Joint Transmission), P ∊ {2,4,8,12,16,24,32} for K = 1, P ∊ {2,4,8,12,16} for K = 2, P ∊ {2,4,8} for 2 < K ≤ 8. A UE selects one CSI-RS resource and determines RI, PMI and CQI by using a channel measurement on the selected CSI-RS resource. An index of the selected CSI-RS resource corresponds to the reported CRI. For PMI codebook for CJT, P ∊ {4,8,12,16,24,32} for K ∊ {1,2,3,4}. A UE reports RI, PMI and CQI by using channel measured on all the configured CSI-RS resources. CSI-RS measurement CSI-RS blocks are defined as a set of indexes of subcarriers and OFDM (Orthogonal FrequencyDivision Multiplexing) symbols (^′, ^′). Thus, CSI-RS Resource Element (RE) mapping withing PRB(Physical Resource Block) is determined by indexes of starting subcarrier and OFDM symbol of CSI-RS blocks (^^, ^)̅ for a given CSI-RS block. Some example time-frequency-code domain CSI-RS blocksare illustrated in Figure 1. CSI-RS resource higher-layer configuration may include one or more of the following parameters. - frequencyDomainAllocation - contains bitmap [b5,…,b0], indicating subcarrier indexes for CSI-RS blocks ^^, where ^^^^^ = 2^(^), f(i) is the bit number of the ith bit in the bitmap set to 1- nrofPorts – number of ports per CSI-RS resource (P) - firstOFDMSymbolInTimeDomain – starting orthogonal frequency division multiplexed (OFDM) symbol of the first CSI-RS RE block (^^̅ ∈ {0,13})- firstOFDMSymbolInTimeDomain2 – starting OFDM symbol of the second CSI-RS RE block (^^̅ ∈ {2,12})- cdm-Type – code division multiplexing (CDM) type (‘noCDM’, ‘fd-CDM2’, ‘cdm4-FD2-TD2’, ‘cdm8-FD2-TD4’) - density – CSI-RS density given by the number of CSI-RS RE per CSI-RS port per physical resource block (PRB) (D) - freqBand – initial PRB index (PRBinit) and number of PRBs (PRBnum) allocated for CSI-RS - periodicityAndOffset – periodicity (T) and slot offset (KP) for periodic CSI-RS - aperiodicTriggeringOffset – slot offset (KA) for aperiodic CSI-RS Efficiency of CSI-RS measurements may depond on distance in time and frequency between CSI-RS ports processed together. Legacy NR specifications, including CSI-RS RE mapping, is optimized for up to 32 ports processed together. To further increase the number of CSI-RS ports processed in a single PMI report up to 128, configuration of multiple CSI-RS resources may be used. In particular, different rows of a precoding matrix corresponding to a PMI may be mapped to different CSI-RS ports of different CSI-RS resources. In one embodiment CSI-RS resource mapping configuration is extended across PRB boundary in frequency domain. The number of bits in a bitmap for CSI-RS RE mapping in frequency domain [bN-1, …, b0], may be extended to support N > 6 and the number of consecutive subcarriers to apply the bitmap is extended from 1 to 2·N. This pattern may repeat every 2N subcarriers and M PRBs. If bit bnis set to 1 for n > (6·Z-1), the starting subcarrier index for CSI-RS block (2·n) is located in the Zth PRB closest to the PRB for CSI-RS mapping. M is a natural number which satisfies the following equation mod(6·M, N) = 0, where mod() is the modulo operation. CSI-RS density is 6 / N. Figure 2a depicts an example of M=2 and the bitmap is extended to N=12. The CSI-RS RE pattern repeats every 2 PRBs, and the resulting CSI-RS density is 0.5. Figure 2b depicts another example where M=4 and the bitmap is extended to N=8. The CSI- RS RE pattern repeats every 16 subcarriers and 4 PRBs. The resulting CSI-RS density is 3 / 4. In another example (not shown for the sake of lack of redundancy), M=8 and the bitmap is extended to N=16. The CSI-RS RE pattern repeats every 32 subcarriers and 8 PRBs. The resulting CSI-RS density is 3 / 8. Figure 3 depicts various examples of CSI-RS RE mapping options. In Figure 3, different groups of resources are indicated by different letters (e.g., “A”, “B,” “C,” etc.). The specific alphabetic designations of these elements are for the sake of description of these particular figures only, and are not intended to convey any information beyond “this element is different than that element.” Additionally, although different ones of the letters are used between different Figures (e.g., between Figure 3a and 3b), unless specifically indicated to the contrary, the alphabetic designations are not intended to correlate to one another. In other words, the resources designated by “A” in Figure 3a are not necessarily the same as the resources designated by “A” in Figure 3b, unless indicated otherwise. Alternatively, the CSI-RS resources mapping configuration may be extended to cross PRB boundary by a RE offset ^^^which defines starting subcarrier within a PRB to start CSI-RS bitmap application, and the bitmap size is unchanged in this case, e.g., kept to N=6 for the applicable CSI-RS block configurations. The RE offset may be configurable from a small set of possible values {0, 8} to realize the example in Figure 3a where RE offset of 8 is shown for CSI-RS resources represented by the letters “B” and “D.: Furthermore, the set of possible values may include all even starting RE within a PRB cases, {0,2,4,6,8,10}. Even further, the other alternative possible offsets are {0,4,8} and {0,1,2,3,4,5,6,7,8,9,10,11}. In an option, mapping of CSI-RS resource across PRBs, may be controlled by the CSI-RSdensity parameter ^. In addition to {0.5, 1} density, ^ =^ ^ density may be introduced, meaning that there are three CSI-RS REs mapped across four PRBs with a total offset of 16 REs. The new density parameter applicability may be limited to the cases with 8 CSI-RS REs within a PRB, e.g., for X = 8,16,32 and the rows 6, 11, 12, 16, 17, 18 cited in “Table 7.4.1.5.3-1: CSI-RS locations within a slot” of TS 38.211. In other embodiment, as shown in Figure 3b CSI-RS resource mapping configuration is extended across PRB (slot) boundary in time domain. The second OFDM symbol for CSI-RS REblock mapping may be mapped into symbol indexed ^^̅ ∈ {2, ^}, where ^ > 13 for Normal CyclicPrefix (NCP) and ^ > 11 for Extended Cyclic Prefix (ECP). If ^^̅ > 13 for NCP or ^^̅ > 11 for ECP, thestarting subcarrier for CSI-RS block is located in the adjacent slot closest to the slot for CSI-RS mapping. In relation to the above embodiment, a UE may not expect the CSI-RS resourceconfiguration which supports ^ > 13(11) which overlaps with semi-static UL or semi-static flexiblesymbols. In other embodiment, as shown in Figure 3c, the total number of CSI-RS ports configured for a CSI report K·P may be larger than PPMI, where PPMI is the number of CSI-RS ports for PMI reporting. In this case, RI, PMI and CQI are determined based on CSI-RS ports with indexes h ≤ PPMI. In order to support this case, a separate parameter PPMI may be introduced and signaled in RRC. It will be noted in Figure 3c that the CSI-RS REs that are filled in as black may not be used for the CSI report. In one embodiment, a plurality of CSI-RS resources may be linked / bundled for generation of a single CSI report with PPMI ports. In particular, a UE may not expect different linked CSI-RS resources to be contained in multiple slots. Alternatively, more than one slots may be used to accommodate all linked CSI-RS resources. In one option, the definition of a single CSI resource (e.g., NZP-CSI-RS-Resource), may be extended to support more than 32 ports by accommodating multiple time division multiplexed (TDM) / frequency division multiplexed (FDM) / CDM group resources in a single CSI resource. A new resource mapping information element, e.g., resourceMapping-r19 may be introduced (as indicated by the bold and italics elements) which is a combination of up to M legacy resourceMapping information elements, as illustrated in the following example NZP-CSI-RS- Resource information element. Here M may be at least 4, so that 128 ports are achieved by 4 x 32 port CSI-RS resources. Further, the list may be either composed from the same size CSI-RS resources or from different size CSI-RS resources. NZP-CSI-RS-Resource information element -- ASN1START -- TAG-NZP-CSI-RS-RESOURCE-START NZP-CSI-RS-Resource ::= SEQUENCE { nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId, resourceMapping CSI-RS-ResourceMapping, powerControlOffset INTEGER (-8..15), powerControlOffsetSS ENUMERATED{db-3, db0, db3, db6} OPTIONAL, -- Need R scramblingID ScramblingId, periodicityAndOffset CSI- ResourcePeriodicityAndOffset OPTIONAL, -- Cond PeriodicOrSemiPersistent qcl-InfoPeriodicCSI-RS TCI-StateId OPTIONAL, -- Cond Periodic ..., [[ subcarrierSpacing-r18 SubcarrierSpacing OPTIONAL, -- Cond LTM absoluteFrequencyPointA-r18 ARFCN-ValueNR OPTIONAL, -- Cond LTM cyclicPrefix-r18 ENUMERATED {extended} OPTIONAL -- Cond LTM resourceMapping-r19 SEQUENCE (SIZE (1..M)) OF resourceMapping ]] } -- TAG-NZP-CSI-RS-RESOURCE-STOP -- ASN1STOP In another option, the resource mapping information element may be extended to support > 32 CSI-RS ports by keeping the specified number of ports and CDM type and repeating the basic structure as per one of the options discussed above. As illustrated in the following CSI-RS- ResourceMapping information element, an additional parameter repetitionType may be added (as indicated by the bold and italic elements, wherein particular repetition option, e.g., type1, type2, etc., may indicate how the CSI-RS of up 32 ports is repeated over PRBs and / or symbols in a slot to reach > 32 CSI ports in total. In this case, a given type also indicates multiplication of the nrofPorts parameter. CSI-RS-ResourceMapping information element -- ASN1START -- TAG-CSI-RS-RESOURCEMAPPING-START CSI-RS-ResourceMapping ::= SEQUENCE { frequencyDomainAllocation CHOICE { row1 BIT STRING (SIZE (4)), row2 BIT STRING (SIZE (12)), row4 BIT STRING (SIZE (3)), other BIT STRING (SIZE (6)) }, nrofPorts ENUMERATED {p1,p2,p4,p8,p12,p16,p24,p32}, firstOFDMSymbolInTimeDomain INTEGER (0..13), firstOFDMSymbolInTimeDomain2 INTEGER (2..12) OPTIONAL, -- Need R cdm-Type ENUMERATED {noCDM, fd-CDM2, cdm4-FD2-TD2, cdm8-FD2-TD4}, density CHOICE { dot5 ENUMERATED {evenPRBs, oddPRBs}, one NULL, three NULL, spare NULL }, freqBand CSI-FrequencyOccupation, … repetitionType ENUMERATED {type1, type2, type3, spare,…} } -- TAG-CSI-RS-RESOURCEMAPPING-STOP -- ASN1STOP In another option, the indication of linked CSI-RS resources for one CSI report may be supported by introducing an explicit table of association of a CSI resource configuration ID and a list of nzp-CSI-RS-ResourceSetList which are used for one CSI report. In particular, the multiple nzp-CSI-RS-Resources from the list as part of NZP-CSI-RS-ResourceSet, may be linked / bundled for one CSI report of > 32 ports. The bundling may be implicit, so that when CSI report indicates the codebook configuration with the number of ports larger than the number of ports associated with the referred NZP-CSI-RS- Resource (for example, 2N1N2> nrofPorts), then for one CSI report, series of NZP-CSI-RS-Resources from the list is taken one-by-one so that 2N1N2 = sum(nrofPorts_i), where i – the consecutive indexes of the CSI-RS resources in the list. In another option, one parameter in the NZP-CSI-RS-ResourceSet may be used to indicate that the CSI-RS resources in the CSI-RS resource set are configured to form a CSI-RS resource with > 32 ports. In one example, if 64-, 96- and 128-ports CSI-RS resource is defined, one two-bit parameter in the NZP-CSI-RS-ResourceSet may be used to indicate whether 64-, 96- and 128-ports CSI-RS resource is configured. For instance, bit ‘00’ may be used to indicate that no CSI-RS port bundling or grouping is applied; bit ‘01’ may be used to indicate that 64-port CSI-RS resource is formed; bit ‘10’ may be used to indicate that 96-port CSI-RS resource is formed and bit ‘11’ may be used to indicate that 128-port CSI-RS resource is formed; The bundling may be explicit, by introducing a list of resource IDs composing a single resource bundle / tuple. The following example NZP-CSI-RS-ResourceSet information element illustrates this approach when the tuples of NZP-CSI-RS-ResourceId sets are bundled by a new IE NZP-CSI-RS-Tuples-r19 (as indicated by the bold and italics elements). NZP-CSI-RS-ResourceSet information element -- ASN1START -- TAG-NZP-CSI-RS-RESOURCESET-START NZP-CSI-RS-ResourceSet ::= SEQUENCE { nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId, nzp-CSI-RS-Resources SEQUENCE (SIZE (1..maxNrofNZP- CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceId, repetition ENUMERATED { on, off } OPTIONAL, -- Need S aperiodicTriggeringOffset INTEGER(0..6) OPTIONAL, -- Need S trs-Info ENUMERATED {true} OPTIONAL, -- Need R ..., [[ aperiodicTriggeringOffset-r16 INTEGER(0..31) OPTIONAL -- Need S ]], [[ pdc-Info-r17 ENUMERATED {true} OPTIONAL, -- Need R cmrGroupingAndPairing-r17 CMRGroupingAndPairing-r17 OPTIONAL, -- Need R aperiodicTriggeringOffset-r17 INTEGER (0..124) OPTIONAL, -- Need S aperiodicTriggeringOffsetL2-r17 INTEGER(0..31) OPTIONAL -- Need R ]], [[ resourceType-r18 ENUMERATED {periodic} OPTIONAL -- Cond LTM ]] nzp-CSI-RS-Resource-Tuples-r19 NZP-CSI-RS-Tuples-r19 OPTIONAL } NZP-CSI-RS-Tuples-r19 ::= SEQUENCE (SIZE (1..maxNrofNZP-CSI- RS-ResourcesPerSet )) of { nzp-CSI-RS-Resources SEQUENCE (SIZE (1..M)) OF NZP- CSI-RS-ResourceId } CMRGroupingAndPairing-r17 ::= SEQUENCE { nrofResourcesGroup1-r17 INTEGER (1..7), pair1OfNZP-CSI-RS-r17 NZP-CSI-RS-Pairing-r17 OPTIONAL, -- Need R pair2OfNZP-CSI-RS-r17 NZP-CSI-RS-Pairing-r17 OPTIONAL -- Need R } NZP-CSI-RS-Pairing-r17 ::= SEQUENCE { nzp-CSI-RS-ResourceId1-r17 INTEGER (1..7), nzp-CSI-RS-ResourceId2-r17 INTEGER (1..7) } -- TAG-NZP-CSI-RS-RESOURCESET-STOP -- ASN1STOP In other embodiment number of ports Piis considered separately per CSI-RS resource i ∊{1,2,…K}. The total number of CSI-RS resources used for PMI is !"# = ∑% ^&^ ^. In other embodiment slot offset for aperiodic CSI-RS KA is separately per CSI- RS resource. Different CSI-RS RE mapping options are illustrated in Figure 3, where a RE grid is presented with OFDM symbols in horizontal dimension and subcarriers in vertical dimension. As previously noted, RE mapping for CSI-RS resources jointly used for PMI are presented by use of different alphabetic indicators, for illustration purpose it is assumed that CSI-RS blocks are configured in such way that CSI-RS resource occupies continuous set of adjacent subcarriers in one / two adjacent PRBs and in one / two adjacent slots. Total number of CSI-RS ports across all CSI- RS resources used for PMI is K·P ≥ 128. The number of CSI-RS ports in one CSI-RS resource corresponds to the number of REs with the corresponding alphabetic designation. Specifically, Figure 3a indicates an example of a CSI-RS resource mapping configuration across PRB boundary in frequency domain. Figure 3b indicates an example of a CSI-RS resource mapping configuration across slot boundary in time domain. Figure 3c indicates an example of a total number of CSI-RS ports K·P > PPMI, CSI-RS REs highlighted by pattern fill are not used for the CSI report. Figure 3d indicates an example of a CSI-RS configuration with K = 16 and P = 8. Figure 3e indicates an example where a number of ports P is different per CSI-RS resource configured for PMI. Figure 3f indicates an example wherein a slot offset for aperiodic CSI-RS KAis configured separately per CSI-RS resource. It will be understood that these examples are for the sake of discussion only, and are not intended to be limiting of embodiments to only these specific configurations. CSI processing aspects CSI feedback involves intensive processing at the UE side. Given limited memory and processing power at the UE, there are specific features in NR physical layer specification which allow to limit the CSI processing burden at the UE. Such features include CSI processing units (CPU) occupancy, active CSI-RS resources counting, and minimum CSI processing time. In one embodiment number of CPUs occupied by a CSI report with PPMIports used for PMI calculation is determined as ceil(PPMI / T), where ceil() is ceil function. In one option T is fixed in specification (e.g., T = 32). In other option T is reported by the UE as part of UE capability signaling. In other embodiment number of CPUs occupied by a CSI report with K CSI-RS resources jointly used for PMI is determined as T·K + U or ceil(T·K + U). In one option T and / or U is fixed in specification (e.g., T = 2 and U = 1). In other option T and / or U is reported by the UE as part of UE capability signaling. In one embodiment if multiple CSI sub-configurations are used for a CSI report, the number of CPUs occupied by the CSI report is a sum of number of CPU occupied by the sub- configuration, where number of CPUs occupied by a sub-configuration are determined using methods described above. In one embodiment K CSI-RS resources jointly used for PMI are counted as 1 active CSI-RS resource. In other embodiment K CSI-RS resources jointly used for PMI are counted as ceil(PPMI / B) active CSI-RS resources or ceil(K / B) active CSI-RS resources. In one option B is fixed in specification (e.g., B = 32). In other option B is reported by the UE as part of UE capability signaling. In one aspect a UE configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to ‘128-port-CSI’ is expected to be configured with 1 ≤ Y ≤ 4 CSI-RS resources in a resource set for channel measurement. If interference measurement is performed on CSI-IM, only one resource is configured in the corresponding csi-IM-ResourceSet. If interference measurement is performed on NZP CSI-RS, only one resource is configured in the corresponding NZP-CSI-RS- ResourceSet for interference measurement. In one aspect if the UE is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to '128-port-CSI', codebookType set to '128-port-CSI' and the corresponding NZP-CSI-RSResourceSet for channel measurement is configured with 1 ≤ Y ≤ 4 resources, each resource can contain, at most, 32 CSI-RS ports In one aspect if the UE configured with NZP-CSI-RSResourceSet for channel measurement is configured with 1 ≤ Y ≤ 4 resources, the set of multiple resources is ordered. In one aspect if the UE configured with NZP-CSI-RSResourceSet for channel measurement is configured with 1 ≤ Y ≤ 4 resources, the same value of powerControlOffset (power offset of PDSCH RE to NZP CSI-RS RE) is used for all the resources. In one aspect if the UE configured with NZP-CSI-RSResourceSet for channel measurement is configured with 1 ≤ Y ≤ 4 resources, the same value of powerControlOffsetSS (power offset of NZP CSI-RS RE to SSS RE) is used for all the resources. In one aspect if the UE configured with NZP-CSI-RSResourceSet for channel measurement is configured with 1 ≤ Y ≤ 4 resources, the same qcl-InfoPeriodicCSI-RS (contains a reference to one TCI-State in TCI-States for providing the QCL source and QCL type) is used for all the resources. SYSTEMS AND IMPLEMENTATIONS Figures 4-7 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments. Figure 4 illustrates a network 400 in accordance with various embodiments. The network 400 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like. The network 400 may include a UE 402, which may include any mobile or non-mobile computing device designed to communicate with a RAN 404 via an over-the-air connection. The UE 402 may be communicatively coupled with the RAN 404 by a Uu interface. The UE 402 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc. In some embodiments, the network 400 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. In some embodiments, the UE 402 may additionally communicate with an AP 406 via an over-the-air connection. The AP 406 may manage a WLAN connection, which may serve to offload some / all network traffic from the RAN 404. The connection between the UE 402 and the AP 406 may be consistent with any IEEE 802.11 protocol, wherein the AP 406 could be a wireless fidelity (Wi- Fi®) router. In some embodiments, the UE 402, RAN 404, and AP 406 may utilize cellular-WLAN aggregation (for example, LWA / LWIP). Cellular-WLAN aggregation may involve the UE 402 being configured by the RAN 404 to utilize both cellular radio resources and WLAN resources. The RAN 404 may include one or more access nodes, for example, AN 408. AN 408 may terminate air-interface protocols for the UE 402 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 408 may enable data / voice connectivity between CN 420 and the UE 402. In some embodiments, the AN 408 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 408 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 408 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. In embodiments in which the RAN 404 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 404 is an LTE RAN) or an Xn interface (if the RAN 404 is a 5G RAN). The X2 / Xn interfaces, which may be separated into control / user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data / context transfers, mobility, load management, interference coordination, etc. The ANs of the RAN 404 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 402 with an air interface for network access. The UE 402 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 404. For example, the UE 402 and RAN 404 may use carrier aggregation to allow the UE 402 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first / second ANs may be any combination of eNB, gNB, ng-eNB, etc. The RAN 404 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCells / Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium / carrier-sensing operations based on, for example, a listen-before- talk (LBT) protocol. In V2X scenarios the UE 402 or AN 408 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications / software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular / WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network. In some embodiments, the RAN 404 may be an LTE RAN 410 with eNBs, for example, eNB 412. The LTE RAN 410 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operating on sub-6 GHz bands. In some embodiments, the RAN 404 may be an NG-RAN 414 with gNBs, for example, gNB 416, or ng-eNBs, for example, ng-eNB 418. The gNB 416 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 416 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 418 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 416 and the ng-eNB 418 may connect with each other over an Xn interface. In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 414 and a UPF 448 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN414 and an AMF 444 (e.g., N2 interface). The NG-RAN 414 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS / SSS / PBCH. In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 402 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 402, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 402 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 402 and in some cases at the gNB 416. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load. The RAN 404 is communicatively coupled to CN 420 that includes network elements to provide various functions to support data and telecommunications services to customers / subscribers (for example, users of UE 402). The components of the CN 420 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 420 onto physical compute / storage resources in servers, switches, etc. A logical instantiation of the CN 420 may be referred to as a network slice, and a logical instantiation of a portion of the CN 420 may be referred to as a network sub-slice. In some embodiments, the CN 420 may be an LTE CN 422, which may also be referred to as an EPC. The LTE CN 422 may include MME 424, SGW 426, SGSN 428, HSS 430, PGW 432, and PCRF 434 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 422 may be briefly introduced as follows. The MME 424 may implement mobility management functions to track a current location of the UE 402 to facilitate paging, bearer activation / deactivation, handovers, gateway selection, authentication, etc. The SGW 426 may terminate an S1 interface toward the RAN and route data packets between the RAN and the LTE CN 422. The SGW 426 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. The SGSN 428 may track a location of the UE 402 and perform security functions and access control. In addition, the SGSN 428 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 424; MME selection for handovers; etc. The S3 reference point between the MME 424 and the SGSN 428 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active states. The HSS 430 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 430 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 430 and the MME 424 may enable transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN 420. The PGW 432 may terminate an SGi interface toward a data network (DN) 436 that may include an application / content server 438. The PGW 432 may route data packets between the LTE CN 422 and the data network 436. The PGW 432 may be coupled with the SGW 426 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 432 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 432 and the data network 436 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 432 may be coupled with a PCRF 434 via a Gx reference point. The PCRF 434 is the policy and charging control element of the LTE CN 422. The PCRF 434 may be communicatively coupled to the app / content server 438 to determine appropriate QoS and charging parameters for service flows. The PCRF 432 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI. In some embodiments, the CN 420 may be a 5GC 440. The 5GC 440 may include an AUSF 442, AMF 444, SMF 446, UPF 448, NSSF 450, NEF 452, NRF 454, PCF 456, UDM 458, and AF 460 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 440 may be briefly introduced as follows. The AUSF 442 may store data for authentication of UE 402 and handle authentication-related functionality. The AUSF 442 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 440 over reference points as shown, the AUSF 442 may exhibit an Nausf service-based interface. The AMF 444 may allow other functions of the 5GC 440 to communicate with the UE 402 and the RAN 404 and to subscribe to notifications about mobility events with respect to the UE 402. The AMF 444 may be responsible for registration management (for example, for registering UE 402), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 444 may provide transport for SM messages between the UE 402 and the SMF 446, and act as a transparent proxy for routing SM messages. AMF 444 may also provide transport for SMS messages between UE 402 and an SMSF. AMF 444 may interact with the AUSF 442 and the UE 402 to perform various security anchor and context management functions. Furthermore, AMF 444 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 404 and the AMF 444; and the AMF 444 may be a termination point of NAS (N1) signaling, and perform NAS ciphering and integrity protection. AMF 444 may also support NAS signaling with the UE 402 over an N3 IWF interface. The SMF 446 may be responsible for SM (for example, session establishment, tunnel management between UPF 448 and AN 408); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 448 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 444 over N2 to AN 408; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 402 and the data network 436. The UPF 448 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 436, and a branching point to support multi- homed PDU session. The UPF 448 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 448 may include an uplink classifier to support routing traffic flows to a data network. The NSSF 450 may select a set of network slice instances serving the UE 402. The NSSF 450 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 450 may also determine the AMF set to be used to serve the UE 402, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 454. The selection of a set of network slice instances for the UE 402 may be triggered by the AMF 444 with which the UE 402 is registered by interacting with the NSSF 450, which may lead to a change of AMF. The NSSF 450 may interact with the AMF 444 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 450 may exhibit an Nnssf service-based interface. The NEF 452 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure / re-exposure, AFs (e.g., AF 460), edge computing or fog computing systems, etc. In such embodiments, the NEF 452 may authenticate, authorize, or throttle the AFs. NEF 452 may also translate information exchanged with the AF 460 and information exchanged with internal network functions. For example, the NEF 452 may translate between an AF- Service-Identifier and an internal 5GC information. NEF 452 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 452 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 452 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 452 may exhibit an Nnef service-based interface. The NRF 454 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 454 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 454 may exhibit the Nnrf service-based interface. The PCF 456 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 456 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 458. In addition to communicating with functions over reference points as shown, the PCF 456 exhibit an Npcf service-based interface. The UDM 458 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 402. For example, subscription data may be communicated via an N8 reference point between the UDM 458 and the AMF 444. The UDM 458 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 458 and the PCF 456, and / or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 402) for the NEF 452. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 458, PCF 456, and NEF 452 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 458 may exhibit the Nudm service-based interface. The AF 460 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control. In some embodiments, the 5GC 440 may enable edge computing by selecting operator / 3rdparty services to be geographically close to a point that the UE 402 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 440 may select a UPF 448 close to the UE 402 and execute traffic steering from the UPF 448 to data network 436 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 460. In this way, the AF 460 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 460 is considered to be a trusted entity, the network operator may permit AF 460 to interact directly with relevant NFs. Additionally, the AF 460 may exhibit an Naf service-based interface. The data network 436 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application / content server 438. Figure 5 schematically illustrates a wireless network 500 in accordance with various embodiments. The wireless network 500 may include a UE 502 in wireless communication with an AN 504. The UE 502 and AN 504 may be similar to, and substantially interchangeable with, like- named components described elsewhere herein. The UE 502 may be communicatively coupled with the AN 504 via connection 506. The connection 506 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies. The UE 502 may include a host platform 508 coupled with a modem platform 510. The host platform 508 may include application processing circuitry 512, which may be coupled with protocol processing circuitry 514 of the modem platform 510. The application processing circuitry 512 may run various applications for the UE 502 that source / sink application data. The application processing circuitry 512 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations The protocol processing circuitry 514 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 506. The layer operations implemented by the protocol processing circuitry 514 may include, for example, MAC, RLC, PDCP, RRC and NAS operations. The modem platform 510 may further include digital baseband circuitry 516 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 514 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / de-mapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions. The modem platform 510 may further include transmit circuitry 518, receive circuitry 520, RF circuitry 522, and RF front end (RFFE) 524, which may include or connect to one or more antenna panels 526. Briefly, the transmit circuitry 518 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 520 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 522 may include a low- noise amplifier, a power amplifier, power tracking components, etc.; RFFE 524 may include filters (for example, surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 518, receive circuitry 520, RF circuitry 522, RFFE 524, and antenna panels 526 (referred generically as “transmit / receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be disposed in the same or different chips / modules, etc. In some embodiments, the protocol processing circuitry 514 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components. A UE reception may be established by and via the antenna panels 526, RFFE 524, RF circuitry 522, receive circuitry 520, digital baseband circuitry 516, and protocol processing circuitry 514. In some embodiments, the antenna panels 526 may receive a transmission from the AN 504 by receive-beamforming signals received by a plurality of antennas / antenna elements of the one or more antenna panels 526. A UE transmission may be established by and via the protocol processing circuitry 514, digital baseband circuitry 516, transmit circuitry 518, RF circuitry 522, RFFE 524, and antenna panels 526. In some embodiments, the transmit components of the UE 504 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 526. Similar to the UE 502, the AN 504 may include a host platform 528 coupled with a modem platform 530. The host platform 528 may include application processing circuitry 532 coupled with protocol processing circuitry 534 of the modem platform 530. The modem platform may further include digital baseband circuitry 536, transmit circuitry 538, receive circuitry 540, RF circuitry 542, RFFE circuitry 544, and antenna panels 546. The components of the AN 504 may be similar to and substantially interchangeable with like-named components of the UE 502. In addition to performing data transmission / reception as described above, the components of the AN 508 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling. Figure 6 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 6 shows a diagrammatic representation of hardware resources 600 including one or more processors (or processor cores) 610, one or more memory / storage devices 620, and one or more communication resources 630, each of which may be communicatively coupled via a bus 640 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 602 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 600. The processors 610 may include, for example, a processor 612 and a processor 614. The processors 610 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof. The memory / storage devices 620 may include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 620 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc. The communication resources 630 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 604 or one or more databases 606 or other network elements via a network 608. For example, the communication resources 630 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components. Instructions 650 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 610 to perform any one or more of the methodologies discussed herein. The instructions 650 may reside, completely or partially, within at least one of the processors 610 (e.g., within the processor’s cache memory), the memory / storage devices 620, or any suitable combination thereof. Furthermore, any portion of the instructions 650 may be transferred to the hardware resources 600 from any combination of the peripheral devices 604 or the databases 606. Accordingly, the memory of processors 610, the memory / storage devices 620, the peripheral devices 604, and the databases 606 are examples of computer-readable and machine-readable media. Figure 7 illustrates a network 700 in accordance with various embodiments. The network 700 may operate in a matter consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 700 may operate concurrently with network 400. For example, in some embodiments, the network 700 may share one or more frequency or bandwidth resources with network 400. As one specific example, a UE (e.g., UE 702) may be configured to operate in both network 700 and network 400. Such configuration may be based on a UE including circuitry configured for communication with frequency and bandwidth resources of both networks 400 and 700. In general, several elements of network 700 may share one or more characteristics with elements of network 400. For the sake of brevity and clarity, such elements may not be repeated in the description of network 700. The network 700 may include a UE 702, which may include any mobile or non-mobile computing device designed to communicate with a RAN 708 via an over-the-air connection. The UE 702 may be similar to, for example, UE 402. The UE 702 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc. Although not specifically shown in Figure 7, in some embodiments the network 700 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in Figure 7, the UE 702 may be communicatively coupled with an AP such as AP 406 as described with respect to Figure 4. Additionally, although not specifically shown in Figure 7, in some embodiments the RAN 708 may include one or more ANss such as AN 408 as described with respect to Figure 4. The RAN 708 and / or the AN of the RAN 708 may be referred to as a base station (BS), a RAN node, or using some other term or name. The UE 702 and the RAN 708 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features such as communication in a terahertz (THz) or sub-THz bandwidth, or joint communication and sensing. As used herein, the term “joint communication and sensing” may refer to a system that allows for wireless communication as well as radar-based sensing via various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communication in the 80 GHz and above frequency ranges. Such frequency ranges may additionally or alternatively be referred to as “millimeter wave” or “mmWave” frequency ranges. The RAN 708 may allow for communication between the UE 702 and a 6G core network (CN) 710. Specifically, the RAN 708 may facilitate the transmission and reception of data between the UE 702 and the 6G CN 710. The 6G CN 710 may include various functions such as NSSF 450, NEF 452, NRF 454, PCF 456, UDM 458, AF 460, SMF 446, and AUSF 442. The 6G CN 710 may additional include UPF 448 and DN 436 as shown in Figure 7. Additionally, the RAN 708 may include various additional functions that are in addition to, or alternative to, functions of a legacy cellular network such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 724 and a Compute Service Function (Comp SF) 736. The Comp CF 724 and the Comp SF 736 may be parts or functions of the Computing Service Plane. Comp CF 724 may be a control plane function that provides functionalities such as management of the Comp SF 736, computing task context generation and management (e.g., create, read, modify, delete), interaction with the underlying computing infrastructure for computing resource management, etc.. Comp SF 736 may be a user plane function that serves as the gateway to interface computing service users (such as UE 702) and computing nodes behind a Comp SF instance. Some functionalities of the Comp SF 736 may include: parse computing service data received from users to compute tasks executable by computing nodes; hold service mesh ingress gateway or service API gateway; service and charging policies enforcement; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 736 instance may serve as the user plane gateway for a cluster of computing nodes. A Comp CF 724 instance may control one or more Comp SF 736 instances. Two other such functions may include a Communication Control Function (Comm CF) 728 and a Communication Service Function (Comm SF) 738, which may be parts of the Communication Service Plane. The Comm CF 728 may be the control plane function for managing the Comm SF 738, communication sessions creation / configuration / releasing, and managing communication session context. The Comm SF 738 may be a user plane function for data transport. Comm CF 728 and Comm SF 738 may be considered as upgrades of SMF 446 and UPF 448, which were described with respect to a 5G system in Figure 4. The upgrades provided by the Comm CF 728 and the Comm SF 738 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, SMF 446 and UPF 448 may still be used. Two other such functions may include a Data Control Function (Data CF) 722 and Data Service Function (Data SF) 732 may be parts of the Data Service Plane. Data CF 722 may be a control plane function and provides functionalities such as Data SF 732 management, Data service creation / configuration / releasing, Data service context management, etc. Data SF 732 may be a user plane function and serve as the gateway between data service users (such as UE 702 and the various functions of the 6G CN 710) and data service endpoints behind the gateway. Specific functionalities may include include: parse data service user data and forward to corresponding data service endpoints, generate charging data, report data service status. Another such function may be the Service Orchestration and Chaining Function (SOCF) 720, which may discover, orchestrate and chain up communication / computing / data services provided by functions in the network. Upon receiving service requests from users, SOCF 720 may interact with one or more of Comp CF 724, Comm CF 728, and Data CF 722 to identify Comp SF 736, Comm SF 738, and Data SF 732 instances, configure service resources, and generate the service chain, which could contain multiple Comp SF 736, Comm SF 738, and Data SF 732 instances and their associated computing endpoints. Workload processing and data movement may then be conducted within the generated service chain. The SOCF 720 may also responsible for maintaining, updating, and releasing a created service chain. Another such function may be the service registration function (SRF) 714, which may act as a registry for system services provided in the user plane such as services provided by service endpoints behind Comp SF 736 and Data SF 732 gateways and services provided by the UE 702. The SRF 714 may be considered a counterpart of NRF 454, which may act as the registry for network functions. Other such functions may include an evolved service communication proxy (eSCP) and service infrastructure control function (SICF) 726, which may provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G with user plane service communication proxy capabilities being added. The eSCP is therefore expressed in two parts: eCSP-C 712 and eSCP-U 734, for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 726 may control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc. Another such function is the AMF 744. The AMF 744 may be similar to 444, but with additional functionality. Specifically, the AMF 744 may include potential functional repartition, such as move the message forwarding functionality from the AMF 744 to the RAN 708. Another such function is the service orchestration exposure function (SOEF) 718. The SOEF may be configured to expose service orchestration and chaining services to external users such as applications. The UE 702 may include an additional function that is referred to as a computing client service function (comp CSF) 704. The comp CSF 704 may have both the control plane functionalities and user plane functionalities, and may interact with corresponding network side functions such as SOCF 720, Comp CF 724, Comp SF 736, Data CF 722, and / or Data SF 732 for service discovery, request / response, compute task workload exchange, etc. The Comp CSF 704 may also work with network side functions to decide on whether a computing task should be run on the UE 702, the RAN 708, and / or an element of the 6G CN 710. The UE 702 and / or the Comp CSF 704 may include a service mesh proxy 706. The service mesh proxy 706 may act as a proxy for service-to-service communication in the user plane. Capabilities of the service mesh proxy 706 may include one or more of addressing, security, load balancing, etc. EXAMPLEPROCEDURESIn some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 4-7, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in Figure 8. For example, the process may include, at 801, receiving configuration information for channel state information (CSI) resources, wherein a first CSI resource of the CSI resources spans across a physical resource block (PRB) boundary in the frequency domain and / or across a slot boundary in the time domain. At 802, the process may further include generating CSI based on measurements of a CSI – reference signal (CSI-RS) in the respective CSI resources. At 803, the process may further include sending a CSI report with the CSI. The CSI may include, for example, a RI, a PMI, and / or a CQI. Figure 9 illustrates another example process in accordance with various embodiments. In some embodiments, the process of Figure 9 may be performed by a gNB or a portion thereof. At 901, the process may include encoding, for transmission to a user equipment (UE), configuration information for channel state information (CSI) resources, wherein a first CSI resource of the CSI resources spans across a physical resource block (PRB) boundary in the frequency domain and / or across a slot boundary in the time domain. At 902, the process may further include receiving, from the UE, a CSI report with CSI based on the CSI resources. The CSI may include, for example, a RI, a PMI, and / or a CQI. Figure 10 illustrates another example process in accordance with various embodiments. Specifically, Figure 10 depicts a process to be performed by a user equipment (UE), one or more elements of a UE, and / or one or more electronic devices that include and / or implement a UE. The process may include identifying, at 1001, channel state information (CSI)-reference signal (RS) information received from greater than 32 CSI-RS ports of a base station of a cellular network; performing, at 1002, one or more CSI measurements on CSI-RS information received from a subset of the greater than 32 CSI-RS ports, wherein the subset of CSI-RS ports includes 32 or fewer CSI-RS ports; and generating, at 1003 based on the CSI measurements, a CSI report that includes a CSI value related to the greater than 32 CSI-RS ports. Another such process is depicted in Figure 11. The process of Figure 11 may include or relate to a process to be performed by a base station, one or more elements of a base station, and / or one or more electronic devices that include and / or implement a base station. The process may include transmitting, at 1101, channel state information (CSI)-reference signal (RS) information from greater than 32 CSI-RS ports of the base station; and identifying, at 1102 from a UE, a CSI report that includes a CSI value related to the greater than 32 CSI-RS ports, wherein the CSI value is based on one or more CSI measurements performed by the UE on CSI-RS information received from a subset of the greater than 32 CSI-RS ports, wherein the subset of CSI-RS ports includes 32 or fewer CSI-RS ports. For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section. EXAMPLES Example 1 may include the method of channel state information (CSI) measurements and reporting at the user equipment (UE) with more than 32 CSI-RS ports, wherein the method includes: Configuring CSI measurements and reporting at the UE; Measuring CSI-RS (CSI Reference Signals) on K CSI-RS resources; and Calculating and reporting of CSI based on measured CSI-RS, wherein CSI-RS ports across all the configured CSI-RS resources are used jointly for Rank Indicator (RI), Precoding Matrix Indicator and / or Channel Quality Indicator (CQI). Example 2 may include the method of example 1 and / or some other example herein, wherein a CSI-RS resource spans across PRB boundary in frequency domain. Example 3 may include the method of example 2 and / or some other example herein, wherein the UE is configured with bitmap [b(N-1),…,b(0)] indicating initial subcarrier for L subcarriers of CSI-RS, bit b(n) indicates CSI-RS in L last subcarriers of PRB A, bit b(n+1) indicates CSI-RS in L first subcarriers of PRB A+1. Example 4 may include the method of example 3 and / or some other example herein, wherein CSI-RS resource is repeated every 2N subcarriers and M PRBs. Example 5 may include the method of example 2 and / or some other example herein, wherein offset of O subcarriers is indicated per CSI-RS or per group of CSI-RS resource(s), initial subcarrier of a CSI-RS transmission is shifted by O subcarriers. Example 6 may include the method of example 2 and / or some other example herein, wherein a CSI-RS resource is repeated in frequency domain every 1 / ρ PRB and 1 / ρ is not an integer, where ρ is configured via higher layers. Example 7 may include the method of example 1 and / or some other example herein, wherein a CSI-RS resource spans across slot boundary in time domain, first initial symbol for a CSI- RS resource is configured in the first slot l(1) < 14, second initial symbol for the CSI-RS resource is configured in the second slot l(2) ≥ 14. Example 8 may include the method of example 1 and / or some other example herein, wherein number of ports across K CSI-RS resources K·P is larger than the number of CSI-RS ports used for RI, PMI and CQI PPMI > K·P. Example 9 may include the method of example 8 and / or some other example herein, wherein last K·P - PPMI ports are not measured by the UE for the CSI. Example 10 may include the method of example 1 and / or some other example herein, wherein number of ports P(i) is configured separately per CSI-RS resource i ∊ {1,2,…K}. The total number of CSI-RS resources used for RI, PMI and CQI PPMI is sum of P(i) for i ∊ {1,2,…K}. Example 11 may include the method of example 1 and / or some other example herein, wherein slot offset for aperiodic CSI-RS KAis configured separately per CSI-RS resource or per group of CSI-RS resources. Example 12 may include the method of example 1 and / or some other example herein, wherein the CSI is not required to update the CSI report if the number of occupied CSI processing units is larger than reported as capability. Example 13 may include the method of example 12 and / or some other example herein, wherein number of CPUs occupied by the CSI report is ceil(PPMI / T), where ceil() is ceil function, PPMI the number of CSI-RS ports used for RI, PMI and CQI, T is fixed or indicated by the UE as capability. Example 14 may include the method of example 12 and / or some other example herein, wherein number of CPUs occupied by a CSI report is T·K + U or ceil(T·K + U), T and / or U is fixed in specification or T and / or U is reported by the UE as capability. Example 15 may include the method of example 12 and / or some other example herein, wherein, if UE is configured with multiple CSI sub-configurations, the number of CPUs occupied by the CSI report is a sum of number of CPU occupied by the sub-configurations. Example 16 may include the method of example 1 and / or some other example herein, wherein the UE is not expected to have more active CSI-RS resources than reported as capability. Example 17 may include the method of example 16 and / or some other example herein, wherein K CSI-RS resources are counted as 1 active CSI-RS resource. Example 18 may include the method of example 16 and / or some other example herein, wherein K CSI-RS resources are counted as ceil(PPMI / B) active CSI-RS resources or ceil(K / B) active CSI-RS resources, where ceil() is ceil function, PPMI the number of CSI-RS ports used for RI, PMI and CQI B is fixed in specification or B is reported by the UE as capability. Example 19 may include a method of a user equipment (UE), the method comprising: receiving configuration information for channel state information (CSI) resources, wherein a first CSI resource of the CSI resources spans across a physical resource block (PRB) boundary in the frequency domain and / or across a slot boundary in the time domain; generating CSI based on measurements of a CSI – reference signal (CSI-RS) in the respective CSI resources; and sending a CSI report with the CSI. Example 20 may include the method of example 19 and / or some other example herein, wherein the CSI includes a Rank Indicator (RI), a Precoding Matrix Indicator (PMI), and / or a Channel Quality Indicator (CQI). Example 21 may include the method of example 19-20 and / or some other example herein, wherein the CSI resources correspond to more than 32 CSI-RS ports. Example 22 may include the method of example 19-21 and / or some other example herein, wherein the configuration information includes a bitmap to indicate an initial subcarrier for the first CSI resource. Example 23 may include the method of example 22 and / or some other example herein, wherein the bitmap includes N bits, and wherein the first CSI-RS resource is repeated every 2N subcarriers. Example 24 may include the method of example 23 and / or some other example herein, wherein the CSI-RS resource is further repeated every M PRBs. Example 25 may include the method of example 19-24 and / or some other example herein, wherein the configuration information includes an offset of one or more subcarriers for the first CSI-RS resource and / or a group of CSI-RS resources, and wherein an initial subcarrier of the first CSI-RS resource is shifted by the offset. Example 26 may include the method of example 19-25 and / or some other example herein, wherein the first CSI-RS resource is repeated in frequency domain every 1 / ρ PRB, wherein 1 / ρ is not an integer. Example 27 may include the method of example 26 and / or some other example herein, wherein the configuration information indicates the value of ρ. Example 28 may include the method of example 19-27 and / or some other example herein, wherein the first CSI-RS resource spans across the slot boundary in the time domain, wherein a first initial symbol for the first CSI-RS resource is configured in a first slot l(1) < 14, and a second initial symbol for the first CSI-RS resource is configured in the second slot l(2) ≥ 14. Example 29 may include the method of example 19-28 and / or some other example herein, wherein a number of ports across the CSI-RS resources is larger than a number of CSI-RS ports used to generate the CSI. Example 30 may include the method of example 19-29 and / or some other example herein, wherein the configuration information indicates a respective number of ports for individual CSI-RS resources. Example 31 may include the method of example 19-29 and / or some other example herein, wherein the configuration information indicates a respective slot offset for aperiodic CSI-RS for individual CSI-RS resources. Example 32 may include the method of example 19-31 and / or some other example herein, wherein a number of CSI processing units (CPUs) occupied by the CSI report is ceil(PPMI / T), where ceil() is ceiling function, PPMI the number of CSI-RS ports used for the CSI, and T is fixed or indicated by the UE in capability information. Example 33 may include the method of example 19-31 and / or some other example herein, wherein a number of CSI processing units (CPUs) occupied by the CSI report is T·K + U or ceil(T·K + U), wherein K is a number of the CSI resources used in the CSI report, and T and / or U is predefined or indicated by the UE in capability information. Example 34 may include the method of example 19-33 and / or some other example herein, further comprising encoding capability information for transmission, wherein the capability information indicates a number of active CSI-RS resources that are supported by the UE. Example 35 may include a method of a gNodeB (gNB), the method comprising: encoding, for transmission to a user equipment (UE), configuration information for channel state information (CSI) resources, wherein a first CSI resource of the CSI resources spans across a physical resource block (PRB) boundary in the frequency domain and / or across a slot boundary in the time domain; and receiving, from the UE, a CSI report with CSI based on the CSI resources. Example 36 may include the method of example 35 and / or some other example herein, wherein the CSI includes a Rank Indicator (RI), a Precoding Matrix Indicator (PMI), and / or a Channel Quality Indicator (CQI). Example 37 may include the method of example 35-36 and / or some other example herein, wherein the CSI resources correspond to more than 32 CSI-RS ports. Example 38 may include the method of example 35-37 and / or some other example herein, wherein the configuration information includes a bitmap to indicate an initial subcarrier for the first CSI resource. Example 39 may include the method of example 38 and / or some other example herein, wherein the bitmap includes N bits, and wherein the first CSI-RS resource is repeated every 2N subcarriers. Example 40 may include the method of example 39 and / or some other example herein, wherein the CSI-RS resource is further repeated every M PRBs. Example 41 may include the method of example 35-40 and / or some other example herein, wherein the configuration information includes an offset of one or more subcarriers for the first CSI-RS resource and / or a group of CSI-RS resources, and wherein an initial subcarrier of the first CSI-RS resource is shifted by the offset. Example 42 may include the method of example 35-41 and / or some other example herein, wherein the first CSI-RS resource is repeated in frequency domain every 1 / ρ PRB, wherein 1 / ρ is not an integer. Example 43 may include the method of example 42 and / or some other example herein, wherein the configuration information indicates the value of ρ. Example 44 may include the method of example 35-43 and / or some other example herein, wherein the first CSI-RS resource spans across the slot boundary in the time domain, wherein a first initial symbol for the first CSI-RS resource is configured in a first slot l(1) < 14, and a second initial symbol for the first CSI-RS resource is configured in the second slot l(2) ≥ 14. Example 45 may include the method of example 35-44 and / or some other example herein, wherein a number of ports across the CSI-RS resources is larger than a number of CSI-RS ports used to generate the CSI. Example 46 may include the method of example 35-45 and / or some other example herein, wherein the configuration information indicates a respective number of ports for individual CSI-RS resources. Example 47 may include the method of example 35-46 and / or some other example herein, wherein the configuration information indicates a respective slot offset for aperiodic CSI-RS for individual CSI-RS resources. Example 48 may include the method of example 35-47 and / or some other example herein, wherein a number of CSI processing units (CPUs) occupied by the CSI report is ceil(PPMI / T), where ceil() is ceiling function, PPMI the number of CSI-RS ports used for the CSI, and T is fixed or indicated by the UE in capability information. Example 49 may include the method of example 35-47 and / or some other example herein, wherein a number of CSI processing units (CPUs) occupied by the CSI report is T·K + U or ceil(T·K + U), wherein K is a number of the CSI resources used in the CSI report, and T and / or U is predefined or indicated by the UE in capability information. Example 50 may include the method of example 35-49 and / or some other example herein, further comprising encoding capability information for transmission, wherein the capability information indicates a number of active CSI-RS resources that are supported by the UE. Example 51 may include the method of example 35-50 and / or some other example herein, further comprising transmitting a CSI-RS in the respective CSI-RS resources. Example 52 may include a method to be performed by a user equipment (UE), one or more elements of a UE, and / or one or more electronic devices that include and / or implement a UE, wherein the method comprises: identifying channel state information (CSI)-reference signal (RS) information received from greater than 32 CSI-RS ports of a base station of a cellular network; performing one or more CSI measurements on CSI-RS information received from a subset of the greater than 32 CSI-RS ports, wherein the subset of CSI-RS ports includes 32 or fewer CSI-RS ports; and generating, based on the CSI measurements, a CSI report that includes a CSI value related to the greater than 32 CSI-RS ports. Example 53 may include the method of example 52, and / or one or more other examples herein, wherein the greater than 32 CSI-RS ports cross a physical resource block (PRB) boundary in a frequency domain. Example 54 may include the method of any of examples 52-53, and / or one or more other examples herein, wherein the greater than 32 CSI-RS ports cross a slot boundary in a time domain. Example 55 may include the method of any of examples 52-54, and / or one or more other examples herein, wherein the CSI value is a rank indicator (RI) value related to the greater than 32 CSI-RS ports. Example 56 may include the method of any of examples 52-55, and / or one or more other examples herein, wherein the CSI value is a precoding matrix indicator (PMI) value related to the greater than 32 CSI-RS ports. Example 57 may include the method of any of examples 52-56, and / or one or more other examples herein, wherein the CSI value is a channel quality indicator (CQI) value related to the greater than 32 CSI-RS ports. Example 58 may include the method of any of examples 52-57, and / or one or more other examples herein, wherein the CSI-RS information includes respective RSs transmitted from respective CSI-RS ports of the greater than 32 CSI-RS portsgreater than 32. Example 59 may include the method of any of examples 52-58, and / or one or more other examples herein, further comprising identifying, by the UE based on a number of the greater than 32 CSI-RS ports, a number of occupied CSI processing units (CPUs) that are to perform the one or more CSI measurements or generate the CSI report. Example 60 may include the method of example 59, and / or one or more other examples herein, wherein the method further comprises: identifying, by the UE, a previous CSI report; and identifying, based on the number of occupied CPUs, whether generation of the CSI report includes updating the previous CSI report. Example 61 may include the method of any of examples 52-60, and / or one or more other examples herein, further comprising: identifying a number of active CSI resources related to the greater than 32 CSI-RS ports; and identifying, based on the number of active CSI resources, whether generation of the CSI report includes updating the previous CSI report. Example 62 may include a method to be performed by a base station, one or more elements of a base station, and / or one or more electronic devices that include and / or implement a base station, wherein the method comprises: transmitting channel state information (CSI)-reference signal (RS) information from greater than 32 CSI-RS ports of the base station; and identifying, from a UE, a CSI report that includes a CSI value related to the greater than 32 CSI-RS ports, wherein the CSI value is based on one or more CSI measurements performed by the UE on CSI-RS information received from a subset of the greater than 32 CSI-RS ports, wherein the subset of CSI-RS ports includes 32 or fewer CSI-RS ports. Example 63 may include the method of example 62, and / or one or more other examples herein, wherein the greater than 32 CSI-RS ports cross a physical resource block (PRB) boundary in a frequency domain. Example 64 may include the method of any of examples 62-63, and / or one or more other examples herein, wherein the greater than 32 CSI-RS ports cross a slot boundary in a time domain. Example 65 may include the method of any of examples 62-64, and / or one or more other examples herein, wherein the CSI value is a rank indicator (RI) value related to the greater than 32 CSI-RS ports. Example 66 may include the method of any of examples 62-65, and / or one or more other examples herein, wherein the CSI value is a precoding matrix indicator (PMI) value related to the greater than 32 CSI-RS ports. Example 67 may include the method of any of examples 62-66, and / or one or more other examples herein, wherein the CSI value is a channel quality indicator (CQI) value related to the greater than 32 CSI-RS ports. Example 68 may include the method of any of examples 62-67, and / or one or more other examples herein, wherein the CSI-RS information includes respective RSs transmitted from respective CSI-RS ports of the greater than 32 CSI-RS ports of the base station. Example 69 may include the method of any of examples 62-68, and / or one or more other examples herein, further comprising identifying, by the base station based on a number of the greater than 32 CSI-RS ports, a number of occupied CSI processing units (CPUs) that are to facilitate transmission of the CSI-RS information from the greater than 32 CSI-RS ports. Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-69, and / or any other method or process described herein. Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-69, and / or any other method or process described herein. Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-69, and / or any other method or process described herein. Example Z04 may include a method, technique, or process as described in or related to any of examples 1-69, and / or portions or parts thereof. Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-69, and / or portions thereof. Example Z06 may include a signal as described in or related to any of examples 1-69, or portions or parts thereof. Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-69, and / or portions or parts thereof, or otherwise described in the present disclosure. Example Z08 may include a signal encoded with data as described in or related to any of examples 1-69, and / or portions or parts thereof, or otherwise described in the present disclosure. Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-69, and / or portions or parts thereof, or otherwise described in the present disclosure. Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-69, and / or portions thereof. Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-69, and / or portions thereof. Example Z12 may include a signal in a wireless network as shown and described herein. Example Z13 may include a method of communicating in a wireless network as shown and described herein. Example Z14 may include a system for providing wireless communication as shown and described herein. Example Z15 may include a device for providing wireless communication as shown and described herein. Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Claims

CLAIMS 1. An apparatus for use in a user equipment (UE), wherein the apparatus comprises: memory to store channel state information (CSI)-reference signal (RS) information received from greater than 32 CSI-RS ports of a base station of a cellular network; and one or more processors configured to: perform one or more CSI measurements on CSI-RS information received from a subset of the greater than 32 CSI-RS ports, wherein the subset of CSI-RS ports includes 32 or fewer CSI-RS ports; and generate, based on the CSI measurements, a CSI report that includes a CSI value related to the greater than 32 CSI-RS ports.

2. The apparatus of claim 1, wherein the greater than 32 CSI-RS ports cross a physical resource block (PRB) boundary in a frequency domain.

3. The apparatus of claim 1, wherein the greater than 32 CSI-RS ports cross a slot boundary in a time domain.

4. The apparatus of claim 1, wherein the CSI value is a rank indicator (RI) value related to the greater than 32 CSI-RS ports.

5. The apparatus of claim 1, wherein the CSI value is a precoding matrix indicator (PMI) value related to the greater than 32 CSI-RS ports.

6. The apparatus of claim 1, wherein the CSI value is a channel quality indicator (CQI) value related to the greater than 32 CSI-RS ports.

7. The apparatus of claim 1, wherein the CSI-RS information includes respective RSs transmitted from respective CSI-RS ports of the greater than 32 CSI-RS portsgreater than 32.

8. The apparatus of any of claims 1-7, wherein the one or more processors are further configured to identify, based on a number of the greater than 32 CSI-RS ports, a number of occupied CSI processing units (CPUs) that are to perform the one or more CSI measurements or generate the CSI report.

9. The apparatus of claim 8, wherein the one or more processors are further configured to: identify a previous CSI report; and identify, based on the number of occupied CPUs, whether generation of the CSI report includes updating the previous CSI report.

10. The apparatus of any of claims 1-7, further comprising: identifying a number of active CSI resources related to the greater than 32 CSI-RS ports; and identifying, based on the number of active CSI resources, whether generation of the CSI report includes updating the previous CSI report.

11. One or more computer-readable media comprising instructions that, upon execution of the instructions by one or more processors of an electronic device, are to cause a base station to: transmit channel state information (CSI)-reference signal (RS) information from greater than 32 CSI-RS ports of the base station; and identify, from a UE, a CSI report that includes a CSI value related to the greater than 32 CSI-RS ports, wherein the CSI value is based on one or more CSI measurements performed by the UE on CSI-RS information received from a subset of the greater than 32 CSI-RS ports, wherein the subset of CSI-RS ports includes 32 or fewer CSI-RS ports.

12. The one or more computer-readable media of claim 11, wherein the greater than 32 CSI-RS ports cross a physical resource block (PRB) boundary in a frequency domain.

13. The one or more computer-readable media of claim 11, wherein the greater than 32 CSI-RS ports cross a slot boundary in a time domain.

14. The one or more computer-readable media of claim 11, wherein the CSI value is a rank indicator (RI) value related to the greater than 32 CSI-RS ports, a precoding matrix indicator (PMI) value related to the greater than 32 CSI-RS ports, or a channel quality indicator (CQI) value related to the greater than 32 CSI-RS ports.

15. The one or more computer-readable media of any of claims 11-14, wherein the CSI- RS information includes respective RSs transmitted from respective CSI-RS ports of the greater than 32 CSI-RS ports of the base station.

16. The one or more computer-readable media of any of claims 11-14, wherein the instructions are further to cause the base station to identify, based on a number of the greater than 32 CSI-RS ports, a number of occupied CSI processing units (CPUs) that are to facilitate transmission of the CSI-RS information from the greater than 32 CSI-RS ports.

17. One or more computer-readable media comprising instructions that, upon execution of the instructions by one or more processors of an electronic device, are to cause a user equipment (UE) to: identify channel state information (CSI)-reference signal (RS) information received from greater than 32 CSI-RS ports of a base station of a cellular network; perform one or more CSI measurements on CSI-RS information received from a subset of the greater than 32 CSI-RS ports, wherein the subset of CSI-RS ports includes 32 or fewer CSI-RS ports; and generate, based on the CSI measurements, a CSI report that includes a CSI value related to the greater than 32 CSI-RS ports.

18. The one or more computer-readable media of claim 17, wherein the greater than 32 CSI-RS ports cross a physical resource block (PRB) boundary in a frequency domain or a slot boundary in a time domain.

19. The one or more computer-readable media of any of claims 17-18, wherein the instructions are further to cause the UE to identify, based on a number of the greater than 32 CSI-RS ports, a number of occupied CSI processing units (CPUs) that are to perform the one or more CSI measurements or generate the CSI report.

20. The one or more computer-readable media of any of claims 17-18, wherein the instructions are further to cause the UE to: identify a number of active CSI resources related to the greater than 32 CSI-RS ports; andidentify, based on the number of active CSI resources, whether generation of the CSI report includes updating the previous CSI report.

Images