Configuration of quasi co-location information

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. An apparatus and method for configuring quasi-co-location (QCL) information are provided. A method performed by a user equipment includes receiving a configuration including information about (i) a number of non-zero power (NZP) channel state information-reference signal (CSI-RS) resources and (ii) quasi-co-location information (QCL information) common for at least one of the number of NZP CSI-RS resources, where the configuration includes information about (i) the number of non-zero power (NZP) channel state information-reference signal (CSI-RS) resources and (ii) the number of quasi-co-location information (QCL information) common for at least one of the number of NZP CSI-RS resources. The QCL information indicates at least one source RS and a QCL type. The QCL type indicates at least one channel attribute of the at least one source RS. The method further includes, based on the configuration, applying QCL information for channel measurement via one of the plurality of NZP CSI-RS resources based on a hypothesis that at least one channel attribute of the plurality of NZP CSI-RS resources is the same as at least one channel attribute of the indicated at least one source RS.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to a wireless communication system, and more particularly, the present disclosure relates to an apparatus and method for configuring quasi co-location (QCL) information. BACKGROUND

[0002] Wireless communication is one of the most successful innovations in modern history. Recently, the number of users of wireless communication services has exceeded 5 billion and continues to grow rapidly. As smart phones and other mobile data devices (e.g., tablets, "notebook" computers, netbooks, e-book readers, and machine-type devices) are increasingly popular among consumers and enterprises, the demand for wireless data traffic is rapidly growing. In order to meet the high-speed growth of mobile data traffic and support new applications and deployments, improving the efficiency and coverage of the radio interface is critical. In order to meet the demand for wireless data traffic that has increased since the deployment of 4G communication systems, and to implement various vertical applications, 5G communication systems have been developed and are currently being deployed.

[0003] The fifth generation (5G) mobile communication technology defines a wide band, making it possible to achieve high transmission rates and new services, and can be implemented not only in a "sub-6GHz" (e.g., 3.5GHz) frequency band, but also in a "6GHz or more" frequency band, including 28GHz and 39GHz, which is called millimeter wave. In addition, in order to achieve a transmission rate 50 times faster than the 5G mobile communication technology and an ultra-low latency of 1 / 10 of the 5G mobile communication technology, 6G mobile communication technology (referred to as Beyond 5G system) has been considered in a terahertz band (e.g., 95GHz to 3THz band).

[0004] At the early stage of the development of 5G mobile communication technology, in order to support services and meet the performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization has been conducted on technologies for mitigating radio wave path loss and increasing radio wave transmission distance in mmWave, beamforming and massive MIMO, supporting dynamic operation of numerologies (e.g., operating multiple subcarrier spacings) and slot formats for efficient use of mmWave resources, supporting initial access techniques for multi-beam transmission and wideband, definition and operation of BWP (BandWidth Part), new channel coding methods (such as LDPC (Low Density Parity Check) code for large data transmission and polar code for high-reliability transmission of control information), L2 pre-processing, and network slicing for providing a dedicated network dedicated to a specific service.

[0005] Currently, in consideration of services to be supported by 5G mobile communication technologies, discussions are underway on improvements and performance enhancements of initial 5G mobile communication technologies, and there has been ongoing standardization on physical layers, such as V2X (Vehicle-to-Everything) for determining and enhancing user convenience based on information about a position and a state of a vehicle transmitted by the vehicle to assist driving of an autonomous vehicle, NR-U (New Radio Unlicensed) aiming to operate a system in compliance with various regulatory requirements in an unlicensed band, NR UE power saving, non-terrestrial networks (NTN) as a direct communication of a UE-satellite for providing coverage in an area where communication with a terrestrial network is unavailable, and positioning.

[0006] In addition, in the field of radio interface architecture / protocol, there are ongoing standardization efforts on technologies such as industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (2-step RACH for NR) for simplifying random access procedures. In terms of system architecture / services, there are also ongoing standardization efforts on a 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software-defined networking (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE location.

[0007] With the commercialization of 5G mobile communication systems, exponentially increasing connected devices will be connected to communication networks, and thus, it is expected that enhanced functionality and performance of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is planned in relation to extended reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), etc., improvement of 5G performance and reduction of 5G complexity by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0008] In addition, such development of 5G mobile communication systems will serve as a basis for not only developing new waveforms for providing coverage for terahertz bands, multi-antenna transmission techniques such as Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas, metamaterials-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing techniques using OAM (Orbital Angular Momentum), and RISs (Reconfigurable Intelligent Surfaces), but also developing full-duplex techniques for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication techniques for system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing techniques for implementing services at a level of complexity that exceeds the limit of UE operation capabilities by utilizing super-high-performance communication and computing resources.

[0009] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present disclosure. SUMMARY

[0010] PROBLEMS TO BE SOLVED BY THE INVENTION

[0011] The disclosure relates to configuring QCL information.

[0012] The technical objects to be achieved by various embodiments of the present disclosure are not limited to what has been mentioned above and other technical objects not mentioned above will be clearly understood from the following description by those skilled in the art.

[0013] TECHNICAL SOLUTION

[0014] In one embodiment, a user equipment (UE) is provided. The UE includes a transceiver configured to receive a configuration including information about (i) a number of non-zero-power (NZP) channel state information-reference signal (CSI-RS) resources and (ii) quasi co-location information (QCL information) common for at least of the number of NZP CSI-RS resources, wherein the QCL information indicates at least one source RS and a QCL type. The QCL type indicates at least one channel property of the at least one source RS. The UE further includes a processor operably coupled to the transceiver. The processor, based on the configuration, is configured to: assume, based on the at least one channel property of the number of NZP CSI-RS resources being the same as the at least one channel property of the indicated at least one source RS, that of the number of NZP CSI-RS resources. ​​​​One, for channel measurement applications QCL information.

[0015] In another embodiment, a base station (BS) is provided. The BS includes a processor and a transceiver operatively coupled to the processor. The transceiver is configured to transmit in a configuration that includes information about (i) One non-zero power (NZP) channel state information-reference signal (CSI-RS) resource and (ii) shared in At least one of the NZP CSI-RS resources The information of each quasi-co-addressable information (QCL information), among which, The QCL information indicates at least one source RS and the QCL type. The QCL type indicates at least one channel attribute of at least one source RS. This configuration indication is based on... The assumption that at least one channel attribute of an NZP CSI-RS resource is the same as at least one channel attribute of the indicated at least one source RS is passed through In NZP CSI-RS resources One, for channel measurement applications QCL information.

[0016] In yet another embodiment, a method performed by a user equipment is provided. The method includes receiving a configuration, the configuration including information about (i) One non-zero power (NZP) channel state information-reference signal (CSI-RS) resource and (ii) shared in At least one of the NZP CSI-RS resources The information of each quasi-co-addressable information (QCL information), among which, The QCL information indicates at least one source RS and a QCL type. The QCL type indicates at least one channel attribute of at least one source RS. The method also includes, based on this configuration, The assumption that at least one channel attribute of an NZP CSI-RS resource is the same as at least one channel attribute of the indicated at least one source RS is passed through In NZP CSI-RS resources One, for channel measurement applications QCL information.

[0017] Other technical features will be apparent to those skilled in the art from the following figures, description and claims.

[0018] [Beneficial effects of the invention]

[0019] This disclosure pertains to configuring QCL information.

[0020] The effects that can be achieved by the present disclosure are not limited to the effects mentioned in the various embodiments, and other effects not mentioned will become apparent to those skilled in the art from the following description.

[0021] Before undertaking the detailed description below, it can be advantageous to set forth definitions of certain terms and phrases used in this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms "transmit," "receive," and "communicate," as well as derivatives thereof, encompass both direct and indirect communication. The terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation. The term "or" is inclusive, meaning and / or. The phrase "associated with," as well as derivatives thereof, means to include, be

[0022] In addition, various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code. The terms "application" and "program" include one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof that can be implemented by appropriate computer readable program code. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer readable medium" includes any type of media capable of storing computer readable program code that is accessible by a computer, such as, without limitation, a read-only memory (ROM), a random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A "non-transitory" computer readable medium excludes wired, wireless, optical, or other communication links that do not carry program code permanently. Non-transitory computer readable media include volatile and non-volatile media that can store data and / or computer readable instructions which can be temporary or permanent, such as, without limitation, RAM, ROM, EPROM, EEPROM, flash memory, or any other memory storage technology. The term "program code" includes any type of computer code, including source code, object code, and executable code.

[0023] Definitions for other certain words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many if not most instances, such definitions apply to prior as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF DRAWINGS

[0024] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings in which like parts are marked with like numerals:

[0025] Figure 1 An example wireless network, in accordance with embodiments of the present disclosure, is illustrated;

[0026] Figure 2 An example gNodeB (gNB), in accordance with embodiments of the present disclosure, is illustrated;

[0027] Figure 3 An example UE, in accordance with embodiments of the present disclosure, is illustrated;

[0028] Figure 4A An example of a wireless transmit path, in accordance with embodiments of the present disclosure, is illustrated;

[0029] Figure 4B An example of a wireless receive path, in accordance with embodiments of the present disclosure, is illustrated;

[0030] Figure 5 An example of a transmitter structure for beamforming, in accordance with embodiments of the present disclosure, is illustrated;

[0031] Figure 6 An example of a transmitter structure for a physical downlink shared channel (PDSCH) in a subframe, in accordance with embodiments of the present disclosure, is illustrated;

[0032] Figure 7 An example of a receiver structure for a PDSCH in a subframe, in accordance with embodiments of the present disclosure, is illustrated;

[0033] Figure 8 An example of a transmitter structure for a physical uplink shared channel (PUSCH) in a subframe, in accordance with embodiments of the present disclosure, is illustrated;

[0034] Figure 9 An example of a receiver structure for a PUSCH in a subframe, in accordance with embodiments of the present disclosure, is illustrated;

[0035] Figure 10 An example of an antenna port layout, in accordance with embodiments of the present disclosure, is illustrated;

[0036] Figure 11 An example of a UE moving on a trajectory located in co-located and distributed transmission-reception points (TRPs), in accordance with embodiments of the present disclosure, is illustrated;

[0037] Figure 12 A timeline of an example spatial domain (SD) unit and a frequency domain (FD) unit according to embodiments of the disclosure is shown; and

[0038] Figure 13 An example method performed by a UE in a wireless communication system according to embodiments of the disclosure is shown. DETAILED DESCRIPTION

[0039] The following discussion is presented to enable a better understanding of the principles of the disclosure as claimed Figures 1 to 13 The principles of the disclosure described in this patent document can be implemented in any of the following arrangements, which are examples only and should not be construed as limiting the scope of the disclosure. Those skilled in the art will understand that the principles of the disclosure can be implemented in any suitably arranged system or device.

[0040] To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, efforts have been made to develop an improved 5G / NR communication system or a pre-5G communication system. Therefore, the 5G / NR or pre-5G communication system is also called a beyond 4G network or a post-LTE system.

[0041] In addition, in 5G / NR communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, a technology for coordination between cells, D2D communication, wireless backhaul, a moving network, a cooperative communication, Coordinated Multi-Points (CoMP), reception-end interference cancellation and the like.

[0042] 5G systems and frequency bands associated therewith are discussed for reference, as certain embodiments of the disclosure can be implemented in 5G systems. However, the disclosure is not limited to 5G systems or frequency bands associated therewith, and embodiments of the disclosure can be used in conjunction with any frequency band. For example, aspects of the disclosure can also be used for deployment of 5G communication systems, 6G or even higher versions which can use terahertz (THz) bands.

[0043] The following documents and standards descriptions are incorporated by reference into the disclosure herein as if fully set forth herein: [1] 3GPP TS 36.211 v17.3.0 “E-UTRA, Physical channels and modulation,” [2] 3GPP TS 36.212 v17.1.0 “E-UTRA, Multiplexing and Channel coding,” [3] 3GPP TS 36.213 v17.3.0 “E-UTRA, Physical Layer Procedures,” [4] 3GPP TS 36.321 v17.3.0 “E-UTRA, Medium Access Control (MAC) protocol specification,” [5] 3GPP TS 36.331 v17.3.0 “E-UTRA, Radio Resource Control (RRC) Protocol Specification,” [6] 3GPP TR 22.891 v1.2.0; [7] 3GPP TS 38.212 v17.3.0 “E-UTRA, NR, Multiplexing and Channel coding,” [8] 3GPP TS 38.214 v17.3.0 “E-UTRA, NR, Physical layer procedures for data,” and [9] 3GPP TS 38.211 v17.3.0 “E-UTRA, NR, Physical channels and modulation.”

[0044] The following Figures 1 to 13 Various embodiments implemented in wireless communication systems are described. Figures 1 to 3 The description of the representative features of the various embodiments is not meant to imply that physical or architectural limitations are present in any particular implementation. Different embodiments of the present disclosure can be implemented in any suitable arrangement.

[0045] Figure 1 An example wireless network 100 according to embodiments of the present disclosure is illustrated. Figure 1 The illustrated embodiment of wireless network 100 is for illustration only. Other embodiments of the wireless network 100 can be used without departing from the scope of the present disclosure.

[0046] As Figure 1 illustrated, wireless network 100 includes a gNB 101 (e.g., base station BS), a gNB 102, and a gNB 103. gNB 101 communicates with the gNB 102 and the gNB 103. gNB 101 also

[0047] gNB 102 provides wireless broadband access to the network 130 for a first plurality of user equipment devices (UEs) within a coverage area 120 of gNB 102. The first plurality of UEs includes a UE 111, which can be located in a small business; a UE 112, which can be located in an enterprise network; a UE 113, which can be a WiFi hotspot; a UE 114, which can be located in a first residence; a UE 115, which can be located in a second residence; and a UE 116, which can be a mobile device, such as a cell phone, a wireless laptop, a wireless PDA, and so on. gNB 103 provides wireless broadband access to the network 130 for a second plurality of UEs within a coverage area 125 of gNB 103. The second plurality of UEs includes the UE 115 and the UE 116. In some embodiments, one or more of the gNBs 101-103 can communicate with each other and with UEs 111-116 using 5G / NR, long term evolution (LTE), long term evolution

[0048] Depending on the network type, the term "base station" or "BS" can refer to any component (or collection of components) configured to provide wireless access to a network, such as a transmit point (TP), transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled devices. Base stations can provide wireless access to the Internet or a PBX telephone network or both via one or more wired networks and / or wireless networks. A base station can provide wireless access to one or more communication protocols, such as 5G / NR Third Generation Partnership Project (3GPP) NR, Long-Term Evolution (LTE), LTE Advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For the sake of convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Also, depending on the network type, the term "user equipment" or "UE" can refer to any component, such as a "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receive point," or "user device." For the sake of convenience, the terms "user equipment" and "UE" are used interchangeably in this patent document to refer to remote wireless equipment that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile telephone or smartphone) or is normally considered a fixed device (such as a desktop computer or vending machine).

[0049] Dotted lines show the approximate extents of the coverage areas 120 and 125 as they can be depicted as approximately circular for purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with gNBs (such as the coverage areas 120 and 125) can have other shapes, including irregular shapes, depending upon the configuration of gNBs and variations in the radio environment associated with natural and man-made obstructions.

[0050] As described in more detail below, one or more of the UEs 111-116 include circuitry, programs, or a combination thereof for identifying and utilizing a configuration of QCL information. In certain embodiments, one or more of the BSs 101-103 include circuitry, programs, or a combination thereof to support configuring QCL information.

[0051] Although Figure 1 One example of a wireless network is illustrated, but Figure 1Various changes can be made. For example, the wireless network 100 could include any number of gNBs and any number of UEs in any suitable arrangement. Also, the gNB 101 could communicate directly with any number of UEs and provide those UEs access to the network 130 via the wireless wide area network. Similarly, each gNB 102-103 could communicate directly with the network 130 and provide UEs access to the network 130 via the wireless wide area network. Further, the gNBs 101, 102, and / or 103 could provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0052] Figure 2 An example gNB 102 according to embodiments of the present disclosure is illustrated. Figure 2 The embodiment of the gNB 102 shown is for illustration only Figure 1 The gNBs 101 and 103 can have the same or similar configuration. However, gNBs have a wide variety of configurations and Figure 2 The scope of the present disclosure is not limited to the embodiment of the gNB.

[0053] As shown, the gNB 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, memory 230, and a backhaul or network interface 235. Figure 2

[0054] The transceivers 210a-210n receive input RF signals, such as signals transmitted by UEs in the wireless network 100, from the antennas 205a-205n. The transceivers 210a-210n down-convert the input RF signals to generate IF or baseband signals. The IF or baseband signals are processed by the transceivers 210a-210n and / or RX processing circuitry in the controller / processor 225 by filtering, decoding, and / or digitizing the baseband or IF signals, to generate processed baseband signals. The controller / processor 225 can further process the baseband signals.

[0055] The transceivers 210a-210n and / or TX processing circuitry in the controller / processor 225 receive analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. The transceivers 210a-210n up-convert the baseband or IF signals to RF signals that are transmitted via the antennas 205a-205n.

[0056] ​The controller / processor 225 may include one or more processors or other processing devices for controlling the overall operation of the gNB 102. For example, the controller / processor 225 may control the transceivers 210a-210n to receive uplink (UL) channel signals and transmit downlink (DL) channel signals according to well-known principles. The controller / processor 225 may also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 225 may support beamforming or directional routing operations, wherein the output / input signals from / to multiple antennas 205a-205n are weighted differently to effectively guide the output signal in a desired direction. As another example, the controller / processor 225 may support methods for configuring QCL information. Any of a variety of other functions may be supported by the controller / processor 225 in the gNB 102.

[0057] The controller / processor 225 is also capable of executing programs and other processes residing in the memory 230, such as processes that support configuring QCL information. The controller / processor 225 can move data into or out of the memory 230 as needed for the execution process.

[0058] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or network. Interface 235 can support communication via any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (e.g., a cellular communication system supporting 5G / NR, LTE, or LTE-A), interface 235 can allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, interface 235 can allow the gNB 102 to communicate via a wired or wireless local area network or via a wired or wireless connection to a larger network (e.g., the Internet). Interface 235 includes any suitable architecture supporting communication via wired or wireless connections, such as Ethernet or a transceiver.

[0059] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, while another portion of memory 230 may include flash memory or other ROM.

[0060] although Figure 2 An example of gNB 102 is shown, but it is possible to compare it with other models. Figure 2 Various changes can be made. For example, gNB 102 can include... Figure 2 Each component can be represented in any number of different quantities. Furthermore, Figure 2The various components in the system 100 can be combined, further subdivided, or omitted and additional components can be added in accordance with particular needs.

[0061] Figure 3 An example UE 116 according to embodiments of the disclosure is shown. Figure 3 The illustrated embodiment of the UE 116 is for illustration only, and Figure 1 The UEs 111-115 can have the same or similar configuration. However, UEs come in a wide variety of configurations, and Figure 3 The scope of the disclosure is not limited to any particular implementation of a UE.

[0062] As Figure 3 The UE 116 includes an antenna 305, a transceiver 310, and a microphone 320, as shown. The UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0063] The transceiver 310 receives, from the antenna 305, incoming RF signals transmitted by gNBs of the wireless network 100. The transceiver 310 down-converts the incoming RF signals to generate intermediate frequency (IF) or baseband signals. The IF or baseband signals are processed by RX processing circuitry in the transceiver 310 and / or the processor 340 by filtering, decoding, and / or digitizing the baseband or IF signals to generate processed baseband signals. The RX processing circuitry sends the processed baseband signals to the speaker 330 (e.g., for voice data) or to the processor 340 for processing (e.g., for web browsing data).

[0064] The transceiver 310 and / or TX processing circuitry in the processor 340 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (e.g., web browsing data, e-mail, or interactive video game data) from the processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. The transceiver 310 up-converts the baseband or IF signals to RF signals that are transmitted via the antenna 305.

[0065] The processor 340 can include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 in order to control the overall operation of the UE 116. For example, the processor 340 could control the reception of DL channel signals and the transmission of UL channel signals by the transceiver 310, in accordance with well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0066] The processor 340 is also capable of executing other processes and programs resident in the memory 360. The processor 340 can be one of any number of processors of a

[0067] The processor 340 is also coupled to the input 350 and the display 355, which permit the UE 116 to interact with a user. The input 350 can include, for example, a

[0068] The memory 360 is coupled to the processor 340. The portion of the memory 360 can include random access memory (RAM) and the portion of the memory 360 can include

[0069] Although Figure 3 various changes can be made to the Figure 3 For example, Figure 3 various components in the Figure 3 may be combined, further subdivided, or omitted and additional components can be added according to particular needs. As a specific example, the processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, the transceiver 310 can include any number of transceivers and signal processing chains and can be connected to any number of antennas. Further, although

[0070] Figure 4A and Figure 4BExamples of wireless transmit and receive paths 400 and 450, respectively, are shown in accordance with embodiments of the present disclosure. For example, transmit path 400 can be described as implemented in a gNB (e.g., gNB 102), while receive path 450 can be described as implemented in a UE (e.g., UE 116). However, it is to be understood that receive path 450 can be implemented in a gNB, and transmit path 400 can be implemented in a UE. In some embodiments, transmit path 400 and / or receive path 450 are configured for identifying and utilizing configurations of QCL information, as described in embodiments of the present disclosure.

[0071] As shown, transmit path 400 includes channel coding and modulation block 405, serial-to-parallel (S-P) block 410, Inverse Fast Fourier Transform (IFFT) block 415 of size N, parallel-to-serial (P-S) block 420, add cyclic prefix block 425, and up-converter (UC) 430. Receive path 450 includes down-converter (DC) 455, remove cyclic prefix block 460, S-P block 465, Fast Fourier Transform (FFT) block 470 of size N, parallel-to-serial (P-S) block 475, and channel decoding and demodulation block 480. Figure 4A

[0072] In the transmit path 400, channel coding and modulation block 405 receives a set of information bits, applies coding (e.g., Low Density Parity Check (LDPC) coding), and modulates the input bits (e.g., using Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of frequency-domain modulation symbols. Serial-to-parallel block 410 converts (e.g., de-multiplexes) the serial modulated symbols to parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in the gNB and the UE. Inverse Fast Fourier Transform (IFFT) block 415 performs an IFFT operation on the N parallel symbol streams to generate time-domain output signals. Parallel-to-serial block 420 converts (e.g., multiplexes) the parallel time-domain output symbols from IFFT block 415 to generate a serial time-domain signal. Add cyclic prefix block 425 inserts a cyclic prefix to the time-domain signal. Up-converter 430 modulates (e.g., up-converts) the output of add cyclic prefix block 425 to an RF frequency for transmission via a wireless channel. The signal can also be filtered at baseband before conversion to the RF frequency.

[0073] As shown, transmit path 400 includes channel coding and modulation block 405, serial-to-parallel (S-P) block 410, Inverse Fast Fourier Transform (IFFT) block 415 of size N, parallel-to-serial (P-S) block 420, add cyclic prefix block 425, and up-converter (UC) 430. Receive path 450 includes down-converter (DC) 455, remove cyclic prefix block 460, S-P block 465, Fast Fourier Transform (FFT) block 470 of size N, parallel-to-serial (P-S) block 475, and channel decoding and demodulation block 480. Figure 4B ​As shown, downconverter 455 downconverts the received signal to the baseband frequency, and cyclic prefix removal module 460 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel block 465 converts the time-domain baseband signal into a parallel time-domain signal. FFT block 470 of size N executes the FFT algorithm to generate N parallel frequency-domain signals. (PS) block 475 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 480 demodulates and decodes the modulated symbols to recover the original input data stream.

[0074] Each of gNBs 101-103 can implement a transmission path 400 similar to that sent to UEs 111-116 in the downlink, and a reception path 450 similar to that received from UEs 111-116 in the uplink. Similarly, each of UEs 111-116 can implement a transmission path 400 for sending to gNBs 101-103 in the uplink, and a reception path 450 for receiving from gNBs 101-103 in the downlink.

[0075] Figure 4A and Figure 4B Each component in the system can be implemented using only hardware or a combination of hardware and software / firmware. As a specific example, Figure 4A and Figure 4B At least some components can be implemented in software, while others can be implemented in configurable hardware or a hybrid of software and configurable hardware. For example, FFT block 470 and IFFT block 415 can be implemented as configurable software algorithms, where the value of size N can be modified depending on the implementation.

[0076] Furthermore, although described as using FFT and IFFT, this is merely illustrative and should not be construed as limiting the scope of this disclosure. Other types of transforms may be used, such as the Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions. It should be understood that for the DFT and IDFT functions, the value of the variable N can be any integer (e.g., 1, 2, 3, 4, etc.), while for the FFT and IFFT functions, the value of the variable N can be any integer that is a power of 2 (e.g., 1, 2, 4, 8, 16, etc.).

[0077] although Figure 4A and Figure 4B Examples of wireless transmit and receive paths 400 and 450 are shown respectively, but more details can be found on the other side. Figure 4A and Figure 4B Make various changes. For example, Figure 4A and Figure 4B The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. Furthermore,Figure 4A and Figure 4B This example illustrates the types of transmit and receive path types that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0078] Figure 5 An example of a transmitter structure 500 for beamforming according to an embodiment of the present disclosure is shown. In some embodiments, one or more of gNB 102 or UE 116 include transmitter structure 500. For example, one or more antennas 205 and their associated systems or antenna 305 and their associated systems may be included in transmitter structure 500. This example is for illustration only, and other embodiments may be used without departing from the scope of the present disclosure.

[0079] Therefore, embodiments of this disclosure recognize that Release 14 LTE and Release 15 NR support up to 32 CSI Reference Signal (CSI-RS) antenna ports, enabling eNBs or gNBs to be equipped with a large number of antenna elements (e.g., 64 or 128). Multiple antenna elements can then be mapped onto a single CSI-RS port. For millimeter-wave bands, while the number of antenna elements can be larger for a given form factor, the number of CSI-RS ports (which may correspond to the number of digital precoding ports) may be limited by hardware constraints (e.g., the feasibility of mounting a large number of analog-to-digital converters (ADCs) / digital-to-analog converters (DACs) at millimeter-wave frequencies), such as... Figure 5 As shown. A CSI-RS port can then be mapped to a large number of antenna elements that can be controlled by a set of analog phase shifters 501. A CSI-RS port can correspond to a subarray that generates a narrow analog beam through analog beamforming 505. This analog beam can be configured to sweep a wider range of angles 520 by changing the set of phase shifters on symbols or time slots / subframes. The number of subarrays (equal to the number of RF chains) is related to the number of CSI-RS ports N. CSI-PORT The number is the same. The digital beamforming unit 510 is in N CSI-PORT Linear combination is performed on the analog beam to further increase the precoding gain. While the analog beam is broadband (and therefore not frequency-selective), digital precoding can vary across frequency subbands or resource blocks. Receiver operation can be envisioned similarly.

[0080] because Figure 5The transmitter structure 500 utilizes multiple analog beams for transmission and reception (where, for example, one or a few analog beams are selected from a large number of analog beams after a training duration performed occasionally or periodically), so the term "multi-beam operation" is used to refer to this aspect of the entire system. For illustrative purposes, this includes indicating the assigned DL or UL TX beam (also referred to as "beam indication"), measuring at least one reference signal for calculating and performing beam reporting (also referred to as "beam measurement" and "beam reporting," respectively), and receiving DL or UL transmissions by selecting the appropriate RX beam. Figure 5 The system is also suitable for higher frequency bands, such as >52.6 GHz (also known as frequency range 4 or FR4). In this case, the system can only use analog beams. Due to O2 absorption losses near 60 GHz (an additional loss of about 10 dB per 100 meters), a larger number and narrower analog beams (and therefore a larger number of radiators in the array) are essential to compensate for the additional path loss.

[0081] This disclosure generally relates to wireless communication systems, and more specifically, to QCL configurations.

[0082] A communication system comprises a downlink (DL) and an uplink (UL). The downlink transmits signals from a transmission point, such as a base station (BS) or NodeB, to a user equipment (UE), while the uplink transmits signals from the UE to a receiving point, such as a NodeB. A UE, often referred to as a terminal or mobile station, can be fixed or mobile and can be a cellular phone, personal computer device, or automated equipment. An eNodeB is typically a fixed station and may also be referred to as an access point or other equivalent terms. In LTE systems, a NodeB is typically referred to as an eNodeB.

[0083] In communication systems such as LTE, DL signals may include data signals that transmit information content, control signals that transmit DL control information (DCI), and reference signals (RS) also known as pilot signals. The eNodeB transmits data information through the Physical DL Shared Channel (PDSCH). The eNodeB transmits DCI through the Physical Downlink Control Channel (PDCCH) or Enhanced PDCCH (EPDCCH)—see documents and standards [3]. In response to a data transmission block (TB) transmission from the UE, the eNodeB transmits acknowledgment information in the Physical Hybrid Automatic Repeat Request Indicator Channel (PHICH). The eNodeB transmits one or more of several types of RS, including UE Common RS (CRS), Channel State Information RS (CSI-RS), or Demodulated RS (DMRS). CRS is transmitted over the DL system bandwidth (BW) and can be used by the UE to obtain channel estimates, demodulate data or control information, or perform measurements. To reduce CRS overhead, the eNodeB may transmit CSI-RS in the time and / or frequency domains at a lower density than CRS. DMRS can be transmitted only in the corresponding BW of PDSCH or EPDCCH, and the UE can use DMRS to demodulate data or control information in PDSCH or EPDCCH respectively. The transmission time interval of the DL channel is called a subframe (or time slot) and can have a duration of, for example, 1 millisecond.

[0084] The DL signal also includes the transmission of logical channels carrying system control information. When the Broadcast Control Channel (BCCH) transmits the Master Information Block (MIB), the BCCH is mapped to a transport channel called the Broadcast Channel (BCH), or when it transmits the System Information Block (SIB), the BCCH is mapped to the DL Shared Channel (DL-SCH)—see Documents and Standards [3] and Documents and Standards [5]. Most system information is included in different SIBs transmitted using the DL-SCH. The presence of system information on the DL-SCH in a subframe (or time slot) can be indicated by the transmission of the corresponding PDCCH, which transmits codewords with cyclic redundancy check (CRC) scrambled with a special system information radio network temporary identifier (SI-RNTI). Alternatively, scheduling information for the SIB transmission can be provided in an earlier SIB, and scheduling information for the first SIB (SIB-1) can be provided by the MIB.

[0085] DL resource allocation is performed on a per-subframe (or time slot) and per-set-Physical Resource Blocks (PRBs). A transport BW consists of frequency resource units called resource blocks (RBs). Each RB includes... Subcarriers or resource elements (REs), for example, 12 REs. A unit of one RB on a subframe (or slot) is called a PRB. For PDSCH transmission BW, the UE can be allocated a total of One RE RB.

[0086] UL signals can include data signals for transmitting data information, control signals for transmitting UL control information (UCI), and UL RS. UL RS includes DMRS and SNR (Sounding RS). The UE only transmits DMRS in the BW of the corresponding PUSCH or Physical UL Control Channel (PUCCH). The eNodeB can use DMRS to demodulate data signals or UCI signals. The UE transmits SRS to provide ULCSI to the eNodeB. The UE transmits data information or UCI through the corresponding PUSCH or PUCCH. If the UE needs to transmit data information and UCI in the same UL subframe (or time slot), it can multiplex the data information and UCI in the PUSCH. UCI includes: Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information, indicating a correct (ACK) or incorrect (NACK) detection of data TB in the PDSCH or a missing (DTX) detection in the PDCCH; a scheduling request (SR), indicating whether the UE has data in its buffer; a rank indicator (RI); and channel state information (CSI), enabling the eNodeB to perform link adaptation for PDSCH transmissions to the UE. In response to the detection of a PDCCH / Enhanced PDCCH (EPDCCH) indicating the release of a semi-persistent PDSCH, HARQ-ACK information is also sent by the UE (see also document and standard [3]).

[0087] A UL subframe (or time slot) consists of two time slots. Each time slot includes space for transmitting data information, UCI, DMRS, or SRS. The frequency resource unit (RB) of the UL system BW is one symbol. For the transmission BW, the UE can be allocated a total of [number missing] symbols. One RE One RB. For PUCCH, The last subframe (or time slot) symbol can be used to multiplex SRS transmissions from one or more UEs. The number of subframe (or time slot) symbols available for data / UCI / DMRS transmissions is... Where, if the last subframe (or time slot) symbol is used to transmit SRS, then ,otherwise, .

[0088] Figure 6 An example of a transmitter structure 600 for PDSCH in a subframe according to an embodiment of this disclosure is shown. For example, the transmitter structure 600 can be... Figure 1 This is implemented in gNB 102. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0089] like Figure 6 As shown, information bits 610 are encoded by encoder 620 (e.g., turbo encoder) and modulated by modulator 630, for example, using quadrature phase shift keying (QPSK) modulation. A serial-to-parallel (S / P) converter 640 generates M modulation symbols, which are then provided to mapper 650 to be mapped to REs selected by transmission BW selection unit 655 for the assigned PDSCH transmission. Unit 660 applies inverse fast Fourier transform (IFFT), and the output is then serialized by parallel-to-serial (P / S) converter 670 to create a time-domain signal. Filtering is applied by filter 680, and the signal is transmitted at 690. Additional features such as data scrambling, cyclic prefix insertion, time windowing, and interleaving are well known in the art and are not shown for simplicity.

[0090] Figure 7 An example of a PDSCH receiver structure 700 in a subframe according to an embodiment of the present disclosure is shown. For example, the receiver structure 700 may be composed of... Figure 1 This can be implemented using any of UEs 111-116. This example is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.

[0091] refer to Figure 7 Filter 720 filters the received signal 710, the RE 730 for the allocated receive BW is selected by BW selector 735, unit 740 applies Fast Fourier Transform (FFT), and the output is serialized by serializer 750 in parallel. Subsequently, demodulator 760 coherently demodulates data symbols by applying a channel estimate obtained from DMRS or CRS (not shown), and decoder 770 (e.g., turbo decoder) decodes the demodulated data to provide an estimate of information data bits 780. For simplicity, additional functions such as time windows, cyclic prefix removal, descrambling, channel estimation, and deinterleaving are not shown.

[0092] Figure 8 An example of a transmitter structure 800 for PUSCH in a subframe according to an embodiment of this disclosure is shown. For example, the transmitter structure 800 can be... Figure 1 This is implemented in gNB 103. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0093] like Figure 8As shown, information data bits 810 are encoded by encoder 820 (e.g., turbo encoder) and modulated by modulator 830. Discrete Fourier Transform (DFT) unit 840 applies DFT to the modulated data bits, RE 850 corresponding to the allocated PUSCH transmission bandwidth is selected by transmission BW selection unit 855, unit 860 applies IFFT, and after cyclic prefix insertion (not shown), filter 870 applies filtering, and signal 880 transmits the signal.

[0094] Figure 9 An example of a receiver structure 900 for PUSCH in a subframe according to an embodiment of this disclosure is shown; for example, the receiver structure 900 may be composed of... Figure 3 This is implemented using UE 116. This example is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.

[0095] like Figure 9 As shown, the received signal 910 is filtered by filter 920. Subsequently, after the cyclic prefix (not shown) is removed, unit 930 applies FFT, RE 940 corresponding to the assigned PUSCH receive BW is selected by receive BW selector 945, unit 950 applies inverse DFT (IDFT), demodulator 960 coherently demodulates data symbols by applying channel estimation obtained from DMRS (not shown), and decoder 970 (e.g., turbo decoder) decodes the demodulated data to provide an estimate of information data bits 980.

[0096] The 3GPP 5G NR specification defines two types of frequency ranges (FRs). The range below 6 GHz is called frequency range 1 (FR1), and the millimeter wave range is called frequency range 2 (FR2). Examples of FR1 and FR2 frequency ranges are shown here.

[0097] Table 1

[0098]

[0099] For MIMO in FR1, a maximum of 32 CSI-RS antenna ports are supported, while in FR2, a maximum of 8 CSI-RS antenna ports are supported. In next-generation cellular standards (e.g., 6G), new carrier bands can be considered in addition to FR1 and FR2, such as FR4 (>52.6GHz), terahertz (>100GHz), and mid-to-high frequency bands (10-15GHz). The number of CSI-RS ports that these new bands can support may differ from that of FR1 and FR2. Specifically, for the 10-15GHz band, the maximum number of CSI-RS antenna ports may exceed that of FR1 because of the smaller antenna form factor and the feasibility of fully digital beamforming (as in FR1) at these frequencies. For example, the number of CSI-RS antenna ports could increase to 128. Furthermore, NW deployments / topologies at these frequencies (e.g., Network 130) are also expected to be more densely / distributed. For example, antenna ports on multiple (non-co-located, and therefore geographically separated) TRPs distributed across a cellular area are likely to be the main scenario of interest. For this reason, the number of CSI-RS antenna ports used for MIMO may be even greater (e.g., up to 256).

[0100] (Spatial or digital) precoding / beamforming can be used on these numerous antenna ports to achieve MIMO gain. Depending on the carrier frequency and the feasibility of the RF / HW-related components, (spatial) precoding / beamforming can be entirely digital or a hybrid analog-digital approach. In fully digital beamforming, there can be a one-to-one mapping between antenna ports and antenna elements, or multiple antenna elements can be used in a 'static / fixed' virtualization of a single antenna port. Each antenna port can be digitally controlled. Therefore, spatial multiplexing across antenna ports is provided.

[0101] In wireless communication systems, MIMO is often recognized as a fundamental feature for achieving high system throughput requirements. A key component of MIMO transmission schemes is acquiring accurate CSI at the eNB (or gNB) (or TRP). Specifically, for multi-user (MU) MIMO, the availability of accurate CSI is necessary to guarantee high MU performance. For TDD systems, CSI can be acquired using SRS transmissions that rely on channel reciprocity. On the other hand, for frequency division duplex (FDD) systems, CSI can be acquired using CSI-RS transmissions from the eNB (or gNB) as well as CSI acquisition and feedback from the UE. In common FDD systems, the CSI feedback framework is 'implicit' in the form of Rank Indicator (RI) / Precoding Matrix Indicator (PMI) / Channel Quality Indicator (CQI) (along with CQI Reporting Interval (CRI) and Layer Index (LI)), which are derived from a codebook using SU transmissions from the eNB (or gNB).

[0102] In 5G or NR systems (Documents and Standards [7], Documents and Standards [8]), the 'implicit' CSI reporting paradigm from LTE mentioned herein is also supported and referred to as Type I CSI reporting. Furthermore, high-resolution CSI reporting (referred to as Type II CSI reporting) is also supported in the Release 15 specification to provide more accurate CSI information to gNBs for use cases such as high-order MU-MIMO. However, embodiments of this disclosure recognize that the overhead of Type II CSI reporting can be a problem in practical UE implementations. One approach to reducing Type II CSI overhead is based on frequency domain (FD) compression. In Release 16 NR, DFT-based FD compression for Type II CSI is already supported (referred to as the Enhanced Type II Codebook in Release 16, Documents and Standards [8]). Some key components of this feature include (a) spatial domain (SD) base (b) FD base (c) The coefficients of the linear combination of the SD and FD bases In non-reciprocal FDD systems, the complete CSI (including each component) needs to be reported by the UE (e.g., UE 116). However, when there is indeed reciprocity or partial reciprocity between the UL and DL, some CSI components can be obtained based on the UL channel estimated using SRS transmissions from the UE. In version 16 NR, DFT-based FD compression was extended to this partial reciprocity case (referred to as the Enhanced Type II Port Selection Codebook in version 16, document and standard [8]), where, The DFT-based SD base in the code is replaced by the SD CSI-RS port selection, i.e. Of the CSI-RS ports One port is selected (this selection is shared for both antenna polarizations or both halves of the CSI-RS port). In this case, beamforming is performed on the CSI-RS port in SD (UL-DL channel reciprocity in the angle domain), and beamforming information can be obtained at gNB 102 based on the UL channel estimated using SRS measurements.

[0103] In version 17 NR, CSI reporting has been enhanced to support the following:

[0104] Further Enhanced Type II Port Selection Codebook: As is known in the literature, if the UL-DL duplex distance is small, UL-DL channel reciprocity can exist in both the angle and delay domains. Since the delay transform (or closely correlated) in the time domain with the basis vectors in the frequency domain (FD), the port selection of Version 16 Enhanced Type II can be further extended to the angle and delay domains (or SD and FD). Specifically, DFT-based SD basis and The DFT-based FD basis in the code can be replaced by SD and FD port selection, i.e. One CSI-RS port is selected in the SD, or / and The port is selected in FD. In this case, the CSI-RS port is beamformed in SD (UL-DL channel reciprocity in the angle domain) and / or FD (UL-DL channel reciprocity in the delay / frequency domain), and the corresponding SD or / and FD beamforming information can be obtained at gNB 102 based on the UL channel estimated using SRS measurements. In version 17, such a codebook is supported (referred to in the document and standard [8] as the version 17 further enhanced type II port selection codebook).

[0105] Non-Coherent Joint Transport (NCJT) CSI Report: When a UE can communicate with multiple TRPs distributed in different spatial locations (e.g., within a cell), the CSI report can correspond to a single TRP assumption (i.e., a CSI report for one of the multiple TRPs) or a multi-TRP assumption (i.e., a CSI report for at least two of the multiple TRPs). Single-TRP and multi-TRP assumption CSI reporting are supported in Release 17. However, multi-TRP CSI reporting implies NCJT, meaning that the transport layer (and precoder) is restricted to being sent from only one TRP.

[0106] In version 18, MIMO WID includes the following CSI enhancement targets:

[0107] If reasonable, the study specifies enhanced CSI acquisition for coherent JTs on FR1 and up to 4 TRPs, which implies ideal backhaul and synchronization as well as the same number of antenna ports on the TRPs, as follows:

[0108] Version 16 / 17 is a Type II codebook refinement for Coherent Joint Transport (CJT) Multi-TRP (mTRP) in FDD and its associated CSI reports, taking into account the trade-off between throughput and overhead.

[0109] If appropriate, by utilizing temporal correlation / Doppler domain information to assist DL precoding, we can study specific enhancements to CSI reporting for high / medium UE speeds, targeting FR1, as shown below:

[0110] Version 16 / 17 Type II codebook refinement, without modifying the spatial and frequency domain fundamentals.

[0111] UE report of time-domain channel attributes measured via CSI-RS for tracking.

[0112] While version 18 CJT CSI can support up to 128 antenna ports by configuring four CSI-RS resources (each with 32 antenna ports), supporting up to 128 antenna ports using Type I CSI has also generated interest, as it requires less feedback overhead than version 18 CJT CSI. Currently, a single CSI-RS resource can support up to 32 antenna ports for Type I single-board (SP) and multi-board (MP) CSI. By using multiple CSI-RS resources for Type I CSI, up to 64 antenna ports can be configured according to one of the following two schemes:

[0113] Two CSI-RS resources, each with 32 antenna ports, for version 17 NCJT (Type I CSI).

[0114] Eight CSI-RS resources, each with eight antenna ports, for Type I SP CSI or Type I MPCSI.

[0115] However, neither of these schemes provides CSI feedback associated with the entire channel across 64 antenna ports. Instead, they are designed for specific use cases: 1) NCJTs from two TRPs, and 2) a single CSI-RS resource selection and reporting associated with a selected CSI-RS resource. Therefore, embodiments of this disclosure recognize that CSI for Type-I with more than 32 antenna ports is limited in terms of use cases and requires some enhancement.

[0116] In next-generation MIMO systems, for example, for carrier frequencies in the mid-to-high frequency band (10-15 GHz), the number of antenna ports is expected to increase further (e.g., up to 256); NW (e.g., network 130) deployments may be denser / more distributed (when compared to 5G NR); and the system is expected to work seamlessly even in challenging scenarios such as mid-to-high speed (e.g., 120 kmph) UEs and higher-order multi-user MIMO.

[0117] Similar to the common scenario (version 15 / 18 NR), both low-resolution (also known as Type I) and high-resolution (also known as Type II) CSI reporting for distributed systems, as discussed in this article, are necessary and beneficial, depending on the use case and scenario. However, unlike the common scenario, it is best to have a common framework or component between the two CSI reporting settings so that there is a simple, future-proof, and scalable solution that is more feasible in actual deployments.

[0118] This disclosure provides a framework for such CSI reporting, based on the Enhanced Type II codebook of version 16 and Type II CJT codebook of version 18. Specifically, based on the provided framework, several examples are provided to facilitate low-resolution (also known as Type I) CJT CSI reporting over multiple antenna port groups or NZP CSI-RS resources.

[0119] This disclosure relates to a CSI reporting framework in next-generation MIMO systems. Specifically, this disclosure relates to CSI reporting based on low-resolution (or Type I) or high-resolution (also known as Type II) codebooks, which include spatial, frequency, and / or temporal (Doppler) domain components for mTRP CJTs with distributed antenna structures (DMIMO). Three novel aspects are as follows:

[0120] QCL assumptions for an NZP CSI-RS resource in three use cases: (1) requiring co-located deployment of antenna groups (and thus resources) of a single / shared QCL across a resource; (2) requiring non-co-located / distributed deployment of each antenna group (and thus each resource) of an independent QCL across a resource; and (3) requiring non-co-located / distributed deployment of multiple antenna groups (and thus resource groups) of independent QCLs across resource groups.

[0121] Signaling / configuration for one of three use cases

[0122] QCL types and resources

[0123] Applicability to different codebooks and numbers of CSI-RS ports

[0124] From the following detailed description, aspects, features, and advantages of this disclosure will become apparent simply by illustrating several specific embodiments and implementations, including the best mode contemplated for carrying out this disclosure. Embodiments of this disclosure are also capable of other different embodiments, and several details thereof may be modified in various obvious ways without departing from the spirit and scope of this disclosure. Therefore, the drawings and description are to be considered illustrative in nature and not restrictive. Embodiments of this disclosure are shown in the drawings by way of example and not limitation.

[0125] In the following text, for the sake of brevity, both FDD and TDD are considered to be duplexing methods used for DL ​​and UL signaling.

[0126] Although the following exemplary description and embodiments suggest orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), this disclosure can be extended to other OFDM-based transmission waveforms or multiple access schemes, such as filtered OFDM (F-OFDM).

[0127] This disclosure covers several components that can be combined or used together, or can operate as a standalone solution.

[0128] Each of the following components and embodiments is applicable to UL transmissions with CP-OFDM (Cyclic Prefix OFDM) waveforms as well as DFT-SOFDM (DFT Extended OFDM) and SC-FDMA (Single Carrier FDMA) waveforms. Furthermore, each of the following components and embodiments is applicable to UL transmissions when the time scheduling unit is a subframe (which may include one or more time slots) or a time slot.

[0129] In this disclosure, the frequency resolution (reporting granularity) and span (reporting bandwidth) of a CSI report can be defined according to the frequency "subband" and "CSI Reporting Band" (CRB), respectively.

[0130] The subband used for CSI reporting is defined as a set of consecutive PRBs, representing the smallest frequency unit used for CSI reporting. For a given DL system bandwidth value, the number of PRBs in a subband can be fixed, semi-statically configured via higher-layer / RRC signaling, or dynamically configured via L1 DL control signaling or MAC control elements (MAC CE). The number of PRBs in a subband can be included in the CSI reporting settings.

[0131] A “CSI reporting band” is defined as a set of continuous or non-contiguous sub-bands where CSI reporting is performed. For example, a CSI reporting band may include every sub-band within the DL system bandwidth. This can also be referred to as a “full band.” Alternatively, a CSI reporting band may include only a set of sub-bands within the DL system bandwidth. This can also be referred to as a “partial band.”

[0132] The term “CSI Reporting Band” is used only as an example to indicate a function. Other terms may also be used, such as “CSI Reporting Subband Set” or “CSI Reporting Bandwidth” or Bandwidth Portion (BWP).

[0133] Regarding UE configuration, a UE (e.g., UE 116) can be configured with at least one CSI reporting band. This configuration can be semi-static (via higher-layer signaling or RRC) or dynamic (via MAC CE or L1 DL control signaling). When multiple (N) CSI reporting bands are configured (e.g., via RRC signaling), the UE can report CSIs associated with n ≤ N CSI reporting bands. For example, multiple CSI reporting bands may require a large system bandwidth > 6 GHz. The value of n can be configured semi-static (via higher-layer signaling or RRC) or dynamic (via MAC CE or L1 DL control signaling). Alternatively, the UE can report a recommended value of n via the UL channel.

[0134] Therefore, the frequency granularity of CSI parameters can be defined for each CSI reporting frequency band as follows. When M within the CSI reporting frequency band n When each of the sub-bands has a CSI parameter, the CSI parameter is configured to have M n A single report per sub-band of the CSI reporting band. When M is within the CSI reporting band... n When each sub-band reports a CSI parameter, the CSI parameter is configured to have M n The CSI report band is a sub-band of the frequency band.

[0135] Figure 10 A schematic diagram of an antenna port layout 1000 according to an embodiment of the present disclosure is shown. For example, the antenna port layout 1000 can be constructed by... Figure 2 The BS 102 implementation. This example is for illustrative purposes only and may be used without departing from the scope of this disclosure.

[0136] refer to Figure 10 N1 and N2 are the number of antenna ports with the same polarization in the first and second dimensions, respectively. For a 2D antenna port layout, N1>1, N2>1; for a 1D antenna port layout, N1>1, N2=1. Therefore, for a dual-polarized antenna port layout, when each antenna is mapped to one antenna port, the total number of antenna ports is... “X” represents two antenna polarizations. In this disclosure, the term “polarization” refers to a set of antenna ports. For example, antenna ports Including the first antenna polarization, and the antenna port. Including second-day antenna polarization, among which, It refers to the number of CSI-RS antenna ports, and It is the starting antenna port number (e.g., If the antenna ports are 3000, 3001, 3002, ..., then the antenna ports are 3000, 3001, 3002, ... . This disclosure assumes a dual-polarized antenna layout. However, the embodiments (and examples) in this disclosure are general and also applicable to single-polarized antenna layouts.

[0137] set up This refers to the number of antenna arrays (AGs). (Reference) Figure 10 When there are multiple antenna groups ( When ), each group ( ) including those with two dimensions and The dual-polarized antenna port. Note that the antenna port layout may be the same in different antenna groups. and (This may also differ in antenna groups.) For groups The number of antenna ports is or (Used for common polarization or dual polarization respectively).

[0138] In one example, the antenna group corresponds to an antenna panel. In one example, the antenna group corresponds to a TRP. In one example, the antenna group corresponds to a Remote Radio Head (RRH). In one example, the antenna group corresponds to a CSI-RS antenna port of an NZP CSI-RS resource. In one example, the antenna group corresponds to a subset of CSI-RS antenna ports of an NZP CSI-RS resource (comprising multiple antenna groups). In one example, the antenna group corresponds to CSI-RS antenna ports of multiple NZP CSI-RS resources (e.g., comprising a set of CSI-RS resources).

[0139] In one example, the antenna group corresponds to a reconfigurable smart surface (RIS), where the antenna group can be more dynamically (e.g., via MAC CE and / or DCI) reconfigured. For example, the number of antenna ports associated with the antenna group can change dynamically.

[0140] refer to Figure 11 In one example scenario, multiple access groups (AGs) can be co-located or distributed, and can serve static (non-mobile) or mobile UEs. An illustration of an AG serving a mobile UE is shown. When a UE moves from location A to another location B, the UE measures the channel, for example via NZP CSI-RS resources (or interference, for example via CSI Interference Measurement (CSI-IM) resources or CSI-RS resources for interference measurement), and uses this measurement to determine / report the CSI taking into account joint transmissions from multiple AGs. The reported CSI can be based on a codebook. The codebook may include components that consider multiple AGs, as well as frequency / delay domain channel characteristics and time / Doppler domain channel characteristics.

[0141] In one example, the antenna architecture of the MIMO system is structured. For instance, the antenna structure of each AG is dual-polarized (e.g., Figure 10 As shown, this can be a single-panel or multi-panel antenna. The antenna structure at each AG can be the same, or the antenna structure at one AG can be different from that of another AG. Similarly, the number of ports at each AG can be the same, or the number of ports at one AG can be different from that of another AG.

[0142] In another example, the antenna architecture of a MIMO system is unstructured. For instance, the antenna structure at one AG can differ from that at another AG.

[0143] In various embodiments, a structured antenna architecture is assumed. For simplicity, each AG can be equivalent to a panel (see...). Figure 10 Although in practice an AG can have multiple panels, this disclosure is not limited to the single panel assumption at each AG and can be readily extended (covered) to the case when an AG has multiple antenna panels.

[0144] Figure 11 An example of a UE moving along a trajectory 1100 located in a co-located and distributed TRP according to an embodiment of the present disclosure is shown. For example, the trajectory 1100 located in a co-located and distributed TRP can be... Figure 1 This example is for illustrative purposes only and may be used without departing from the scope of this disclosure.

[0145] In one implementation, AG constitutes (or corresponds to or is equivalent to) at least one of the following:

[0146] In one example, AG corresponds to TRP.

[0147] In one example, AG corresponds to CSI-RS resources. The UE is configured with There are multiple non-zero power (NZP) CSI-RS resources, and CSI reporting is configured to span multiple CSI-RS resources. This is similar to the Class B K>1 configuration in Release 14 LTE. An NZP CSI-RS resource can belong to one CSI-RS resource set or multiple CSI-RS resource sets (e.g., Each resource set contains one CSI-RS resource. Details are as explained in the public information herein.

[0148] In one example, AG corresponds to a CSI-RS resource group, where the group includes one or more NZP CSI-RS resources. The UE is configured with... A non-zero power (NZP) CSI-RS resource, and CSI reporting is configured to span multiple CSI-RS resources from the resource group. This is similar to the Class B K>1 configuration in Release 14 LTE. An NZP CSI-RS resource can belong to one CSI-RS resource set or multiple CSI-RS resource sets (e.g., Each resource set comprises one CSI-RS resource. Details are as explained in the public disclosure herein. Specifically, Each CSI-RS resource can be divided into Resource groups. Information about resource groups can be provided along with CSI-RS resource settings / configuration, or with CSI reporting settings / configuration, or with CSI-RS resource configuration.

[0149] In one example, AG corresponds to a subset (or group) of CSI-RS ports. The UE is configured with at least one NZPCSI-RS resource that includes (or is associated with) CSI-RS ports, which can be grouped (or divided) into multiple subsets / groups / parts of antenna ports, each corresponding to (or constituting) an AG. Information about port subsets or port groups can be provided along with CSI-RS resource settings / configurations, or CSI reporting settings / configurations, or CSI-RS resource configurations.

[0150] In one example, depending on the configuration, AG corresponds to one or more examples described herein. For instance, the configuration may be explicit via parameters (e.g., RRC parameters). Alternatively, the configuration may be implicit.

[0151] In one example, when implicit, the configuration can be based on The value. For example, when it has When there are multiple CSI-RS resources, the AG corresponds to one or more examples described in this document. For example, when there are... When there are multiple CSI-RS resources, AG corresponds to one or more examples described in this article.

[0152] In another example, the configuration can be based on the configured codebook. For example, according to one or more examples described herein, when the codebook corresponds to a decoupled codebook (a modular or separate codebook for each AG), the AG corresponds to a CSI-RS resource or a resource group; when the codebook corresponds to a coupled (joint or coherent) codebook (a joint codebook on the AG), the AG corresponds to a subset (or group) of CSI-RS ports.

[0153] In one example, when an AG maps (or corresponds to) a CSI-RS resource or resource group, and the UE can select a subset of AGs (resources or resource groups) and report the CSI of the selected AG (resource or resource group), the selected AG can be reported via an indicator. For example, the indicator can be a CRI or PMI (component) or a new indicator.

[0154] In one example, when an AG maps (or corresponds to) a CSI-RS port group, and the UE can select a subset of AGs (port groups) and report the CSI of the selected AG (port group), the selected AG can be reported via an indicator. For example, the indicator can be a CRI or PMI (component) or a new indicator.

[0155] In one example, when targeting Each AG is configured with multiple ( When using CSI-RS resources, use / configure a decoupled (modular) codebook, and when targeting Each AG is configured with a single ( When using CSI-RS resources, use / configure the union codebook.

[0156] In this disclosure, symbols and The term has been used interchangeably to indicate the number of AG or TRP or CSI-RS resources (in a CSI resource set) linked to CSI reports (as described later).

[0157] Figure 12 A timeline 1200 of example SD and FD units according to an embodiment of this disclosure is shown. For example, the timeline 1200 of example SD and FD units can be... Figure 1 Following any of UEs 111-116. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0158] In one embodiment, the UE is configured with CSI reporting (e.g., via higher-level CSI configuration information), where the CSI reporting is based on channel measurements (and interference measurements) and codebook. When CSI reporting is configured to be aperiodic, it is triggered via a DCI field (e.g., a CSI request field) in the DCI.

[0159] CSI reports can be based on... Channel measurements are performed on a number of Channel Measurement Resources (CMRs), transmitted from multiple Spatial Domain (SD) elements (e.g., SD element = CSI-RS antenna port) and measured via multiple Frequency Domain (FD) elements (e.g., FD element = one or more PRB / SB) and via Time Domain (TD) elements or multiple TD elements (e.g., TD element = one or more time slots). In one example, the CMR may be an NZP-CSI-RS resource.

[0160] A CSI report can be associated with multiple FD units and multiple TD units associated with channel measurements. Alternatively, a CSI report can be associated with a second set of FD units (different from the multiple FD units associated with channel measurements) and / or a second set of TD units (different from the multiple TD units associated with channel measurements). In the latter case, based on channel measurements, the UE can perform predictions (interpolation or extrapolation) in the second set of FD units and / or the second set of TD units associated with the CSI report.

[0161] See Figure 12 The diagram shows the SD unit (first and second antenna sizes), FD unit, and TD unit.

[0162] The first dimension is associated with the first antenna port dimension and includes Units;

[0163] The second dimension is related to the second antenna port dimension and includes... Units;

[0164] The third dimension is related to the frequency dimension and includes Units; and

[0165] The fourth dimension is associated with the time / Doppler dimension and includes... Units.

[0166] Multiple SD units can be coupled with one or more antenna groups (i.e. The antenna ports are associated with each other (e.g., located at the same site or distributed across multiple sites), and the spatial domain characteristics of the channel measurements are dimensioned.

[0167] when At that time, there exists a group including CMR for each CSI-RS antenna port.

[0168] when At that time, there exists a group including For each port of the AG, the CSI report is based on channel measurements from that AG.

[0169] When it exists When there is one AG, the CSI report is based on channel measurements from / across multiple AGs.

[0170] when In this case, multiple Channel Mapping Regulators (CMRs) exist, and the CSI report is based on channel measurements across multiple CMRs. In one example, a CMR corresponds to an Aggregate AG (one-to-one mapping). In another example, multiple CMRs may correspond to a single Aggregate AG (many-to-one mapping).

[0171] In one example, when When all antenna ports are located at one site In one example, when When the antenna ports are distributed across multiple sites (not all located together), .

[0172] In one example, when When multiple antenna ports are located at a single site and within a single antenna panel In one example, when When an antenna port is distributed across multiple antenna panels (which can be co-located or non-co-located). .

[0173] The value can be configured, for example, via higher-level RRC parameters, or indicated via MAC CE, or provided via the DCI field.

[0174] same, The value can be configured, for example, via higher-level RRC parameters, or indicated via MAC CE, or provided via the DCI field.

[0175] In one example . The value can be configured, for example, via higher-level RRC parameters. Or it can be indicated via MAC CE. Or it can be provided via the DCI field.

[0176] In one example The value is based on The value determines this. In one example, The value is based on The value determines it.

[0177] Multiple FD units can be associated with frequency domain allocations of resources (e.g., one or more CSI reporting bands, each including multiple PRBs) and dimensionalize the frequency domain (or delay) characteristics of channel measurements.

[0178] Multiple TD units can be associated with the temporal allocation of resources (e.g., one or more CSI reporting windows, each containing multiple time slots) and dimensionalize the temporal (or Doppler) characteristics of channel measurements.

[0179] The CSI report includes information about the precoding matrix (e.g., indicators such as PMI). Information about the precoding matrix includes / contains at least two components ( and First component () This includes a basis corresponding to a set of base entities (e.g., DFT vectors). The second component ( )include:

[0180] For low resolution (Type I), select base entities (e.g., DFT vectors) from the base entities (per layer) and keep them in phase across two polarizations.

[0181] For high resolution (Type II), the combination coefficients of linearly combined base entities, i.e., the precoding matrix, can be represented as a weighted sum over the base entities, where the weights are the combination coefficients.

[0182] First Component It is codebook-based. When a base needs to be reported (or is configured to be reported), the codebook configured for CSI reporting includes at least one function for reporting bases. The component. This component is similar to a common codebook (e.g., the codebooks of Type I and II in 5G NR). However, due to and Separation, allowing for future upgrades as new antenna types become available, is possible. The basis offers more options and parameterization. It can be specified (or associated with) at least one of the spatial domain characteristics, frequency (or delay) domain characteristics, or time (Doppler) domain characteristics of the channel measurements. Even though the number of CSI-RS antenna ports can be large (e.g., 256), the antenna ports are expected to have some antenna structure (e.g., similar to a 2D active antenna array). Therefore, SD channel characteristics can be represented using SD basis entities, where the SD basis entity has a parameter that depends on the number of SD elements (…). or or or The dimension of FD channel features may be correlated across FD units, and time-division duplex (DD) / time-division (TD) channel features are also expected to have some correlation across DD / TD units (e.g., for low-to-medium speed UEs). Therefore, FD and DD / TD channel features can be represented using FD and DD / TD base entities, respectively, where their dimensions depend on the number of FD units ( ). ) and the number of DD / TD units ( ).

[0183] Second component ( It is also codebook-based, and based on channel measurements and Derived. For example, channel measurements can be projected onto a base. Above, and the projected channel can be used for export. Components (coefficients), for example, codebooks based on type I or type II in 5G NR.

[0184] In one example The number of antenna ports on each CSI-RS resource is the same. For example, Each of the CSI-RS resources can be connected to Each antenna port is associated. In this case, the total number of antenna ports is... .

[0185] In one example The number of antenna ports on each CSI-RS resource can be the same or different. For example, Each of the CSI-RS resources can be connected to Each antenna port is associated. In this case, the total number of antenna ports is... .

[0186] In port numbering scheme 1, CSI-RS ports are determined according to (polarization) NZP CSI-RS resources Number them in the order of ), for example, The CSI-RS port, followed by The CSI-RS port, followed by The CSI-RS port, followed by The CSI-RS port, followed by The CSI-RS port, followed by The CSI-RS port.

[0187] In port numbering scheme 2, CSI-RS ports are based on (polarization) NZP CSI-RS resources The sequential numbering of ) is:

[0188] The CSI-RS port, followed by The CSI-RS port, ..., followed by CSI-RS port; and

[0189] Then it is The CSI-RS port, followed by The CSI-RS port, ..., followed by The CSI-RS port.

[0190] In one embodiment, the UE is configured with One NZP CSI-RS resource (or a CSI-RS antenna port or antenna port group within an NZP CSI-RS resource) CSI reports are associated with (or span across) these resources (a subset of these resources). CSI reports are based on reports corresponding to... and The codebase of the components is determined. Specifically, the layer... The precoder is given by the following formula:

[0191]

[0192] Here,

[0193] yes vector, where, ,

[0194] It includes A block diagonal matrix of blocks, where two blocks are associated with two antenna polarizations (two halves or two groups of CSI-RS antenna ports) for each NZP CSI-RS resource, and each block is... SD base or port selection matrix (similar to the CJT codebook of type I or type II of type II or type II of type II or port selection (PS) or CJTPS codebook of type II ...

[0195] It is a coefficient matrix, where, ,as well as

[0196] It is a standardization factor.

[0197] In one example and This refers to the number of NZP CSI-RS resources configured for channel measurements (e.g., within a CSI resource set). In one example, It is either fixed (e.g., 2, 3, or 4) or configured (e.g., via a higher layer from {2, 3, 4} or {1, 2, 3, 4}), or reported by the UE (e.g., as part of a UE capability). In one example, The value can be In one example, The value can be In one example, The value is configured (e.g., via a higher level). In one example, The value is reported by the UE (e.g., as part of a CSI report). In one example, the UE (e.g., UE 116) is configured with (i.e., do not select NZP CSI-RS resources) or (That is, the UE dynamically selects NZP CSI-RS resources). When the UE performs dynamic selection, the selected NZP CSI-RS resources can be reported via part 1 of the two parts of CSI (or UCI). This report can be transmitted via size... Bitmap indicator.

[0198] In one example, for port numbering scheme 1, It includes The block diagonal matrix of blocks , among which, the piece and With NZPCSI-RS resources The two antenna polarizations (two halves or two groups of CSI-RS antenna ports) are associated. For type I, It is a block matrix and , yes Element column (selection) vector, in element or It contains the value 1 in one position and the value 0 in other positions. It is a coefficient. Note that when hour, ,therefore, No report is required. Therefore, when hour, Reported. For type II, It is a linear (summation) combination basis vectors Vector (see W2 of type II in version 15 / 16 / 17).

[0199] In one example, for port numbering scheme 2, It includes The block diagonal matrix of blocks , among which, the piece and With NZP CSI-RS resources The two antenna polarizations (two halves or two groups of CSI-RS antenna ports) are associated. For type I, It is a block matrix and yes Element column (selection) vector, in element or It contains the value 1 in one position and the value 0 in other positions. It is a coefficient. Note that when hour, ,therefore, No report is required. Therefore, when hour, Reported. For type II, It is a linear (summation) combination A vector of basis vectors (see W2 of type II, version 15 / 16 / 17).

[0200] For each CSI-RS resource or yes SD basis matrix, wherein, includes Columns Each SD basis vector is determined in the same manner as the version 15 type I or version 15 / 16 / 17 type II codebook (refer to 5.2.2.2.1 / 2 / 3, REF 8).

[0201] For a given antenna port layout and two-dimensional oversampling factor DFT vector It can be represented as follows.

[0202]

[0203] in, and Here, It can be fixed, such as (1,1), (2,2), (2,1), (2,2), (4,1) or (4,4), or it can be configured. This may vary depending on the resources available. It can depend on .For example, or ,in, It can be fixed, such as 64 or 128, or it can be configured.

[0204] set up It is related to CSI-RS resources The number of associated CSI-RS ports. Let... It is the total number of resources or port groups, where, It is the first The number of resources in the dimension, and In one example, the UE is configured with one of the following:

[0205] In one example, the UE is configured with or and .

[0206] In one example, the UE is configured with or and .

[0207] In one example, the UE is configured with and .

[0208] In one example, the UE is configured with or and .

[0209] In one example, the UE is configured with one of the parameters from a set of supported value combinations, which can be each of the combinations shown in Table 2 or a subset thereof.

[0210] Table 2

[0211]

[0212]

[0213]

[0214] As described in Section 5.1.5 of TS 38.214, a UE can be configured with a QCL assumption of NZP CSI-RS resources (i.e., QCL source RS and QCL type).

[0215] -Start: TS 38.214 [REF8] Section 5.1.5-

[0216] The UE can be configured with a list of up to M TCI-State configurations within the higher-layer parameter PDSCH-Config to decode the PDSCH based on the detected PDCCH with DCI for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI-State contains parameters for configuring a quasi-co-address relationship between one or two downlink reference signals and the DMRS port of the PDSCH, the DMRS port of the PDCCH, or the CSI-RS port of the CSI-RS resource. The quasi-co-address relationship is configured by the higher-layer parameter qcl-Type1 for the first DL RS and qcl-Type2 for the second DL RS (if configured). In the case of two DL RSs, the QCL type should not be the same, regardless of whether the reference is for the same DL RS or different DL RSs. The quasi-co-address type corresponding to each DL RS is given by the higher-layer parameter qcl-Type in QCL-Info and can take one of the following values:

[0217] - 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}

[0218] - 'typeB': {Doppler shift, Doppler spread}

[0219] - 'typeC': {Doppler shift, average delay}

[0220] - 'typeD': {space receive parameters}

[0221] The UE can be configured with a list of up to 128 TCI-State configurations in the higher-level parameter dl-OrJoint-TCIStateList in PDSCH-Config, which are used to provide reference signals for quasi-co-addressing of the DMRS of PDSCH and PDCCH in BWP / Component Carrier (CC), for CSI-RS, and to provide references, and, if applicable, to determine UL TX spatial filters and SRS for PUSCH and PUCCH resources based on dynamic granting and configuration granting in BWP / CC.

[0222] If the BWP of a CC does not contain a TCI-State or UL-TCI-State configuration, the UE can apply the TCI-State or UL-TCI-State configuration from the reference BWP of the reference CC. If the UE is configured with dl-OrJoint-TCIStateList or UL-TCI-State in any CC in the same frequency band, it is not expected that the UE will be configured with tci-StatesToAddModList, SpatialRelationInfo, or PUCCH-SpatialRelationInfo, except for SpatialRelationInfoPos in the CC of the same frequency band. The UE can expect that when the UE has tci-StatesToAddModList configured in any CC in the CC list configured by simultaneousTCI-UpdateList1-r16, simultaneousTCI-UpdateList2-r16, simultaneousSpatial-UpdatedList1-r16 or simultaneousSpatial-UpdatedList2-r16, the UE is not configured with dl-OrJoint-TCIStateList or UL-TCI-State in any CC within the same frequency band in the CC list.

[0223] The UE receives an activation command, as described in Clause 6.1.3.14 of [10, TS 38.321] or Clause 6.1.3.47 of [10, TS 38.321], to map up to eight Transmission Configuration Indication (TCI) states and / or TC state pairs (where one TCI state is for a DL channel / signal and one TCI state is for a UL channel / signal) to the code point of the DCI field 'Transmission Configuration Indication' of one or a set of CC / DL BWPs (if applicable, one or a set of CC / UL BWPs). When a set of TCI state IDs is activated for a set of CC / DL BWPs and, if applicable, for a set of CC / DL BWPs, wherein the list of applicable CCs is determined by the CCs indicated in the activation command, the same set of TCI state IDs is applied to the DL and / or UL BWPs in the indicated CCs. If the activation command maps TCI-State and / or UL-TCI-State to only one TCI code point, the UE shall apply the indicated TCI-State and / or UL-TCI-State to one or a set of CC / DL BWPs, and, if applicable, once the indicated mapping for a single TCI code point is applied as described in [11, TS 38.133], apply one or a set of CC / UL BWPs.

[0224] When no bwp-id or cell for the QCL-Type A / D source RS is configured in the QCL information of the TCI state, the UE assumes that the QCL-Type A / D source RS is configured in the CC / DL BWP applicable to the TCI state.

[0225] When tci-PresentInDCI is set to 'Enabled' or tci-PresentDCI-1-2 is configured for CORESET, a UE configured with a dl-OrJoint-TCIStateList having an active TCI-State or UL-TCI-State receives DCI format 1_1 / 1_2, which is a CC or each CC in the same CC list configured by simultaneousU-TCI-UpdateList1-r17, simultaneousU-TCI-UpdateList2-r17, simultaneousU-TCI-UpdateList3-r17, and simultaneousU-TCI-UpdateList4-r17 provides an indicated TCI-State and / or UL-TCI-State. DCI format 1_1 / 1_2 may or may not have a DL allocation, if applicable. If DCI format 1_1 / 1_2 has no DL allocation, the UE can expect the following:

[0226] - The configured scheduled RNTI (CS-RNTI) is used to scramble the CRC of the DCI.

[0227] The following DCI field values ​​are set as follows:

[0228] -RV='1's

[0229] -MCS='1's

[0230] -NDI=0

[0231] - For Frequency Domain Resource Allocation (FDRA) type 0, set to '0's; for FDRA type 1, set to '1's; for dynamic switching, set to '0's (same as Table 10.2-4 of [6, TS 38.213]).

[0232] -End: TS 38.214 [REF8] Section 5.1.5-

[0233] TCI-State Information Element

[0234] -- ASN1START

[0235] -- TAG-TCI-STATE-START

[0236] TCI-State ::= SEQUENCE {

[0237] tci-StateId TCI-StateId,

[0238] qcl-Type1 QCL-Info,

[0239] qcl-Type2 QCL-Info OPTIONAL, -- Need R

[0240] ..., [[

[0242] additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL,-- Need R

[0243] pathlossReferenceRS-Id-r17 PUSCH-PathlossReferenceRS-Id-r17 OPTIONAL, -- Cond JointTCI

[0244] ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL-- Cond JointTCI ]]

[0246] }

[0247] QCL-Info ::= SEQUENCE {

[0248] cell ServCellIndex OPTIONAL, -- Need R

[0249] bwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-Indicated

[0250] referenceSignal CHOICE {

[0251] csi-rs NZP-CSI-RS-ResourceId,

[0252] ssb SSB-Index

[0253] },

[0254] qcl-Type ENUMERATED {typeA, typeB,typeC, typeD}, ...

[0256] }

[0257] -- TAG-TCI-STATE-STOP

[0258] -- ASN1STOP

[0259] QCL Information Field Description

[0260] bwp-Id: The DL BWP where RS is located.

[0261] cell: The serving cell of the UE that has referenceSignal configured. If this field is not present, it applies to the serving cell that has applied TCI-State. RS can be located on a serving cell other than the serving cell that has TCI-State configured, only if qcl-Type is configured as typeC or typeD. See section 5.1.5 of TS 38.214 [REF8]

[19] .

[0262] Reference Signal: The reference signal that provides quasi-matching information as specified in Clause 5.1.5 of TS 38.214 [REF8]

[19] .

[0263] qcl-Type: The QCL type specified in Section 5.1.5 of TS 38.214 [REF8]

[19] .

[0264] Table 3

[0265]

[0266] In one example, NZP CSI-RS resources can be configured using at least one of the following QCL assumptions (summarized in Table 3).

[0267] In one example, for a periodic (P)-CSI-RS that is a TRS (also known as a P-TRS), the QCL type can be (typeC, typeD), as described in this article.

[0268] For periodic CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher-level parameter trs-Info, the UE (e.g., UE 116) will expect TCI-State to indicate one of the following quasi-co-address types:

[0269] - 'type C' has a Synchronization Signal / Physical Broadcast Channel (SSB / PBCH) block, and 'type D' has the same SS / PBCH block where applicable, the SS / PBCH block may have a Physical Cell ID (PCI) different from the serving cell's PCI. The UE can expect that the center frequency, subcarrier spacing (SCS), and single-frequency network (SFN) offset of the SS / PBCH block from the serving cell and the SS / PBCH block with a PCI different from the serving cell are the same, or...

[0270] - 'typeC' has SS / PBCH blocks, and where applicable, in an NZP-CSI-RS-ResourceSet configured with the higher-layer parameter repetition, 'typeD' has CSI-RS resources, where the SS / PBCH blocks can have a PCI different from the serving cell's PCI. The UE can expect that the center frequency, SCS, and SFN offset of the SS / PBCH blocks from the serving cell and the SS / PBCH blocks with a different PCI from the serving cell are the same.

[0271] For periodic / semi-persistent CSI-RS, if the UE is configured with dl-OrJoint-TCIStateList, the UE can expect that the indicated TCI-State is not applied.

[0272] In one example, for aperiodic (AP)-CSI-RS as a TRS (also known as AP-TRS), the QCL type can be as described in this paper (typeA, typeD).

[0273] For non-periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet that are configured with the higher-level parameter trs-Info, the UE sets the expected TCI-State indication qcl-Type to 'typeA'. For periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet that are configured with the higher-level parameter trs-Info and, where applicable, qcl-Type is set to 'typeD', having the same periodic CSI-RS resources.

[0274] In one example, NZP CSI-RS resources can be configured for CSI reporting, where the number of reports includes content from QCL type = (typeA, typeD) or typeB (without typeD) (rank indicator (RI), precoding matrix indicator (PMI), channel quality indicator (CQI), CQI reporting interval (CRI), layer index (LI)), as described herein.

[0275] For CSI-RS resources in the NZP-CSI-RS-ResourceSet configured without higher-level parameters trs-Info and repetition, the UE will expect TCI-State to indicate one of the following quasi-co-address types:

[0276] -'typeA' has CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher-level parameter trs-Info, and 'typeD' has the same CSI-RS resources where applicable; or

[0277] -'typeA' has CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher-layer parameter trs-Info, and 'typeD' has SS / PBCH blocks where, where applicable, the SS / PBCH blocks can have a PCI different from that of the serving cell. The UE can expect that the center frequency, SCS, and SFN offset of the SS / PBCH blocks from the serving cell and the SS / PBCH blocks with a PCI different from that of the serving cell are the same; or

[0278] -'typeA' indicates that a CSI-RS resource is available in an NZP-CSI-RS-ResourceSet configured with the higher-level parameter trs-Info, and 'typeD' indicates that a CSI-RS resource is available in an NZP-CSI-RS-ResourceSet configured with the higher-level parameter repetition, where applicable; or

[0279] -'typeB', when 'typeD' is not applicable, has CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher-level parameter trs-Info.

[0280] In one example, the NZP CSI-RS resource can be configured for CSI / beam reporting, where the reporting volume includes content from (LI, CRI, RI, CQI, PMI or CRI / Synchronization Signal Block Resource Indicator (SSBRI)), L1-Reference Signal Received Power (RSRP) / L1-Signal Interference-Noise Ratio (SINR) / CapabilityIndex), where QCL type = (typeA, typeD) or (typeC, typeD), as described herein.

[0281] For CSI-RS resources in an NZP-CSI-RS-ResourceSet configured with the higher-level parameter repetition, the UE will expect TCI-State to indicate one of the following quasi-co-location types:

[0282] -'typeA' has CSI-RS resources in the NZP-CSI-RS-ResourceSet configured with the higher-level parameter trs-Info, and 'typeD' has the same CSI-RS resources where applicable; or

[0283] -'typeA' indicates that a CSI-RS resource is available in an NZP-CSI-RS-ResourceSet configured with the higher-level parameter trs-Info, and 'typeD' indicates that a CSI-RS resource is available in an NZP-CSI-RS-ResourceSet configured with the higher-level parameter repetition, where applicable; or

[0284] -'typeC' has an SS / PBCH block, and 'typeD' has the same SS / PBCH block when applicable. The reference RS can also be an SS / PBCH block with a PCI different from that of the serving cell. The UE can expect that the center frequency, SCS, and SFN offset of the SS / PBCH block from the serving cell and the SS / PBCH block with a PCI different from that of the serving cell are the same.

[0285] In this disclosure, several examples are for linking CSI reports based on codebooks (e.g., via codebookType in IE CSI-ReportConfig). The quasi-co-location (QCL) assumption on NZP CSI-RS resources is provided.

[0286] An NZP CSI-RS resource can be accessed via CSI-ResourceConfig, NZP CSI-RS-ResourceSet, CSI-MeasConfig, CSI-ReportConfig (which can be the same as a codebook-based CSI report), or CSI-AperiodicTriggerStateList (e.g., when...). (When an NZP CSI-RS resource is an AP or / and the CSI report is an AP) or via CSI-SemiPersistentOnPUSCH-TriggerStateList (e.g., when...) An NZP CSI-RS resource is an SP (or / and the CSI report is an SP) or configured via a new IC (different from the IE mentioned above).

[0287] In one example, when the preencoder (or preencoding matrix) of one (or more) layers is from When one of the NZP CSI-RS resources is sent or associated with that resource, it corresponds to the Non-Coherent Joint Transmission (NCJT) precoder.

[0288] In one example, when the preencoder (or preencoding matrix) of one (or more) layers is from When at least two of the NZP CSI-RS resources are transmitted or associated with at least two of the resources, it corresponds to a Coherent Joint Transmission (CJT) precoder.

[0289] In one example, when the preencoder (or preencoding matrix) of one (or more) layers is from When an NZP CSI-RS resource is sent or associated with a resource, it is a full CJT (F-CJT).

[0290] In one example, when the preencoder (or preencoding matrix) of one (or more) layers is from In NZP CSI-RS resources A sender or a connection to that When resources are associated, it is a partial CJT (P-CJT), where, .

[0291] In one embodiment, based on the use of The UE is configured to link to CSI reports using a codebook for each port (e.g., configured via codebookType in IE CSI-ReportConfig). One NZP CSI-RS resource. yes The total number of CSI-RS ports on each NZP CSI-RS resource. Each of the CSI-RS resources and The value is based on one of the examples described in this article.

[0292] In one example, the codebook corresponds to a (low-resolution) Type I codebook, as described in this disclosure. As described in sections 5.2.2.2.1 and 5.2.2.2 of TS 38.214, examples of Type I codebooks may resemble (or be based on) one of NR Type I codebooks, including their correspondence to... An extension of one CSI-RS port (as described in this disclosure).

[0293] In one example, the type I codebook is a single-pane codebook, i.e., CodebookType = typeI-SinglePanel (represented as C1).

[0294] In one example, the type I codebook is a multi-panel codebook, i.e., CodebookType = typeI-MultiPanel (represented as C2).

[0295] In one example, the type I codebook is a single-pane or multi-pane codebook, i.e., CodebookType = typeI-SinglePanel or typeI-MultiPanel.

[0296] In one example, the codebook corresponds to a (high-resolution) Type II codebook, as described in this disclosure. As described in sections 5.2.2.2.3 through 5.2.2.2.11 of TS38.214, examples of Type II codebooks may resemble (or be based on) one of the NR Type II codebooks, including their correspondence to... An extension of one CSI-RS port (as described in this disclosure).

[0297] In one example, the type II codebook is a regular type II codebook, i.e., CodebookType = typeII (represented as C3).

[0298] In one example, the Type II codebook is a Type II port selection codebook, i.e., CodebookType=TypeII-portselection (represented as C4).

[0299] In one example, the Type II codebook is either a regular or Type II port-selective codebook, i.e., CodebookType = C3 or C4.

[0300] In one example, the type II codebook is a regular enhanced type II codebook, i.e., CodebookType = typeII-r16 (represented as C5).

[0301] In one example, the Type II codebook is an enhanced Type II port selection codebook, i.e., CodebookType = typeII-PortSelection-r16 (represented as C6).

[0302] In one example, the Type II codebook is a further enhanced Type II port selection codebook, i.e., CodebookType = typeII-PortSelection-r17 (represented as C7).

[0303] In one example, the Type II codebook is either a regular or Type II port-selective codebook, i.e., CodebookType = C5 or C6 / C7.

[0304] In one example, the type II codebook is the regular enhanced type IICJT codebook, i.e., CodebookType = typeII-CJT-r18 (represented as C8).

[0305] In one example, the Type II codebook is n further enhanced Type IICJT port selection codebooks, i.e., CodebookType = typeII-CJT-PortSelection-r18 (represented as C9).

[0306] In one example, the Type II codebook is C8 or C9, i.e., CodebookType = C8 or C9.

[0307] In one example, the Type II codebook is a regular enhanced Type II Doppler codebook, i.e., CodebookType= typeII-Doppler-r18 (represented as C10).

[0308] In one example, the Type II codebook is n further enhanced Type II Doppler port selection codebooks, i.e., CodebookType = typeII-Doppler-PortSelection-r18 (denoted as C11).

[0309] In one example, the Type II codebook is C10 or C11, i.e., CodebookType = C10 or C11.

[0310] In one example, the codebook may be only a type I codebook, which may be fixed (according to at least one example described herein) or configured by one of a number of supported type I codebooks (according to an example described herein).

[0311] In one example, the codebook may be only a Type II codebook, which may be fixed (according to at least one example described herein) or configured by one of a number of supported Type I codebooks (according to an example described herein).

[0312] In one example, the codebook corresponds to either a (low-resolution) Type I codebook or a (high-resolution) Type II codebook, wherein the Type I and Type II codebooks are based on at least one of the corresponding examples described herein. One of the two codebooks can be configured via a higher level (e.g., CodebookType). The Type I codebook can be fixed (based on at least one example described herein) or one of several supported Type I codebooks (from the examples described herein). The Type II codebook can be fixed (based on at least one example described herein) or one of several supported Type II codebooks (from the examples described herein).

[0313] In one example, the collection Including values ,For example, or .

[0314] In one example, the collection Includes values ​​from {4, 8, 12, 16, 24, 32, 48, 64, 96, 128}.

[0315] In one example, when At that time, the codebook is associated with a CSI-RS port in a CSI-RS resource.

[0316] in this case, or and CRI instructions One of the CSI-RS resources.

[0317] In one example, when hour:

[0318] The codebook is associated with a CSI-RS port in a CSI-RS resource. In this case... or and CRI instructions One of the CSI-RS resources, and each CSI-RS resource is associated with Each port is associated.

[0319] codebook and cross The CSI-RS ports of each CSI-RS resource aggregation are associated.

[0320] codebook and cross The CSI-RS ports of each CSI-RS resource aggregation are associated.

[0321] In one embodiment, The QCL assumptions (i.e., QCL source RS and QCL type) for an NZP CSI-RS resource can be the same / shared, meaning a shared QCL assumption is used / configured for... One of the motivations for sharing / identifying the same QCL is the availability of NZP CSI-RS resources. Each NZP CSI-RS resource is used to simulate the behavior of an NZP CSI-RS resource (as in a shared Type I codebook). Another motivation is that it can facilitate scalable NZP CSI-RS resource configuration for various use cases (co-located or non-co-located) and frequency bands (<1GHz, FR1, IF band, 6-15GHz or FR2) and antenna architectures.

[0322] In one example, the same / shared QCL (source RS and QCL type) can be configured according to one of the shared QCL configurations shown in Table 3.

[0323] In one example, the shared QCL configuration corresponds only to one of Q4-Q7, for example, Q4.

[0324] In one example, the shared QCL configuration corresponds to two of Q4-Q7, such as (Q4, Q5) or (Q4, Q7).

[0325] In one example, the shared QCL configuration corresponds to three of Q4-Q7, for example, (Q4, Q5, Q7) or (Q4, Q4, Q6).

[0326] In one example, the shared QCL configuration corresponds to Q4-Q7.

[0327] In one example, the shared QCL configuration corresponds to Q4-Q10.

[0328] In one example, the shared QCL configuration corresponds to Q1-Q10.

[0329] Table 4: Examples of QCL Information

[0330]

[0331] In one example, the same / shared QCL (source RS and QCL type) corresponds to only one QCL information (corresponding to one of the shared QCL types A / B / C / D), which can be one of the examples R1 to R20 shown in Table 4.

[0332] In one example, only one QCL message is fixed, and it corresponds to typeA.

[0333] In one example, only one QCL message is fixed, and it corresponds to type B.

[0334] In one example, only one QCL message is fixed, and it corresponds to type C.

[0335] In one example, only one QCL message is fixed, and it corresponds to typeD.

[0336] In one example, only one QCL message is configured and corresponds to one of T1 = (typeA, typeB).

[0337] In one example, only one QCL message is configured and corresponds to one of T2 = (typeA, typeC).

[0338] In one example, only one QCL message is configured and corresponds to one of T3 = (typeA, typeD).

[0339] In one example, only one QCL message is configured and corresponds to one of T4 = (typeB, typeC).

[0340] In one example, only one QCL message is configured and corresponds to one of T5 = (typeB, typeD).

[0341] In one example, only one QCL message is configured and corresponds to one of T6 = (typeC, typeD).

[0342] In one example, only one QCL message is configured and corresponds to one of S1 = (typeA, typeB, typeC).

[0343] In one example, only one QCL message is configured and corresponds to one of S2 = (typeA, typeB, typeD).

[0344] In one example, only one QCL message is configured and corresponds to one of S3 = (typeA, typeC, typeD).

[0345] In one example, only one QCL message is configured and corresponds to one of S4 = (typeB, typeC, typeD).

[0346] In one example, only one QCL message is configured and corresponds to one of (typeA, typeB, typeC, typeD).

[0347] In one example, the same / shared QCL (source RS and QCL type) includes two QCL pieces of information (corresponding to two different QCL types, from shared QCL types A / B / C / D), each of which can be one of the examples R1 to R20 shown in Table 4. In one example, the source RS is the same for both QCL pieces of information. In one example, the source RS is different for both QCL pieces of information. In one example, the source RS can be the same or different for both QCL pieces of information.

[0348] In one example, two QCL messages are fixed and correspond to T1 = (typeA, typeB).

[0349] In one example, two QCL messages are fixed and correspond to T2 = (typeA, typeC).

[0350] In one example, two QCL messages are fixed and correspond to T3 = (typeA, typeD).

[0351] In one example, two QCL messages are fixed and correspond to T4 = (typeB, typeC).

[0352] In one example, two QCL messages are fixed and correspond to T5 = (typeB, typeD).

[0353] In one example, two QCL messages are fixed and correspond to T6 = (typeC, typeD).

[0354] In one example, two QCL messages are configured and correspond to one of {T1, T2}.

[0355] In one example, two QCL messages are configured and correspond to one of {T1, T3}.

[0356] In one example, two QCL messages are configured and correspond to one of {T1, T4}.

[0357] In one example, two QCL messages are configured and correspond to one of {T1, T5}.

[0358] In one example, two QCL messages are configured and correspond to one of {T1, T6}.

[0359] In one example, two QCL messages are configured and correspond to one of {T2, T3}.

[0360] In one example, two QCL messages are configured and correspond to one of {T2, T4}.

[0361] In one example, two QCL messages are configured and correspond to one of {T2, T5}.

[0362] In one example, two QCL messages are configured and correspond to one of {T2, T6}.

[0363] In one example, two QCL messages are configured and correspond to one of {T3, T4}.

[0364] In one example, two QCL messages are configured and correspond to one of {T3, T5}.

[0365] In one example, two QCL messages are configured and correspond to one of {T3, T6}.

[0366] In one example, two QCL messages are configured and correspond to one of {T4, T5}.

[0367] In one example, two QCL messages are configured and correspond to one of {T4, T6}.

[0368] In one example, two QCL messages are configured and correspond to one of {T5, T6}.

[0369] In one example, two QCL messages are configured and correspond to one of {T1, T2, T3}.

[0370] In one example, two QCL messages are configured and correspond to one of {T1, T2, T4}.

[0371] In one example, two QCL messages are configured and correspond to one of {T1, T2, T5}.

[0372] In one example, two QCL messages are configured and correspond to one of {T1, T2, T6}.

[0373] In one example, two QCL messages are configured and correspond to one of {T1, T3, T4}.

[0374] In one example, two QCL messages are configured and correspond to one of {T1, T3, T5}.

[0375] In one example, two QCL messages are configured and correspond to one of {T1, T3, T6}.

[0376] In one example, two QCL messages are configured and correspond to one of {T1, T4, T5}.

[0377] In one example, two QCL messages are configured and correspond to one of {T1, T4, T6}.

[0378] In one example, two QCL messages are configured and correspond to one of {T1, T5, T6}.

[0379] In one example, two QCL messages are configured and correspond to one of {T2, T3, T4}.

[0380] In one example, two QCL messages are configured and correspond to one of {T2, T3, T5}.

[0381] In one example, two QCL messages are configured and correspond to one of {T2, T3, T6}.

[0382] In one example, two QCL messages are configured and correspond to one of {T2, T4, T5}.

[0383] In one example, two QCL messages are configured and correspond to one of {T2, T4, T6}.

[0384] In one example, two QCL messages are configured and correspond to one of {T2, T5, T6}.

[0385] In one example, two QCL messages are configured and correspond to one of {T3, T4, T5}.

[0386] In one example, two QCL messages are configured and correspond to one of {T3, T4, T6}.

[0387] In one example, two QCL messages are configured and correspond to one of {T3, T5, T6}.

[0388] In one example, two QCL messages are configured and correspond to one of {T4, T5, T6}.

[0389] In one example, two QCL messages are configured and correspond to one of {T1, T2, T3, T4}.

[0390] In one example, two QCL messages are configured and correspond to one of {T1, T2, T3, T5}.

[0391] In one example, two QCL messages are configured and correspond to one of {T1, T2, T3, T6}.

[0392] In one example, two QCL messages are configured and correspond to one of {T1, T2, T4, T5}.

[0393] In one example, two QCL messages are configured and correspond to one of {T1, T2, T4, T6}.

[0394] In one example, two QCL messages are configured and correspond to one of {T1, T2, T5, T6}.

[0395] In one example, two QCL messages are configured and correspond to one of {T1, T3, T4, T5}.

[0396] In one example, two QCL messages are configured and correspond to one of {T1, T3, T4, T6}.

[0397] In one example, two QCL messages are configured and correspond to one of {T1, T3, T5, T6}.

[0398] In one example, two QCL messages are configured and correspond to one of {T1, T4, T5, T6}.

[0399] In one example, two QCL messages are configured and correspond to one of {T2, T3, T4, T5}.

[0400] In one example, two QCL messages are configured and correspond to one of {T2, T3, T4, T6}.

[0401] In one example, two QCL messages are configured and correspond to one of {T2, T3, T5, T6}.

[0402] In one example, two QCL messages are configured and correspond to one of {T2, T4, T5, T6}.

[0403] In one example, two QCL messages are configured and correspond to one of {T3, T4, T5, T6}.

[0404] In one example, two QCL messages are configured and correspond to one of {T1, T2, T3, T4, T5}.

[0405] In one example, two QCL messages are configured and correspond to one of {T1, T2, T3, T4, T6}.

[0406] In one example, two QCL messages are configured and correspond to one of {T1, T2, T3, T5, T6}.

[0407] In one example, two QCL messages are configured and correspond to one of {T1, T2, T4, T5, T6}.

[0408] In one example, two QCL messages are configured and correspond to one of {T1, T3, T4, T5, T6}.

[0409] In one example, two QCL messages are configured and correspond to one of {T2, T3, T4, T5, T6}.

[0410] In one example, two QCL messages are configured and correspond to one of {T1, T2, T3, T4, T5, T6}.

[0411] In one example, the same / shared QCL (source RS and QCL type) includes three QCL pieces of information (corresponding to three different QCL types, from the shared QCL type A / B / C / D). Each can be based on one of the examples R1 to R20 shown in Table 4, where S1-S4 are defined herein. In one example, the source RS is the same for any two of the three QCL pieces of information. In one example, the source RS is different for any two of the three QCL pieces of information. In one example, the source RS can be the same or different for any two of the three QCL pieces of information.

[0412] In one example, the three QCL messages are fixed and correspond to S1.

[0413] In one example, the three QCL messages are fixed and correspond to S2.

[0414] In one example, three QCL messages are fixed and correspond to S3.

[0415] In one example, three QCL messages are fixed and correspond to S4.

[0416] In one example, three QCL messages are configured and correspond to one of {S1, S2}.

[0417] In one example, three QCL messages are configured and correspond to one of {S1, S3}.

[0418] In one example, three QCL messages are configured and correspond to one of {S1, S4}.

[0419] In one example, three QCL messages are configured and correspond to one of {S2, S3}.

[0420] In one example, three QCL messages are configured and correspond to one of {S2, S4}.

[0421] In one example, three QCL messages are configured and correspond to one of {S3, S4}.

[0422] In one example, three QCL messages are configured and correspond to one of {S1, S2, S3}.

[0423] In one example, three QCL messages are configured and correspond to one of {S1, S2, S4}.

[0424] In one example, three QCL messages are configured and correspond to one of {S1, S3, S4}.

[0425] In one example, three QCL messages are configured and correspond to one of {S2, S3, S4}.

[0426] In one example, three QCL messages are configured and correspond to one of {S1, S2, S3, S4}.

[0427] In one example, the same / shared QCL (source RS and QCL type) includes a QCL information (corresponding to a new QCL type, TypeE), each of which can be based on one of the four corresponding examples (R5, R10, R15, R20) shown in Table 4. In one example, TypeE corresponds to a QCL type that will The NZP CSI-RS resources are linked together for CSI reporting via a unified codebook on K resources.

[0428] In one example, the same / shared QCL (source RS and QCL type) includes two QCL pieces of information (a shared type A / B / C / D and a new QCL type, TypeE). Each can be based on one of the examples R1 to R20 shown in Table 4. In one example, or in one or more examples described herein, TypeE replaces one of the two QCL pieces of information.

[0429] In one example, the same / shared QCL (source RS and QCL type) includes three QCL pieces of information (two shared types A / B / C / D and a new QCL type, TypeE). Each can be one of the examples R1 to R20 shown in Table 4. In one example, or in one or more examples described herein, TypeE replaces one of the three QCL pieces of information.

[0430] In one example, the same / shared QCL (source RS and QCL type) includes four QCL pieces of information (three shared types A / B / C / D and a new QCL type, TypeE). Each can be one of the examples R1 to R20 shown in Table 4. In one example, or in one or more examples described herein, TypeE replaces one of the four QCL pieces of information.

[0431] In one example, the UE is also configured with a CSI-IM resource set for interference measurements (e.g., via CSI-IM-ResourceSet) and linked to a CSI report, as explained herein (e.g., this link could be via CSI-ReportConfig). The CSI-IM resource set may include... Each CSI-IM resource, QCL assumption, and QCL type. In one example... In one example, (One-to-one correspondence). In one example,

[0432] In one example The QCL assumptions and QCL types of each CSI-IM resource are as follows: Resources can be the same or shared.

[0433] In one example The QCL assumptions and QCL types of each CSI-IM resource are as follows: The resources can be different or independent.

[0434] In one embodiment, the UE is configured based on a codebook for CSI reporting. One NZP CSI-RS resource, details as described in this article, except for a subset of the CSI-RS resources (including...). In NZP CSI-RS resources (each) has the same / shared QCL assumptions (based on at least one example described herein). Here, In one example, It is fixed (e.g., 1), configured (e.g., via higher-level parameters), or reported by the UE (e.g., via UCI parameters or UL MAC CE).

[0435] Remaining The QCL assumptions for individual CSI-RS resources can be the same as those for shared resources; that is, for each remaining CSI-RS resource, they can be different / independent. Alternatively, the QCL assumptions for the remaining K-K CSI-RS resources can be the same / shared (but different from those for...) The assumptions about the resources may be different, and they may be provided using shared or new mechanisms.

[0436] In one example, a subset of CSI-RS resources can be fixed.

[0437] In one example, the subset corresponds to the previous There are NZP CSI-RS resources, which can be based on NZP CSI-RS resource IDs sorted in ascending or descending order.

[0438] In one example, this subset corresponds to the first part of the CSI-RS resource set. One NZP CSI-RS resource.

[0439] In one example, information about a subset of CSI-RS resources can be configured. In one example, this information corresponds to size. A bitmap (sequence) of bits (one bit per resource). In one example, this information corresponds to a parameter indicating a subset of CSI-RS resources. In another example, this information corresponds to a list / pool / set of NZP CSI-RS resources or a list / pool / set of NZP CSI-RS resource IDs.

[0440] In one example, this information can be configured via higher-level parameters (RRC). In another example, this information can be included within an existing higher-level IE, such as NZP CSI-RS-resource, or NZP CSI-RS-resource set, or CSI-ResourceConfig, or CSI-ReportConfig, or CSI-AperiodicTriggerStateList, or CSI-SemiPersistentOnPUSCH-TriggerStateList, or QCL-Info, or TCI status. In yet another example, a new IE indicating the information can be defined.

[0441] In one example, the information can be configured via a MAC CE. In one example, for AP CSI-RS / CSI reporting, the information can be provided / indicated via an existing MAC CE activation command that activates a subset of Ap-TriggerStates and maps it to code points in the DCI field of the DCI (e.g., triggering AP-CSI UL-DCI via the CSI request field). In one example, for SP CSI-RS / CSI reporting, the information can be provided / indicated via an existing MAC CE activation command that activates a subset of TriggerStates and maps it to code points in the DCI field of the DCI (e.g., triggering SP-CSI UL-DCI via the CSI request field). In one example, a new MAC CE indicating this information can be defined.

[0442] In one example, this information can be configured via DCI.

[0443] In one example, the DCI is a DL-DCI (e.g., format 1_1, 1_2). In one example, the information may be included in an existing DCI field (e.g., TCI status) or a new DCI field.

[0444] In one example, the DCI is UL-DCI (e.g., format 0_0, 0_1, 0_2). In one example, this information can be included in an existing DCI field (e.g., a CSI request field) or a new DCI field.

[0445] In one example, the information can be configured via a combination of MAC CE and DCI. For example, MAC CE can activate a fixed number (i.e., The CSI-RS resources, then the DCI can indicate One CSI-RS resource.

[0446] In one example, information about a subset of CSI-RS resources can be reported by the UE (e.g., UE 116). In one example, the information is included in the UCI (e.g., a portion of the UCI on the PUCCH or both portions of the UCI on the PUCCH / PUSCH) parameters. In one example, the information is included in the UL MAC CE (e.g., an existing UL MAC CE, such as the MAC CE for PHR-Config, or a new UL MAC CE).

[0447] In one embodiment, the UE is configured based on a codebook for CSI reporting. One NZP CSI-RS resource, details as described in this article, except for (a) (a) CSI-RS resources have the same / shared QCL assumptions (as described in one or more embodiments herein), or (b) a subset of CSI-RS resources (including In NZP CSI-RS resources Each of the four QCL hypotheses has the same / shared assumptions (as described in one or more embodiments herein). In one example, the parameter is used to configure / indicate one of the QCL hypotheses (a) and (b).

[0448] In one example, this parameter can be configured via a higher-level RRC (e.g., via NZP CSI-RS-resource, or NZP CSI-RS-resource set, or CSI-ResourceConfig, or CSI-ReportConfig, or CSI-non-AperiodicTriggerStateList, or CSI-SemiPersistentOnPUSCH-TriggerStateList, or QCL-Info, or TCI-State).

[0449] In one example, this parameter can be configured via MAC CE.

[0450] In one example, this parameter can be configured via DCI (e.g., DL-DCI or UL-DCI).

[0451] In one embodiment, for AP CSI-RS / CSI reports according to the codebook described herein, a restriction can be enabled in the CSI-AperiodicTriggerState definition. Similarly, for SP CSI-RS / CSI reports according to the codebook described herein, a restriction can be enabled in the CSI-SemiPersistentTriggerState definition.

[0452] In one example, this limitation corresponds to... The same / shared QCL assumptions for NZP CSI-RS resources (e.g., in a CSI resource set).

[0453] In one example A pool of NZP CSI-RS resources (e.g., within a CSI resource set) can be partitioned into NZP CSI-RS resources. Each subset includes 1 subset. Each NZP CSI-RS resource has the same / shared QCL assumptions. One of the subsets can be activated / indicated via MAC CE and / or DCI. Alternatively, MAC CE can activate... A subset, and when When a subset is activated, one of the activated subsets can be indicated via a DCI indicator.

[0454] In one embodiment, for AP CSI-RS / CSI reports according to the codebook described herein, QCL information for each AP CSI-RS resource is not provided in the CSI-AperiodicTriggerState, or is omitted (if provided), and the shared / identical QCL assumption is instead provided via MAC CE or DCI. Similarly, for SP CSI-RS / CSI reports according to the codebook described herein, QCL information for each SP CSI-RS resource is not provided in the CSI-Semi-PersistentTriggerState, or is omitted (if provided), and the shared / identical QCL assumption is instead provided via MAC CE or DCI.

[0455] In one example, the shared / identical QCL assumption is provided by indicating the TCI status in the DL-DCI. In one example, the TCI status can be provided along with a TCI field (version 15 or version 17 uTCI). In one example, a new DCI field can be provided to the TCI status. In one example, an unused DCI field or code point can be provided to the TCI status. In one example, such an indication is provided when the higher-level parameter tciPresentInDCI or commonTciPresentInDCI is enabled.

[0456] In one example, the shared / identical QCL assumption is provided by indicating a TCI state in the UL-DCI. In one example, the TCI state can be provided along with the CSI request field. In one example, a new DCI field can be provided to the TCI state. In one example, an unused DCI field or code point can be provided to the TCI state. In one example, such an indication is provided when the higher-level parameter tciPresentInDCI or commonTciPresentInDCI is enabled.

[0457] In one example, the shared / identical QCL assumption is provided by indicating the TCI status in the MAC CE.

[0458] In one example, the shared / identical QCL assumption is provided through the TCI state in the combination of MAC CE and DCI. For example, MAC CE can activate There are 1 TCI states, and when more than 1 TCI states are activated, one of the activated TCI states can be indicated by DCI.

[0459] In one embodiment, restrictions may be enabled within the CSI-AperiodicTriggerState, CSI-SemiPersistentTriggerState, or NZP-CSI-RS-Resource set for P CSI-RS resources and P / AP / SP-CSI reports according to the codebook described herein.

[0460] In one example, this limitation corresponds to... The same / shared QCL assumptions for NZP CSI-RS resources (e.g., in a CSI resource set).

[0461] In one example A pool of NZP CSI-RS resources (e.g., within a CSI resource set) can be partitioned into NZP CSI-RS resources. Each subset includes 1 subset. Each NZP CSI-RS resource has the same / shared QCL assumptions. One of the subsets can be activated / indicated via MAC CE and / or DCI. Alternatively, MAC CE can activate a subset, and when >1 subset is activated, one of the activated subsets can be indicated via DCI.

[0462] In one embodiment, for P CSI-RS resources and P / AP / SP-CSI reports according to the codebook described herein, the QCL information for each P CSI-RS resource is not provided via qcl-InfoPeriodicCSI-RS in IE NZP-CSI-RS-Resource, or is ignored (if provided), and shared / identical QCL is assumed to be provided instead via MAC CE or DCI.

[0463] In one example, the shared / identical QCL assumption is provided by indicating the TCI status in the DL-DCI. In one example, the TCI status can be provided along with a TCI field (version 15 or version 17uTCI). In one example, a new DCI field can be provided to the TCI status. In one example, the TCI status can be provided with an unused DCI field or code point. In one example, such an indication is provided when the higher-level parameter tciPresentInDCI or commonTciPresentInDCI is enabled.

[0464] In one example, the shared / identical QCL assumption is provided by indicating a TCI state in the UL-DCI. In one example, the TCI state can be provided along with the CSI request field. In one example, the TCI state can be provided for a new DCI field. In one example, the TCI state can be provided for an unused DCI field or code point. In one example, such an indication is provided when the higher-level parameter tciPresentInDCI or commonTciPresentInDCI is enabled.

[0465] In one example, the shared / identical QCL assumption is provided by indicating the TCI status in the MAC CE.

[0466] In one example, the shared / identical QCL assumption is provided through the TCI state in the combination of MAC CE and DCI. For example, MAC CE can activate There are 1 TCI states. When more than 1 TCI state is active, one of the active TCI states can be indicated by DCI.

[0467] Figure 13 An example method 1300 performed by a UE in a wireless communication system according to an embodiment of this disclosure is shown. Figure 13 Method 1300 can be derived from Figure 1 Any of the UE 111-116 executions, for example, Figure 3 UE 116, and the corresponding method can be provided by Figure 1 Any of the executions in BS 101-103, for example, Figure 2 BS 102. Method 1300 is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.

[0468] Method 1300 begins with UE reception configuration, which includes information about... NZP CSI-RS resources and shared use in At least one of the NZP CSI-RS resources Information about each QCL (1310). For example, in 1310, The QCL information indicates at least one source RS and a QCL type, and the QCL type indicates at least one channel attribute of at least one source RS. Then, the UE via... In NZP CSI-RS resources One, applies QCL information for channel measurement (1320). For example, in 1320, the UE determines the application of QCL information based on this configuration. In various embodiments, channel measurement is based on The assumption is that at least one channel attribute of an NZP CSI-RS resource is the same as at least one channel attribute of the indicated at least one source RS.

[0469] In various embodiments, the UE may also: receive configuration regarding CSI reports; based on cross-... NZP CSI-RS resource aggregation The codebook associated with each CSI-RS port is used to determine the CSI report and to send the CSI report.

[0470] In various embodiments, this configuration includes information about Information regarding the TD behavior of an NZP CSI-RS resource, whether it is periodic, SP, or AP, is included in this configuration. This configuration includes the ID of the NZP-CSI-RS-Resource-Set, and the set includes... The ID of each NZP CSI-RS resource and the ID of the QCL information. For example, when the TD behavior is periodic, each NZP CSI-RS resource in this set may or may not include individual QCL information, and when individual QCL information is included, the UE may ignore or overwrite the individual QCL information.

[0471] In various embodiments, the QCL type is one of the following: Type A, wherein at least one channel attribute includes Doppler shift, Doppler spread, average delay, and delay spread; Type B, wherein at least one channel attribute includes Doppler shift and Doppler spread; Type C, wherein at least one channel attribute includes Doppler shift and average delay; or Type D, wherein at least one channel attribute includes a spatial Rx parameter. In various embodiments, the QCL type is Type A or Type B when at least one source RS is an NZP CSI-RS resource with a higher-level parameter trs-info, and the QCL type is Type C when at least one source RS is a synchronization signal block (SSB).

[0472] In various embodiments, the configuration includes information about a second QCL information having a second QCL type different from the QCL type of the QCL information and a source RS that is the same as or different from the source of the QCL information.

[0473] In various embodiments, when At that time, QCL information is used for all One NZP CSI-RS resource, when At that time, QCL information is used for One NZP CSI-RS resource, and for the remaining One NZP CSI-RS resource, used for all The second QCL information for each NZP CSI-RS resource is provided, or used for Second QCL information is provided for each of the NZPCSI-RS resources.

[0474] Any of the above-described variations can be used independently or in combination with at least one other variation. The flowcharts above illustrate example methods that can be implemented according to the principles of this disclosure, and various changes can be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the individual steps in each figure can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, a step can be omitted or replaced by another step.

[0475] Although this disclosure has been described with reference to exemplary embodiments, various changes and modifications will be apparent to those skilled in the art. This disclosure is intended to include such changes and modifications that fall within the scope of the appended claims. No description in this application should be construed as implying that any particular element, step, or function is an essential element that must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A user equipment (UE), comprising: transceiver; and A processor, operatively coupled to the transceiver, is configured to: Receive configuration, the configuration including information about (i) One non-zero power (NZP) channel state information-reference signal (CSI-RS) resource and (ii) shared in At least one of the NZP CSI-RS resources The information of each quasi-co-addressable information (QCL information), among which, The QCL information indicates at least one source RS and a QCL type, and the QCL type indicates at least one channel attribute of the at least one source RS; and Based on the configuration, based on the The assumption that at least one channel attribute of an NZP CSI-RS resource is the same as at least one channel attribute of the indicated at least one source RS, via the aforementioned The NZP CSI-RS resources mentioned The QCL information is used for channel measurement.

2. The UE according to claim 1, wherein, The processor is also configured to: Configuration for receiving Channel State Information (CSI) reports; Send the CSI report; as well as Based on and across NZP CSI-RS resource aggregation The codebook associated with each CSI-RS port determines the CSI report.

3. The UE according to claim 1, wherein: The configuration includes information about the above. Information regarding the time-domain (TD) behavior of an NZP CSI-RS resource: whether it is periodic, semi-persistent (SP), or aperiodic (AP). The configuration includes an identifier (ID) for the set NZP-CSI-RS-Resource-Set, and the set includes the... The ID of the NZP CSI-RS resource and the ID of the QCL information. When the TD behavior is periodic, each NZP CSI-RS resource in the set either does not include individual QCL information or includes the individual QCL information. When the individual QCL information is included, the processor is configured to (i) ignore the individual QCL information or (ii) overwrite the individual QCL information.

4. The UE according to claim 1, wherein, The QCL type is one of the following: Type A, wherein at least one channel property is indicated, including Doppler frequency shift, Doppler spread, average delay, and delay spread. Type B, wherein at least one channel property indicated includes Doppler frequency shift and Doppler spread. Type C, wherein at least one channel property indicated includes Doppler frequency shift and average delay, or Type D, wherein at least one channel attribute indicated includes a spatial Rx parameter, and in: When the at least one source RS is an NZP CSI-RS resource with a higher-level parameter trs-info, the QCL type is type A or type B, and When the at least one source RS is a synchronization signal block (SSB), the QCL type is type C.

5. The UE according to claim 1, wherein, The configuration includes information about the second QCL information, which has the following characteristics: The second QCL type, which is different from the QCL type of the QCL information, and The source RS may be the same as or different from the source of the QCL information.

6. The UE according to claim 1, wherein: when At that time, the QCL information is used in all of the above. One NZP CSI-RS resource, when At that time, the QCL information is used for the... One NZP CSI-RS resource, and For the remaining One NZP CSI-RS resource, Used in all of the above The second QCL information for each NZP CSI-RS resource is provided, or For the Second QCL information is provided for each of the NZP CSI-RS resources.

7. A base station (BS), comprising: transceiver; and A processor, operatively coupled to the transceiver, is configured to: Send configuration, which includes information about (i) One non-zero power (NZP) channel state information-reference signal (CSI-RS) resource and (ii) shared in At least one of the NZP CSI-RS resources The information of each quasi-co-addressable information (QCL information), among which, , The QCL information indicates at least one source RS and QCL type. Wherein, the QCL type indicates at least one channel attribute of the at least one source RS; and Wherein, the configuration indication is based on the The assumption that at least one channel attribute of an NZP CSI-RS resource is the same as at least one channel attribute of the indicated at least one source RS, via the aforementioned The NZP CSI-RS resources mentioned The QCL information is used for channel measurement.

8. The BS according to claim 7, wherein, The transceiver is also configured to: Configuration for sending Channel State Information (CSI) reports; and Receive the CSI report, the CSI report being based on and across the NZP CSI-RS resource aggregation The codebook associated with each CSI-RS port.

9. The BS according to claim 7, wherein: The configuration includes information about the above. Information regarding the time-domain (TD) behavior of an NZP CSI-RS resource: whether it is periodic, semi-persistent (SP), or aperiodic (AP). The configuration includes an identifier (ID) for the set NZP-CSI-RS-Resource-Set, and the set includes the... The ID of the NZP CSI-RS resource and the ID of the QCL information. When the TD behavior is periodic, each NZP CSI-RS resource in the set either does not include individual QCL information or includes the individual QCL information. When the individual QCL information is included, the individual QCL information is ignored or overwritten.

10. The BS according to claim 7, wherein, The QCL type is one of the following: Type A, wherein at least one channel property is indicated, including Doppler frequency shift, Doppler spread, average delay, and delay spread. Type B, wherein at least one channel property indicated includes Doppler frequency shift and Doppler spread. Type C, wherein at least one channel property indicated includes Doppler frequency shift and average delay, or Type D, wherein at least one channel attribute indicated includes a spatial Rx parameter, and in: When the at least one source RS is an NZP CSI-RS resource with a higher-level parameter trs-info, the QCL type is type A or type B, and When the at least one source RS is a synchronization signal block (SSB), the QCL type is type C.

11. The BS according to claim 7, wherein, The configuration includes information about the second QCL information, which has the following characteristics: The second QCL type, which is different from the QCL type of the QCL information, and The source RS may be the same as or different from the source of the QCL information.

12. The BS according to claim 7, wherein: when At that time, the QCL information is used in all of the above. One NZP CSI-RS resource, when At that time, the QCL information is used for the... One NZP CSI-RS resource, and For the remaining One NZP CSI-RS resource, Used in all of the above The second QCL information for each NZP CSI-RS resource is provided, or For the Second QCL information is provided for each of the NZP CSI-RS resources.

13. A method performed by a user equipment, the method comprising: Receive configuration, the configuration including information about (i) One non-zero power (NZP) channel state information-reference signal (CSI-RS) resource and (ii) shared in At least one of the NZP CSI-RS resources The information of each quasi-co-addressable information (QCL information), among which, The QCL information indicates at least one source RS and a QCL type, and the QCL type indicates at least one channel attribute of the at least one source RS; and Based on the configuration, based on the The assumption that at least one channel attribute of an NZP CSI-RS resource is the same as at least one channel attribute of the indicated at least one source RS, via the aforementioned The NZP CSI-RS resources mentioned The QCL information is used for channel measurement.

14. The method of claim 13, further comprising: Configuration for receiving Channel State Information (CSI) reports; Send the CSI report; as well as Based on and across NZP CSI-RS resource aggregation The codebook associated with each CSI-RS port determines the CSI report.

15. A method performed by a base station, the method comprising: Send configuration, which includes information about (i) One non-zero power (NZP) channel state information-reference signal (CSI-RS) resource and (ii) shared in At least one of the NZP CSI-RS resources The information of each quasi-co-addressable information (QCL information), among which, , The QCL information indicates at least one source RS and QCL type. Wherein, the QCL type indicates at least one channel attribute of the at least one source RS; and Wherein, the configuration indication is based on the The assumption that at least one channel attribute of an NZP CSI-RS resource is the same as at least one channel attribute of the indicated at least one source RS, via the aforementioned The NZP CSI-RS resources mentioned The QCL information is used for channel measurement.

Images