Linear Combination Coefficient Coding for Channel State Information Reporting in Multi-Transmit / Receive Point Coherent Joint Transmission

Abstract

An apparatus, a processor, and a method for channel state information (CSI) reporting for coherent joint transmission using multiple transmit / receive points (TRPs) are provided. In one example, a baseband processor of a user equipment (UE) is configured to determine multiple non-zero coefficients (NZCs) corresponding to linear combination coefficients based on channel state information (CSI) measurement resources transmitted by the multiple transmit / receive points (TRPs). The baseband processor selects a reported NZC from the multiple NZCs, each set of the reported NZCs being associated with a respective transmission layer, and 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 information regarding the reported NZCs for each transmission layer, and to perform the CSI report.

Description

[Background technology]

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

[0002] Multi-transmission reception point (TRP) communication involves a user equipment (UE) exchanging signals with two or more TRPs. Multiple TRPs can be integrated into the same base station or different base stations. A UE can communicate with different TRPs using different beams. Data transmitted and received between a UE and multiple TRPs can 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.

[0003] Some examples of circuits, devices and / or methods are described below, by way of example only, and in this context, reference is made to the accompanying figures. [Brief explanation of the drawings]

[0004] [Figure 1A] 1 illustrates a UE that receives channel state information (CSI) measurement resources from a plurality of TRPs and transmits a CSI report based on measurements on the CSI measurement resources, in accordance with various described aspects.

[0005] [Figure 1B]1 illustrates a UE receiving coherent joint transmissions of a physical downlink shared channel (PDSCH) from multiple TRPs in accordance with various described aspects.

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

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

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

[0009] [Figure 5] FIG. 1 illustrates an example network according to one or more implementations described herein.

[0010] [Figure 6] FIG. 1 illustrates a simplified block diagram of a user equipment wireless communication device, in accordance with various described aspects. DETAILED DESCRIPTION OF THE INVENTION

[0011] The present disclosure is described with reference to the accompanying drawings. The figures are not drawn to scale and are provided solely to explain the present disclosure. Several aspects of the present disclosure are described below with reference to exemplary uses for illustration. Numerous specific details, relationships, and methods are set forth to provide an understanding of the present disclosure. The present disclosure is not limited to the illustrated order of acts or events, as some acts may occur in different orders and / or contemporaneously with other acts or events. Furthermore, not all illustrated acts or events are required to implement selected methodologies in accordance with the present disclosure. Multi-TRP coherent joint transmission

[0012] Multiple input, multiple output (MIMO) communication systems utilize joint transmission in which transmitted signals from multiple antennas are processed jointly at a receiving device. The set of signals processed jointly at a receiving device is called a transmission layer. Each signal in a transmission layer is called 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 on multiple transmission points and selects beamforming coefficients (phase and amplitude) for the spatial streams transmitted by each antenna such that the spatial streams together concentrate the transmit energy at the UE. To support CJT, the network may use knowledge of the downlink channel for each antenna, or may use the same downlink channel information if the antennas are co-located. In NCJT, the network does not coordinate spatial streams from different antennas to concentrate the energy at the UE, and the spatial streams are received independently by the UE.

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

[0015] 1A and 1B, a wireless communication network 100 is shown that includes a UE 101 and two TRPs 110, 120. A multi-TRP CJT is used to transmit physical downlink shared channels (PDSCHs) at two transmission layers from the TRPs 110, 120 to the UE 101. While the TRPs are shown as being located on different base stations, in other examples, the TRPs may be mounted on the same base station or on other structures. Each TRP is shown as having eight antenna elements, four with horizontal polarization and four with vertical polarization (each pair of elements with opposite polarization is indicated by a bold X in FIGS. 1A and 1B). Thus, in the illustrated network, there are 2 x 8, or 16, spatial bases (8 spatial bases for each TRP). In the illustrated example, the UE has two receive antennas, and therefore 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 is pre-configured with a codebook (e.g., a Type II MIMO codebook) that defines an index 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 a CSI measurement resource (e.g., a CSI-RS), which is received and measured by the UE to determine the best beam and corresponding beamforming coefficients for the downlink CJT. The index of the coefficients is reported by the UE in the CSI report for each codebook. As shown in FIG. 1B, the TRP sets the corresponding beamforming coefficients for transmitting PDSCH to the UE in transmission layer 1 and transmission layer 2.

[0017] The CSI report includes a spatial basis, a frequency basis, and a precoder matrix indicator (PMI) component that encodes the corresponding coefficients selected by the UE. Figure 2 shows the codebook (W) that encodes the precoding information for transmission layer l using three matrices. 1 ) is shown. The W1 matrix indicates which of the spatial bases is selected according to the maximum value per network-configured transmission layer (e.g., 8 in some examples).

number

number

number

[0018] Figure 3 shows 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 W1 matrix, and each column corresponds to

number

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

[0020] In multi-TRP CJT, there is a W2 matrix per TRP per transmission layer. As the number of transmission layers and TRPs increases, the number of reported NZCs coded in the CSI report increases. The CSI report construction should feature efficient coding of the W2 matrix location, phase quantization, and amplitude quantization to save signaling overhead.

[0021] Figure 4 is a message flow diagram illustrating an overview of multi-TRP CJT. The UE is preconfigured with a Type II MIMO codebook and a CSI reporting configuration that specifies parameters for reported quantities, the report format, etc. At 410, the TRP transmits CSI measurement resources. The UE measures the measurement resources, selects a preferred beam, ranks the beams based on strength, generates a CSI report based on the codebook, and reports information about the preferred beam, including the W1, W2 matrices (one matrix per transmission layer and TRP), and the W3 matrix. At 420, the UE transmits the CSI report to at least one TRP or another node coordinating the multi-TRP CJT. At 430, multiple TRPs transmit PDSCH in one or more transmission layers according to the codebook reported by the UE in the CSI.

[0022] Here, several techniques for encoding the reported NZC locations and indicating the phase and amplitude quantization information for each reported NZC in the CSI report are disclosed. Depending on the use case, the different disclosed approaches can be configured as needed or dynamically indicated. Location and number of NZCs reported

[0023] There are several ways to encode the NZC location. The reported NZC location can be coded independently for each transmission layer (meaning the NZC location can be different for different transmission layers), for each transmission layer and polarization and TRP (meaning the NZC location can be different for each unique combination of transmission layer / polarization / TRP), or for each TRP (meaning the NZC location can be different for each unique combination of transmission layer / TRP). The reported NZC location can be coded jointly for each transmission layer (meaning the NZC location is the same for all transmission layers), for each transmission layer and polarization and TRP (meaning the NZC location is the same for each unique combination of transmission layer / polarization / TRP), or for each TRP (meaning the NZC location is the same across all TRPs).

[0024] There are several approaches to configuring the maximum number of reported NZCs. In one example, the network may configure a maximum number of reported NZCs per transmission layer, K, with no upper limit on the total number of reported NZCs. NZC In another example, the network may configure the maximum number of reported NZCs per transmission layer (K NZC ) and the transmission layer threshold. In this case, the maximum total number of NZCs reported is the transmission layer threshold multiplied by K NZC For example, if the transmission layer threshold is 2, the number of reported NZCs for any transmission layer is K NZC The total number of NZCs reported across all transmission layers cannot exceed 2 K NZC In other examples, the network can configure the maximum number of reported NZCs per polarization per transmission layer, or per TRP per transmission layer, 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 able 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 Part 1 or CSI Part 2). Reporting Group

[0026] To efficiently encode the phase quantization and amplitude quantization indication for each reported NZC, the reported NZCs may be grouped into one or more groups, each group containing a reference NZC. Different reporting groups may be used for phase quantization reporting and amplitude quantization reporting. In the following description, the groups are referred to as:

number

number

number

number

number

number

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

[0028] In another example, the reported NZCs are grouped into different groups per TRP per transmission layer or per TRP group per transmission layer. In this example, all 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 different groups per transmission layer per TRP per polarization, or per transmission layer per TRP group per polarization. In this example, all 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, in the case of phase encoding, all the reference

number

number

number

number

number

[0031] In one example, the phase quantization of the remaining NZCs (e.g., non-reference NZCs) may be performed by dividing the phase quantization of the remaining NZCs by their respective groups.

number

number

[0032] In one example, each criterion

number

number

[0033] In one example, in the case of amplitude coding, all the criteria

number

number

number

number

number

[0034] In one example, the amplitude quantization of the remaining NZCs (e.g., non-reference NZCs) is performed by dividing the amplitude quantization of the remaining NZCs by their respective groups.

number

number

[0035] In one example, each criterion

number

number

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

[0037] The systems and devices of the exemplary network 500 may operate according to one or more communication standards, such as the 3rd generation partnership project (3GPP) second generation (2G), third generation (3G), fourth generation (4G) (e.g., long-term evolution (LTE)), and / or fifth generation (5G) (e.g., new radio (NR)) communication standards. Additionally or alternatively, one or more of the systems and devices of exemplary 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 others.

[0038] As shown, an example of UE 101 may include a smartphone (e.g., a handheld touchscreen mobile computing device capable of connecting to one or more wireless communications networks). Additionally or alternatively, UE 101 may include other types of mobile or non-mobile computing devices capable of wireless communications, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, etc. In some implementations, UE 101 may include an internet of things (IoT) device (or IoT UE), which may include a network access layer designed for low-power IoT applications that utilize short-lived UE connections.

[0039] The UE 101 may communicate with and establish a connection with (e.g., be communicatively coupled to) the RAN 520, which may include one or more wireless channels 514-1 and 514-2, each of which may include a physical communication interface / layer.

[0040] As described herein, the UE 101-2 may operate in a multi-TRP mode in which the UE simultaneously communicates 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 a 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 the functions described above with respect to encoding a CSI report for the multi-TRP CJT. The multi-TRP CJT CSI report information may include instructions or algorithms used by the UE to determine how to code determined linear combination coefficients according to a MIMO type-II codebook in the CSI report.

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

[0042] The RAN 520 may include one or more RAN nodes 522-1 and 522-2 (collectively referred to as RAN nodes 522 and individually referred to as RAN node 522) that enable channels 514-1 and 514-2 to be established between the UE 101 and the RAN 520. The RAN node 522 may include a network access point configured to provide wireless baseband functionality for data and / or voice connectivity between a user and a network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi, etc.). Thus, by way of example, the 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, an NR base station, a next-generation eNB (gNB), etc.). The RAN node 522 may include a roadside unit (RSU), a transmission reception point (TRxP or TRP), and one or more other types of ground equipment. In some scenarios, the 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 a femtocell, picocell, etc., having a smaller coverage area, lower user capacity, or wider bandwidth compared to a macrocell.

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

[0044] The RAN nodes 522 may be configured to communicate with each other via an interface 523. In an implementation where the system is an LTE system, the interface 523 may be an X2 interface. In an NR system, the 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 an evolved packet core (EPC) or CN 530, and / or between two eNBs that connect to the EPC.

[0045] As shown, the RAN 520 may be connected (e.g., communicatively coupled) to the CN 530. The CN 530 may comprise a number of network elements 532 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UEs 101) connected to the CN 530 via the RAN 520. In some implementations, the CN 530 may include an evolved packet core (EPC), a 5G CN, and / or one or more additional or alternative types of CN.

[0046] As shown, the CN 530, the application server 540, and the external network 550 may be connected to each other via interfaces 534, 536, and 538, which may include IP network interfaces. The application server 540 may include one or more server devices or network elements (e.g., virtual network functions (VNFs)) that provide applications that use IP bearer resources in the CN 530 (e.g., universal mobile telecommunications system packet service (UMTS PS) domain, LTE PS data services, etc.). The application server 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 the UE 101 via the CN 530. Similarly, the external network 550 may include one or more of a variety of networks, including the Internet, that may provide the mobile communication network and the UE 101 of the network with access to a variety of additional services, information, interconnectivity, and other network functions.

[0047] 6 is a diagram of an example of components of a UE device or apparatus according to one or more implementations described herein. In some implementations, the apparatus 600 may include, coupled together at least as shown, 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. The components of the illustrated apparatus 600 may be included in a UE (101 in FIG. 1) or a RAN node (e.g., TRP 110, 120 in FIG. 1). In some implementations, the apparatus 600 may 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 may include one or more application processors. For example, the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core processors or multi-core processors. The processor(s) may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor(s) may be coupled to or may include memory / storage and may 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, the processor of the application circuitry 602 may process IP data packets received from the EPC.

[0049] The baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 604 may include one or more baseband processors or control logic that processes baseband signals received from a receive signal path of the RF circuitry 606 and generates baseband signals for a transmit signal path of the RF circuitry 606. The baseband circuitry 604 may interface with the application circuitry 602 for generating and processing the baseband signals and for controlling the operation of the RF circuitry 606. For example, in some implementations, the baseband circuitry 604 may include a 3G baseband processor 604A, a 4G baseband processor 604B, a 5G baseband processor 604C, or another baseband processor(s) 604D for other existing, developing, or future generations (e.g., 5G, 6G, etc.). The baseband circuitry 604 (e.g., one or more of the baseband processors 604A-D) may handle various radio control functions that enable communication with one or more wireless networks via the RF circuitry 606. In other implementations, some or all of the functionality of the baseband processors 604A-604D may be contained in modules stored in memory 604G and executed via a central processing unit (CPU) 604E.

[0050] In some implementations, the memory 604G may store and process multi-TRP CJT CSI report information that causes the UE to perform the 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 the functions described above with respect to encoding a CSI report for a multi-TRP CJT. The multi-TRP CJT CSI report information may include instructions that, when executed by the BB processor 604C or the CPU 604E, cause the UE to encode the determined linear combination coefficients according to a MIMO Type II codebook in the CSI report.

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

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

[0053] The RF circuitry 606 can enable communication with a wireless network using modulated electromagnetic radiation over a non-solid medium. In various implementations, the RF circuitry 606 can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuitry 606 can include a receive signal path that can include circuitry to downconvert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604. The RF circuitry 606 can also include a transmit signal path that can include circuitry to upconvert baseband signals provided by the baseband circuitry 604 and provide an RF output signal 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. The RF circuitry 606 can also include combiner circuitry 606D that combines frequencies used by the mixer circuitry 606A for the receive and transmit signal paths.

[0055] 6 shows the PMC 612 coupled only to the baseband circuitry 604. However, in other implementations, the PMC 612 may additionally or alternatively be coupled to other components, including but not limited to the application circuitry 602, the RF circuitry 606, or the FEM circuitry 608, to perform similar power management operations on these other components.

[0056] The processors of the application circuitry 602 and the baseband circuitry 604 can be used to execute elements of one or more instances of a protocol stack. For example, the processors of the baseband circuitry 604 can be used alone or in combination to execute Layer 3, Layer 2, or Layer 1 functionality, while the processor of the baseband circuitry 604 can utilize data (e.g., packet data) received from these layers to execute Layer 4 functionality (e.g., the Transmission Communication Protocol (TCP) layer and the User Datagram Protocol (UDP) layer). As mentioned herein, Layer 3 can include an RRC layer, which is described in further detail below. As mentioned herein, Layer 2 can include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which are described in further detail below. As mentioned herein, Layer 1 may include the physical (PHY) layer of the UE / RAN node, which is described in more detail below.

[0057] The above are several flow diagrams outlining exemplary methods and message exchanges. In this description and the appended claims, the use of the term "determine" with respect to certain entities (e.g., parameters, variables, etc.) in describing method steps or functions should be interpreted broadly. For example, "determine" should be interpreted to encompass, for example, receiving and analyzing communications encoding the entity or the value of the entity. "Determine" should be interpreted to encompass accessing and reading memory (e.g., lookup tables, registers, device memory, remote memory, etc.) that stores the entity or the value of the entity. "Determine" should be interpreted to encompass calculating or deriving the entity or the value of the entity based on other quantities or entities. "Determine" should be interpreted to encompass any method of inferring or identifying the entity or the value of the entity.

[0058] As used herein, the term "identify," when used with respect to any entity or value of an entity, should be interpreted broadly to encompass any method of determining the entity or the value of the entity. For example, the term "identify" should be interpreted to encompass, for example, receiving and analyzing a communication that encodes the entity or the value of the entity. The term "identify" should be interpreted to encompass accessing and reading a memory (e.g., a device queue, lookup table, register, device memory, remote memory, etc.) that stores the entity or the value of the entity.

[0059] As used herein, the term encoding, when used with respect to any entity or value of an entity, should be interpreted broadly to encompass any method or technique for producing a data sequence or signal that communicates the entity to another entity.

[0060] As used herein, the term "selecting," when used with respect to any entity or entity value, should be interpreted broadly to encompass any method of determining the entity or entity value from among multiple or a range of possible choices. For example, the term "selecting" should be interpreted to encompass accessing and reading a memory (e.g., a lookup table, a register, a device memory, a remote memory, etc.) that stores the entity or entity value and returning an entity or entity value from among the stored entity or entity values. The term "selecting" should be interpreted as applying one or more constraints or rules to a set of input parameters to determine an appropriate entity or entity value. The term "selecting" should be interpreted broadly to encompass any method of selecting an entity based on one or more parameters or conditions.

[0061] As used herein, the term deriving should be interpreted broadly when used in reference to any entity or value of an entity. "Deriving" should be interpreted to encompass accessing and reading memory (e.g., a lookup table, a register, a device memory, a remote memory, etc.) that stores some initial or base value, and performing processing and / or logical / mathematical operations on one or more values ​​to produce a derived entity or value of the entity. The term deriving should be interpreted to encompass calculating or computing an entity or value of an entity based on other quantities or entities. The term deriving should be interpreted to encompass any method of inferring or identifying an entity or value of an entity.

[0062] As used herein, the term indicate, when used with respect to any entity (e.g., a parameter or setting) or value of an entity, should be interpreted broadly to encompass any manner of communicating the entity or value of the entity, either explicitly or implicitly. For example, a bit in a transmitted message may be used to explicitly encode the indicated value, or may encode an index or other indicator that was mapped to the indicated value by a previous configuration. The absence of a field in a message may implicitly indicate the value of the entity based on the previous configuration.

[0063] Examples of the present specification may include subject matter such as a method, means for performing operations or blocks of the method, and at least one machine-readable medium containing executable instructions that, when executed by a machine or circuit configuration (e.g., a processor with memory (e.g., a processor), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), etc.), cause the machine to perform the operations of a method or apparatus or system for simultaneous communication using multiple communication techniques according to the described implementations and examples.

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

[0065] Example 2 includes the subject matter of Example 1 with or without the optional element that the CSI report independently encodes the location of the NZP in the preconfigured matrix for each transmission layer, for each transmission layer and polarization and TRP, or for each TRP.

[0066] Example 3 includes the subject matter of Example 1 with or without the optional element that the CSI report commonly encodes the location of the NZP in the preconfigured matrix per transmission layer, per transmission layer and polarization and TRP, or per TRP.

[0067] Example 4 includes the subject matter of Example 1 with or without an optional element further configured to determine the reported NZC based on a maximum number of network-configured NZCs per transmission layer.

[0068] Example 5 includes the subject matter of Example 4 with or without any element, where the maximum number of network-configured NZCs per layer is independent of the number of transmission layers.

[0069] Example 6 includes the subject matter of Example 4 with or without an optional element further configured to determine the reported NZC based on the maximum total number of network-configured NZCs across all transmission layers.

[0070] Example 7 includes the subject matter of Example 6, including or omitting optional elements, where the maximum total number of NZCs is based on a preconfigured threshold number of selected transmission layers, and 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 with or without any optional elements further configured to determine the reported NZC based on a maximum number of network-configured NZCs per transmission layer and polarization or per transmission layer and TRP.

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

[0073] Example 10 includes the subject matter of Example 1 with or without an optional element further configured to select a number of NZPs to be reported equal to the maximum number of network-configured NZCs.

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

[0075] Example 12 includes the subject matter of Example 11 with or without an optional element further configured to group the reported NZCs into reporting groups by transmission layer.

[0076] Example 13 includes the subject matter of Example 11 with or without any 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 any element further configured to group the reported NZCs into reporting groups by transmission layer and TRP, or by transmission layer and TRP group.

[0078] Example 15 includes the subject matter of Example 11 with or without an optional element further configured to group the reported NZCs into reporting groups by transmission layer and TRP and polarization.

[0079] Example 16 includes the subject matter of example 11 with or without an optional element further configured to group the reported NZCs by polarization into reporting groups.

[0080] Example 17 includes the subject matter of Example 11 with or without an optional element further configured to group the reported NZCs into reporting groups by transmission layer and by polarization.

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

[0082] Example 19 includes the subject matter of Example 11 with or without any elements, where the phase quantization indication of the reference NZC does not encode phase quantization information indicating a value of zero.

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

[0084] Example 21 includes the subject matter of Example 11, including or omitting an optional element further configured to encode, for another reference NZC, an indication of phase quantization based on a phase difference between the reference NZC and the primary reference NZC.

[0085] Example 22 includes the subject matter of Example 20, including or omitting any element in which the phase quantization instruction 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 any element in which the phase quantization instruction indicates a phase quantization value of zero for the reference NZC by not encoding phase quantization information for the reference NZC.

[0087] Example 24 includes the subject matter of Example 11 with or without any optional element further configured to quantize the phase of the reference NZC using more bits than the number of bits used to quantize the remaining NZCs.

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

[0089] Example 26 includes the subject matter of example 11 with or without any element where the amplitude quantization instruction for the reference NZC does not encode amplitude quantization information indicating a value of 1.

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

[0091] Example 28 includes the subject matter of Example 27, including or omitting an optional element, further configured to encode an indication of amplitude quantization for another reference NZC based on an amplitude difference between the reference NZC and the primary reference NZC.

[0092] Example 29 includes the subject matter of Example 27, including or omitting any element in which the amplitude quantization instruction indicates an amplitude quantization value of 1 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 any element in which the amplitude quantization instruction indicates an amplitude quantization value of 1 for the reference NZC by not encoding amplitude quantization information for the reference NZC.

[0094] Example 31 includes the subject matter of Example 11 with or without an optional element further configured to quantize the amplitude of the reference NZC using more bits than the number of bits used to quantize the remaining NZCs.

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

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

[0097] Example 45 is a user equipment configured to perform any of the actions or any combination of actions substantially described as being included in the user equipment in the "Form for Implementing the Invention" of this specification.

[0098] Example 35 is a network node configured to perform any of the actions or any combination of actions substantially described as being included in a network node in the "Forms for Implementing the Invention" of this specification.

[0099] Example 36 is a non-transitory computer-readable medium storing instructions that, when executed, result in the performance of any action or combination of actions substantially as described in the "Description of Embodiments" section of this specification.

[0100] Example 37 is an apparatus for user equipment including a memory and one or more processors that execute instructions stored in the memory to cause the UE to perform any action or combination of actions substantially as described in the "Forms for Implementing the Invention" section of this specification.

[0101] Example 38 is an apparatus for a network node, one or a processor that executes instructions stored in memory to cause the network node to perform any action or combination of actions substantially as described in the "Description of Embodiments" section of this specification.

[0102] The above description of illustrated examples, implementations, aspects, etc. of the disclosed subject matter, including what is set forth 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. have been described herein for illustrative purposes, those skilled in the art will recognize that various modifications are possible that are considered to be within the scope of such examples, implementations, aspects, etc.

[0103] While the method is illustrated and described above as a series of acts or events, it is understood that the illustrated order of such acts or events should not be construed in a limiting sense. For example, some acts may occur in a different order and / or concurrently with other acts or events other than those illustrated and / or described herein. In addition, not all illustrated acts are required to implement one or more aspects or embodiments of the present disclosure. Also, one or more of the acts illustrated herein may be performed in one or more separate acts and / or phases. In some embodiments, the above-described method may be implemented on a computer-readable medium using instructions stored in a memory. Many other embodiments and variations are possible within the scope of the claimed disclosure.

[0104] The term "coupled" is used throughout this specification. This term can cover connections, communications, or signal paths that enable a functional relationship consistent with the description of this disclosure. For example, in a first example, device A is coupled to device B if device A generates signals to control device B to perform an operation, or in a second example, device A is coupled to device B via an intervening component C if the intervening component C does not substantially change the functional relationship between device A and device B, such that device B is controlled by device A via control signals generated by device A.

[0105] It is well understood that use of personally identifiable information should comply with generally recognized privacy policies and practices that meet or exceed industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Claims

1. 1. A user equipment (UE) comprising a memory and a baseband processor, the baseband processor, when executing instructions stored in the memory, 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, each set of reported NZCs being associated with a respective transmission layer, and at least one of the sets of reported NZCs including NZCs associated with at least two different TRPs; The UE transmits a CSI report that encodes information regarding the reported NZC for each transmission layer.

2. 2. The UE of claim 1, wherein the CSI report encodes the location of NZPs in a preconfigured matrix independently for each transmission layer, for each transmission layer and polarization and TRP, or for each TRP.

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

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

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

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

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

8. 1. 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, each set of reported NZCs being associated with a respective transmission layer, and at least one of the sets of reported NZCs including NZCs associated with at least two different TRPs; transmitting a CSI report that encodes information regarding the reported NZC for each transmission layer.

9. 9. The method of claim 8, wherein the CSI report encodes the location of the NZP in a pre-configured matrix independently for each transmission layer, for each transmission layer and polarization and TRP, or for each TRP.

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

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

12. 12. The method of claim 11, wherein the maximum total number of NZCs is based on a preconfigured threshold number of selected transmission layers, and 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. selecting a number of NZPs to be reported that is less than or equal to a maximum number of network-configured NZCs; indicating the selected number of reported NZCs in the CSI report; and The method of any one of claims 8 to 12, further comprising:

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

15. 1. A processor for a network node, the processor causing the network node to: configured to receive CSI reports encoding information about reported non-zero coefficients (NZCs) corresponding to linear combination coefficients, each NZC based on a respective CSI signal transmitted by a plurality of transmission / reception points (TRPs), the CSI signals including a CSI signal transmitted by the network node; A processor wherein, in the CSI report, each set of reported NZCs is associated with a respective transmission layer, and at least one of the sets of reported NZCs includes NZCs associated with at least two different TRPs.

16. 16. The processor of claim 15, wherein the CSI report encodes the location of NZPs in a preconfigured matrix independently for each transmission layer, for each transmission layer and polarization and TRP, or for each TRP.

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

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

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

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

21. The CSI report groups the reported NZCs into one report group, the report group including a reference NZC and zero or more remaining NZCs; the CSI report encodes a phase quantization indication or an amplitude quantization indication for the reported NZC based on the report group.

16. The processor of claim 15.

Images