Channel state information (CSI) measurement for large antenna arrays

Abstract

Various embodiments herein provide techniques related to the transmission of CSI-RS information by a base station on more than 32 Channel State Information (CSI)-Reference Signal (RS) ports. A User Equipment (UE) can perform one or more CSI measurements on CSI-RS information received from a subset of more than 32 CSI-RS ports, wherein the subset comprises 32 or fewer CSI-RS ports. The UE can then generate a CSI report based on the CSI measurements, the CSI report including CSI values ​​associated with the more than 32 CSI-RS ports; other embodiments may be described and / or claimed.

Description

Cross-reference to related applications

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 550,526, filed February 6, 2024, and U.S. Provisional Patent Application No. 63 / 554,818, filed February 16, 2024. Background Technology

[0002] Various embodiments can typically relate to the field of wireless communications. Attached Figure Description

[0003] The embodiments will be readily understood from the following detailed description taken in conjunction with the accompanying drawings. For ease of description, similar reference numerals denote similar structural elements. In the figures, embodiments are illustrated by way of example rather than limitation.

[0004] Figure 1 Examples of Channel State Information (CSI)-Reference Signal (RS) blocks according to various embodiments are depicted.

[0005] Figure 2a and Figure 2b (Collectively referred to as Figure 2) depicts examples of CSI-RS according to various embodiments.

[0006] Figure 3a , Figure 3b , Figure 3c , Figure 3d , Figure 3e and Figure 3f (Collectively referred to as Figure 3) illustrates examples of different CSI-RS resource element (RE) mapping options according to various embodiments.

[0007] Figure 4 Wireless networks according to various embodiments are schematically illustrated.

[0008] Figure 5 The components of a wireless network according to various embodiments are schematically illustrated.

[0009] Figure 6 These are block diagrams based on some example embodiments, illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more methods discussed herein.

[0010] Figure 7 The diagram illustrates networks according to various embodiments.

[0011] Figure 8 Example flows for practicing the various embodiments discussed herein are described.

[0012] Figure 9Another example flow is described for practicing the various embodiments discussed herein.

[0013] Figure 10 Another example flow is described for practicing the various embodiments discussed herein.

[0014] Figure 11 Another example flow is described for the practice of the various embodiments described herein. Detailed Implementation

[0015] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details such as particular structures, architectures, interfaces, technologies, etc., are set forth for purposes of explanation and not limitation in order to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art, who benefit from this disclosure, that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrases “A or B” and “A / B” mean (A), (B), or (A and B). Unless otherwise used herein, terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR 21.905 v16.0.0 (2019-06).

[0016] The performance of Physical Downlink Shared Channel (PDSCH) transmission in fifth-generation (5G) New Radio (NR) cellular communication systems can depend on the availability of CSI at base stations such as gNodeBs (gNBs). CSI feedback (e.g., as can be reported by user equipment (UEs)) can be used by the gNB to derive CSI.

[0017] Advances in active antenna array technology have enabled the fabrication of antenna arrays with a large number of antenna ports for digital beamforming and spatial multiplexing of data streams. Traditional commercial gNB antenna arrays can support at least 64 antenna ports for transmission and reception. However, the CSI in the traditional 5G NR physical layer 3GPP specification can be optimized for a smaller number of antenna ports. Specifically, for gNBs with more than 32 antenna ports, optimized CSI-RS configurations and precoding matrix indicator (PMI) codebooks may not be available in traditional specifications.

[0018] The various embodiments described herein provide techniques for precoded CSI-RS configurations with more than 32 CSI-RS ports, and may also relate to UE CSI processing aspects for such configurations. Aspects of the various embodiments may be incorporated into 5G NR and / or future physical layer specifications, such as 3GPP Technology Standards (TS) 38.214, 38.213 and / or other standards.

[0019] Implementations may include CSI-RS resource configuration, CSI processing unit (CPU) occupancy rules, and active CSI-RS resource counts for an enhanced Type II precoding matrix indicator (PMI) codebook for coherent joint transport (CJT).

[0020] More generally, embodiments may provide enhancements to 5G NR physical layer specifications that support or describe CSI reference signal (CSI-RS) configurations to support CSI-RS configurations and resource mappings for precoding with more than 32 CSI-RS ports. Embodiments may also relate to UE CSI processing aspects for such configurations, including CSI processing unit (CPU) occupancy and active CSI-RS resource counts.

[0021] 1.1 Channel State Information Feedback CSI feedback can be used in 5G NR (New Radio) systems to assist in scheduling, link adaptation, precoding, and spatial multiplexing operations of PDSCH transmissions. CSI reports can be transmitted from the UE to the gNB via the Physical Uplink Control Channel (PUCCH) and / or the Physical Uplink Shared Channel (PUSCH).

[0022] The following are three sample components of a CSI report: • CSI-RS Resource Indicator (CRI): Indicates the CSI-RS resource selected by the UE and used to calculate other CSI components in the CSI report; • Rank Indicator (RI): Contains information about the number of spatial layers (ranks) recommended by the UE for PDSCH; • PMI: Contains information about the precoding matrix recommended by the UE for PDSCH; • Channel Quality Indicator (CQI): Contains information about modulation and coding schemes recommended by the UE for the PDSCH.

[0023] For a given CSI report, the UE is configured with K ≥ 1 CSI-RS resources, each CSI-RS resource corresponding to P ≥ 1 CSI-RS ports. To determine the CRI / RI / PMI / CQI used for CSI reporting, the UE measures the channels for the configured CSI-RS resources and CSI-RS ports.

[0024] For the PMI codebook supported by NR, except for the PMI codebook used for CJT (coherent joint transmission), when K=1, P {2,4,8,12,16,24,32}; when K=2, P {2,4,8,12,16}; when 2<K≤8, P {2,4,8}. The UE selects a CSI-RS resource, and determines RI, PMI and CQI by performing channel measurement using the selected CSI-RS resource. The index of the selected CSI-RS resource corresponds to the reported CRI.

[0025] For the PMI codebook for CJT, when K {1,2,3,4}, P {4,8,12,16,24,32}. The UE reports RI, PMI and CQI by using channels measured for all configured CSI-RS resources.

[0026] CSI-RS measurement A CSI-RS block is defined as a set of indexes of subcarriers and OFDM (Orthogonal Frequency Division Multiplexing) symbols . Therefore, for a given CSI-RS block, the mapping of CSI-RS resource elements (RE) within a PRB (Physical Resource Block) is determined by the starting subcarrier of the CSI-RS block and the index of the OFDM symbol determined. Figure 1 Some exemplary time-frequency code-domain CSI-RS blocks are illustrated.

[0027] Higher layer configuration of a CSI-RS resource may include one or more of the following parameters.

[0028] - frequencyDomainAllocation - Comprises a bitmap [b5,...,b0], which indicates subcarrier indexes used for a CSI-RS block , wherein , f(i) is the bit number of the i-th bit set to 1 in the bitmap.

[0029] - nrofPorts - Number of ports per CSI-RS resource (P) - firstOFDMSymbolInTimeDomain - Starting orthogonal frequency division multiplexing (OFDM) symbol of a first CSI-RS RE block - firstOFDMSymbolInTimeDomain2 - Starting OFDM symbol of a second CSI-RS RE block - cdm-type- Code Division Multiplexing (CDM) type ('no CDM','fd-CDM2','cdm4-FD2-TD2','cdm8-FD2-TD4') - density - CSI-RS density (D) is given by the number of CSI-RS REs per CSI-RS port in each physical resource block (PRB). - freqBand - Initial PRB index assigned to CSI-RS (PRB) init ) and the number of PRBs (PRB) num ) - periodicityAndOffset -Period (T) and slot offset (K) of periodic CSI-RS P ) - aperiodicTriggeringOffset - Slot offset of non-periodic CSI-RS (K A ) The efficiency of CSI-RS measurements can depend on the temporal and frequency distances between CSI-RS ports processed together. Traditional NR specifications, including CSI-RS RE mapping, are optimized for processing up to 32 ports together. To further increase the number of CSI-RS ports processed in a single PMI report to 128, a configuration of multiple CSI-RS resources can be used. Specifically, different rows of the precoding matrix corresponding to the PMI can be mapped to different CSI-RS ports of different CSI-RS resources.

[0030] In one embodiment, the CSI-RS resource mapping configuration extends across the PRB boundary in the frequency domain. Bitmap for CSI-RS RE mapping in the frequency domain [b] N-1 The number of bits in [b0, ..., b0] can be expanded to support N>6, and the number of consecutive subcarriers for which the bitmap is applied is expanded from 1 to 2N. This pattern can be repeated every 2N subcarriers and M PRBs. If for n>(6·Z-1), bits b0... n If set to 1, the starting subcarrier index for the CSI-RS block (2·n) is located in the Zth PRB closest to the PRB used for CSI-RS mapping. M is a natural number satisfying the following equation: mod(6·M,N)=0, where mod() is the modulo operation. The CSI-RS density is 6 / N.

[0031] Figure 2a An example with M=2 was depicted, and the bitmap was extended to N=12. The CSI-RS RE pattern was repeated every 2 PRBs, and the resulting CSI-RS density was 0.5.

[0032] Figure 2bAnother example is depicted where M=4 and the bitmap is expanded to N=8. The CSI-RS RE pattern repeats every 16 subcarriers and 4 PRBs. The resulting CSI-RS density is 3 / 4.

[0033] In another example (not shown to avoid redundancy), M=8 and the bitmap is expanded to N=16. The CSI-RS RE pattern repeats every 32 subcarriers and 8 PRBs. The resulting CSI-RS density is 3 / 8.

[0034] Figure 3 illustrates various examples of CSI-RS RE mapping options. In Figure 3, different resource groups are indicated by different letters (e.g., "A", "B", "C", etc.). The specific letter designation of these elements is for the purpose of describing these particular diagrams only and is not intended to convey any information beyond "this element is different from another element". Additionally, although between different diagrams (e.g., in...) Figure 3a and Figure 3b Different letters are used between them, but unless otherwise explicitly indicated, these letter designations are not intended to be associated with each other. In other words, unless otherwise indicated, in Figure 3a The resource specified by "A" in the middle is not necessarily the same as the one in the middle. Figure 3b The resource specified by "A" is the same.

[0035] Alternatively, CSI-RS resource mapping configuration can be achieved via RE offset. Extend to cross PRB boundary, RE offset Define the starting subcarrier within the PRB for initiating the CSI-RS bitmap application, and in this case, the bitmap size remains unchanged; for example, for the applicable CSI-RS block configuration, the bitmap size is maintained at N=6. The RE offset can be configured from a small set of possible values ​​{0,8} to achieve this. Figure 3a The example in the example shows an RE offset of 8 for CSI-RS resources represented by the letters "B" and "D". Furthermore, the set of possible values ​​can include the case of all even-numbered starting REs within the PRB: {0,2,4,6,8,10}. Further, other possible offsets are {0,4,8} and {0,1,2,3,4,5,6,7,8,9,10,11}.

[0036] In one option, the mapping of CSI-RS resources across the PRB can be determined by the CSI-RS density parameter. Control. In addition to the {0.5,1} density, other parameters can be introduced. Density, which means there are three CSI-RS REs mapped across four PRBs with a total offset of 16 REs. The applicability of the new density parameter can be limited to the case of having 8 CSI-RS REs within a PRB, for example, rows 6, 11, 12, 16, 17, and 18 referenced in "Table 7.4.1.5.3-1: CSI-RS Locations within Slots" of TS 38.211 for X=8, 16, 32.

[0037] In other embodiments, such as Figure 3b As shown, the CSI-RS resource mapping configuration extends across the PRB (time slot) boundary in the time domain. The second OFDM symbol used for CSI-RS RE block mapping can be mapped to an index of... In the symbols, where, for the regular cyclic prefix (NCP), For the extended cyclic prefix (ECP), If for NCP, Or for ECP, If the starting subcarrier used for the CSI-RS block is located in the adjacent time slot of the time slot closest to the CSI-RS mapping, then the starting subcarrier is located in the adjacent time slot.

[0038] Regarding the above embodiments, the UE may not expect to support overlap with semi-static UL or semi-static flexible symbols. CSI-RS resource configuration.

[0039] In other embodiments, such as Figure 3c As shown, the total number of CSI-RS ports configured for CSI reporting, K·P, can be greater than P. PMI , where P PMI This refers to the number of CSI-RS ports used for PMI reporting. In this case, it is based on having an index h ≤ P. PMI The CSI-RS port determines RI, PMI, and CQI. To support this, a separate parameter P can be introduced in the RRC and signaled using signaling. PMI Please note that, Figure 3c In the CSI report, CSI-RS RE filled in black may not be used.

[0040] In one embodiment, multiple CSI-RS resources can be linked / bundled to generate a P PMI A single CSI report for each port. In particular, the UE may not expect different linked CSI-RS resources to be contained in multiple time slots. Alternatively, more than one time slot can be used to accommodate all linked CSI-RS resources.

[0041] In one option, by accommodating multiple Time Division Multiplexing (TDM) / Frequency Division Multiplexing (FDM) / CDM group resources within a CSI resource, the definition of a single CSI resource (e.g., NZP-CSI-RS-Resource) can be extended to support more than 32 ports. New resource mapping information elements (e.g., resourceMapping-r19) (as indicated by bold and italic elements) can be introduced, which are combinations of up to M conventional resourceMapping information elements, as shown in the example below. NZP-CSI-RS-Resource The information element description states that M can be at least 4, thus enabling 128 ports through 4×32-port CSI-RS resources. Furthermore, the list can consist of CSI-RS resources of the same size or of different sizes.

[0042] NZP-CSI-RS-Resource Information elements -- ASN1START -- TAG-NZP-CSI-RS-RESOURCE-START NZP-CSI-RS-Resource ::=SEQUENCE { nzp-CSI-RS-ResourceIdNZP-CSI-RS-ResourceId, resourceMappingCSI-RS-ResourceMapping, powerControlOffsetINTEGER (-8..15), powerControlOffsetSSENUMERATED{db-3, db0, db3, db6}OPTIONAL, -- NeedR scramblingIDScramblingId, periodicityAndOffsetCSI- ResourcePeriodicityAndOffsetOPTIONAL, -- Cond PeriodicOrSemiPersistent qcl-InfoPeriodicCSI-RSTCI-StateIdOPTIONAL, -- Cond Periodic ..., [[ subcarrierSpacing-r18SubcarrierSpacingOPTIONAL, -- Cond LTM absoluteFrequencyPointA-r18 ARFCN-ValueNROPTIONAL, -- Cond LTM cyclicPrefix-r18ENUMERATED {extended}OPTIONAL -- Cond LTM resourceMapping-r19SEQUENCE (SIZE (1..M)) OF resourceMapping ]] } -- TAG-NZP-CSI-RS-RESOURCE-STOP -- ASN1STOP.

[0043] In another option, by maintaining a specified number of ports and CDM types and repeating the basic structure according to one of the options discussed above, the Resource Mapping Information element can be expanded to support more than 32 CSI-RS ports. See below. CSI- RS-ResourceMapping As indicated by the information element, an additional parameter, repetitionType (as indicated by bold and italic elements), can be added. Specific repetition options (e.g., type1, type2, etc.) can indicate how CSI-RS for up to 32 ports can be repeated on PRBs and / or symbols within a time slot, to total more than 32 CSI ports. In this case, the given type also indicates a multiple of the nrofPorts parameter.

[0044] CSI-RS-ResourceMapping Information elements -- ASN1START -- TAG-CSI-RS-RESOURCEMAPPING-START CSI-RS-ResourceMapping ::= SEQUENCE { frequencyDomainAllocationCHOICE { row1BIT STRING (SIZE (4)), row2BIT STRING (SIZE (12)), row4BIT STRING (SIZE (3)), otherBIT STRING (SIZE (6)) }, nrofPortsENUMERATED {p1,p2,p4,p8,p12,p16,p24,p32}, firstOFDMSymbolInTimeDomain INTEGER (0..13), firstOFDMSymbolInTimeDomain2 INTEGER (2..12)OPTIONAL, -- Need R cdm-TypeENUMERATED {noCDM, fd-CDM2, cdm4-FD2-TD2, cdm8-FD2-TD4}, densityCHOICE { dot5ENUMERATED {evenPRBs, oddPRBs}, oneNULL, threeNULL, spareNULL }, freqBandCSI-FrequencyOccupation, … repetitionTypeENUMERATED {type1, type2, type3, spare,…} } -- TAG-CSI-RS-RESOURCEMAPPING-STOP -- ASN1STOP.

[0045] In another option, an explicit table can be introduced to indicate the CSI-RS resources linked for a CSI report. This table associates the CSI resource configuration IDs used for a CSI report with a list of nzp-CSI-RS-ResourceSetLists. Specifically, multiple nzp-CSI-RS resources from the list (as part of an NZP-CSI-RS-ResourceSet) can be linked or bundled for a CSI report with more than 32 ports.

[0046] Bundling can be implicit, such that when a CSI report indicates a codebook configuration with a number of ports greater than the number of ports associated with the referenced NZP-CSI-RS-Resource (e.g., 2N1N2>nrofPorts), for a CSI report, a series of NZP-CSI-RS-Resources are retrieved one by one from the list, such that 2N1N2=sum(nrofPorts_i), where i is a consecutive index of the CSI-RS resource in the list.

[0047] In another option, a parameter in the NZP-CSI-RS-ResourceSet can be used to indicate that CSI-RS resources in the CSI-RS resource set are configured to form CSI-RS resources with more than 32 ports. In one example, if 64-port, 96-port, and 128-port CSI-RS resources are defined, a two-bit parameter in the NZP-CSI-RS-ResourceSet can be used to indicate whether 64-port, 96-port, and 128-port CSI-RS resources are configured. For example, bit '00' can be used to indicate that CSI-RS port bundling or grouping is not applied; bit '01' can be used to indicate that a 64-port CSI-RS resource is formed; bit '10' can be used to indicate that a 96-port CSI-RS resource is formed; and bit '11' can be used to indicate that a 128-port CSI-RS resource is formed.

[0048] Bundling can be explicit by including a list of resource IDs that make up a single resource bundle / tuple. The following example illustrates how tuples of the NZP-CSI-RS-ResourceId collection are bundled using the new IE NZP-CSI-RS-Tuples-r19 (as indicated by bold and italic elements). NZP-CSI-RS-ResourceSet The information element illustrates this method.

[0049] NZP-CSI-RS-ResourceSet Information elements -- ASN1START -- TAG-NZP-CSI-RS-RESOURCESET-START NZP-CSI-RS-ResourceSet ::= SEQUENCE { nzp-CSI-ResourceSetIdNZP-CSI-RS-ResourceSetId, nzp-CSI-RS-ResourcesSEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceId, repetitionENUMERATED { on, off}OPTIONAL, -- Need S aperiodicTriggeringOffsetINTEGER(0..6)OPTIONAL, -- Need S trs-InfoENUMERATED {true}OPTIONAL, -- Need R ..., [[ aperiodicTriggeringOffset-r16 INTEGER(0..31)OPTIONAL -- Need S ]], [[ pdc-Info-r17ENUMERATED {true}OPTIONAL, -- Need R cmrGroupingAndPairing-r17CMRGroupingAndPairing-r17OPTIONAL, -- Need R aperiodicTriggeringOffset-r17 INTEGER (0..124)OPTIONAL, -- Need S aperiodicTriggeringOffsetL2-r17 INTEGER(0..31)OPTIONAL -- Need R ]], [[ resourceType-r18ENUMERATED {periodic}OPTIONAL -- Cond LTM ]] nzp-CSI-RS-Resource-Tuples-r19 NZP-CSI-RS-Tuples-r19OPTIONAL } NZP-CSI-RS-Tuples-r19 ::= SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS- ResourcesPerSet )) of { nzp-CSI-RS-ResourcesSEQUENCE (SIZE (1..M)) OF NZP-CSI-RS-ResourceId } CMRGroupingAndPairing-r17 ::= SEQUENCE { nrofResourcesGroup1-r17INTEGER (1..7), pair1OfNZP-CSI-RS-r17NZP-CSI-RS-Pairing-r17OPTIONAL, -- Need R pair2OfNZP-CSI-RS-r17NZP-CSI-RS-Pairing-r17OPTIONAL -- Need R } NZP-CSI-RS-Pairing-r17 ::= SEQUENCE { nzp-CSI-RS-ResourceId1-r17INTEGER (1..7), nzp-CSI-RS-ResourceId2-r17INTEGER (1..7) } -- TAG-NZP-CSI-RS-RESOURCESET-STOP -- ASN1STOP.

[0050] In other embodiments, for each CSI-RS resource i {1,2,...K}, the number of ports P i They are considered separately. The total number of CSI-RS resources used for PMI is .

[0051] In other embodiments, a slot offset K for each aperiodic CSI-RS resource is configured. A .

[0052] Figure 3 illustrates different CSI-RS RE mapping options, where the RE grid is presented in the horizontal dimension using OFDM symbols and in the vertical dimension using subcarriers. As previously mentioned, the RE mapping of CSI-RS resources used in common for PMI is presented using different letter indicators. For illustrative purposes, it is assumed that CSI-RS blocks are configured such that CSI-RS resources occupy a continuous set of consecutive adjacent subcarriers in one or two adjacent PRBs and in one or two adjacent time slots. The total number of CSI-RS ports on all CSI-RS resources used for PMI is K·P ≥ 128. The number of CSI-RS ports in a CSI-RS resource corresponds to the number of REs with the corresponding letter designations.

[0053] Specifically, Figure 3a An example of CSI-RS resource mapping configuration across PRB boundaries in the frequency domain is indicated. Figure 3b This indicates an example of a CSI-RS resource mapping configuration across time slot boundaries in the time domain. Figure 3c The total number of CSI-RS ports K·P>P is indicated. PMI For example, the CSI-RS RE highlighted with a pattern fill is not used in CSI reports. Figure 3d An example of a CSI-RS configuration with K=16 and P=8 is shown. Figure 3e This indicates an example where the number of ports P varies for each CSI-RS resource configured for PMI. Figure 3f This indicates the slot offset K used for aperiodic CSI-RS. A Examples of separate configurations for each CSI-RS resource are provided. It will be understood that these examples are for discussion purposes only and are not intended to limit the embodiments to only these specific configurations.

[0054] CSI processing CSI feedback involves intensive processing at the UE side. Considering the limited memory and processing power at the UE, the NR physical layer specification includes specific features that allow for limiting the CSI processing burden at the UE. These features include CSI processing unit (CPU) occupancy, active CSI-RS resource count, and minimum CSI processing time.

[0055] In one embodiment, P is used for PMI calculation. PMI The number of CPUs used by the CSI reports for each port was determined to be ceil(P). PMI / T), where ceil() is the floor function. In one option, T is fixed in the specification (e.g., T=32). In other options, T is reported by the UE as part of the UE capability signaling.

[0056] In other embodiments, the number of CPUs occupied by CSI reports 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 are fixed in the specification (e.g., T=2 and U=1). In other options, T and / or U are reported by the UE as part of the UE capability signaling.

[0057] In one embodiment, if multiple CSI sub-configurations are used for CSI reporting, the number of CPUs used by CSI reporting is the sum of the number of CPUs used by the sub-configurations, wherein the number of CPUs used by the sub-configurations is determined using the method described above.

[0058] In one embodiment, K CSI-RS resources used together for PMI are counted as 1 active CSI-RS resource.

[0059] In other embodiments, the K CSI-RS resources jointly used for PMI are counted as ceil(P PMI / B) active CSI-RS resources or ceil(K / B) active CSI-RS resources. In one option, B is fixed in the specification (e.g., B=32). In others, B is reported by the UE as part of the UE capability signaling.

[0060] In one aspect, it is configured with CSI-ReportConfig (Higher-level parameters) reportQuantity A UE configured with '128-port-CSI' expects 1 ≤ K ≤ 4 CSI-RS resources in the resource set used for channel measurements. If interference measurements are performed on CSI-IM, then in the corresponding csi-IM-ResourceSet Only one resource is configured. If interference measurements are performed on the NZP CSI-RS, then the corresponding resource used for the interference measurement... NZP-CSI-RS-ResourceSet Only one resource is configured in the middle.

[0061] In one aspect, if the UE is configured with CSI-ReportConfig (Higher-level parameters) reportQuantity It is set to '128-port-CSI'. codebookType (Set to '128-port-CSI') and the corresponding channel measurement NZP-CSI-RSResourceSet If there are 1≤K≤4 resources configured, each resource can contain up to 32 CSI-RS ports.

[0062] In one aspect, if a channel measurement is configured... NZP-CSI-RSResourceSet If a UE is configured with 1 ≤ K ≤ 4 resources, then the set of multiple resources is ordered. In one aspect, if resources are configured for channel measurement... NZP-CSI-RSResourceSet If a UE is configured with 1 ≤ K ≤ 4 resources, then the same value powerControlOffset (The power offset of the PDSCH RE relative to the NZP CSI-RS RE) is used for all resources. In one aspect, if channel measurements are configured... NZP-CSI-RSResourceSet If a UE is configured with 1 ≤ K ≤ 4 resources, then the same value powerControlOffsetSS (The power offset of the NZP CSI-RS RE relative to the SSS RE) is used for all resources. In one aspect, if a channel measurement is configured... NZP-CSI-RSResourceSet If a UE is configured with 1 ≤ K ≤ 4 resources, then the same qcl-InfoPeriodicCSI-RS(Contains a reference to a TCI-State in TCI-States, used to provide the QCL source and QCL type) is used for all resources.

[0063] System and Implementation Figures 4 to 10 Various systems, devices, and components that can implement aspects of the disclosed embodiments are illustrated.

[0064] Figure 4 The illustration depicts a network 400 according to various embodiments. Network 400 can operate in a manner consistent with 3GPP technical specifications for LET or 5G / NR systems. However, the exemplary embodiments are not limited in this respect, and the described embodiments can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems.

[0065] Network 400 may include UE 402, which may include any mobile or non-mobile computing device designed to communicate with RAN 404 via an over-the-air connection. UE 402 may be communicatively connected to RAN 404 via a Uu interface. UE 402 may be, but is not limited to, smartphones, tablets, wearable computing devices, desktop computers, laptops, in-vehicle infotainment systems, in-vehicle entertainment devices, dashboards, head-up displays, in-vehicle diagnostic equipment, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked devices, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0066] In some embodiments, network 400 may include multiple UEs that are directly connected to each other via sidelink interfaces. The UEs may be M2M devices / D2D devices that communicate using physical sidelink channels (such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.).

[0067] In some embodiments, UE 402 may additionally communicate with AP 406 via an over-the-air connection. AP 406 may manage a WLAN connection, which may be used to offload some / all of the network traffic from RAN 404. The connection between UE 402 and AP 406 may conform to any IEEE 802.11 protocol, wherein AP 406 may be a Wi-Fi hotspot. ®Router. In some embodiments, UE 402, RAN 404, and AP 406 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve RAN 404 configuring UE 402 to utilize both cellular radio resources and WLAN resources.

[0068] RAN 404 may include one or more access nodes, such as AN 408. AN 408 can terminate the air interface protocol for UE 402 by providing an access layer protocol that includes RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 408 can establish a data / voice connection between CN 420 and UE 402. In some embodiments, AN 408 may be implemented in a discrete device or as one or more software entities running on a server computer as part of, for example, a virtual network, which may be referred to as CRAN or a virtual baseband unit pool. AN 408 may be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 408 may be a macrocell base station or a low-power base station such as a femtocell, picocell, etc., that provides a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0069] In embodiments where RAN 404 includes multiple ANs, the multiple ANs can be interconnected via an X2 interface (in the case of RAN 404 being an LTE RAN) or an Xn interface (in the case of RAN 404 being a 5G RAN). In some embodiments, the X2 interface / Xn interface, which can be divided into a control plane interface / user plane interface, can allow ANs to transmit and handover, data transfer / context transfer, mobility, load management, interference coordination, and other related information.

[0070] Each AN of RAN 404 can manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE 402. UE 402 can simultaneously connect to multiple cells provided by the same or different ANs of RAN 404. For example, UE 402 and RAN 404 can use carrier aggregation to allow UE 402 to connect to multiple component carriers, each component carrier corresponding to a Pcell or Scell. In a dual-connectivity scenario, the first AN can be the primary node providing the MCG, and the second AN can be the secondary node providing the SCG. The first AN / second AN can be any combination of eNB, gNB, ng-eNB, etc.

[0071] RAN 404 can provide an air interface using either licensed or unlicensed spectrum. To operate on unlicensed spectrum, nodes can use LAA, eLAA, and / or feLAA mechanisms based on CA technology employing PCell / Scell. Before accessing unlicensed spectrum, nodes can perform medium / carrier sensing operations based on, for example, a Listen-After-Speak (LBT) protocol.

[0072] In V2X scenarios, UE 402 or AN 408 can be or act as an RSU, where RSU can refer to any transport infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE can be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU"; an RSU implemented in or by a gNB can be referred to as a "gNB-type RSU," and so on. In one example, the RSU is a computing device coupled to roadside radio frequency circuitry that provides connectivity support for passing vehicle UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU can provide extremely low-latency communication required for high-speed events such as collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU can provide other cellular / WLAN communication services. RSU components can be enclosed in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing wired connections (e.g., Ethernet) to traffic signal controllers or backhaul networks.

[0073] In some embodiments, RAN 404 may be an LTE RAN 410 with an eNB (e.g., eNB 412). LTE RAN 410 may provide an LTE air interface with the following characteristics: a 15 kHz SCS; CP-OFDM waveforms for DL ​​and SC-FDMA waveforms 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; rely on PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and rely on 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 operate in frequency bands below 6 GHz.

[0074] In some embodiments, RAN 404 may be an NG-RAN 414 having a gNB (e.g., gNB 416) or an ng-eNB (e.g., ng-eNB 418). gNB 416 can connect to a 5G-enabled UE using a 5G NR interface. gNB 416 can connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. ng-eNB 418 can also connect to the 5G core via an NG interface, but can connect to the UE via an LTE air interface. gNB 416 and ng-eNB 418 can connect to each other via an Xn interface.

[0075] In some embodiments, the NG interface can be divided into two parts: the NG user plane (NG-U) interface (e.g., the N3 interface), which carries traffic data between the nodes of NG-RAN 414 and UPF 448; and the NG control plane (NG-C) interface (e.g., the N2 interface), which is the signaling interface between the nodes of NG-RAN 414 and AMF 444.

[0076] NG-RAN 414 can 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 codes, repetition codes, simple codes and Reed-Muller codes for control, and LDPC for data. Similar to the LTE air interface, the 5G-NR air interface can rely on CSI-RS, PDSCH / PDCCH DMRS. The 5G-NR air interface may not use CRS, but can use PBCH DMRS for PBCH demodulation; PTRS for PDSCH phase tracking; and a tracking reference signal for time tracking. The 5G-NR air interface can operate on the FR1 band, which includes frequency bands below 6 GHz, or the FR2 band, which includes frequency bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface can include SSBs for areas of downlink resource grids containing PSS / SSS / PBCH.

[0077] In some embodiments, the 5G-NR air interface can utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCS. For instance, UE 402 can be configured with multiple BWPs, each configured with a different SCS. When a BWP is indicated to UE 402 for a change, the transmitted SCS also changes. Another use case for BWPs is related to power saving. In particular, multiple BWPs with different numbers of frequency resources (e.g., PRBs) can be configured for UE 402 to support data transmission under different traffic load scenarios. BWPs with a smaller number of PRBs can be used for data transmission with low traffic loads, while allowing power saving at UE 402 and, in some cases, at gNB 416. BWPs with a larger number of PRBs can be used for scenarios with high traffic loads.

[0078] RAN 404 is communicatively connected to CN 420, which includes network elements to provide various functions to support the delivery of data and telecommunications services to customers / subscribers (e.g., users of UE 402). Components of CN 420 may be implemented in a single physical node or in separate physical nodes. In some embodiments, NFV may be used to virtualize any or all of the functions provided by the network elements of CN 420 onto physical computing / storage resources such as servers, switches, etc. A logical instantiation of CN 420 may be referred to as a network slice, and a logical instantiation of a portion of CN 420 may be referred to as a network subslice.

[0079] In some embodiments, CN 420 may be LTE CN 422, which may also be referred to as EPC. LTE CN 422 may include MME 424, SGW 426, SGSN 428, HSS 430, PGW 432, and PCRF 434 interconnected via interfaces (or "reference points"), as shown in the figure. The functions of the components of LTE CN 422 can be briefly described below.

[0080] MME 424 enables mobility management functions to track the current location of UE 402, thereby supporting paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0081] The SGW 426 can terminate the S1 interface toward the RAN and route data packets between the RAN and the LTE CN 422. The SGW 426 can serve as a local mobility anchor for handover between RAN nodes and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0082] SGSN 428 can track the location of UE 402 and perform security functions and access control. Furthermore, SGSN 428 can perform EPC inter-node signaling for mobility between different RAT networks, such as PDN and S-GW selection specified by MME 424, and MME selection for handover. The S3 reference point between MME 424 and SGSN 428 enables the exchange of user and bearer information for mobility between 3GPP access networks in idle / active states.

[0083] The HSS 430 can contain a database of network users, including subscription-related information, to support network entities in handling communication sessions. The HSS 430 provides support for routing / roaming, authentication, authorization, naming / addressing resolution, and location dependencies. The S6a reference point between the HSS 430 and the MME 424 enables the transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN420.

[0084] PGW 432 can terminate the SGi interface toward data network (DN) 436, which may include application / content server 438. PGW 432 can route data packets between LTE CN 422 and data network 436. PGW 432 can connect to SGW 426 via an S5 reference point to support user plane tunneling and tunnel management. PGW 432 may also include nodes for policy enforcement and charging data collection (e.g., PCEF). Additionally, the SGi reference point between PGW 432 and data network 436 can be an external public or private PDN or an in-carrier data network, for example, for providing IMS services. PGW 432 can connect to PCRF 434 via a Gx reference point.

[0085] PCRF 434 is the policy and charging control unit of LTE CN 422. PCRF 434 can communicatively connect to application / content server 438 to determine appropriate QoS and charging parameters for service flows. PCRF 432 (via Gx reference point) configures the associated rules into PCEF, which have appropriate TFT and QCI.

[0086] In some embodiments, CN 420 may be 5GC 440. 5GC 440 may include AUSF 442, AMF 444, SMF 446, UPF 448, NSSF 450, NEF 452, NRF 454, PCF456, UDM 458, and AF 460 connected to each other via interfaces (or "reference points"), as shown in the figure. The functions of the components of 5GC 440 can be briefly described below.

[0087] The AUSF 442 can store data used for UE 402 authentication and handle authentication-related functions. The AUSF 442 supports common authentication frameworks for various access types. In addition to communicating with other components of the 5GC440 via a reference point as shown in the figure, the AUSF 442 also provides a service-based Nausf interface.

[0088] AMF 444 allows other functions of 5GC 440 to communicate with UE 402 and RAN 404, and to subscribe to notifications regarding mobility events for UE 402. AMF 444 can handle registration management (e.g., for UE 402 registration), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. AMF 444 can provide SM message transmission between UE 402 and SMF 446 and act as a transparent broker for routing SM messages. AMF 444 can also provide SMS message transmission between UE 402 and SMSF. AMF 444 can interact with AMFF 442 and UE 402 to perform various security anchoring and context management functions. Furthermore, AMF 444 can be the endpoint of the RAN CP interface, which may include or be the N2 reference point between RAN 404 and AMF 444; and AMF 444 can be the endpoint of NAS (N1) signaling, performing NAS encryption and integrity protection. AMF 444 can also support NAS signaling with UE 402 via the N3 IWF interface.

[0089] SMF 446 can be responsible for SM (e.g., session establishment, tunnel management between UPF 448 and AN 408); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic bootstrapping at UPF 448 to route traffic to appropriate destinations; termination of interfaces for policy control functions; control of policy enforcement, charging, and QoS portions; lawful interception (for SM events and interfaces to the LI system); termination of the SM portion of NAS messages; downlink data notification; initiating AN-specific SM messages, which are sent to AN 408 via AMF 444 through N2; and determining the SSC mode of the session. SM can refer to the management of PDU sessions, and a PDU session or "session" can refer to the PDU connection service that provides or enables the exchange of PDUs between UE 402 and data network 436.

[0090] UPF 448 can act as an anchor point for mobility within and between RATs, an interconnection point for external PDU sessions to the data network 436, and a branch point supporting multi-homed PDU sessions. UPF 448 can also perform packet routing and forwarding; perform packet inspection; enforce the user plane portion of policy rules; enforce legitimate packet interception (UP collection); perform traffic usage reporting; perform user plane QoS processing (e.g., packet filtering, gating, UL / DL rate enforcement); perform uplink traffic authentication (e.g., SDF-to-QoS flow mapping), transport layer packet marking in uplink and downlink; and perform downlink packet buffering and downlink data notification triggering. UPF 448 may include an uplink classifier to support traffic flow routing to the data network.

[0091] NSSF 450 can select a set of network slice instances to serve UE 402. If needed, NSSF 450 can also determine the allowed NSSAIs and the mapping to subscribed S-NSSAIs. NSSF 450 can also determine a set of AMFs or a list of candidate AMFs to serve UE 402 based on appropriate configuration and possibly by querying NRF 454. The selection of a set of network slice instances for UE 402 can be triggered by AMF 444 registered by UE 402 interacting with NSSF 450, which may result in a change of AMF. NSSF 450 can interact with AMF 444 via reference point N22; and can communicate with another NSSF (not shown) in the access network via reference point N31. Additionally, NSSF 450 can provide a service-based NNSSF interface.

[0092] NEF 452 can securely expose services and capabilities provided by 3GPP network functions to third parties, internal open / reopened systems, AFs (e.g., AF 460), edge computing systems, or fog computing systems. In this embodiment, NEF 452 can authenticate, authorize, or rate-limit AFs. NEF 452 can also translate information exchanged with AF 460 and information exchanged with internal network functions. For example, NEF 452 can translate between AF service identifiers and internal 5GC information. NEF 452 can also receive information from other NFs based on their open capabilities. This information can be stored as structured data at NEF 452 or stored at a data storage NF using a standardized interface. Subsequently, NEF 452 can reopen the stored information to other NFs and AFs, or use it for other purposes such as analysis. Additionally, NEF 452 can provide a service-based Nnef interface.

[0093] NRF 454 supports service discovery, receives NF discovery requests from NF instances, and provides information about discovered NF instances to the NF instances. NRF 454 also maintains information about available NF instances and the services they support. As used herein, the terms "instantiation process," "instantiation," etc., can refer to the creation of an instance, and "instance" can refer to the concrete occurrence of an object, such as during the execution of program code. Furthermore, NRF 454 can provide a service-based NRF interface.

[0094] PCF 456 can provide policy rules to control plane functions for policy enforcement and can also support a unified policy framework to govern network behavior. PCF 456 can also implement a front-end to access subscription information related to policy decisions in the UDR of UDM 458. In addition to communicating with functions via reference points as shown in the figure, PCF 456 also provides a service-based NPCF interface.

[0095] UDM 458 can process subscription-related information to support network entities in handling communication sessions and can store subscription data for UE 402. For example, subscription data can be transmitted via the N8 reference point between UDM 458 and AMF 444. UDM 458 can consist of two parts: an application front-end and a UDR. The UDR can store subscription data and policy data for UDM 458 and PCF 456, and / or structured data for NEF 452 for open applications, as well as application data (including PFDs for application detection and application request information for multiple UEs 402). UDR 221 can provide a service-based Nudr interface to allow UDM 458, PCF 456, and NEF 452 to access specific sets of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of related data changes in the UDR. UDM can include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front-ends can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identity processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via a reference point as shown in the figure, the UDM 458 also provides a service-based Nudm interface.

[0096] The AF 460 can provide application impact on traffic routing, provide access to NEF, and interact with the policy framework to achieve policy control.

[0097] In some embodiments, 5GC 440 can enable edge computing by selecting an operator / third-party service that is geographically close to the point where UE 402 is attached to the network. This can reduce latency and load on the network. To provide edge computing implementation, 5GC 440 can select a UPF 448 close to UE 402 and perform traffic routing from UPF 448 to data network 436 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 460. In this way, AF 460 can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 460 is considered a trusted entity, the network operator can allow AF 460 to interact directly with the relevant NF. Additionally, AF 460 can provide a service-based Naf interface.

[0098] Data network 436 can refer to various network operator services, Internet access, or third-party services that can be provided by one or more servers, such as application / content server 438.

[0099] Figure 5 A wireless network 500 according to various embodiments is schematically illustrated. The wireless network 500 may include a UE 502 that wirelessly communicates with an AN 504. The UE 502 and the AN 504 may be similarly named components described elsewhere herein and are substantially interchangeable with similarly named components described elsewhere herein.

[0100] UE 502 can be communicatively connected to AN 504 via connection 506. Connection 506 is illustrated as an air interface for communication connectivity and is compatible with cellular communication protocols such as LTE or 5G NR protocols operating at millimeter wave or sub-6 GHz frequencies.

[0101] UE 502 may include a host platform 508 connected to modem platform 510. Host platform 508 may include application processing circuitry 512, which may be connected to protocol processing circuitry 514 of modem platform 510. Application processing circuitry 512 may run various applications for generating / receiving application data for UE 502. Application processing circuitry 512 may also implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport layer (e.g., UDP) operations and Internet layer (e.g., IP) operations.

[0102] The protocol processing circuit 514 can implement one or more layer operations to support data transmission or reception via connection 506. The layer operations implemented by the protocol processing circuit 514 may include, for example, MAC operations, RLC operations, PDCP operations, RRC operations, and NAS operations.

[0103] The modem platform 510 may also include digital baseband circuitry 516, which can implement one or more layer operations that are "below" the layer operations performed by the protocol processing circuitry 514 in the network protocol stack. These operations may include, for example, PHY operations, which include one or more of the following: HARQ-ACK functionality, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding, and PHY operations may include one or more of the following: space-time, space-frequency, or space coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals, and other related functions.

[0104] The modem platform 510 may also include transmitting circuitry 518, receiving circuitry 520, RF circuitry 522, and an RF front-end (RFFE) 524, which may include or be connected to one or more antenna panels 526. In short, transmitting circuitry 518 may include a digital-to-analog converter, mixer, intermediate frequency (IF) component, etc.; receiving circuitry 520 may include an analog-to-digital converter, mixer, IF component, etc.; RF circuitry 522 may include a low-noise amplifier, power amplifier, power point tracking component, etc.; and RFFE 524 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of components of transmitting circuitry 518, receiving circuitry 520, RF circuitry 522, RFFE 524, and antenna panels 526 (collectively referred to as the "transmitter assembly / receiver assembly") may be specific to implementation details, such as whether the communication is TDM or FDM, whether it is in millimeter waves or at frequencies below 6 GHz, etc. In some embodiments, the transmitting / receiving components can be arranged in multiple parallel transmitting / receiving chains, and can be located in the same or different chips / modules, etc.

[0105] 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 transmitting / receiving component.

[0106] UE reception can be established via and through antenna panel 526, RFFE 524, RF circuit 522, receiving circuit 520, digital baseband circuit 516, and protocol processing circuit 514. In some embodiments, antenna panel 526 can receive transmissions from AN 504 via receive beamforming signals received by a plurality of antennas / antenna elements of one or more antenna panels 526.

[0107] UE transmission can be established via and through protocol processing circuitry 514, digital baseband circuitry 516, transmission circuitry 518, RF circuitry 522, RFFE 524, and antenna panel 526. In some embodiments, the transmission components of UE 504 may apply a spatial filter to the data to be transmitted to form a transmission beam emitted by the antenna elements of antenna panel 526.

[0108] Similar to UE 502, AN 504 may include a host platform 528 coupled to modem platform 530. Host platform 528 may include application processing circuitry 532 coupled to protocol processing circuitry 534 of modem platform 530. The modem platform may also include digital baseband circuitry 536, transmitting circuitry 538, receiving circuitry 540, RF circuitry 542, RFFE circuitry 544, and antenna panel 546. Components of AN 504 may be similar to and substantially interchangeable with similarly named components of UE 502. In addition to performing data transmission / reception as described above, components of AN 508 may also perform various logical functions, including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and packet scheduling.

[0109] Figure 6 These are block diagrams, based on some example embodiments, illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any or more methods discussed herein. Specifically, Figure 6 A schematic representation of hardware resource 600 is shown, which includes 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 can be communicatively connected via bus 640 or other interface circuitry. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 602 can be executed to provide an execution environment for one or more network slices / subslices utilizing hardware resource 600.

[0110] Processor 610 may include, for example, processor 612 and processor 614. Processor 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.

[0111] Memory / storage device 620 may include main memory, disk storage, or any suitable combination thereof. Memory / storage device 620 may include, but is 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.

[0112] Communication resource 630 may include an interconnect or network interface controller, component, or other suitable device for communicating with one or more peripheral devices 604 or one or more databases 606 or other network elements via network 608. For example, communication resource 630 may include wired communication components (e.g., for connections via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth, etc. ® (or Bluetooth) ® Low-power components, Wi-Fi ® Components and other communication components.

[0113] Instruction 650 may include software, programs, applications, applets, application programs, or other executable code for causing at least any one of the processors 610 to perform one or more methods discussed herein. Instruction 650 may reside wholly or partially in at least one of the processors 610 (e.g., within the processor's cache memory), memory / storage device 620, or any suitable combination thereof. Furthermore, any portion of instruction 650 may be transferred to hardware resource 600 from any combination of peripheral device 604 or database 606. Therefore, the memory of processor 610, memory / storage device 620, peripheral device 604, and database 606 are examples of computer-readable and machine-readable media.

[0114] Figure 7The illustration depicts a network 700 according to various embodiments. Network 700 can operate in accordance with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, network 700 can operate simultaneously with network 400. For example, in some embodiments, network 700 can share one or more frequency resources or bandwidth resources with network 400. As a specific example, a UE (e.g., UE 702) can be configured to operate in both network 700 and network 400. This configuration may be based on the UE including circuitry configured to communicate with the frequency and bandwidth resources of both network 400 and network 700. Generally, certain elements of network 700 can 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.

[0115] Network 700 may include UE 702, which may include any mobile or non-mobile computing device designed to communicate with RAN 708 via an over-the-air connection. UE 702 may be similar to, for example, UE 402. UE 702 may be, but is not limited to: smartphones, tablet computers, wearable computing devices, desktop computers, laptop computers, in-vehicle infotainment systems, in-vehicle entertainment devices, dashboards, head-up displays, in-vehicle diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked devices, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0116] Although not in Figure 7 While specifically illustrated, in some embodiments, network 700 may include multiple UEs directly interconnected via sidelink interfaces. The UEs may be M2M / D2D devices communicating using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not explicitly shown... Figure 7 As specifically shown in the diagram, UE 702 can be used with, for example, (as per the description of...) Figure 4 (Description) AP 406 AP communication ground connection. Furthermore, although not in Figure 7 The specific details are shown below, but in some embodiments, RAN 708 may include, for example, (as per [reference]). Figure 4 (Description) One or more ANs of AN 408. ANs of RAN 708 and / or RAN 708 may be referred to as base stations (BS), RAN nodes, or some other term or name.

[0117] UE 702 and RAN 708 can 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 the terahertz (THz) or Asia-Pacific Hertz (APH) bandwidth, or combined communication and sensing. As used herein, the term “combined communication and sensing” may refer to a system that allows wireless communication and radar-based sensing via various types of multiplexing. As used herein, the terahertz or APH bandwidth may refer to communication in a frequency range of 80 GHz and above. This frequency range may additionally or alternatively be referred to as “millimeter wave” or “millimeter wave frequency range”.

[0118] RAN 708 enables communication between UE 702 and 6G core network (CN) 710. Specifically, RAN 708 supports data transmission and reception between UE 702 and 6G CN 710. 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. 6G CN 710 may additionally include UPF 448 and DN 436, such as... Figure 7 As shown.

[0119] Additionally, RAN 708 may include various additional functions beyond or replacing those of traditional cellular networks (such as 4G or 5G networks). Two such functions may include a Compute Control Function (Comp CF) 724 and a Compute Service Function (Comp SF) 736. Comp CF 724 and Comp SF 736 may be parts or functions of the Compute Service Plane. Comp CF 724 may be a control plane function that provides functions such as managing Comp SF 736, generating and managing compute task contexts (e.g., creating, reading, modifying, and deleting), and interacting with the underlying compute infrastructure for compute resource management. Comp SF 736 may be a user plane function that acts as a gateway connecting compute service users (such as UE 702) and compute nodes behind the Comp SF instance. Some functionalities of the Comp SF 736 may include: parsing compute service data received from users into compute tasks executable by compute nodes; managing a service mesh ingress gateway or service API gateway; enforcing service and billing policies; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 736 instance can be used as a user plane gateway for a cluster of compute nodes. A Comp CF 724 instance can control one or more Comp SF 736 instances.

[0120] Two other such functions may include a communication control function (CommCF) 728 and a communication service function (Comm SF) 738, which may be part of the communication service plane. Comm CF 728 may be a control plane function for managing Comm SF 738, creating / configuring / releasing communication sessions, and managing communication session contexts. Comm SF 738 may be a user plane function for data transfer. Comm CF 728 and Comm SF 738 can be considered as referenced... Figure 7 The 5G system described in the text is an upgrade of the SMF 446 and UPF 448. Upgrades provided by Comm CF 728 and Comm SF 738 enable service-aware transport. For legacy (e.g., 4G or 5G) data transmission, the SMF 446 and UPF 448 can still be used.

[0121] Two other such functions may include a Data Control Function (DataCF) 722 and a Data Service Function (DataSF) 732, which can be part of the data service plane. DataCF 722 can be a control plane function and provides functions such as DataSF 732 management, data service creation / configuration / release, and data service context management. DataSF 732 can be a user plane function and acts as a gateway between data service users (such as various functions of UE 702 and 6G CN 710) and the data service endpoints located behind the gateway. Specific functions may include: parsing data service user data and forwarding it to the appropriate data service endpoint; generating billing data; and reporting data service status.

[0122] Another such function could be the Service Orchestration and Linking Function (SOCF) 720, which can discover, orchestrate, and link communication services / computing services / data services provided by functions within the network. Upon receiving a service request from a user, SOCF 720 can interact with one or more of Comp CF 724, Comm CF 728, and Data CF 722 to identify Comp SF 736 instances, Comm SF 738 instances, and Data SF 732 instances, configure service resources, and generate a service chain that can contain multiple Comp SF 736 instances, Comm SF 738 instances, and Data SF 732 instances, along with their associated compute endpoints. Workload processing and data movement can then be performed within the generated service chain. SOCF 720 can also be responsible for maintaining, updating, and releasing the created service chains.

[0123] Another such function could be a Service Registration Function (SRF) 714, which can act as a registry center for system services provided in the user plane, such as services provided by service endpoints located behind the Comp SF 736 gateway and the Data SF 732 gateway, and services provided by the UE 702. SRF 714 can be considered a counterpart to NRF 754, which can act as a registry center for network functions.

[0124] Other such functionalities may include the Evolved Serving Communication Agent (eSCP) and the Service Infrastructure Control Function (SICF) 726, which provide the service communication infrastructure for control plane services and user plane services. The eSCP can be associated with a 5G Service Communication Agent (SCP) with added user plane service communication agent capabilities. Therefore, the eSCP is represented as two parts: eCSP-C 712 and eSCP-U 734, used for the control plane service communication agent and the user plane service communication agent, respectively. SICF 726 can control and configure the eCSP instance in terms of service traffic routing policies, access rules, load balancing configuration, and performance monitoring.

[0125] Another such function is AMF 744. AMF 744 can be similar to 444, but with additional functions. Specifically, AMF 744 can include potential function refactoring, such as moving message forwarding functions from AMF 744 to RAN 708.

[0126] Another such feature is the Service Orchestration Open Function (SOEF) 718. SOEF can be configured to open service orchestration and linking services to external users such as applications.

[0127] UE 702 may include additional functionality known as Computational Client Service Function (Comp CSF) 704. CompCSF 704 may have both control plane and user plane functions and can 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. CompCSF 704 can also collaborate with network-side functions to determine whether compute tasks should run on elements of UE 702, RAN 708, and / or 6G CN 710.

[0128] UE 702 and / or component 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. The capabilities of the service mesh proxy 706 may include one or more of addressing, security, load balancing, etc.

[0129] Example Process In some embodiments, Figures 4-7 Electronic devices, networks, systems, chips, or components, or portions thereof, or implementations thereof, in some other figures herein, may be configured to perform one or more processes, techniques, or methods, or portions thereof, as described herein. Figure 8 The document describes such a process. For example, the process may include: at 801, receiving configuration information for Channel State Information (CSI) resources, wherein a first CSI resource in the CSI resources spans a Physical Resource Block (PRB) boundary in the frequency domain and / or a timeslot boundary in the time domain. At 802, the process may further include: generating a CSI based on measurements of the CSI-Reference Signal (CSI-RS) in the corresponding CSI resource. At 803, the process may further include: sending a CSI report with the CSI. The CSI may include, for example, RI, PMI, and / or CQI.

[0130] Figure 9 Another example process according to various embodiments is illustrated. In some embodiments, Figure 9 The process can be performed by the gNB or a portion thereof. At 901, the process may include: encoding configuration information for Channel State Information (CSI) resources for transmission to the User Equipment (UE), wherein a first CSI resource in the CSI resources crosses a Physical Resource Block (PRB) boundary in the frequency domain and / or a timeslot boundary in the time domain. At 902, the process may further include: receiving a CSI report with CSI from the UE based on the CSI resources. The CSI may include, for example, RI, PMI, and / or CQI.

[0131] Figure 10 Another example process according to various embodiments is illustrated. Specifically, Figure 10The document describes a process to be performed by a User Equipment (UE), one or more components of the UE, and / or one or more electronic devices including and / or implementing the UE. The process may include: at 1001, identifying Channel State Information (CSI)-Reference Signal (RS) information received from more than 32 CSI-RS ports of a base station of a cellular network; at 1002, performing one or more CSI measurements on the CSI-RS information received from a subset of the more than 32 CSI-RS ports, wherein the subset of CSI-RS ports includes 32 or fewer CSI-RS ports; and at 1003, generating a CSI report based on the CSI measurements, the CSI report including CSI values ​​associated with the more than 32 CSI-RS ports.

[0132] Figure 11 Another such process is described. Figure 11 The process may include or involve a process to be performed by a base station, one or more elements of the base station, and / or one or more electronic devices including and / or implementing the base station. The process may include: at 1101, transmitting Channel State Information (CSI)-Reference Signal (RS) information from more than 32 CSI-RS ports of the base station; and at 1102, identifying a CSI report from the UE, the CSI report including CSI values ​​associated with more than 32 CSI-RS ports, wherein the CSI values ​​are based on one or more CSI measurements performed by the UE on CSI-RS information received from a subset of the more than 32 CSI-RS ports, wherein the subset of CSI-RS ports includes 32 or fewer CSI-RS ports.

[0133] For one or more embodiments, at least one of the components illustrated in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as illustrated in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the Examples section below. For another example, circuitry associated with a UE, base station, network element, etc., as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the Examples section below.

[0134] Example Example 1 may include a method for measuring and reporting Channel State Information (CSI) at a User Equipment (UE) having more than 32 CSI-RS ports, wherein the method includes: configuring CSI measurement and reporting at the UE; measuring CSI-RS (CSI Reference Signals) on K CSI-RS resources; and calculating and reporting CSI based on the measured CSI-RS, wherein the CSI-RS ports across all configured CSI-RS resources are jointly used for the Rank Indicator (RI), Precoding Matrix Indicator, and / or Channel Quality Indicator (CQI).

[0135] Example 2 may include the method of Example 1 and / or some other examples in this document, wherein the CSI-RS resource crosses the PRB boundary in the frequency domain.

[0136] Example 3 may include the method of Example 2 and / or some other examples herein, wherein the UE is configured with a bitmap [b(N-1),...,b(0)], which indicates the initial subcarriers of the L subcarriers for CSI-RS, bit b(n) indicates the CSI-RS in the last L subcarriers of PRB A, and bit b(n+1) indicates the CSI-RS in the first L subcarriers of PRB A+1.

[0137] Example 4 may include the method of Example 3 and / or some other examples herein, wherein the CSI-RS resources are repeated every 2N subcarriers and M PRBs.

[0138] Example 5 may include the method of Example 2 and / or some other examples herein, wherein for each CSI-RS resource or each group of CSI-RS resources, an offset of O subcarriers is indicated, and the initial subcarriers of the CSI-RS transmission are shifted by O subcarriers.

[0139] Example 6 may include the method of Example 2 and / or some other examples herein, wherein the CSI-RS resource is repeated every 1 / ρ PRB in the frequency domain, and 1 / ρ is not an integer, wherein ρ is configured via a higher layer.

[0140] Example 7 may include Example 1 and / or some other examples in this document, wherein the CSI-RS resource spans a time slot boundary in the time domain, a first initial symbol for the CSI-RS resource is configured in a first time slot, l(1)<14; and a second initial symbol for the CSI-RS resource is configured in a second time slot, l(2)≥14.

[0141] Example 8 may include the method of Example 1 and / or some other examples herein, wherein the number of ports K·P across K CSI-RS resources is greater than the number of CSI-RS ports used for RI, PMI and CQI, where PPMI > K·P.

[0142] Example 9 may include the method of Example 8 and / or some other examples in this document, wherein the last K·P-PPMI ports are not measured by the UE for CSI.

[0143] Example 10 may include the method of Example 1 and / or some other examples in this document, wherein the number of ports P(i) is for each CSI-RS resource i {1,2,...K} are configured separately. The total number of CSI-RS resources used for RI, PMI, and CQI is PPMI for i The sum of P(i) for {1,2,...K}.

[0144] Example 11 may include the method of Example 1 and / or some other examples herein, wherein the slot offset K of the aperiodic CSI-RS A Each CSI-RS resource or each group of CSI-RS resources is configured separately.

[0145] Example 12 may include the method of Example 1 and / or some other examples in this document, wherein if the number of occupied CSI processing units is greater than the value of the reporting capability, then the CSI does not need to update the CSI report.

[0146] Example 13 may include the method of Example 12 and / or some other examples herein, wherein the number of CPUs occupied by the CSI report is ceil(PPMI / T), where ceil() is a round-up function, PPMI is the number of CSI-RS ports used for RI, PMI and CQI, and T is fixed or indicated by the UE as a capability.

[0147] Example 14 may include the method of Example 12 and / or some other examples herein, wherein the number of CPUs occupied reported by the CSI is T·K+U or ceil(T·K+U), where T and / or U are fixed in the specification, or T and / or U are reported by the UE as a capability.

[0148] Example 15 may include the method of Example 12 and / or some other examples herein, wherein if the UE is configured with multiple CSI sub-configurations, the number of CPUs occupied by the CSI report is the sum of the number of CPUs occupied by the sub-configurations.

[0149] Example 16 may include the method of Example 1 and / or some other examples herein, wherein the UE is not expected to have more active CSI-RS resources than is reported as capable.

[0150] Example 17 may include the method of Example 16 and / or some other examples herein, wherein K CSI-RS resources are counted as 1 active CSI-RS resource.

[0151] Example 18 may include the method of Example 16 and / or some other examples 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 a round-up function, PPMI is the number of CSI-RS ports used for RI, PMI and CQI, and B is fixed in the specification or B is reported by the UE as a capability.

[0152] Example 19 may include a method for a user equipment (UE) that includes: The system receives configuration information for Channel State Information (CSI) resources, wherein the first CSI resource crosses a Physical Resource Block (PRB) boundary in the frequency domain and / or a Time Slot boundary in the time domain; generates a CSI based on measurements of the CSI-Reference Signal (CSI-RS) in the corresponding CSI resource; and sends a CSI report with the CSI.

[0153] Example 20 may include the method of Example 19 and / or some other examples herein, wherein the CSI includes a rank indicator (RI), a precoding matrix indicator (PMI), and / or a channel quality indicator (CQI).

[0154] Example 21 may include the methods of Examples 19-20 and / or some other examples herein, wherein the CSI resources correspond to more than 32 CSI-RS ports.

[0155] Example 22 may include the methods of Examples 19-21 and / or some other examples herein, wherein the configuration information includes a bitmap to indicate the initial subcarriers for the first CSI resource.

[0156] Example 23 may include the method of Example 22 and / or some other examples herein, wherein the bitmap comprises N bits, and wherein the first CSI-RS resource is repeated every 2N subcarriers.

[0157] Example 24 may include the method of Example 23 and / or some other examples in this document, wherein the CSI-RS resource is further repeated every M PRBs.

[0158] Example 25 may include the methods of Examples 19-24 and / or some other examples herein, wherein the configuration information includes offsets for one or more subcarriers of a first CSI-RS resource and / or a set of CSI-RS resources, and wherein the initial subcarriers of the first CSI-RS resource are shifted according to the offsets.

[0159] Example 26 may include the methods of Examples 19-25 and / or some other examples herein, wherein the first CSI-RS resource is repeated every 1 / ρ PRB in the frequency domain, where 1 / ρ is not an integer.

[0160] Example 27 may include the method of Example 26 and / or some other examples in this document, wherein the configuration information indicates the value of ρ.

[0161] Example 28 may include the methods of Examples 19-27 and / or some other examples herein, wherein the first CSI-RS resource spans a time slot boundary in the time domain, wherein the first initial symbol of the first CSI-RS resource is configured in the first time slot, l(1)<14, and the second initial symbol of the first CSI-RS resource is configured in the second time slot, l(2)≥14.

[0162] Example 29 may include the methods of Examples 19-28 and / or some other examples herein, wherein the number of ports across CSI-RS resources is greater than the number of CSI-RS ports used to generate CSI.

[0163] Example 30 may include the methods of Examples 19-29 and / or some other examples herein, wherein the configuration information indicates the corresponding number of ports for each CSI-RS resource.

[0164] Example 31 may include the methods of Examples 19-29 and / or some other examples herein, wherein the configuration information indicates the corresponding slot offset for the aperiodic CSI-RS for each CSI-RS resource.

[0165] Example 32 may include the methods of Examples 19-31 and / or some other examples herein, wherein the number of CSI processing units (CPUs) occupied by the CSI report is ceil(PPMI / T), where ceil() is a round-up function, PPMI is the number of CSI-RS ports used for CSI, and T is fixed or indicated by the UE in the capability information.

[0166] Example 33 may include the methods of Examples 19-31 and / or some other examples herein, wherein the number of CSI processing units (CPUs) occupied by the CSI report is T·K+U or ceil(T·K+U), where K is the number of CSI resources used in the CSI report, and T and / or U are predefined or indicated by the UE in the capability information.

[0167] Example 34 may include the methods of Examples 19-33 and / or some other examples herein, and may also include: encoding capability information for transmission, wherein the capability information indicates the number of active CSI-RS resources supported by the UE.

[0168] Example 35 may include a method for a gNodeB (gNB) comprising: encoding configuration information of a Channel State Information (CSI) resource for transmission to a User Equipment (UE), wherein a first CSI resource in the CSI resource crosses a Physical Resource Block (PRB) boundary in the frequency domain and / or a timeslot boundary in the time domain; and receiving a CSI report with CSI from the UE based on the CSI resource.

[0169] Example 36 may include the method of Example 35 and / or some other examples herein, wherein the CSI includes a rank indicator (RI), a precoding matrix indicator (PMI), and / or a channel quality indicator (CQI).

[0170] Example 37 may include the methods of Examples 35-36 and / or some other examples herein, wherein the CSI resource corresponds to more than 32 CSI-RS ports.

[0171] Example 38 may include the methods of Examples 35-37 and / or some other examples herein, wherein the configuration information includes a bitmap to indicate the initial subcarriers for the first CSI resource.

[0172] Example 39 may include the method of Example 38 and / or some other examples herein, wherein the bitmap comprises N bits, and wherein the first CSI-RS resource repeats every 2N subcarriers.

[0173] Example 40 may include the method of Example 39 and / or some other examples in this document, wherein the CSI-RS resource is further repeated every M PRBs.

[0174] Example 41 may include the methods of Examples 35-40 and / or some other examples herein, wherein the configuration information includes offsets for one or more subcarriers of a first CSI-RS resource and / or a set of CSI-RS resources, and wherein the initial subcarriers of the first CSI-RS resource are shifted according to the offsets.

[0175] Example 42 may include the methods of Examples 35-41 and / or some other examples herein, wherein the first CSI-RS resource is repeated every 1 / ρ PRB in the frequency domain, where 1 / ρ is not an integer.

[0176] Example 43 may include the method of Example 42 and / or some other examples in this document, wherein the configuration information indicates the value of ρ.

[0177] Example 44 may include the methods of Examples 35-43 and / or some other examples herein, wherein the first CSI-RS resource spans a time slot boundary in the time domain, wherein a first initial symbol of the first CSI-RS resource is configured in a first time slot, l(1)<14, and a second initial symbol of the first CSI-RS resource is configured in a second time slot, l(2)≥14.

[0178] Example 45 may include the methods of Examples 35-44 and / or some other examples herein, wherein the number of ports across CSI-RS resources is greater than the number of CSI-RS ports used to generate CSI.

[0179] Example 46 may include the methods of Examples 35-45 and / or some other examples herein, wherein the configuration information indicates the corresponding number of ports for each CSI-RS resource.

[0180] Example 47 may include the methods of Examples 35-46 and / or some other examples herein, wherein the configuration information indicates the corresponding slot offset for the aperiodic CSI-RS for each CSI-RS resource.

[0181] Example 48 may include the methods of Examples 35-47 and / or some other examples herein, wherein the number of CSI processing units (CPUs) occupied by the CSI report is ceil(PPMI / T), where ceil() is a round-up function, PPMI is the number of CSI-RS ports used for CSI, and T is fixed or indicated by the UE in the capability information.

[0182] Example 49 may include the methods of Examples 35-47 and / or some other examples herein, wherein the number of CSI processing units (CPUs) occupied by the CSI report is T·K+U or ceil(T·K+U), where K is the number of CSI resources used in the CSI report, and T and / or U are predefined or indicated by the UE in the capability information.

[0183] Example 50 may include the methods of Examples 35-49 and / or some other examples herein, and may also include: encoding capability information for transmission, wherein the capability information indicates the number of active CSI-RS resources supported by the UE.

[0184] Example 51 may include the methods of Examples 35-50 and / or some other examples herein, and may also include: sending CSI-RS in the appropriate CSI-RS resource.

[0185] Example 52 may include a method to be performed by a user equipment (UE), one or more elements of the UE, and / or one or more electronic devices including and / or implementing the UE, wherein the method includes: identifying CSI-RS information received from more than 32 Channel State Information (CSI)-Reference Signal (RS) ports of a base station of a cellular network; performing one or more CSI measurements on the CSI-RS information received from a subset of the more than 32 CSI-RS ports, wherein the subset of CSI-RS ports includes 32 or fewer CSI-RS ports; and generating a CSI report based on the CSI measurements, the CSI report including CSI values ​​associated with the more than 32 CSI-RS ports.

[0186] Example 53 may include the method of Example 52 and / or one or more other examples herein, wherein more than 32 CSI-RS ports span a Physical Resource Block (PRB) boundary in the frequency domain.

[0187] Example 54 may include the method of any of Examples 52-53 and / or one or more other examples herein, wherein more than 32 CSI-RS ports span time slot boundaries in the time domain.

[0188] 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 the rank indicator (RI) value associated with more than 32 CSI-RS ports.

[0189] 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 associated with more than 32 CSI-RS ports.

[0190] 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 associated with more than 32 CSI-RS ports.

[0191] 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 the corresponding RS sent from the corresponding CSI-RS port among more than 32 CSI-RS ports.

[0192] Example 59 may include the methods of any of Examples 52-58 and / or one or more other examples herein, and may also include: the number of occupied CSI processing units (CPUs) identified by the UE for performing one or more CSI measurements or generating CSI reports based on the number of more than 32 CSI-RS ports.

[0193] Example 60 may include the method of Example 59 and / or one or more other examples herein, wherein the method further includes: identifying a previous CSI report by the UE; and identifying whether the generation of the CSI report includes updating the previous CSI report based on the amount of CPU used.

[0194] Example 61 may include the methods of any of Examples 52-60 and / or one or more other examples herein, and further includes: identifying the number of active CSI resources associated with more than 32 CSI-RS ports; and determining, based on the number of active CSI resources, whether the generation of the CSI report includes updating previous CSI reports.

[0195] Example 62 may include a method to be performed by a base station, one or more elements of the base station, and / or one or more electronic devices including and / or implementing the base station, wherein the method includes: transmitting CSI-RS information from more than 32 Channel State Information (CSI)-Reference Signal (RS) ports of the base station; and identifying a CSI report from a UE, the CSI report including CSI values ​​associated with more than 32 CSI-RS ports, wherein the CSI values ​​are based on one or more CSI measurements performed by the UE on CSI-RS information received from a subset of more than 32 CSI-RS ports, wherein the subset of CSI-RS ports includes 32 or fewer CSI-RS ports.

[0196] Example 63 may include the method of Example 62 and / or one or more other examples herein, wherein more than 32 CSI-RS ports span a Physical Resource Block (PRB) boundary in the frequency domain.

[0197] Example 64 may include the method of any of Examples 62-63 and / or one or more other examples herein, wherein more than 32 CSI-RS ports span time slot boundaries in the time domain.

[0198] 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 the rank indicator (RI) value associated with more than 32 CSI-RS ports.

[0199] 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 associated with more than 32 CSI-RS ports.

[0200] 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 associated with more than 32 CSI-RS ports.

[0201] 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 the corresponding RS transmitted from the corresponding CSI-RS port among more than 32 CSI-RS ports of the base station.

[0202] Example 69 may include the method of any of Examples 62-68 and / or one or more other examples herein, and further includes: identifying, based on the number of more than 32 CSI-RS ports, the number of occupied CSI processing units (CPUs) that support the transmission of CSI-RS information from more than 32 CSI-RS ports.

[0203] Example Z01 may include an apparatus comprising one or more elements of the methods described in or associated with any of Examples 1-69, and / or any other methods or processes described herein.

[0204] Example Z02 may include one or more non-transitory computer-readable media, including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the methods described in or associated with any of Examples 1-69, and / or any other methods or processes described herein.

[0205] Example Z03 may include an apparatus, including logic, modules, or circuits, to perform one or more elements of the methods described in or associated with any of Examples 1-69, and / or any other methods or processes described herein.

[0206] Example Z04 may include methods, techniques, or processes, and / or parts or components thereof, as described in or related to any of Examples 1-69.

[0207] Example Z05 may include an apparatus comprising: one or more processors; and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, and / or a portion thereof, as described in or related to any of Examples 1-69.

[0208] Example Z06 may include a signal, or a portion thereof, as described in or associated with any of Examples 1-69.

[0209] Example Z07 may include datagrams, packets, frames, segments, protocol data units (PDUs) or messages as described in or associated with any of Examples 1-69, and / or portions or components thereof, or otherwise described in this disclosure.

[0210] Example Z08 may include signals encoded with data as described in or associated with any of Examples 1-69, and / or portions or components thereof, or otherwise described in this disclosure.

[0211] Example Z09 may include signals encoded in datagrams, packets, frames, segments, protocol data units (PDUs) or messages as described in or associated with any of Examples 1-69, and / or portions or components thereof, or otherwise described in this disclosure.

[0212] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause one or more processors to perform a method, technique, or process, and / or a portion thereof, as described in or related to any of Examples 1-69.

[0213] Example Z11 may include a computer program, including instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process, and / or a portion thereof, as described in or related to any of Examples 1-69.

[0214] Example Z12 may include a signal in a wireless network as shown in the figure and described herein.

[0215] Example Z13 may include a method of communication in a wireless network as shown in the figure and described herein.

[0216] Example Z14 may include a system for providing wireless communication, as shown in the figure and described herein.

[0217] Example Z15 may include a device for providing wireless communication, as shown in the figure and described herein.

[0218] Unless otherwise expressly stated, any of the examples described above can be combined with any other example (or combination of examples). The foregoing description of one or more implementations provides illustrations and descriptions, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations can be made, or modifications and variations can be obtained from practice of various embodiments.

Claims

1. An apparatus for a user equipment (UE), wherein, The device includes: A memory, the memory being used to store CSI-RS information received from more than 32 Channel State Information (CSI)-Reference Signal (RS) ports of a base station of a cellular network; and One or more processors, said one or more processors being configured to: Perform one or more CSI measurements on CSI-RS information received from a subset of the more than 32 CSI-RS ports, wherein the subset of CSI-RS ports comprises 32 or fewer CSI-RS ports; and Based on the CSI measurements, a CSI report is generated that includes CSI values ​​associated with the more than 32 CSI-RS ports.

2. The apparatus of claim 1, wherein, The more than 32 CSI-RS ports span the Physical Resource Block (PRB) boundary in the frequency domain.

3. The apparatus of claim 1, wherein, The more than 32 CSI-RS ports span time slot boundaries in the time domain.

4. The apparatus of claim 1, wherein, The CSI value is the rank indicator (RI) value associated with the more than 32 CSI-RS ports.

5. The apparatus of claim 1, wherein, The CSI value is the precoding matrix indicator (PMI) value associated with the more than 32 CSI-RS ports.

6. The apparatus of claim 1, wherein, The CSI value is the Channel Quality Indicator (CQI) value associated with the more than 32 CSI-RS ports.

7. The apparatus according to claim 1, wherein, The CSI-RS information includes the corresponding RS sent from the corresponding CSI-RS port among the more than 32 CSI-RS ports.

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

9. The apparatus according to claim 8, wherein, The one or more processors are further configured to: Identify previous CSI reports; and Based on the amount of CPU used, determine whether the generation of the CSI report includes updating the previous CSI report.

10. The apparatus according to any one of claims 1-7, further comprising: Identify the number of active CSI resources associated with the more than 32 CSI-RS ports; as well as Based on the number of active CSI resources, determine whether the generation of the CSI report includes updating the previous CSI report.

11. One or more computer-readable media, including instructions that, when executed by one or more processors of an electronic device, cause a base station to: CSI-RS information is transmitted from more than 32 Channel State Information (CSI)-Reference Signal (RS) ports of the base station; and Identify CSI reports from the UE, the CSI reports including CSI values ​​associated with the more 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 more than 32 CSI-RS ports, wherein the subset of CSI-RS ports includes 32 or fewer CSI-RS ports.

12. One or more computer-readable media according to claim 11, wherein, The more than 32 CSI-RS ports span the Physical Resource Block (PRB) boundary in the frequency domain.

13. One or more computer-readable media according to claim 11, wherein, The more than 32 CSI-RS ports span time slot boundaries in the time domain.

14. One or more computer-readable media according to claim 11, wherein, The CSI values ​​are the rank indicator (RI) values ​​associated with the more than 32 CSI-RS ports, the precoding matrix indicator (PMI) values ​​associated with the more than 32 CSI-RS ports, or the channel quality indicator (CQI) values ​​associated with the more than 32 CSI-RS ports.

15. One or more computer-readable media according to any one of claims 11-14, wherein, The CSI-RS information includes the corresponding RS transmitted from the corresponding CSI-RS port among the more than 32 CSI-RS ports of the base station.

16. One or more computer-readable media according to any one of claims 11-14, wherein, The instructions also enable the base station to: identify the number of occupied CSI processing units (CPUs) based on the number of more than 32 CSI-RS ports, wherein the occupied CSI processing units (CPUs) support the transmission of the CSI-RS information from the more than 32 CSI-RS ports.

17. One or more computer-readable media, including instructions that, when executed by one or more processors of an electronic device, cause a user equipment (UE) to: Identify channel CSI-RS information received from more than 32 channel state information (CSI)-reference signal (RS) ports of a base station in a cellular network; For CSI-RS information received from a subset of the more than 32 CSI-RS ports, perform one or more CSI measurements, wherein, The subset of CSI-RS ports comprises 32 or fewer CSI-RS ports; and Based on the CSI measurements, a CSI report is generated that includes CSI values ​​associated with the more than 32 CSI-RS ports.

18. One or more computer-readable media according to claim 17, wherein, The more than 32 CSI-RS ports span physical resource block (PRB) boundaries in the frequency domain or time slot boundaries in the time domain.

19. One or more computer-readable media according to any one of claims 17-18, wherein, The instructions also instruct the UE to: identify the number of occupied CSI processing units (CPUs) based on the number of the more than 32 CSI-RS ports, wherein the occupied CSI processing units (CPUs) perform the one or more CSI measurements or generate the CSI report.

20. One or more computer-readable media according to any one of claims 17-18, wherein, The instruction also causes the UE to: Identify the number of active CSI resources associated with the more than 32 CSI-RS ports; as well as Based on the number of active CSI resources, determine whether the generation of the CSI report includes updating the previous CSI report.

Images