WO2024097003A1

WO2024097003A1 - Linear combination coefficient encoding for channel state information reporting in multi-transmission reception point coherent joint transmission

Info

Publication number: WO2024097003A1
Application number: PCT/US2023/034775
Authority: WO
Inventors: Haitong Sun; Ismael GUTIERREZ GONZALEZ; David Neumann; Dawei Zhang; Wei Zeng; Weidong Yang; Ghaith HATTAB; Louay Jalloul
Original assignee: Apple Inc.
Priority date: 2022-11-04
Filing date: 2023-10-10
Publication date: 2024-05-10

Abstract

Apparatus, processors, and methods are provided for channel state information (CSI) reporting for coherent joint transmission using multiple transmission reception points (TRPs). In one example, a baseband processor of a user equipment (UE), is configured to, based on channel state information (CSI) measurement resources transmitted by a plurality of transmission reception points (TRPs), determine a plurality of non-zero coefficients (NZCs) corresponding to linear combination coefficients. The baseband processor selects reported NZCs from the plurality of NZCs, wherein respective sets of reported NZCs are associated with respective transmission layers, wherein at least one of the sets of reported NZCs includes NZCs associated with at least two different TRPs. The baseband processor is configured to generate a CSI report that encodes, for each transmission layer, information about the reported NZCs and transmit the CSI report.

Description

LINEAR COMBINATION COEFFICIENT ENCODING FOR CHANNEL STATE INFORMATION REPORTING IN MULTI-TRANSMISSION RECEPTION POINT COHERENT JOINT TRANSMISSION

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of priority from U.S. Provisional Patent Application Serial No. 63/422,737, entitled LINEAR COMBINATION COEFFICIENT ENCODING FOR CHANNEL STATE INFORMATION REPORTING IN MULTITRANSMISSION RECEPTION POINT COHERENT JOINT TRANSMISSION, filed on November 4, 2022, the contents of which are incorporated herein by reference in their entirety.

BACKGROUND

[0002] Multi-transmission reception point (TRP) communication involves a user equipment (UE) exchanging signals with more than one TRP. The multiple TRPs may be integrated into a same base station or different base stations. A UE may communicate with different TRPs using different beams. The data transmitted and received between the UE and the multiple TRPs may be jointly processed to improve reliability, coverage, and capacity performance through flexible deployment scenarios. In multi-TRP coherent joint transmission, a single transmission layer includes transmissions from multiple TRPs.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Some examples of circuits, apparatuses and/or methods will be described in the following by way of example only. In this context, reference will be made to the accompanying figures.

[0004] FIG. 1A illustrates a UE receiving channel state information (CSI) measurement resources from multiple TRPs and transmitting a CSI report based on measurements of the CSI measurement resources, in accordance with various aspects described. [0005] FIG. IB illustrates a UE receiving a coherent joint transmission of physical downlink shared channel (PDSCH) from multiple TRPs, in accordance with various aspects described.

[0006] FIG. 2 illustrates an example codebook for a transmission layer, in accordance with various aspects described.

[0007] FIG. 3 illustrates an example linear' combination coefficient matrix for a given TRP, including eight spatial bases, four frequency bases and two polarities, in accordance with various aspects described.

[0008] FIG. 4 illustrates an example message sequence including communication of a CSI report and PDSCH using multi-TRP coherent joint transmission, in accordance with various aspects described.

[0009] FIG. 5 is a diagram of an example network according to one or more implementations described herein.

[0010] FIG. 6 illustrates a simplified block diagram of a user equipment wireless communication device, in accordance with various aspects described.

DETAILED DESCRIPTION

[0011] The present disclosure is described with reference to the attached figures. The figures are not drawn to scale and they are provided merely to illustrate the disclosure. Several aspects of the disclosure are described below with reference to example applications for illustration. Numerous specific details, relationships, and methods are set forth to provide an understanding of the disclosure. The present disclosure is not limited by the illustrated ordering of acts or events, as some acts may occur in different orders and/or concurrently with other acts or events. Furthermore, not all illustrated acts or events are required to implement a methodology in accordance with the selected present disclosure.

Multi-TRP Coherent Joint Transmission

[0012] Multiple input, multiple output (MIMO) communication systems utilize joint transmission in which transmit signals from multiple antennas are jointly processed at a receiving device. A set of signals that are jointly processed at the receiving device is referred to as a transmission layer. Each signal in the transmission layer is referred to as a spatial stream. Each spatial stream corresponds to a set of precoder settings applied to a particular antenna/polarity combination, or spatial basis.

[0013] There are two types of joint transmission, non-coherent joint transmission (NCJT) and coherent joint transmission (CJT). In CJT, the network performs beamforming with multiple transmission points and selects beamforming coefficients (phase and amplitude) for the spatial streams transmitted by each antenna so that, together, the spatial streams focus the transmission energy at the UE. In order to support CIT, the network uses knowledge about the downlink channels for each antenna, or may use the same downlink channel information when the antennas arc co-locatcd. In NCJT the network docs not coordinate the spatial streams from the different antennas to focus energy at the UE and the spatial streams are received independently by the UE.

[0014] Previous releases of the 3GPP specification support NCJT for multi-TRP use cases, however the standard does not currently support non-transparent CJT for multi-TRP use cases. Due to the detailed channel information needed to support CJT in multi-TRP use cases, existing channel state information (CSI) reporting should be extended to allow for reporting of CSI for several (e.g., up to four) different TRPs, which may not be co-located.

[0015] Referring now to FIGs. 1A and IB, a wireless communication network 100 is illustrated that includes UE 101 and two TRPs 110, 120. Multi-TRP CJT is used to transmit a physical downlink shared channel (PDSCH) in two transmission layers from the TRPs 110, 120 to the UE 101. The TRPs are illustrated as being located on different base stations, however, in other examples, the TRPs may be mounted on a same base station or on other structures. Each TRP is illustrated as having eight antenna elements, four antenna elements having horizontal polarity and four antenna elements having vertical polarity (each pair of elements with opposite polarities are illustrated by the bold Xs in FIGs. 1A and IB. Thus, in the illustrated network there are 2x8 or 16 spatial bases (8 spatial bases for each TRP). In the illustrated example, the UE has two receiving antennas and thus two transmission layers may be used for CJT. The number of transmission layers may be signaled via a rank indicator (RI) value. [0016] As shown in FIG. 1A, the UE 101 has been pre-configured with a codebook (e.g., a type II MIMO codebook) that defines indices used by the UE to indicate, in a CSI report, which beamforming coefficients should be used by the TRP for each transmission layer. Each TRP 110, 120 transmits CSI measurement resources (e.g., CSI-RS), which are received and measured by the UE to determine the best beams and corresponding beamforming coefficients for downlink CJT. Indices of the coefficients are reported by the UE in the CSI report per the codebook. As illustrated in FIG. IB, the TRPs set their corresponding beamforming coefficients to transmit the PDSCH in transmission layer 1 and transmission layer 2 to the UE.

[0017] The CSI report includes a precoder matrix indicator (PMI) component that encodes the spatial bases, the frequency bases, and the corresponding coefficients selected by the UE. FIG. 2 illustrates one example of a codebook (W^l ) that encodes the precoding information for a transmission layer 1 using three matrices. A Wi matrix indicates which of the spatial bases are selected subject to a network configured maximum per transmission layer (e.g., 8 in some examples). A matrix indicates which of several configured frequency bases are selected for each spatial basis.

matrix for each transmission layer is included in the codebook and corresponds to a compressed matrix specifying linear combination coefficients that are to be applied to the selected spatial bases indicated in the W i matrix and the frequency bases indicated in the W ¹ matrix. When multi-TRP CJT is used, there may be two different type II codebook structures. A first codebook structure allows for different linear combination coefficients to be specified for different TRPs, while in another codebook structure it is assumed that the same linear combination coefficients are used for all the TRPs. Different techniques for encoding the W2 matrix for transmission in a CSI report are disclosed herein.

[0018] FIG. 3 illustrates an example W2 matrix for a single transmission layer for a single TRP. Each row in the matrix corresponds to one of the spatial bases selected by the Wi matrix and each column corresponds to one of the frequency bases selected by the W ¹ matrix. Each cell in the W2 matrix represents a coefficient having an amplitude quantization and phase quantization that would be applied to the spatial basis and frequency basis. In some configurations, the spatial bases are selected such that half of the spatial bases are of one polarity and half of the spatial bases are of the other polarity. Further, the spatial bases may be selected such that pairs of spatial bases corresponding to a same antenna with a first spatial basis in the pair having a first polarity and the second spatial basis in the pair having a second polarity. A general case is illustrated in FIG. 3 in which the spatial bases are not so constrained.

[0019] Each shaded cell indicates a non-zero linear combination coefficient (hereinafter nonzero coefficient or NZC) for a downlink beam of sufficient strength sensed by the UE whilst the unshaded cells correspond to coefficients that correspond to downlink beams that were not detected or did not meet a threshold strength. The W2 matrix is encoded in the CSI report by first identifying locations of the NZCs in the matrix and then indicating, for each NZC, the corresponding amplitude quantization and phase quantization. The number of NZCs that are included in the CSI report may be limited by the network. Thus, all of the NZCs for the beams detected by the UE as shown in the W2 matrix of FIG. 3 may not be reported. Certain of the NZCs will be selected by the UE for inclusion in the CSI report and these NZCs are referred to herein as reported NZCs.

[0020] In multi-TRP CJT, for each transmission layer there is a W2 matrix for each TRP. As the number of transmission layers and TRPs increases, the number of reported NZCs that are to be encoded in the CSI report increases. The construction of the CSI report should feature efficient encoding of the location, phase quantization, and amplitude quantization of the W2 matrix to conserve signaling overhead.

[0021] FIG. 4 is a message flow diagram outlining multi-TRP CJT. The UE is preconfigured with a type II MIMO codebook and a CSI report configuration that specifies parameters for the quantities to be reported, the format of the report, and so on. At 410, the TRPs transmit CSI measurement resources. The UE measures the measurement resources, selects preferred beams and ranks the beams based on strength, and generates the CSI report based on the codebook to report information about the prcfeiTcd beams including the Wi, W2 (one matrix for each transmission layer and TRP), W3 matrices. At 420 the UE transmits the CSI report to at least one of the TRPs or another node that is coordinating the multi-TRP CJT. At 430 the multiple TRPs transmit a PDSCH in one or more transmission layers according to the codebook reported by the UE in the CSI. [0022] Several techniques for encoding the reported NZC locations, as well as indications of the phase quantization information and amplitude quantization information for each reported NZC in the CSI report will now be disclosed. Depending on use cases, the different disclosed approaches may be optionally configured or dynamically indicated.

Location and Number of Reported NZCs

[0023] There are several approaches to encoding NZC locations. The locations of the reported NZCs may be independently encoded on a per transmission layer basis (meaning that the NZC locations may be different for different transmission layers), a per transmission layer and polarization and TRP basis (meaning that the NZC locations may be different for each unique combination of transmission layer/polarization/TRP), or a per TRP basis (meaning that the NZC locations may be different for different TRPs), or a per transmission layer and TRP basis (meaning that the NZC locations may be different for each unique combination of transmission layer/TRP). The locations of the reported NZCs may be commonly encoded on a per transmission layer basis (meaning that the NZC locations are the same for all transmission layers), a per transmission layer and polarization and TRP basis (meaning that the NZC locations are the same for each unique combination of transmission layer/polarization/TRP), or a per TRP basis (meaning that the NZC locations are the same across all TRPs).

[0024] There are several approaches to configuring a maximum number of reported NZCs. In one example, the network can configure a maximum number of reported NZCs per transmission layer, KNZC, without an upper limit on a total number of reported NZCs. In another example, the network can configure a maximum number of reported NZCs per transmission layer (KNZC) and a transmission layer threshold. In this case the maximum total number of reported NZCs is calculated as the transmission layer threshold multiplied by KNZC. For example, if the transmission layer threshold is 2, then the number of reported NZCs for any transmission layer cannot exceed KNZC, and the total number reported NZCs across all transmission layers cannot exceed 2 ■ KNZC. In other examples, the network can configure a maximum number of reported NZCs per transmission layer per polarization or per transmission layer per TRP, or any other combination of transmission layer, frequency, polarization, and/or TRP. [0025] In one example, the UE may be configured to select a number of reported NZCs that is equal to the configured maximum number of reported NZCs. In another example, the UE may be enabled to select a number of reported NZCs that is less than or equal to the configured maximum number of reported NZCs and report the number of reported NZCs in the CSI report (e.g., in CSI pail 1 or CSI part 2).

Reporting Groups

[0026] To efficiently encode the indication of the phase quantization and amplitude quantization for each reported NZC, the reported NZCs may be grouped into one or more multiple groups, with each group including a reference NZC. Different reporting groups may be used for phase quantization reporting and amplitude quantization reporting. In the following description the multiple groups are indicated as w₂ g, g = 1,2,...,G. G is the number of groups and {w₂}_g represents all the NZC in group g. Within each group one NZC is selected as the reference NZC, denoted as (w₂ )g . The remaining NZCs in the group are denoted as {W₂ g\(W₂ g where \ is the set subtraction operation indicating all the NZCs in {w₂}₅ excluding (w₂)₅.

[0027] The reported NZCs may be divided into reporting groups based on different criteria. In one example, the reported NZCs are grouped into a different reporting group for each transmission layer, regardless of polarization. In another example, the reported NZCs may be grouped into a single reporting group that includes all the reported NZCs. In another example, the reported NZCs are grouped into a different reporting group for each polarization. In another example, the reported NZCs are grouped into a different reporting group on a per transmission layer and per polarization basis.

[0028] In another example, the reported NZCs are grouped into a different groups on a per transmission layer per TRP basis or a per transmission layer per TRP group basis. In this example, all the reported NZCs associated with the same TRP or TRP group in the same transmission layer are in the same reporting group regardless of polarization. Each TRP or TRP group may be represented by one CSI-RS (e.g., channel measurement resource). [0029] In another example, the reported NZCs are grouped into a different groups on a per transmission layer per TRP per polarization basis or a per transmission layer per TRP group per polarization basis. In this example, all the reported NZCs associated with the same TRP or TRP group in the same transmission layer are separated into reporting groups based on polarization. Each TRP or TRP group may be represented by one CSI-RS (e.g., channel measurement resource).

Phase Encoding

[0030] In one example, for phase encoding, among all of the reference NZCs (w^)g, g = 1,2,...,G, one reference NZC is identified as a primary reference NZC

The phase of W2 is assumed to be zero and is not reported. In one example, the other reference NZCs ((w₂)g\ W₂) are phase quantified and reported based on the phase difference between the phase of the corresponding NZC and the phase of the reference NZC. In another example, the other reference NZCs ((w₂)g\ W₂) are assumed to have zero phase and are not reported (e.g., a phase quantization value is not included in the CSI report which indicates a zero value).

[0031] In one example, the phase quantization of the remaining NZCs (e.g., non-reference NZCs) are differentially encoded with respect to the reference NZC for their respective group g In one example, the phase quantization of the remaining NZCs (e.g., non-reference NZCs) are differentially encoded with respect to the primary reference NZC W₂ .

[0032] In one example, the phase quantization of each reference NZC (w^g encoded using a larger number of bits (e.g., 4 bits) whilst the phase quantization of the remaining NZCs

(i. e., (w₂ \ (w^g) are each encoded using a smaller number of bits (e.g., 3 bits).

Amplitude Encoding

[0033] In one example, for amplitude encoding, among all of the reference NZCs (w₂)g, g = 1,2,...,G, one reference NZC is identified as a primary reference NZC W₂ . The amplitude of W₂ is assumed to be one and is not reported. In one example, the other reference NZCs (O₂*)₅\ W2) are amplitude quantified and reported based on a ratio between the amplitude of the corresponding NZC and the amplitude of the reference NZC. In another example, the other reference NZCs {

g\ W2) are assumed to have amplitude of one and arc not reported (e.g., a amplitude quantization value is not included in the CSI report which indicates a value of one).

[0034] In one example, the amplitude quantization of the remaining NZCs (e.g., nonreference NZCs) are differentially encoded with respect to the reference NZC for their respective group g In one example, the amplitude quantization of the remaining NZCs (e.g., nonreference NZCs) are differentially encoded with respect to the primary reference NZC W₂ .

[0035] In one example, the amplitude quantization of each reference NZC (w^g i^s encoded using a larger number of bits (e.g., 4 bits) whilst the amplitude quantization of the remaining

NZCs (i. e., [w₂ } are each encoded using a smaller number of bits (e.g., 3 bits). 9

[0036] FIG. 5 is an example network 500 according to one or more implementations described herein. Example network 500 may include UEs 101-1, 101-2, etc. (referred to collectively as “UEs 101” and individually as “UE 101”), a radio access network (RAN) 520, a core network (CN) 530, application servers 540, and external networks 550.

[0037] The systems and devices of example network 500 may operate in accordance with one or more communication standards, such as 2nd generation (2G), 3rd generation (3G), 4th generation (4G) (e.g., long-term evolution (LTE)), and/or 5th generation (5G) (e.g., new radio (NR)) communication standards of the 3rd generation partnership project (3GPP). Additionally, or alternatively, one or more of the systems and devices of example network 500 may operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc.), institute of electrical and electronics engineers (IEEE) standards (e.g., wireless metropolitan area network (WMAN), worldwide interoperability for microwave access (WiMAX), etc.), and more.

[0038] As shown, UEs 101 may include smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more wireless communication networks). Additionally, or alternatively, UEs 101 may include other types of mobile or non-mobile computing devices capable of wireless communications, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, etc. In some implementations, UEs 101 may include internet of things (loT) devices (or loT UEs) that may comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections.

[0039] UEs 101 may communicate and establish a connection with (e.g., be communicatively coupled) with RAN 520, which may involve one or more wireless channels 514-1 and 514-2, each of which may comprise a physical communications interface / layer.

[0040] As described herein, a UE 101-2 may operate in multi-TRP mode in which the UE is simultaneously communicating with multiple transmission reception points (TRPs) (e.g., a TRP associated with network node 522-1 and a TRP associated with network node 522-2) in multi- TRP CJT. The UE 101-2 is configured to receive, store, and process multi-TRP CJT CSI report information that causes the UE 101-2 to perform functions described above with respect to encoding a CSI report for multi-TRP CJT. The multi-TRP CJT CSI report information may include instructions or algorithms used by the UE for determining how to encode determined linear combination coefficients according to a MIMO type II codebook for within a CSI report.

[0041] As shown, UE 101 may also, or alternatively, connect to access point (AP) 516 via connection interface 518, which may include an air interface enabling UE 101 to communicatively couple with AP 516. AP 516 may comprise a wireless local area network (WLAN), WLAN node, WLAN termination point, etc. The connection to AP 516 may comprise a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and AP 516 may comprise a wireless fidelity (Wi-Fi®) router or other AP. While not explicitly depicted in FIG. 5, AP 516 may be connected to another network (e.g., the Internet) without connecting to RAN 520 or CN 530.

[0042] RAN 520 may include one or more RAN nodes 522-1 and 522-2 (referred to collectively as RAN nodes 522, and individually as RAN node 522) that enable channels 514-1 and 514-2 to be established between UEs 101 and RAN 520. RAN nodes 522 may include network access points configured to provide radio baseband functions for data and/or voice connectivity between users and the network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi, etc.). As examples therefore, a RAN node may be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc.), a next generation base station (e.g., a 5G base station, NR base station, next generation eNBs (gNB), etc.). RAN nodes 522 may include a roadside unit (RSU), a transmission reception point (TRxP or TRP), and one or more other types of ground. In some scenarios, RAN node 522 may be a dedicated physical device, such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or the like having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0043] The PDSCH may carry user data and higher layers signaling to UEs 101. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. The PDCCH may also inform UEs 101 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (e.g., assigning control and shared channel resource blocks to UE 101-2 within a cell) may be performed at any of the RAN nodes 522 based on channel quality information fed back from any of UEs 101 based on the multi-TRP CJT CSI report information. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of UEs 101.

[0044] The RAN nodes 522 may be configured to communicate with one another via interface 523. In implementations where the system is an LTE system, interface 523 may be an X2 interface. In NR systems, interface 523 may be an Xn interface. The X2 interface may be defined between two or more RAN nodes 522 (e.g., two or more eNBs / gNBs or a combination thereof) that connect to evolved packet core (EPC) or CN 530, or between two eNBs connecting to an EPC.

[0045] As shown, RAN 520 may be connected (e.g., communicatively coupled) to CN 530. CN 530 may comprise a plurality of network elements 532, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs 101) who are connected to the CN 530 via the RAN 520. In some implementations, CN 530 may include an evolved packet core (EPC), a 5G CN, and/or one or more additional or alternative types of CNs. [0046] As shown, CN 530, application servers 540, and external networks 550 may be connected to one another via interfaces 534, 536, and 538, which may include IP network interfaces. Application servers 540 may include one or more server devices or network elements (e.g., virtual network functions (VNFs) offering applications that use IP bearer resources with CN 530 (e.g., universal mobile telecommunications system packet services (UMTS PS) domain, LTE PS data services, etc.). Application servers 540 may also, or alternatively, be configured to support one or more communication services (e.g., voice over IP (VoIP sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc.) for UEs 101 via the CN 530. Similarly, external networks 550 may include one or more of a variety of networks, including the Internet, thereby providing the mobile communication network and UEs 101 of the network access to a variety of additional services, information, interconnectivity, and other network features.

[0047] FIG. 6 is a diagram of an example of components of a device or apparatus of a UE according to one or more implementations described herein. In some implementations, the apparatus 600 can include application circuitry 602, baseband circuitry 604, RF circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown. The components of the illustrated apparatus 600 can be included in a UE (101 of FIG. 1) or a RAN node (e.g., TRPs 110, 120 of FIG. 1). In some implementations, the apparatus 600 can include fewer elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor/controller to process IP data received from a CN or an Evolved Packet Core (EPC)).

[0048] The application circuitry 602 can include one or more application processors. For example, the application circuitry 602 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with or can include memory/storage and can be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the UE. In some implementations, processors of application circuitry 602 can process IP data packets received from an EPC. [0049] The baseband circuitry 604 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 604 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606. Baseband circuitry 604 can interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606. For example, in some implementations, the baseband circuitry 604 can include a 3G baseband processor 604 A, a 4G baseband processor 604B, a 5G baseband processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., 5G, 6G, etc.). The baseband circuitry 604 (e.g., one or more of baseband processors 604A-D) can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 606. In other implementations, some or all of the functionality of baseband processors 604 A-D can be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E.

[0050] In some implementations, memory 604G may store and process multi-TRP CJT CSI report information that causes the UE to perform functions described above with respect to common beam management for multi-TRP operation. The multi-TRP CJT CSI report information may cause the UE 101 to perform functions described above with respect to encoding a CSI report for multi-TRP CJT. The multi-TRP CJT CSI report information may include instructions, that when executed by a BB processor 604C or CPU 604E, cause a UE to encode determined linear combination coefficients according to a MIMO type II codebook for within a CSI report.

[0051] In some implementations, the baseband circuitry 604 can include one or more audio digital signal processor(s) (DSP) 604F. The audio DSPs 604F can include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other implementations. Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some implementations. In some implementations, some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 can be implemented together such as, for example, on a system on a chip (SOC).

[0052] In some implementations, the baseband circuitry 604 can provide for communication compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 604 can support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), etc. Implementations in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

[0053] RF circuitry 606 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various implementations, the RF circuitry 606 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 606 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604. RF circuitry 606 can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.

[0054] In some implementations, the receive signal path of the RF circuitry 606 can include mixer circuitry 606A, amplifier circuitry 606B and filter circuitry 606C. In some implementations, the transmit signal path of the RF circuitry 606 can include filter circuitry 606C and mixer circuitry 606A. RF circuitry 606 can also include synthesizer circuitry 606D for synthesizing a frequency for use by the mixer circuitry 606A of the receive signal path and the transmit signal path.

[0055] While Fig. 6 shows the PMC 612 coupled only with the baseband circuitry 604. However, in other implementations, the PMC 612 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM circuitry 608. [0056] Processors of the application circuitry 602 and processors of the baseband circuitry 604 can be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 604, alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the baseband circuitry 604 can utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 can comprise a RRC layer, described in further detail below. As referred to herein, Layer 2 can comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 can comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

[0057] Above are several flow diagrams outlining example methods and exchanges of messages. In this description and the appended claims, use of the term “determine” with reference to some entity (e.g., parameter, variable, and so on) in describing a method step or function is to be construed broadly. For example, “determine” is to be construed to encompass, for example, receiving and parsing a communication that encodes the entity or a value of an entity. “Determine” should be construed to encompass accessing and reading memory (e.g., lookup table, register, device memory, remote memory, and so on) that stores the entity or value for the entity. “Determine” should be construed to encompass computing or deriving the entity or value of the entity based on other quantities or entities. “Determine” should be construed to encompass any manner of deducing or identifying an entity or value of the entity.

[0058] As used herein, the term identify when used with reference to some entity or value of an entity is to be construed broadly as encompassing any manner of determining the entity or value of the entity. For example, the term identify is to be construed to encompass, for example, receiving and parsing a communication that encodes the entity or a value of the entity. The term identify should be construed to encompass accessing and reading memory (e.g., device queue, lookup table, register, device memory, remote memory, and so on) that stores the entity or value for the entity. [0059] As used herein, the term encode when used with reference to some entity or value of an entity is to be construed broadly as encompassing any manner or technique for generating a data sequence or signal that communicates the entity to another component.

[0060] As used herein, the term select when used with reference to some entity or value of an entity is to be construed broadly as encompassing any manner of determining the entity or value of the entity from amongst a plurality or range of possible choices. For example, the term select is to be construed to encompass accessing and reading memory (e.g., lookup table, register, device memory, remote memory, and so on) that stores the entities or values for the entity and returning one entity or entity value from amongst those stored. The term select is to be construed as applying one or more constraints or rules to an input set of parameters to determine an appropriate entity or entity value. The term select is to be construed as broadly encompassing any manner of choosing an entity based on one or more parameters or conditions.

[0061] As used herein, the term derive when used with reference to some entity or value of an entity is to be construed broadly. “Derive” should be construed to encompass accessing and reading memory (e.g., lookup table, register, device memory, remote memory, and so on) that stores some initial value or foundational values and performing processing and/or logical/mathematical operations on the value or values to generate the derived entity or value for the entity. The term derive should be construed to encompass computing or calculating the entity or value of the entity based on other quantities or entities. The term derive should be construed to encompass any manner of deducing or identifying an entity or value of the entity.

[0062] As used herein, the term indicate when used with reference to some entity (e.g., parameter or setting) or value of an entity is to be construed broadly as encompassing any manner of communicating the entity or value of the entity either explicitly or implicitly. For example, bits within a transmitted message may be used to explicitly encode an indicated value or may encode an index or other indicator that is mapped to the indicated value by prior configuration. The absence of a field within a message may implicitly indicate a value of an entity based on prior configuration.

[0063] Examples herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine -readable medium including executable instructions that, when performed by a machine or circuitry (e.g., a processor (e.g., processor , etc.) with memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to implementations and examples described.

[0064] Example 1 is a baseband processor of a user equipment (UE), configured to based on channel state information (CSI) measurement resources transmitted by a plurality of transmission reception points (TRPs), determine a plurality of non-zero coefficients (NZCs) corresponding to linear combination coefficients; select reported NZCs from the plurality of NZCs, wherein respective sets of reported NZCs are associated with respective transmission layers, wherein at least one of the sets of reported NZCs includes NZCs associated with at least two different TRPs; generate a CSI report that encodes, for each transmission layer, information about the reported NZCs; and transmit the CSI report.

[0065] Example 2 includes the subject matter of example 1, including or omitting optional elements, wherein the CSI report independently encodes locations of NZPs within a preconfigured matrix on a per transmission layer basis, a per transmission layer and polarization and TRP basis, or a per TRP basis.

[0066] Example 3 includes the subject matter of example 1, including or omitting optional elements, wherein the CSI report commonly encodes locations of NZPs within a preconfigured matrix on a per transmission layer basis, a per transmission layer and polarization and TRP basis, or per TRP basis.

[0067] Example 4 includes the subject matter of example 1, including or omitting optional elements, further configured to determine the reported NZCs based on a network-configured maximum number of NZCs per transmission layer.

[0068] Example 5 includes the subject matter of example 4, including or omitting optional elements, wherein the network-configured maximum number of NZCs per layer is independent of a number of transmission layers. [0069] Example 6 includes the subject matter of example 4, including or omitting optional elements, further configured to determine the reported NZCs based on a network-configured maximum total number of NZCs across all transmission layers.

[0070] Example 7 includes the subject matter of example 6, including or omitting optional elements, wherein the maximum total number of NZCs is based on a preconfigured threshold number of selected transmission layers, such that the maximum total number of NZCs is based on the product of the maximum number of NZCs per transmission layer and the threshold number.

[0071] Example 8 includes the subject matter of example 1, including or omitting optional elements, further configured to determine the reported NZCs based on network-configured maximum numbers of NZCs per transmission layer and polarization or per transmission layer and TRP.

[0072] Example 9 includes the subject matter of example 1, including or omitting optional elements, further configured to select a number of reported NZPs that is less than or equal to a network-configured maximum number of NZCs; and indicate the selected number of reported NZCs in the CSI report.

[0073] Example 10 includes the subject matter of example 1, including or omitting optional elements, further configured to select a number of reported NZPs that is equal to a network- configured maximum number of NZCs.

[0074] Example 11 includes the subject matter of example 1, including or omitting optional elements, further configured to group the reported NZCs into a plurality of reporting groups, wherein each reporting group includes a reference NZC and zero or more remaining NZCs; and encode an indication of phase quantization or an indication of amplitude quantization for the reported NZCs based on the reporting groups.

[0075] Example 12 includes the subject matter of example 1 1 , including or omitting optional elements, further configured to group the reported NZCs into reporting groups on a per transmission layer basis. [0076] Example 13 includes the subject matter of example 11, including or omitting optional elements, further configured to group the reported NZCs into a single reporting group.

[0077] Example 14 includes the subject matter of example 11, including or omitting optional elements, further configured to group the reported NZCs into reporting groups on a per transmission layer and TRP basis or a per transmission layer and TRP group basis.

[0078] Example 15 includes the subject matter of example 11, including or omitting optional elements, further configured to group the reported NZCs into reporting groups on a per transmission layer and TRP and polarization basis.

[0079] Example 16 includes the subject matter of example 11, including or omitting optional elements, further configured to group the reported NZCs into reporting groups on a per polarization basis.

[0080] Example 17 includes the subject matter of example 11, including or omitting optional elements, further configured to group the reported NZCs into reporting groups on a per transmission layer and per polarization basis.

[0081 ] Example 18 includes the subject matter of example 11, including or omitting optional elements, further configured to, for the remaining NZCs in a reporting group, encode the indication of phase quantization based on a phase differential between the remaining NZC and the reference NZC for the group.

[0082] Example 19 includes the subject matter of example 11, including or omitting optional elements, wherein the indication of phase quantization for the reference NZCs does not encode phase quantization information indicating a value of zero.

[0083] Example 20 includes the subject matter of example 11, including or omitting optional elements, further configured to select one of the reference NZCs as a primary reference NZC; and for each the remaining NZCs in all the reporting groups, encode the indication of phase quantization based on a phase differential between the NZC and the primary reference NZC.

[0084] Example 21 includes the subject matter of example 11, including or omitting optional elements, further configured to, for the other reference NZCs, encode the indication of phase quantization based on a phase differential between the reference NZC and the primary reference NZC.

[0085] Example 22 includes the subject matter of example 20, including or omitting optional elements, wherein the indication of phase quantization indicates a phase quantization value of zero for the primary reference NZC by not encoding phase quantization information for the primary reference NZC.

[0086] Example 23 includes the subject matter of example 22, including or omitting optional elements, wherein the indication of phase quantization indicates a phase quantization value of zero for the reference NZCs by not encoding phase quantization information for the reference NZCs.

[0087] Example 24 includes the subject matter of example 11, including or omitting optional elements, further configured to quantize phase of the reference NZCs using more bits than a number of bits used to quantize the remaining NZCs.

[0088] Example 25 includes the subject matter of example 11, including or omitting optional elements, further configured to, for the remaining NZCs in a reporting group, encode the indication of amplitude quantization based on an amplitude differential between the remaining NZC and the reference NZC for the group.

[0089] Example 26 includes the subject matter of example 11, including or omitting optional elements, wherein the indication of amplitude quantization for the reference NZCs does not encode amplitude quantization information indicating a value of one.

[0090] Example 27 includes the subject matter of example 11, including or omitting optional elements, further configured to select one of the reference NZCs as a primary reference NZC; and for each the remaining NZCs in all the reporting groups, encode the indication of amplitude quantization based on an amplitude differential between the NZC and the primary reference NZC.

[0091 ] Example 28 includes the subject matter of example 27, including or omitting optional elements, further configured to, for the other reference NZCs, encode the indication of amplitude quantization based on a amplitude differential between the reference NZC and the primary reference NZC.

[0092] Example 29 includes the subject matter of example 27, including or omitting optional elements, wherein the indication of amplitude quantization indicates an amplitude quantization value of one for the primary reference NZC by not encoding amplitude quantization information for the primary reference NZC.

[0093] Example 30 includes the subject matter of example 29, including or omitting optional elements, wherein the indication of amplitude quantization indicates a amplitude quantization value of one for the reference NZCs by not encoding amplitude quantization information for the reference NZCs.

[0094] Example 31 includes the subject matter of example 11, including or omitting optional elements, further configured to quantize amplitude of the reference NZCs using more bits than a number of bits used to quantize the remaining NZCs.

[0095] Example 32 is a method that includes any action or combination of actions as substantially described herein in the Detailed Description.

[0096] Example 33 is a method as substantially described herein with reference to each or any combination of the Figures included herein or with reference to each or any combination of paragraphs in the Detailed Description.

[0097] Example 45 is a user equipment configured to perform any action or combination of actions as substantially described herein in the Detailed Description as included in the user equipment.

[0098] Example 35 is a network node configured to perform any action or combination of actions as substantially described herein in the Detailed Description as included in the network node.

[0099] Example 36 is a non-transitory computer-readable medium that stores instructions that, when executed, cause the performance of any action or combination of actions as substantially described herein in the Detailed Description. [00100] Example 37 is an apparatus for a user equipment including a memory and one or processors that execute instructions stored in the memory cause the UE to perform of any action or combination of actions as substantially described herein in the Detailed Description.

[00101 ] Example 38 is an apparatus for a network node one or processors that execute instructions stored in the memory cause the network node to perform of any action or combination of actions as substantially described herein in the Detailed Description.

[00102] The above description of illustrated examples, implementations, aspects, etc., of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. While specific examples, implementations, aspects, etc., are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such examples, implementations, aspects, etc., as those skilled in the relevant art can recognize.

[00103] While the methods are illustrated and described above as a series of acts or events, it will be appreciated that the illustrated ordering of such acts or events are not to be interpreted in a limiting sense. For example, some acts may occur in different orders and/or concurrently with other acts or events apart from those illustrated and/or described herein. In addition, not all illustrated acts may be required to implement one or more aspects or embodiments of the disclosure herein. Also, one or more of the acts depicted herein may be carried out in one or more separate acts and/or phases. In some embodiments, the methods illustrated above may be implemented in a computer readable medium using instructions stored in a memory. Many other embodiments and variations are possible within the scope of the claimed disclosure.

[00104] The term “couple” is used throughout the specification. The term may cover connections, communications, or signal paths that enable a functional relationship consistent with the description of the present disclosure. For example, if device A generates a signal to control device B to perform an action, in a first example device A is coupled to device B, or in a second example device A is coupled to device B through intervening component C if intervening component C does not substantially alter the functional relationship between device A and device B such that device B is controlled by device A via the control signal generated by device A. [00105] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Claims

CLAIMS What is claimed is:

1. A user equipment (UE), comprising a memory and a baseband processor, the baseband processor configured to, when executing instructions stored in the memory: based on channel state information (CSI) signals transmitted by a plurality of transmission reception points (TRPs), determine a plurality of non-zero coefficients (NZCs) corresponding to linear combination coefficients; select reported NZCs from the plurality of NZCs, wherein respective sets of reported NZCs are associated with respective transmission layers, wherein at least one of the sets of reported NZCs includes NZCs associated with at least two different TRPs; and transmit a CSI report that encodes, for each transmission layer, information about the reported NZCs.

2. The UE of claim 1, wherein the CSI report independently encodes locations of NZPs within a preconfigured matrix on a per transmission layer basis, a per transmission layer and polarization and TRP basis, or a per TRP basis.

3. The UE of claim 1, wherein the baseband processor is further configured to determine the reported NZCs based on a network-configured maximum number of NZCs per transmission layer.

4. The UE of claim 3, wherein the baseband processor is further configured to determine the reported NZCs based on a network-configured maximum total number of NZCs across all transmission layers.

5. The UE of claim 4, wherein the maximum total number of NZCs is based on a preconfigured threshold number of selected transmission layers, such that the maximum total number of NZCs is based on the product of the maximum number of NZCs per transmission layer and the threshold number.

6. The UE of any of one of claims 1-5, wherein the baseband processor is further configured to select a number of reported NZPs that is less than or equal to a network-configured maximum number of NZCs; and indicate the selected number of reported NZCs in the CSI report.

7. The UE of claim 1, wherein the baseband processor is further configured to group the reported NZCs into one reporting group, wherein the reporting group includes a reference NZC and zero or more remaining NZCs; and encode an indication of phase quantization or an indication of amplitude quantization for the reported NZCs based on the reporting group.

8. A method for a user equipment (UE), comprising: determining a plurality of non-zero coefficients (NZCs) corresponding to linear combination coefficients based on channel state information (CSI) signals transmitted by a plurality of transmission reception points (TRPs); selecting reported NZCs from the plurality of NZCs, wherein respective sets of reported NZCs are associated with respective transmission layers, wherein at least one of the sets of reported NZCs includes NZCs associated with at least two different TRPs; and transmitting a CSI report that encodes, for each transmission layer, information about the reported NZCs.

9. The method of claim 8, wherein the CSI report independently encodes locations of NZPs within a preconfigured matrix on a per transmission layer basis, a per transmission layer and polarization and TRP basis, or a per TRP basis.

10. The method of claim 8, further comprising selecting the reported NZCs based on a network-configured maximum number of NZCs per transmission layer.

11. The method of claim 10, further comprising selecting the reported NZCs based on a network-configured maximum total number of NZCs across all transmission layers.

12. The method of claim 11, wherein the maximum total number of NZCs is based on a preconfigured threshold number of selected transmission layers, such that the maximum total number of NZCs is based on the product of the maximum number of NZCs per transmission layer and the threshold number.

13. The method of any of one of claims 8-12, further comprising selecting a number of reported NZPs that is less than or equal to a network-configured maximum number of NZCs; and indicating the selected number of reported NZCs in the CSI report.

14. The method of claim 13, further comprising grouping the reported NZCs into one reporting group, wherein the reporting group includes a reference NZC and zero or more remaining NZCs; and encoding an indication of phase quantization or an indication of amplitude quantization for the reported NZCs based on the reporting group.

15. A processor for a network node configured to cause the network node to: receive a CSI report that encodes information about reported non-zero coefficients (NZCs) corresponding to linear combination coefficients, wherein respective NZCs are based on respective CSI signals transmitted by a plurality of transmission reception points (TRPs), wherein the CSI signals include CSI signals transmitted by the network node; and wherein, in the CSI report, respective sets of reported NZCs are associated with respective transmission layers, wherein at least one of the sets of reported NZCs includes NZCs associated with at least two different TRPs.

16. The processor of claim 15, wherein the CSI report independently encodes locations of NZPs within a preconfigured matrix on a per transmission layer basis, a per transmission layer and polarization and TRP basis, or a per TRP basis.

17. The processor of claim 15, wherein a number of reported NZCs is based on a network- configured maximum number of NZCs per transmission layer.

18. The processor of claim 16, wherein a number of reported NZCs is based on a network- configured maximum total number of NZCs across all transmission layers.

19. The processor of claim 18, wherein the maximum total number of NZCs is based on a preconfigured threshold number of selected transmission layers, such that the maximum total number of NZCs is based on the product of the maximum number of NZCs per transmission layer and the threshold number.

20. The processor of any of one of claims 15-19, wherein a number of reported NZPs is less than or equal to a network-configured maximum number of NZCs.

21. The processor of claim 15, wherein the CSI report groups the reported NZCs into one reporting group, wherein the reporting group includes a reference NZC and zero or more remaining NZCs; and the CSI report encodes an indication of phase quantization or an indication of amplitude quantization for the reported NZCs based on the reporting group.