Method and apparatus for transmitting and receiving radio signals in a wireless communication system

Abstract

A method and an apparatus for transmitting and receiving a radio signal in a wireless communication system are disclosed. The method according to an embodiment of the present disclosure may include receiving first configuration information including a list of TCI states from a base station, the list of TCI states providing a reference for determining a reference signal for a QCL for a downlink channel and / or an uplink transmit spatial filter for an uplink channel, receiving second configuration information related to a CORESET from the base station, the second configuration information configuring a plurality of CORESETs having different CORESET pool indexes, and receiving DCI from the base station.

Description

[Technical field]

[0001] The present disclosure relates to wireless communication systems, and more particularly, to methods and apparatus for transmitting and receiving wireless uplink or downlink channels / signals in wireless communication systems. [Background technology]

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, the scope of mobile communication systems has expanded beyond voice to data services, and currently, resource shortages are occurring due to the explosive increase in traffic, and users are demanding faster services, so there is a demand for more advanced mobile communication systems.

[0003] The requirements for the next generation mobile communication system are to accommodate large and explosive data traffic, dramatically increase the transmission rate per user, accommodate a significantly increased number of connected devices, and support very low end-to-end latency and high energy efficiency.To achieve this, various technologies such as dual connectivity, massive multiple input multiple output (MAMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking are being researched. Summary of the Invention [Problem to be solved by the invention]

[0004] A technical problem of the present disclosure is to provide a method and apparatus for transmitting and receiving uplink or downlink channels / signals.

[0005] Furthermore, a further technical object of the present disclosure is to provide a method and apparatus for indicating / updating a common or separate beam for downlink / uplink transmission (i.e., a reference signal for QCL relationship for downlink transmission, a reference for determining an uplink transmit spatial filter for uplink transmission) in a wireless communication system supporting multiple transmission reception points (TRPs).

[0006] The technical problems to be achieved by the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Means for solving the problem]

[0007] A method performed by a terminal in a wireless communication system according to an embodiment of the present disclosure may include a step of receiving first configuration information including a list of transmission configuration indication (TCI) states from a base station, the list of TCI states providing a reference for determining a reference signal for quasi co-location (QCL) for a downlink channel and / or an uplink transmission spatial filter for an uplink channel, a step of receiving second configuration information related to a control resource set (CORESET) from the base station, the second configuration information configuring a plurality of CORESETs having different CORESET pool indices, and a step of receiving downlink control information (DCI) from the base station. Based on the indication of one TCI state in the list of TCI states by the DCI, the indicated one TCI state may be applied to uplink transmission and downlink transmission associated with a CORESET pool index of the CORESET from which the DCI is transmitted.

[0008] A method performed by a base station in a wireless communication system according to a further aspect of the present disclosure may include a step of transmitting, to a terminal, first configuration information including a list of transmission configuration indication (TCI) states, the list of TCI states providing a reference for determining a reference signal for quasi co-location (QCL) for a downlink channel and / or an uplink transmission spatial filter for an uplink channel; a step of transmitting, to the terminal, second configuration information related to a control resource set (CORESET), the second configuration information configuring a plurality of CORESETs having different CORESET pool indices; and a step of transmitting downlink control information (DCI) to the terminal. Based on the indication of one TCI state in the list of TCI states by the DCI, the indicated one TCI state may be applied to uplink transmission and downlink transmission associated with a CORESET pool index of the CORESET from which the DCI is transmitted. Effect of the Invention

[0009] According to an embodiment of the present disclosure, ambiguity in indicating / updating a common or individual beam (i.e., a reference signal for QCL relationship for downlink transmission, a reference for determining an uplink transmit spatial filter for uplink transmission) can be prevented even in a wireless communication system supporting multiple transmission reception points (TRPs).

[0010] The effects obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Brief description of the drawings]

[0011] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide examples of the present disclosure and, together with the detailed description, explain the technical features of the present disclosure.

[0012] [Figure 1] 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied. [Diagram 2] 1 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied. [Diagram 3] 1 illustrates an example of a resource grid in a wireless communication system to which the present disclosure can be applied. [Figure 4] 1 illustrates an example of a physical resource block in a wireless communication system to which the present disclosure can be applied. [Diagram 5] 1 illustrates an example of a slot structure in a wireless communication system to which the present disclosure can be applied. [Figure 6] 1 illustrates examples of physical channels used in a wireless communication system to which the present disclosure can be applied, and a general signal transmission / reception method using the physical channels. [Figure 7] 1 illustrates a multiple TRP transmission method in a wireless communication system to which the present disclosure can be applied. [Figure 8] 4 illustrates a signaling procedure between a network and a terminal for a wireless signal transmission / reception method according to one embodiment of the present disclosure. [Figure 9] 4 illustrates an operation of a terminal with respect to a wireless signal transmission and reception method according to an embodiment of the present disclosure. [Figure 10] 4 illustrates an operation of a base station for a wireless signal transmission and reception method according to an embodiment of the present disclosure. [Figure 11] 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present disclosure, and is not intended to show the only embodiment in which the present disclosure can be implemented. The detailed description below includes specific details to provide a complete understanding of the present disclosure. However, it is understood by those skilled in the art that the present disclosure can be implemented without such specific details.

[0014] In some cases, in order to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or may be shown in the form of a block diagram focusing on the core functions of each structure and device.

[0015] In the present disclosure, when an element is "coupled," "coupled," or "connected" to another element, this can include a direct connection as well as an indirect connection where there is still another element between them. Also, in the present disclosure, the terms "including" or "having" specify the presence of stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0016] In this disclosure, terms such as "first" and "second" are used only to distinguish one component from another component, and are not used to limit the components, and do not limit the order or importance of the components unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0017] The terms used in this disclosure are for the purpose of describing particular embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular form is intended to include the plural form unless the context dictates otherwise. The term "and / or" used in this disclosure means that one of the associated listed items may be included, or any and all possible combinations of two or more of them. Also, in this disclosure, " / " between words has the same meaning as "and / or" unless otherwise specified.

[0018] The present disclosure is described with respect to a wireless communication network or wireless communication system, and operations performed in the wireless communication network may be performed in a process in which a device (e.g., a base station) that manages the wireless communication network controls the network and transmits or receives signals, or in a process in which a terminal coupled to the wireless network transmits or receives signals to or between the network.

[0019] In this disclosure, transmitting or receiving a channel includes transmitting or receiving information or signals on that channel. For example, transmitting a control channel means transmitting control information or signals on the control channel. Similarly, transmitting a data channel means transmitting data information or signals on the data channel.

[0020] In the following, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, a transmitter may be a part of the base station, and a receiver may be a part of the terminal. In the uplink, a transmitter may be a part of the terminal, and a receiver may be a part of the base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. A base station (BS) may be replaced with terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP), network (5G network), AI (Artificial Intelligence) system / module, RSU (road side unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, a terminal may be fixed or mobile, and may be replaced with terms such as User Equipment (UE), Mobile Station (MS), user terminal (UT), Mobile Subscriber Station (MSS), Subscriber Station (SS), Advanced Mobile Station (AMS), Wireless terminal (WT), Machine-Type Communication (MTC) device, Machine-to-Machine (M2M) device, Device-to-Device (D2D) device, vehicle, road side unit (RSU), robot, Artificial Intelligence (AI) module, drone (UAV: Unmanned Aerial Vehicle), Augmented Reality (AR) device, Virtual Reality (VR) device, etc.

[0021] The following technologies may be used for various wireless access systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. TDMA may be implemented by radio technologies such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (registered trademark) (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0022] For clarity of explanation, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​the present disclosure is not limited thereto. LTE refers to technology after 3GPP TS (Technical Specification) 36.xxx Release 8. In detail, LTE technology after 3GPP TS 36.xxx Release 10 is called LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 is called LTE-A pro. 3GPP NR refers to technology after TS 38.xxx Release 15. LTE / NR may be called a 3GPP system. "xxx" refers to a standard document detail number. LTE / NR may be called a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present disclosure, reference may be made to matters described in standard documents published before the present disclosure. For example, the following documents may be referenced.

[0023] In 3GPP LTE, reference can be made to TS 36.211 (physical channels and modulation), TS 36.212 (multiplexing and channel coding), TS 36.213 (physical layer procedures), TS 36.300 (general description), and TS 36.331 (radio resource control).

[0024] For 3GPP NR, reference can be made to TS 38.211 (Physical channels and modulation), TS 38.212 (Multiplexing and channel coding), TS 38.213 (Physical layer procedures for control), TS 38.214 (Physical layer procedures for data), TS 38.300 (General description of NR and NG-RAN (New Generation-Radio Access Network)), and TS 38.331 (Radio resource control protocol standard).

[0025] The following terminology abbreviations may be used in this disclosure:

[0026] - BM: Beam management

[0027] - CQI: channel quality indicator

[0028] - CRI: channel state information-reference signal resource indicator

[0029] - CSI: channel state information

[0030] - CSI-IM: channel state information-interference measurement

[0031] - CSI-RS: Channel state information-reference signal

[0032] - DMRS: Demodulation Reference Signal

[0033] - FDM: Frequency division multiplexing

[0034] - FFT: Fast Fourier transform

[0035] - IFDMA: Interleaved frequency division multiple access

[0036] - IFFT: inverse fast Fourier transform

[0037] - L1-RSRP: Layer 1 reference signal received power

[0038] - L1-RSRQ: Layer 1 reference signal received quality

[0039] - MAC: medium access control

[0040] - NZP: non-zero power

[0041] - OFDM: Orthogonal frequency division multiplexing

[0042] - PDCCH: physical downlink control channel

[0043] - PDSCH: physical downlink shared channel

[0044] - PMI: Precoding matrix indicator

[0045] - RE: resource element

[0046] - RI: Rank indicator

[0047] - RRC: Radio resource control

[0048] - RSSI: received signal strength indicator

[0049] - Rx: Reception

[0050] - QCL: quasi co-location

[0051] - SINR: signal to interference and noise ratio

[0052] - SSB (or SS / PBCH block): Synchronization signal block (including primary synchronization signal (PSS), secondary synchronization signal (SSS) and physical broadcast channel (PBCH))

[0053] - TDM: time division multiplexing

[0054] - TRP: transmission and reception point

[0055] - TRS: Tracking reference signal

[0056] - Tx: transmission

[0057] - UE: User Equipment

[0058] - ZP: Zero power

[0059] System in general

[0060] As more communication devices require larger communication capacity, the need for improved mobile broadband communication compared to existing radio access technologies (RATs) is emerging. Massive Machine Type Communications (MTC), which connects multiple devices and objects to provide various services anytime and anywhere, is also one of the major issues to be considered in next-generation communication. In addition, communication system design considering reliability and latency-sensitive services / terminals is also being discussed. Thus, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), URLLC (Ultra-Reliable and Low Latency Communication), etc. is being discussed, and for convenience in this disclosure, the technology is referred to as NR. NR is an expression representing an example of 5G RAT.

[0061] New RAT systems including NR use an OFDM transmission scheme or a similar transmission scheme. The new RAT system may follow OFDM parameters different from those of LTE. Or, the new RAT system may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Or, one cell may support multiple numerologies. That is, terminals operating with different numerologies may coexist in one cell.

[0062] A numerology corresponds to a subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

[0063] FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0064] Referring to FIG. 1, the NG-RAN is composed of gNBs that provide an NG-Radio Access (NG-RA) user plane (i.e., new access stratum (AS) sublayer / Packet Data Convergence Protocol (PDCP) / Radio Link Control (RLC) / MAC / PHY) and control plane (RRC) protocol termination for the UE. The gNBs are interconnected via an Xn interface. The gNBs are also connected to a New Generation Core (NGC) via an NG interface. More specifically, the gNBs are connected to an Access and Mobility Management Function (AMF) via an N2 interface and to a User Plane Function (UPF) via an N3 interface.

[0065] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0066] The NR system can support multiple numerologies, where the numerology may be defined by subcarrier spacing and cyclic prefix (CP) overhead. In this case, the multiple subcarrier spacing may be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). In addition, the numerology used may be selected independently of the frequency band, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies. In addition, various frame structures with multiple numerologies may be supported in the NR system.

[0067] The following describes OFDM numerologies and frame structures that can be considered in the NR system. A number of OFDM numerologies supported in the NR system may be defined as shown in Table 1 below.

[0068] [Table 1]

[0069] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services, such as 15kHz SCS to support wide areas in traditional cellular bands, 30kHz / 60kHz SCS to support dense-urban, lower latency, and wider carrier bandwidth, and 60kHz or higher SCS to support bandwidths larger than 24.25GHz to overcome phase noise.

[0070] The NR frequency band is defined as two types of frequency ranges (FR1, FR2). FR1 and FR2 may be configured as shown in Table 2 below. FR2 may also refer to millimeter wave (mmW).

[0071] [Table 2]

[0072] In relation to the frame structure in the NR system, the sizes of the various fields in the time domain are T c =1 / (Δf max N f ) where Δf max =480 10 3 Hz and Nf = 4096. Downlink and uplink transmissions are f =1 / (Δf max N f / 100)·T c The radio frame is organized into radio frames each having a duration of T sf =(Δf max N f / 1000)·T c In this case, there may be one set of frames for the uplink and one set of frames for the downlink. Also, the transmission from the terminal in the uplink frame number i starts T TA =(N TA +N TA,offset )T c For a subcarrier spacing configuration μ, a slot is allocated within a subframe. s μ ∈{0,...,N slot subframe,μ -1}, and n s,f μ ∈{0,...,N slot frame,μ -1}. A slot is numbered in increasing order. symb slot It consists of N consecutive OFDM symbols. symb slot is determined by the CP. s μ The start of OFDM symbol n s μ N symb slotNot all terminals can transmit and receive at the same time, which means that not all OFDM symbols in a downlink slot or uplink slot can be used.

[0073] Table 3 shows the number of OFDM symbols per slot (N symb slot ), the number of slots per radio frame (N slot frame,μ ), the number of slots per subframe (N slot subframe,μ ), and Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0074] [Table 3]

[0075] [Table 4]

[0076] Figure 2 is an example when μ=2 (SCS is 60 kHz), and referring to Table 3, one subframe can include 4 slots. One subframe={1, 2, 4} slots shown in Figure 2 is an example, and the number of slots that can be included in one subframe is defined as shown in Table 3 or Table 4. Also, a mini-slot can include 2, 4, or 7 symbols, or more or less symbols.

[0077] In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. may be considered. Hereinafter, the physical resources that can be considered in an NR system will be specifically described.

[0078] First, with respect to antenna ports, the antenna ports are defined such that the channel on which a symbol on an antenna port is carried can be inferred from the channel on which another symbol on the same antenna port is carried. If the large-scale properties of the channel on which a symbol on one antenna port is carried can be inferred from the channel on which a symbol on the other antenna port is carried, the two antenna ports are said to be in a quasi co-located (QC / QCL) relationship. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0079] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure is applicable.

[0080] Referring to FIG. 3, the resource grid is divided into N RB μ N sc RB Each subframe consists of 14·2 subcarriers. μ In the present embodiment, the OFDM symbol is used as an example, but is not limited to, an OFDM symbol. RBμ N sc RB One or more resource grids consisting of subcarriers and two μ N symb (μ) OFDM symbols, where N RB μ ≦N RB max,μ The above N RB max,μ represents the maximum transmission bandwidth, which may vary not only with numerology but also between uplink and downlink. In this case, one resource grid may be set for μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element, and is represented by an index pair: JPEG2025501600000006.jpg617, where k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, JPEG2025501600000007.jpg677 represents the position of a symbol within a subframe. When referring to a resource element in a slot, the index pair (k,l) is used, where l=0,...,N symb μ μ and the resource element for antenna port p. JPEG2025501600000008.jpg617 is a complex value JPEG2025501600000009.jpg811. If there is no risk of confusion or if a specific antenna port or numerology is not specified, the indexes p and μ may be dropped, so that the complex value is JPEG2025501600000010.jpg1030. Also, a resource block (RB) is N sc RB= 12 consecutive subcarriers.

[0081] Point A serves as a common reference point of the resource block grid and is obtained as follows:

[0082] - offsetToPointA for the primary cell (PCell) downlink indicates the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block used by the terminal for initial cell selection. It is expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2.

[0083] - absoluteFrequencyPointA indicates the frequency-location of point A expressed as in ARFCN (absolute radio-frequency channel number).

[0084] Common resource blocks are numbered from 0 upwards in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of common resource block 0 for a subcarrier spacing setting μ coincides with 'point A'. Common resource block number n CRB μ The relationship between k, l and the resource element (k, l) for the subcarrier spacing setting μ is given by the following Equation 1.

[0085]

number

[0086] In Equation 1, k is defined relative to point A such that k=0 corresponds to the subcarrier centered at point A. A physical resource block is a number ranging from 0 to N within a bandwidth part (BWP).BWP,i size,μ The numbering is from -1 to i, where i is the number of the BWP. PRB and common resource block n CRB The relationship between is given by Equation 2 below.

[0087]

number

[0088] N BWP,i start,μ is the common resource block where the BWP starts relative to common resource block 0.

[0089] Fig. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied, and Fig. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0090] 4 and 5, a slot includes a number of symbols in the time domain. For example, in the general CP, one slot includes seven symbols, while in the extended CP, one slot includes six symbols.

[0091] A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) is defined as multiple consecutive (physical) resource blocks in the frequency domain and may correspond to one numerology (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication is performed in the activated BWPs, and only one BWP may be activated for one terminal. Each element in the resource grid is called a resource element (RE), and one complex symbol may be mapped to it.

[0092] The NR system may support up to 400 MHz per component carrier (CC). If a terminal operating in such a wideband CC always operates with the radio frequency (RF) chip for the entire CC turned on, the terminal battery consumption may increase. Alternatively, considering various use cases (e.g., eMBB, URLLC, Mmtc, V2X, etc.) operating in one wideband CC, different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band in the CC. Alternatively, the capability for maximum bandwidth may differ for each terminal. In consideration of this, the base station may instruct the terminal to operate only in a part of the bandwidth rather than the entire bandwidth of the wideband CC, and the part of the bandwidth is defined as a bandwidth part (BWP) for convenience. The BWP may be composed of continuous RBs on the frequency axis and may correspond to one numerology (e.g., subcarrier spacing, CP length, slot / minislot interval).

[0093] Meanwhile, the base station can set multiple BWPs even within one CC set in the terminal. For example, a BWP occupying a relatively small frequency region can be set in the PDCCH monitoring slot, and the PDSCH indicated by the PDCCH can be scheduled on a larger BWP. Alternatively, when UEs are concentrated in a specific BWP, other BWPs can be set in some terminals for load balancing. Alternatively, in consideration of frequency domain inter-cell interference cancellation between adjacent cells, some spectrums of the entire bandwidth can be excluded and both BWPs can be set in the same slot. That is, the base station can set at least one DL / UL BWP in the terminal associated with the wideband CC. The base station can activate at least one DL / UL BWP among the DL / UL BWPs set at a specific time (by L1 signaling, MAC CE (Control Element), RRC signaling, etc.). Also, the base station may instruct switching to another configured DL / UL BWP (by L1 signaling, MAC CE, RRC signaling, etc.). Or, the base station may switch to a predetermined DL / UL BWP when a timer value expires on a timer basis. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP. However, in a situation where the UE is performing an initial access process or before an RRC connection is set up, the UE may not be able to receive the configuration for the DL / UL BWP. In such a situation, the DL / UL BWP assumed by the UE is defined as an initially active DL / UL BWP.

[0094] FIG. 6 illustrates examples of physical channels used in a wireless communication system to which the present disclosure can be applied, and a general signal transmission / reception method using the physical channels.

[0095] In a wireless communication system, a terminal receives information from a base station through a downlink, and transmits information to the base station through an uplink. Information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / purpose of the information they transmit and receive.

[0096] When the terminal is powered on or newly enters a cell, the terminal performs an initial cell search such as synchronizing with the base station (S601). To this end, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell identifier (ID). After that, the terminal receives a physical broadcast channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, the terminal can receive a downlink reference signal (DL RS) during the initial cell search stage to check the downlink channel state.

[0097] After completing the initial cell search, the terminal receives a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on the information carried on the PDCCH, and can obtain more specific system information (S602).

[0098] Meanwhile, when the terminal first connects to the base station or has no radio resources for signal transmission, the terminal can perform a random access procedure (RACH: Random Access Procedure) to the base station (steps S603 to S606). To this end, the terminal can transmit a specific sequence as a preamble on a physical random access channel (PRACH: Physical Random Access Channel) (S603 and S605) and receive a response message to the preamble on a PDCCH and a corresponding PDSCH (S604 and S606). In the case of a contention-based RACH, the terminal can also perform a contention resolution procedure.

[0099] After performing the above-mentioned procedures, the terminal can then perform PDCCH / PDSCH reception (S607) and Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) transmission (S608) as a general uplink / downlink signal transmission procedure. In particular, the terminal receives Downlink Control Information (DCI) through the PDCCH. Here, the DCI includes control information such as resource allocation information for the terminal, and has different formats depending on its purpose.

[0100] Meanwhile, control information that a terminal transmits to a base station in an uplink or that the terminal receives from a base station includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In a 3GPP LTE system, a terminal can transmit the above-mentioned control information such as CQI / PMI / RI in a PUSCH and / or a PUCCH.

[0101] Table 5 shows an example of a DCI format in an NR system.

[0102] [Table 5]

[0103] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to PUSCH scheduling (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transmission block (transport block, TB) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), HARQ (Hybrid- Automatic Repeat and request) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), multiple antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), and power control information (e.g., PUSCH power control, etc.), and the control information included in each of the DCI formats may be predefined.

[0104] DCI format 0_0 is used for scheduling PUSCH in one cell. Information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled by C-RNTI (Cell RNTI: Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and transmitted.

[0105] DCI format 0_1 ​​is used to indicate to a terminal the scheduling of one or more PUSCHs in one cell or downlink feedback information of a configured grant (CG). Information included in DCI format 0_1 ​​is CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI and transmitted.

[0106] DCI format 0_2 is used for scheduling the PUSCH in one cell. Information included in DCI format 0_2 is CRC scrambled by the C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI and transmitted.

[0107] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to PDSCH scheduling (e.g., frequency resource allocation, time resource allocation, VRB (virtual resource block)-PRB (physical resource block) mapping, etc.), transmission block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multiple antenna related information (e.g., antenna port, TCI (transmission configuration indicator), SRS (sounding reference signal) request, etc.), PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each of the DCI formats may be pre-defined.

[0108] DCI format 1_0 is used for scheduling the PDSCH in one DL cell. Information included in DCI format 1_0 is CRC scrambled by the C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.

[0109] DCI format 1_1 is used for scheduling the PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled by the C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.

[0110] DCI format 1_2 is used for scheduling the PDSCH in one cell. Information included in DCI format 1_2 is CRC scrambled by the C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.

[0111] Quasi-Co Location (QCL)

[0112] Antenna ports are defined such that the channel on which symbols on an antenna port are carried can be inferred from the channel on which other symbols on the same antenna port are carried. If the properties of the channel on which symbols on one antenna port are carried can be inferred from the channel on which symbols on the other antenna port are carried, then two antenna ports are said to be in a quasi co-located (QC / QCL) relationship.

[0113] Here, the channel characteristics include one or more of delay spread, Doppler spread, frequency / Doppler shift, average received power, received timing / average delay, and spatial Rx parameter, where the spatial Rx parameter refers to a spatial (reception) channel characteristic parameter such as an angle of arrival.

[0114] The terminal may be configured with a list of up to M TCI-State configurations in the higher layer parameter PDSCH-Config to decode a PDSCH with a detected PDCCH having DCI intended for the terminal and a given serving cell, where M depends on the UE capability.

[0115] Each TCI-State includes parameters for setting up a quasi co-location relationship between one or two DL reference signals and the DM-RS ports of the PDSCH.

[0116] The quasi-co-location relationship is set by the higher layer parameters qcl-Type1 for the first DL RS and qcl-Type2 (if set) for the second DL RS. For two DL RSs, the QCL types are not the same, regardless of whether the references are the same DL RSs or different DL RSs.

[0117] The quasi-co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type of QCL-Info and can take one of the following values:

[0118] - 'QCL-TypeA': {Doppler shift, Doppler spread, mean delay, delay spread}

[0119] - 'QCL-TypeB': {Doppler shift, Doppler spread}

[0120] - 'QCL-TypeC': {Doppler shift, average delay}

[0121] - 'QCL-TypeD': {spatial reception parameters}

[0122] For example, when a target antenna port is a specific NZP CSI-RS, the NZP CSI-RS antenna port may be instructed / configured to be QCLed with a specific TRS in terms of QCL-Type A and with a specific SSB in terms of QCL-Type D. A terminal receiving such instruction / configuration can receive the NZP CSI-RS using Doppler and delay values ​​measured from the QCL-TypeA TRS and apply the receiving beam used for QCL-TypeD SSB reception to the NZP CSI-RS reception.

[0123] The UE can receive an activation command via MAC CE signaling, which is used to map up to eight TCI states to codepoints in the DCI field 'Transmission Configuration Indication'.

[0124] Multi-TRP related operations

[0125] The Coordinated Multi Point (CoMP) technique is a method in which multiple base stations exchange (e.g., using the X2 interface) or utilize channel information (e.g., RI / CQI / PMI / LI (layer indicator)) fed back from terminals to transmit coordinated to terminals, effectively controlling interference. Depending on the method used, CoMP can be classified into joint transmission (JT), coordinated scheduling (CS), coordinated beamforming (CB), dynamic point selection (DPS), dynamic point blocking (DPB), etc.

[0126] The M-TRP transmission method, in which M TRPs transmit data to one terminal, can be broadly divided into i) eMBB M-TRP transmission, which is a method for increasing the transmission rate, and ii) URLLC M-TRP transmission, which is a method for increasing the reception success rate and reducing latency.

[0127] In addition, in terms of DCI transmission, the M-TRP transmission method can be divided into i) M-DCI (multiple DCI)-based M-TRP transmission in which each TRP transmits different DCIs, and ii) S-DCI (single DCI)-based M-TRP transmission in which one TRP transmits DCI. For example, in the case of S-DCI-based M-TRP transmission, all scheduling information for data transmitted by the M TRP needs to be transmitted to the terminal in one DCI, and it may be used in an ideal backhaul (ideal BH) environment in which dynamic coordination between both TRPs is possible.

[0128] For TDM-based URLLC M-TRP transmission, schemes 3 and 4 are currently under standardization discussion. Specifically, scheme 4 refers to a scheme in which one TRP transmits a transmission block (TB) in one slot, and has the effect of increasing the probability of data reception using the same TB received from multiple TRPs in multiple slots. In contrast, scheme 3 refers to a scheme in which one TRP transmits a TB in several consecutive OFDM symbols (i.e., symbol groups), and multiple TRPs in one slot may be configured to transmit the same TB in different symbol groups.

[0129] In addition, the UE can recognize PUSCH (or PUCCH) scheduled by DCI received in different control resource sets (CORESETs) (or CORESETs belonging to different CORESET groups) as PUSCH (or PUCCH) transmitted in different TRPs or as PDSCH (or PDCCH) in different TRPs. In addition, the method for UL transmission (e.g., PUSCH / PUCCH) transmitted in different TRPs described later can be equally applied to UL transmission (e.g., PUSCH / PUCCH) transmitted in different panels belonging to the same TRP.

[0130] Also, MTRP-URLLC may mean that the M-TRP transmits the same TB (Transport Block) using different layers / times / frequencies. A UE configured with the MTRP-URLLC transmission method may assume that various TCI states are indicated by DCI, and data received using QCL RSs in each TCI state are the same TB. Meanwhile, MTRP-eMBB may mean that the M-TRP transmits different TBs using different layers / times / frequencies. A UE configured with the MTRP-eMBB transmission method may assume that various TCI states are indicated by DCI, and data received using QCL RSs in each TCI state are different TBs. In this regard, the UE may determine / decide whether the M-TRP transmission is a URLLC transmission or an eMBB transmission by separately distinguishing and using an RNTI configured for MTRP-URLLC and an RNTI configured for MTRP-eMBB. In other words, if CRC masking of DCI received by the UE is performed using an RNTI configured for MTRP-URLLC use, it may correspond to URLLC transmission, and if CRC masking of DCI is performed using an RNTI configured for MTRP-eMBB use, it may correspond to eMBB transmission.

[0131] Hereinafter, the CORESET group identifier (group ID) described / mentioned in this disclosure may mean an index / identification information (e.g., ID) for distinguishing a CORESET for each TRP / panel. And, a CORESET group may be a group / union of CORESETs distinguished by an index / identification information (e.g., ID) for distinguishing a CORESET for each TRP / panel / the CORESET group ID. As an example, the CORESET group ID may be specific index information defined in a CORSET configuration. In this case, a CORESET group may be set / indicated / defined by an index defined in a CORESET configuration for each CORESET. And / or, the CORESET group ID may mean an index / identification information / indicator for distinguishing / identifying between CORESETs set / associated with each TRP / panel. Hereinafter, the CORESET group ID described / mentioned in the present disclosure may be expressed as a specific index / specific identification information / specific indicator for distinguishing / identifying between CORESETs set / associated with each TRP / panel. The CORESET group ID, i.e., a specific index / specific identification information / specific indicator for distinguishing / identifying between CORESETs set / associated with each TRP / panel, may be set / instructed to the terminal by higher layer signaling (e.g., RRC signaling) / Layer 2 signaling (L2 signaling, e.g., MAC-CE) / Layer 1 signaling (L1 signaling, e.g., DCI). As an example, it may be set / instructed to perform PDCCH detection for each TRP / panel (i.e., for each TRP / panel belonging to the same CORESET group) in the CORESET group unit.And / or, uplink control information (e.g., CSI, HARQ-A / N (ACK / NACK), SR (scheduling request)) and / or uplink physical channel resources (e.g., PUCCH / PRACH / SRS resources) may be configured / instructed to be managed / controlled separately for each TRP / panel (i.e., for each TRP / panel belonging to the same CORESET group) on a per-CORESET group basis. And / or, HARQ A / N (process / retransmission) for PDSCH / PUSCH, etc. scheduled for each TRP / panel (i.e., for each TRP / panel belonging to the same CORESET group) may be managed.

[0132] For example, a ControlResourceSet information element (IE), which is an upper layer parameter, is used to configure a time / frequency control resource set (CORESET). As an example, the control resource set (CORESET) may be related to detection and reception of downlink control information. The ControlResourceSet IE may include a CORESET related ID (e.g., controlResourceSetID), a CORESET pool index (e.g., CORESETPoolIndex) for the CORESET, a time / frequency resource configuration of the CORESET, TCI information related to the CORESET, etc. As an example, a CORESET pool index (e.g., CORESETPoolIndex) may be set to 0 or 1. In the above description, a CORESET group may correspond to a CORESET pool, and a CORESET group ID may correspond to a CORESET pool index (e.g., CORESETPoolIndex).

[0133] NCJT (Non-coherent joint transmission) is a method in which multiple TPs (Transmission Points) transmit data to one terminal using the same time-frequency resources, and transmit data using different layers (i.e., different DMRS ports) between the TPs using different Demodulation Multiplexing Reference Signal (DMRS) ports.

[0134] The TP transmits data scheduling information to the terminal receiving the NCJT by DCI. In this case, a method in which each TP participating in the NCJT transmits scheduling information for its own transmission data by DCI is called 'multi DCI based NCJT'. Since N TPs participating in NCJT transmission transmit DL grant DCI and PDSCH to the UE, the UE receives N DCIs and N PDSCHs from the N TPs. In contrast, a method in which one representative TP transmits scheduling information for its own transmission data and data transmitted by other TPs (i.e., TPs participating in the NCJT) by one DCI is called 'single DCI based NCJT'. In this case, N TPs transmit one PDSCH, but each TP transmits only some layers of multiple layers that make up one PDSCH. For example, when 4-layer data is transmitted, TP1 can transmit 2 layers and TP2 can transmit the remaining 2 layers to the UE.

[0135] Below, we will explain the partially overlapped NCJP.

[0136] In addition, NCJT can be classified into fully overlapped NCJT, in which the time-frequency resources transmitted by each TP completely overlap, and partially overlapped NCJT, in which only some of the time-frequency resources overlap. In other words, in the case of partially overlapped NCJT, both TP1 and TP2 data are transmitted in some time-frequency resources, and only one of the TP data, either TP1 or TP2, is transmitted in the remaining time-frequency resources.

[0137] Below, we will explain the method for improving reliability in multiple (Multi-TRP) systems.

[0138] The following two methods can be considered as transmission and reception methods for improving reliability using transmission with multiple TRPs.

[0139] FIG. 7 illustrates a multiple TRP transmission method in a wireless communication system to which the present disclosure can be applied.

[0140] Referring to FIG. 7(a), a case is shown in which layer groups transmitting the same codeword (CW) / transport block (TB) correspond to different TRPs. In this case, a layer group can mean a predetermined layer set consisting of one or more layers. In this case, the amount of transmission resources increases due to the large number of layers, which has the advantage that robust channel coding with a low code rate can be used for the TB, and since the channels are different from the multiple TRPs, the reliability of the received signal can be improved based on diversity gain.

[0141] Referring to FIG. 7(b), an example is shown in which different CWs are transmitted in layer groups corresponding to different TRPs. In this case, it can be assumed that the TBs corresponding to CW #1 and CW #2 in the figure are the same. That is, CW #1 and CW #2 mean that the same TB is converted into different CWs by channel coding or the like according to different TRPs. Therefore, it can be considered as an example of repeated transmission of the same TB. FIG. 7(b) may have a disadvantage that the code rate corresponding to the TB is higher than that of FIG. 7(a). However, it has an advantage that the code rate can be adjusted by instructing different RV (redundancy version) values ​​for encoded bits generated from the same TB according to the channel environment, or the modulation order of each CW can be adjusted.

[0142] According to the schemes illustrated in Figures 7(a) and 7(b), the same TB is repeatedly transmitted in different layer groups, and each layer group is transmitted by a different TRP / panel, thereby increasing the probability of data reception by the terminal. This is called an SDM (Spatial Division Multiplexing)-based M-TRP URLLC transmission scheme. Layers belonging to different layer groups are transmitted by DMRS ports belonging to different DMRS CDM groups.

[0143] In addition, although the above-mentioned contents related to multiple TRPs have been described based on a spatial division multiplexing (SDM) scheme using different layers, this may of course be extended and applied to a frequency division multiplexing (FDM) scheme based on different frequency domain resources (e.g., RB / PRB (set), etc.) and / or a time division multiplexing (TDM) scheme based on different time domain resources (e.g., slots, symbols, sub-symbols, etc.).

[0144] Beam management method

[0145] This paper describes the receive / transmit beam setting / update / indication between a Rel-15 / 16 base station and a terminal.

[0146] First, a method for setting / instructing a receiving beam to a terminal by a base station and a method for setting / instructing a transmitting beam to a terminal will be described.

[0147] As described above, using the Quasi Co-Located (QCL) concept introduced in Rel-15 NR, the base station uses the TCI state to set / indicate the reception beam (i.e., spatial Rx parameter) to be used when the terminal receives the PDCCH and PDSCH (i.e., when receiving the DMRS of the PDCCH and PDSCH). Using the TCI state, the base station can set / update a DL reference signal (e.g., SS / PBCH block resource indicator (SSB-RI), CRI (periodic (P) / semi persistent (SP) / aperiodic (AP))) as the reference RS or source RS of the QCL Type-D component. As a result, the terminal can be instructed to use the reception beam for receiving the DL RS set as above as a reference when receiving the PDCCH or PDSCH.

[0148] In addition, in Rel-15 NR, a base station can use spatial relation information (spatialRelationInfo) to set / indicate a transmission beam to be used when a terminal transmits an UL channel (e.g., PUSCH, PUCCH, or SRS). The base station can set / update a DL reference signal (i.e., SSB-RI, CRI (P / SP / AP)) or SRS (i.e., SRS resource) as a reference RS for a target UL channel and / or target RS by RRC configuration and / or activation of a MAC control element (CE). As a result, a UL transmission beam (i.e., spatial Tx parameter) to be used when a terminal transmits a PUCCH and SRS can be set / indicated. In addition, when the base station schedules a PUSCH to a terminal, the transmission beam used for SRS transmission (for codebook (CB) or non-codebook (NCB) use) set / updated / instructed by the base station is indicated as the transmission beam for PUSCH in the SRS resource indicator (SRI) field of the UL grant DCI, and can thereby be used as the PUSCH transmission beam of the terminal.

[0149] Next, a method for updating a receiving beam of a terminal by a base station and updating a transmitting beam of a terminal will be described.

[0150] In Rel-15 NR, TCI state configuration is used to set / indicate a receive beam for a target DL RS / channel. If the target DL RS / channel is a CSI-RS, the receive beam of the terminal may be set by configuring a QCL type-D RS (by setting a TCI state identifier in a TCI state pool) at the RRC / MAC CE level (signaling). Also, if the target DL RS / channel is a PDCCH, the terminal receive beam may be set by instructing a specific TCI state ID by the MAC CE after setting up to 64 TCI state IDs in a specific CORESET, and the receive beam of the CORESET may be updated by the same MAC CE message. In addition, the PDSCH receiving beam can be indicated by a TCI indication during DL scheduling by linking / associating up to eight TCI state IDs (within a maximum TCI state pool of 128 TCI states) to the TCI state field of the DL DCI using MAC CE, and the PDSCH receiving beam can be updated by updating the TCI state IDs linked / associated to the TCI state field using the same MAC CE message.

[0151] In Rel-16 NR, in order to reduce the overhead of DL receive beam configuration / indication, the base station-UE operation has been enhanced to enable simultaneous / simultaneous TCI state ID activation on multiple component carriers (CCs) (or BWPs) for PDCCH and PDSCH via MAC CE messages.

[0152] In Rel-15 NR, for PUCCH transmission beam setting / instruction, a transmission beam can be set by concatenating / linking PUCCH-SpatialRelationInfoId for each PUCCH resource by a MAC CE message. Also, a MAC level update for PUCCH-SpatialRelationInfo is possible by the same MAC CE message. Also, for SRS, SRS-SpatialRelationInfo of SRS resources in a semi-persistent SRS resource set can be updated by a MAC CE message that activates SRS transmission for SP (semi persistent)-SRS.

[0153] In Rel-16 NR, in order to reduce the latency of UL transmission beam setting / instruction, the operation between the base station and the terminal has been improved so that the SRS-SpatialRelationInfo for the SRS resources in the aperiodic SRS resource set (aperiodic SRS resource set) can be updated by the MAC CE message for the AP (aperiodic)-SRS. In addition, the operation between the base station and the terminal has been improved so that the simultaneous spatial relation reference RS in multiple CCs (BWP) can be updated for the SP-SRS and AP-SRS by the MAC CE message, as with the DL reception beam. In addition, the concept of PUCCH resource groups (by BWP) has been introduced, and the operation between the base station and the terminal has been improved so that the simultaneous spatial relation update can be performed for the PUSCH resources in the PUCCH resource group.

[0154] As described above, in NR Rel-15 / Rel-16, higher layer signaling such as RRC and MAC CE is mainly used for beam direction / update operations for reception / transmission between a base station and a terminal, and DCI-based beam direction operations are supported for some channels / RS (e.g., PDSCH, PUSCH, etc.).

[0155] In Rel-17, dynamic beam update operation using joint DL / UL TCI state and separate DL / UL TCI state is planned to be introduced. A common beam update operation for terminals, in which a base station uses DCI to instruct / update multiple specific channel / RS combinations of a terminal with one common beam, was standardized. For the target channel / RS of the common beam update, a dedicated CORESET for the UE and a UE-dedicated reception on PDSCH can be configured in DL. In addition, in UL, all or a subset of dynamic grant (DG) / configured grant (CG)-PUSCH and dedicated PUCCH can be configured as the target channel / RS of the common beam update. In addition, AP CSI-RS and SRS for tracking / beam management (BM) can be configured as the target channel / RS. The discussion results of the standardization meeting are described below.

[0156] [agreement]

[0157] On the beam direction signaling medium to support joint or separate DL / UL beam direction in the Rel-17 unified TCI framework:

[0158] - Support L1 (layer 1) based beam direction using at least UE specific (unicast) DCI to indicate joint or separate DL / UL beam direction from active TCI state

[0159] · The existing DCI formats 1_1 and 1_2 are reused for beam direction.

[0160] Supports a mechanism for UE to confirm successful decoding of beam direction

[0161] The ACK / NAK of the PDSCH scheduled by the DCI carrying the beam instruction may also be used as an ACK for the DCI.

[0162] - Supports activation of one or more TCI states using MAC CE similar to Rel-15 / 16:

[0163] · An activated TCI state applies for at least one activated TCI state.

[0164] · The content of MAC CE will be determined based on the outcome of issue 1.

[0165] Note: There is no impact on single TRP or multi-TRP support.

[0166] [agreement]

[0167] To accommodate the case of separate beam pointing for UL and DL in the Rel-17 unified TCI framework:

[0168] - Utilizes two separate TCI states (one for DL ​​and one for UL)

[0169] Note: In the case of FR1, if UL TCI is supported for FR1, the UE does not expect the UL TCI to provide a reference for determining a common UL TX spatial filter.

[0170] - For individual DL TCI:

[0171] The source reference signal of the M TCI provides QCL information for UE-specific reception at least via the PDSCH and UE-specific reception via all or a subset of the CORESET of CCs.

[0172] - For individual UL TCI:

[0173] The N TCI source reference signal provides a reference for determining a common TX spatial filter for at least dynamic-grant / configured-grant based PUSCH, all or a subset of dedicated PUCCH resources within a CC.

[0174] Optionally, this UL TX spatial filter can also be applied to all SRS resources in a resource set configured for antenna switching / codebook-based / non-codebook-based UL transmission.

[0175] Note: this does not exclude UE types that support only one beam tracking loop.

[0176] [agreement]

[0177] In the Rel.17 unified TCI framework, the following terms are defined based on the agreement of RAN1#102-e and 103-e.

[0178] - If M=1:

[0179] · DL TCI: The source reference signal of DL TCI (similar to Rel.15, 2, when qcl_Type2 is set in addition to qcl_Type1) provides QCL information for UE-specific reception at least in PDSCH and all CORESETs in CC.

[0180] - If N=1:

[0181] ·UL TCI: The source reference signal of the UL TCI provides a reference for determining the UL TX spatial filter for at least dynamic grant / configured grant based PUSCH and all dedicated PUCCH resources of the CC.

[0182] - If M=N=1:

[0183] · Joint DL / UL TCI: TCI refers to at least a common source reference RS that is used to determine both the DL QCL information and the UL TX spatial filter.

[0184] · Separate DL / UL TCI: The DL TCI and the UL TCI are separate (and therefore distinct).

[0185] - If M>1:

[0186] DL TCI: Each of the M source reference signals in the M DL TCIs (or 2M, if qcl_Type2 is further set to qcl_Type1) provides QCL information for at least one of the M beam pair links for UE-dedicated reception in the PDSCH and / or on a subset of the CORESET in the CC.

[0187] - If N>1:

[0188] UL TCI: Each of the N source reference signals of the N UL TCIs provides a reference for determining the UL TX spatial filter for at least one of the N beam pair links associated with a subset of the dedicated PUCCH resources in the dynamic grant / configured grant based PUSCH and / or CC.

[0189] - If M>1 and N>1:

[0190] Joint DL / UL TCI: TCI refers to the minimum common source reference RS used to determine the DL QCL information and the UL TX spatial filter, where M=N.

[0191] · Separate DL / UL TCI: M DL TCI and N UL TCI are distinct (and therefore separate).

[0192] Note: Other TCI types / terms such as "common TCI" are not used.

[0193] [agreement]

[0194] In the Rel.17 integrated TCI framework, the source / target QCL relationship currently supported in TS38.214V16.4.0 is supported for QCL Type D.

[0195] For reference, this means that the following source RS types for DL ​​QCL (Type D, in the case of DL RX spatial filter) information for DL ​​UE-specific reception in the entire / subset of PDSCH and CORESET are supported.

[0196] CSI-RS for beam management

[0197] CSI-RS for tracking

[0198] [agreement]

[0199] The following source RS types for the UL TX spatial filter are supported in the Rel.17 unified TCI framework:

[0200] CSI-RS for tracking

[0201] Note: SRS for beam management, SSB and CSI-RS for beam management were agreed upon in RAN1#102-e.

[0202] [agreement]

[0203] In the Rel.17 integrated TCI framework:

[0204] In joint and individual DL / UL TCI, DL large scale QCL properties are inferred from one RS (qcl-Type1) or two RSs (qcl-Type1 and qcl-Type2) similar to Rel.15 / 16.

[0205] In the joint DL / UL TCI, the UL spatial filter is derived from the RS of the DL QCL Type D.

[0206] [agreement]

[0207] For beam pointing with Rel-17 integrated TCI, DCI format without DL assignment is supported:

[0208] - Use a similar ACK / NACK mechanism as for SPS PDSCH release using all Type-1 and Type-2 HARQ-ACK codebooks:

[0209] Upon successful reception of the beam indication DCI, the UE reports an ACK.

[0210] Here, when beam instruction DCI reception fails, a NACK may be reported.

[0211] In addition, in the case of a Type-1 HARQ-ACK codebook, the position of the ACK information in the HARQ-ACK codebook is determined based on the virtual PDSCH indicated by the TDRA (time domain resource allocation) field of the beam indication DCI, based on the time domain allocation list configured for the PDSCH.

[0212] Also, in the case of the Type-2 HARQ-ACK codebook, the location of the ACK information in the HARQ-ACK codebook is determined according to the same rules as for SPS release.

[0213] The ACK is reported in PUCCH k slots after the end of PDCCH reception, where k is indicated by the PDSCH-to-HARQ_feedback timing indicator field in the DCI format or is provided by dl-DataToUL-ACK or dl-DataToUL-ACK-ForDCI-Format1-2-r16 if the PDSCH-to-HARQ_feedback timing indicator field is not present in the DCI.

[0214] - When used for beam direction:

[0215] The CS-RNTI is used to scramble the cyclic redundancy check (CRC) for the DCI.

[0216] The values ​​of the following DCI fields are set as follows:

[0217] RV = all "1", MCS = all "1", NDI = 0, FDRA Type 0 is all "0", FDRA Type 1 is all "1", dynamicSwitch is all set to "0" (same as Table 10.2-4 of TS38.213)

[0218] - Existing TCI field (always present) is used to signal: 1) joint DL / UL TCI status, 2) DL only TCI status (in case of separate DL / UL TCI), 3) UL only TCI status (in case of separate DL / UL TCI).

[0219] - Also uses the following DCI fields as used in Rel-16:

[0220] DCI format identifier, carrier indicator, bandwidth fraction indicator, TDRA, downlink allocation index (if configured), transit power control (TPC) command for scheduled PUCCH, PUCCH resource indicator, PDSCH-to-HARQ_feedback timing indicator (if present).

[0221] - The remaining unused DCI fields and codepoints are reserved for Rel-17.

[0222] - Supports UE to report whether it supports TCI update via DCI format 1_1 / 1_2

[0223] A UE supporting TCI update via DCI format 1_1 / 1_2 shall support TCI update using DCI 1_1 / 1_2 with DL allocation, and the above support for TCI update via DCI format 1_1 / 1_2 without DL allocation is UE optional.

[0224] [agreement]

[0225] For M=N=1, in Rel-17 unified TCI, for separate DL / UL TCI, one instantiation of beam indication using DCI format 1_1 / 1_2 (with and without DL allocation) can be used as follows:

[0226] One TCI field codepoint indicates a pair of DL TCI state and UL TCI state. If the DCI indicates such a TCI field codepoint, the UE applies the corresponding DL TCI state and UL TCI state.

[0227] One TCI field code point indicates only DL TCI state. If the DCI indicates such a TCI field code point, the UE applies the corresponding DL TCI state and maintains the current UL TCI state.

[0228] One TCI field code point indicates only a UL TCI state. If the DCI indicates such a TCI field code point, the UE shall apply this UL TCI state and maintain the current DL TCI state.

[0229] [agreement]

[0230] In the Rel.17 integrated TCI framework,

[0231] - Any DL RS that is a valid target DL RS for a Rel-15 / 16 TCI state based on the Rel-15 / 16 QCL rules may be configured as a target DL RS for a Rel-17 DL TCI (and thus the Rel-17 DL TCI state pool).

[0232] NOTE: This does not mean that all such DL RSs necessarily share the same TCI state.

[0233] DL RS includes CSI-RS and DMRS for PDSCH or PDCCH.

[0234] - Note: This does not mean that the DL and UL TCI status pools are separate or shared for separate DL / UL TCIs.

[0235] [agreement]

[0236] In the Rel.17 unified TCI framework, for a UE configured with joint TCI and separate DL / UL TCI, the configuration of joint TCI and separate DL / UL TCI is based on RRC signaling.

[0237] [agreement]

[0238] Rel.17 beam direction for L1 / L2 centric inter-cell beam management mobility supports:

[0239] - Rel-17 MAC-CE based and / or DCI based beam direction (using DCI format 1_1 / 1_2 with or without DL assignment including at least associated MAC-CE based TCI state activation)

[0240] [agreement]

[0241] In the Rel.17 unified TCI framework, the following DL RSs may share the indicated Rel-17 TCI state, which is the same as UE-dedicated reception over PDSCH and UE-dedicated reception for all or some CORESETs of a CC.

[0242] Aperiodic CSI-RS resource for CSI

[0243] Aperiodic CSI-RS resources for BM (Beam Management)

[0244] [agreement]

[0245] In the Rel.17 integrated TCI framework:

[0246] Aperiodic SRS resource or resource set for BM may share the indicated Rel-17 TCI state that is the same as the entire or a subset of the dedicated PUCCH resources of the dynamic grant / configured grant based PUSCH CC.

[0247] Note: This does not mean that all time domain operations are automatically supported.

[0248] [agreement]

[0249] In the Rel.17 unified TCI framework, for intra-cell beam direction, the following DL RSs may share the indicated Rel-17 TCI state, which is identical for UE-dedicated reception over PDSCH and UE-dedicated reception for all or some CORESETs of a CC:

[0250] - DMRS associated with non-UE-dedicated reception and associated PDSCH in CORESET

[0251] - Channels and signals for intra-cell beam management, excluding channels / signals that are not dedicated to the UE

[0252] - For the applicable channels and signals mentioned above, the SSB associated with the serving cell and other physical cell identities is used as an indirect QCL reference for the DL TCI (if separate DL / UL TCI) or joint TCI, or as an indirect / direct QCL reference for the UL TCI (if separate DL / UL TCI).

[0253] Note: If RS X is an indirect QCL reference for the target channel, there is at least one other source signal in the QCL chain between RS X and the target channel. Here, the Rel-15 / 16 QCL rules are reused to substitute an SSB for an SSB associated with a different physical cell ID than the serving cell.

[0254] For inter-cell beam management, support of more than one Rel-17 active DL TCI state / QCL per band is a UE capability.

[0255] If the UE does not support such capability, switching between two different DL receptions via two separate beams is possible using MAC-CE based beam indication (one TCI state activation).

[0256] Note: Once beam selection is complete, the serving cell does not change.

[0257] Note: This does not preclude the possibility of timing advance (TA) updates for non-serving cells.

[0258] [agreement]

[0259] In the Rel.17 unified TCI framework, for any DL RS that does not share the indicated Rel-17 TCI state that is identical to the UE-dedicated reception via PDSCH and the UE-dedicated reception via all or a subset of the CORESET of the CC, but can be configured as a target DL RS for a Rel-17 DL TCI (hence, the Rel-17 DL TCI state pool), a Rel-17 mechanism that reuses the Rel-15 / 16 TCI state update signaling / configuration design is used to update / configure such DL RS to the Rel-17 TCI state.

[0260] In the unified TCI framework, there is no agreement to support further (M,N) values ​​other than (M,N)=(1,1) for Rel-17.

[0261] [agreement]

[0262] In the Rel.17 Integrated TCI framework, for Rel-17 Integrated TCI:

[0263] For the number of codepoints in the TCI field for DCI-based beam indication (and therefore the number of codepoints activated by MAC-CE-based TCI state activation), the maximum value is 8.

[0264] [agreement]

[0265] In the Rel.17 Integrated TCI framework, for Rel-17 Integrated TCI:

[0266] - For DL ​​channels / signals that do not share the indicated Rel-17 TCI state that is the same as UE-dedicated reception on PDSCH / PDCCH (by Rel-17 MAC-CE / DCI TCI state updates), all QCL rules defined in Section 5.1.5 of 38.214 are supported.

[0267] Note: For CSI-RS used to provide QCL indication for channels that are not dedicated to the UE, the CSI-RS shall only be QCLed from SSBs with the same PCID as the serving cell's PCID.

[0268] -For DL ​​channels / signals sharing an indicated Rel-17 TCI state that is the same as UE-dedicated reception in PDSCH / PDCCH (by Rel-17 MAC-CE / DCI TCI state update), the following options for source RS and QCL-type are supported:

[0269] Option 1: The TRS is configured for the QCL-TypeA source RS and the CSI-RS for BM is configured for the QCL-TypeD source RS.

[0270] · Option 2: TRS is configured for QCL-TypeA and QCL-TypeD source RS.

[0271] Note: For inter-cell beam management, an SSB having a PCID different from that of the serving cell may be used as a QCL Type-C / D source RS for CSI-RS for BM and / or TRS.

[0272] [agreement]

[0273] In the Rel.17 unified TCI framework, a source RS in a Rel-17 TCI state that provides QCL-Type A or QCL-Type B must be in the same CC / BWP as a target channel or RS.

[0274] [agreement]

[0275] In the Rel.17 unified TCI framework, for the Rel-17 unified TCI, the maximum number of configured TCI states is given as follows (following the Rel-15 / 16 principle):

[0276] -If the UE is configured with joint DL / UL TCI: The maximum number of TCI states configured for joint DL / UL TCI status update is 128 per BWP per CC.

[0277] [agreement]

[0278] In the Rel.17 unified TCI framework, for DL ​​or UL channels / signals that can share the indicated Rel-17 TCI state (by Rel-17 MAC-CE / DCI TCI state updates) which is the same for Rel-17 unified TCI, PDSCH / PDCCH, or dynamic grant / configured grant based PUSCH, UE dedicated reception on all dedicated PUCCH resources:

[0279] In DL case: AP CSI-RS for non-UE dedicated PDCCH / PDSCH or BM or CSI associated with the serving cell physical cell identity (PCI) sharing the indicated Rel-17 TCI state which is identical to the UE dedicated reception in PDSCH / PDCCH is configured by RRC (by updating the Rel-17 MAC-CE / DCI TCI state).

[0280] · For UL: SRS for dynamic grant / configured grant based PUSCH, for BMs sharing the indicated Rel-17 TCI state which is identical for all dedicated PUCCH resources, for antenna switching, for codebook / non-codebook based uplink transmissions is configured by RRC (by updating Rel-17 MAC-CE / DCI TCI state).

[0281] [agreement]

[0282] In the Rel.17 unified TCI framework, in the case of Rel-17 unified TCI, when the UE is configured with separate DL / UL TCI

[0283] - The number of configured TCI states that the UE can support is a UE capability with the following possible values ​​per BWP per CC:

[0284] DL TCI: 64, 128

[0285] UL TCI:32,64

[0286] - Note: This does not mean that the UL TCI shares the same TCI state pool as the joint DL / UL TCI or uses a separate TCI state pool.

[0287] For the Rel-17 unified TCI framework, when the indicated Rel-17 TCI state is applied to PDCCH reception and respective PDSCH reception, it is supported by CORESET decision for intra-cell and inter-cell BM as follows:

[0288] - For PDCCH reception and each PDSCH reception on a CORESET (other than CORESET#0) associated with a set (at least or only) [user-specific search space (USS) and / or common search space (CSS) type 3], the UE shall always apply the indicated Rel-17 TCI state.

[0289] [agreement]

[0290] In the Rel-17 unified TCI framework, any SRS resource or resource set that is a valid target signal for a Rel-15 / 16 spatial relation based on the Rel-15 / 16 spatial relation rules (source-target relation) may be configured as a target signal for the Rel-17UL, or joint TCI, if applicable (and thus the Rel-17UL, or joint TCI state pool, if applicable).

[0291] - This feature does not require any new types of source RS other than those supported for UL TCI and joint DL / UL TCI.

[0292] - Note: This does not mean that the DL and UL TCI status pools are separate or shared for separate DL / UL TCIs.

[0293] - Note: A Rel-17 UE does not need to support both the SRS spatial relationship information function and the optional Rel-16 function within the same band.

[0294] Once a UE is configured with Rel-17 TCI in any CC of the band, the UE is not expected to be configured with Rel-15 / Rel-16 TCI / SpatialRelationInfo.

[0295] The CC inventory for Rel-16 multi-CC beam pointing must not include any CCs that are configured as Rel-17 TCIs.

[0296] [agreement]

[0297] In case of Rel-17 unified TCI framework, when applying the indicated Rel-17 TCI state to PDCCH reception and respective PDSCH reception:

[0298] - For the sake of discussion, it is defined as follows:

[0299] "CORESET A": CORESETs other than CORESET#0 related to UE-specific reception via PDCCH in CC, including CORESETs related to: [USS and / or CSS type 3]

[0300] "CORESET B": A CORESET other than CORESET#0 related only to non-UE-dedicated reception in the PDCCH of the CC, including CORESETs related to the following: [CSS or CSS other than type 3]

[0301] "CORESET C": A CORESET other than CORESET#0 associated with UE-dedicated and non-UE-dedicated reception on the PDCCH in the CC.

[0302] CORESET#0

[0303] - Supports the following decisions per CORESET for Rel-17 TCI status indication:

[0304] For PDCCH reception and respective PDSCH reception in “CORESET A”, the UE shall always apply the indicated Rel-17 TCI state.

[0305] For PDCCH reception and respective PDSCH reception in “CORESET B”, whether the UE applies the indicated Rel-17 TCI state associated with the serving cell is decided by RRC on a per CORESET basis.

[0306] [agreement]

[0307] In the Rel.17 unified TCI framework, for updating and activating joint TCI state ID to provide common QCL information for at least UE dedicated PDCCH / PDSCH and / or common TX spatial filter for UE dedicated PUSCH / PUCCH, at least across a set of configured CCs / BWPs:

[0308] - The source RS determined from the indicated common TCI state ID to provide a QCL Type-D indication and determine the UL TX spatial filter for the target CC may be configured in the target CC or another CC.

[0309] - In case of intra-band CA, the following configurations can be supported without further QCL rules:

[0310] This section describes the agreement for activation and update of common TCI state ID for carrier aggregation (CA) cases.

[0311] One source RS across CCs may be determined from the indicated common TCI State ID to provide QCL Type-D indication and determine the UL TX spatial filter for the set of configured CCs.

[0312] One source RS per CC may be determined from the indicated common TCI state ID to provide QCL Type-D indication and determine the UL TX spatial filter for the set of configured CCs, and the CC-specific source RS is further associated with the same QCL-Type-D RS.

[0313] - "Configured CC / BWP set" includes all BWPs in the configured CC set.

[0314] [agreement]

[0315] For updating and activating a common TCI state ID to provide common QCL information for at least a UE dedicated PDCCH / PDSCH and / or a common TX spatial filter for a UE dedicated PUSCH / PUCCH over at least a set of CCs / BWPs:

[0316] - The RRC configured TCI state pool may be configured in the PDSCH configuration (PDSCH-Config) for each BWP / CC, as in Rel-15 / 16.

[0317] Note: Such an RRC configured TCI state pool configuration does not imply that separate DL / UL TCI state pools are excluded or supported.

[0318] - The RRC configured TCI state pool does not need to be present in the PDSCH configuration (PDSCH-Config) for each BWP / CC and is replaced by a reference to the RRC configured TCI state pool in the referenced BWP / CC.

[0319] · In the PDSCH configuration (PDSCH-Config) of the referenced BWP / CC, the RRC configured TCI state pool shall be set.

[0320] If the PDSCH configuration is a BWP / CC that contains a reference to the RRC configured TCI state pool of the reference BWP / CC, the UE shall apply the RRC configured TCI state pool of the reference BWP / CC.

[0321] - If there is no BWP / CC ID (i.e., bwp-Id or cell) for the QCL-Type A / D source RS in the QCL-Info of the TCI state, the UE assumes that there is a QCL-Type A / D source RS in the BWP / CC to which the TCI state applies.

[0322] - Introduces UE capability to report the maximum number of TCI state pools that it can support across BWPs and CCs of a band, with candidate values ​​including at least 1.

[0323] [agreement]

[0324] In the Rel-17 unified TCI framework, support updating and activating common TCI state IDs to provide common QCL information and / or common TX spatial filters across a set of configured CCs:

[0325] · As in Rel.16, a source RS in a Rel.17 TCI state providing QCL-TypeA [or QCL-TypeB] must be on the same CC as the target channel or RS.

[0326] As described above, in the case of DL, a UE-dedicated CORESET and UE-dedicated reception on PDSCH may be configured as the target channel / RS for common beam update.

[0327] Meanwhile, in a specific BWP of a UE, up to two CORESET pools may be configured for multiple TRP (M-TRP) transmission / reception. That is, the UE may be provided with two CORESET pool index (e.g., coresetPoolIndex) values ​​0 and 1 for the first CORESET and the second CORESET, respectively. Alternatively, the UE may be provided with no CORESET pool index (e.g., coresetPoolIndex) value for the first CORESET and may be provided with a CORESET pool index (e.g., coresetPoolIndex) value of 1 for the second CORESET. In this case, the UE can receive DCI from a specific TRP in a CORESET belonging to each pool.

[0328] If the common beam operation is applied to a BWP in which up to two CORESET pools are set (active) as above, a problem may occur in which CORESET beams from two TRPs are integrated into one (Problem 1). In this disclosure, a method for solving such a problem (Problem 1) is proposed.

[0329] In the present disclosure, " / " may be interpreted as "and", "or" or "and / or" depending on the context.

[0330] Hereinafter, in this disclosure, a transmission panel / beam used when transmitting PUCCH / PUSCH can be analyzed / applied to a transmission beam used when transmitting DMRS of PUCCH / PUSCH. Also, in this disclosure, applying a transmission beam when transmitting PUCCH / PUSCH / PRACH / SRS, etc. can mean applying a spatial transmission parameter / spatial domain transmission filter / spatial transmission filter (spatial Tx parameter / spatial domain Tx filter / spatial Tx filter) for transmitting the PUCCH / PUSCH / PRACH / SRS.

[0331] In addition, in the present disclosure, applying a receiving beam when receiving CORESET / PDCCH / PDSCH / CSI-RS, etc. may mean applying a spatial Rx parameter for receiving the CORESET / PDCCH / PDSCH / CSI-RS.

[0332] Example 1: A method for updating a CORESET beam by a UE when performing a common beam update using a joint DL / UL TCI state and / or a separate DL / UL TCI state (e.g., a DL only TCI state or a UL only TCI state) of a base station in a BWP in which a CORESET pool index (e.g., CORESETPoolIndex) of the UE is configured (i.e., a BWP in which multiple CORESET pools are configured)

[0333] Example 1-1: When a common beam update (or instruction) is performed in the corresponding (active) BWP (i.e., a BWP with multiple CORESET pools configured), the UE does not update all CORESET beams in the BWP, even if the (UE-dedicated) CORESET is the target channel / RS of the common beam update. That is, the UE may ignore (override) the base station's DCI-based common beam update instruction for all CORESETs in the BWP (i.e., excluding the common beam target channel / RS). This operation allows the UE to maintain the two CORESET pool settings in the BWP as is. Therefore, the UE can smoothly receive DCI from each TRP by referring to the QCL-type D RS configured / activated / corresponding (TCI state) for each CORESET in each CORESET pool.

[0334] The above operation may mean that when the UE receives a common beam update (or instruction) for the BWP, it does not perform a beam update only for the CORESET. Therefore, the UE can perform a beam update operation according to the common beam update (or instruction) for other target channels / RSs other than the CORESET.

[0335] The operation of Example 1-1 above may also be used for an "update and activation of common TCI status ID for CA case" operation (e.g., among the above agreements, i) one source RS across CCs provides QCL Type-D indication and is determined from the indicated common TCI status ID to determine a UL TX spatial filter for a set of configured CCs (i.e., operation of a common TCI status pool for CCs), and ii) one source RS per CC may provide QCL Type-D indication and is determined from the indicated common TCI status ID to determine a UL TX spatial filter for a set of configured CCs, and a CC-specific source RS may further be linked with the same QCL-Type-D RS (i.e., operation of a TCI status pool per CC)).

[0336] That is, if two CORESET pools are configured for a specific CC / BWP in a configured CC set that is a target for the update / activation, the UE may not update and activate the common TCI status ID for the CA case for all CORESETs in the CC / BWP, and / or the CC / BWP in the configured CC set may be excluded from the TCI status indication for the update and activation of the common TCI status ID.

[0337] Example 1-2: When a common beam update is performed in the corresponding (active) BWP (i.e., a BWP with multiple CORESET pools configured), the UE may perform a common beam update only for the (first) CORESET whose CORESET pool index (e.g., CORESETPoolIndex) is set to 0 or whose CORESET pool index (e.g., CORESETPoolIndex) is not provided, and may not perform a beam update for the remaining (second) CORESET. Or, conversely, the UE may not perform a beam update for the (first) CORESET, but may perform a common beam update for the (second) CORESET. Or, setting / switching for the above two operations may be performed by the base station.

[0338] By such operation, when the UE receives DCI from a primary TRP in the first (or second) CORESET in the BWP, the UE can perform a single beam operation by performing a common beam update operation only for the CORESET corresponding to the primary TRP.

[0339] Similarly, the operation of Example 1-2 may also be used in the "update and activation of common TCI state ID for CA case" operation. For example, the UE can perform common beam update only for a predetermined CC (e.g., a CC with the lowest / highest cell ID) among multiple CCs in which CA is configured, or a CORESET in a CC configured by the base station.

[0340] Meanwhile, in the Rel-17 standardization, as mentioned above, standardization was performed for the case where M, which is the number of DL TCIs including DL source RS (as DL beam reference RS) for common beam operation, and N, which is the number of UL TCIs including UL source RS (as UL beam reference RS), are both 1. Standardization after Rel-17 may standardize for the case where M>1 and / or N>1, and the base station's beam instruction / update instruction and the UE's beam update operation for this are proposed as follows.

[0341] Example 2: When M, the number of DL TCIs for a common beam operation of a UE, and / or N, the number of UL TCIs, are greater than 1, M and / or N may correspond to the number of TRPs for a base station and / or the number of Rx / Tx beams / panels for a UE. Specifically, M, the number of DL TCIs, may correspond to M TRPs (for DL ​​transmission) for a base station or M Rx beams / panels for a terminal. Also, N, the number of UL TCIs, may correspond to M TRPs (for UL reception) for a base station or M Tx beams / panels for a terminal. That is, when M / N is plural, M / N common beam references for a plurality of different TRPs for a base station and a terminal to receive / transmit with a plurality of different beams / panels may be set / instructed.

[0342] As mentioned above, when M>1, each of the M source reference signals in the M DL TCIs (or 2M, when qcl_Type2 is further set to qcl_Type1) can provide QCL information for at least one of the M beam pair links (beam pair links) for UE-dedicated reception on the PDSCH and / or on a subset of the intra-CC CORESET. When N>1, each of the N source reference signals in the N UL TCIs can provide a reference for determining a UL TX spatial filter for at least one of the N beam pair links associated with a subset of dynamic grant / configured grant-based PUSCH and / or intra-CC dedicated PUCCH resources. When M>1 and N>1, the joint DL / UL TCI can refer to the minimum common source reference RS used to determine both the DL QCL information and the UL TX spatial filter. When M>1 and N>1, the M DL TCI and the N UL TCI can be configured separately.

[0343] Example 2-1: The base station can set / update the target channel / RS for applying M / N (DL / UL) TCIs to the UE (in common beam operation) by higher layer signaling (e.g., RRC / MAC CE signaling).

[0344] Here, the target channel / RS may include at least one (i.e., all or a part) of a (M-TRP repetition) PDCCH, a subset of CORESET (e.g., CORESET having a specific CORESETPoolIndex), a (M-TRP repetition) PDSCH, an AP CSI-RS for BM or CSI, a (M-TRP repetition) PUCCH, a subset of dedicated PUCCH resources (e.g., all or a part of PUCCH groups), a (M-TRP repetition) PUSCH, and an SRS. According to such a target channel / RS configuration instruction, the base station may perform a beam operation in a form of setting / indicating a plurality (M and / or N) of common beam references for multiple TRPs / panels. For example, the base station may configure only M DL TCIs to the UE, configure only N UL TCIs to the UE, or configure M (i.e., M=N) joint TCIs to the UE in order to indicate / update a common beam reference for multiple TRPs / panels.

[0345] Example 2-2: In the M / N TCIs, the first TCI may correspond to a first transmission occasion (TO) group of PDCCH / PDSCH / CSI-RS / PUCCH / PUSCH / SRS, a first CORESET having a CORESET pool index (e.g., CORESETPoolIndex) value of 0, and / or a first PUCCH group. The second TCI may correspond to a second TO group of PDCCH / PDSCH / CSI-RS / PUCCH / PUSCH / SRS, a second CORESET having a CORESET pool index (e.g., CORESETPoolIndex) value of 1, and / or a second PUCCH group. Similarly, when M / N is 3 or more, the correspondence may be applied / defined in ascending order. Through such an operation, the base station can clearly set / instruct the terminal which of the M / N TCIs are applied to which part of the target channels / RS of a specific channel / RS.

[0346] Example 2-3: M / N TCI statuses for setting / indicating (having multiple) M / N common reference RSs (associated with joint TCIs) and / or individual reference RSs (associated with individual TCIs) may be associated / mapped / concatenated to each code point in the TCI status field of the DL / UL grant DCI. The base station may then instruct the terminal to apply a common beam for M / N reception / transmission by instructing the terminal with the code point in the DCI. With this operation, unlike Rel-17, the base station may dynamically indicate multiple M / N TCIs and operate multiple (M / N) common beam references for multiple TRPs / panels. The TCI status field may include a mixture of a code point having one DL / UL TCI (i.e., associated / mapped / concatenated) and a code point having multiple DL / UL TCIs (i.e., associated / mapped / concatenated). Here, when a code point having one DL / UL TCI (i.e., associated / mapped / concatenated) is indicated by the base station, the terminal understands / deems that a common beam operation of Rel-17 is performed and can perform a beam update operation. On the other hand, when a code point having multiple DL / UL TCIs (i.e., associated / mapped / concatenated) is indicated by the base station, the terminal understands / deems that multiple TCIs (i.e., M / N TCIs) are applied to the (already set) target channel / RS based on the above embodiment 2-1 / 2-2 and can perform a beam update operation.

[0347] In addition, in a BWP in which two CORESET pools are set, one TCI update and multiple TCI updates can be dynamically switched in the field. Here, when one TCI update is indicated, at least one of the various methods related to the first embodiment may be used for the two CORESET pools.

[0348] The above problem and the following embodiment may be further considered in embodiment 1 (embodiment 1-1 / 1-2) and / or embodiment 2 (embodiment 2-1 / 2-2 / 2-3). When one or more CORESET pools are configured in a specific BWP, the terminal updates all CORESETs (with the same TCI) that are associated with / identical to the CORESET pool index (e.g., CORESETPoolIndex) of the CORESET in which the DCI for TCI update is transmitted, and does not need to update CORESETs in which other CORESET pool indexes (e.g., CORESETPoolIndex) are configured. In addition, when a PUCCH resource group is used during DL / UL reception / transmission beam update using a joint DL / UL TCI, all (with the same TCI) updates can be performed only for the PUCCH resource group associated with the DCI for the TCI update (i.e., all PUCCH resources in the PUCCH resource group).

[0349] Here, the PUCCH resource group associated with the DCI for the TCI update may be, for example, a PUCCH resource group to which a PUCCH resource corresponding to a PUCCH resource indicator (PRI) designated / indicated by the DCI belongs.

[0350] Alternatively, the PUCCH resource group associated with the DCI for the TCI update may be a PUCCH resource group to which a PUCCH resource for which a (non-periodic / semi-persistent) CSI report triggered / activated / deactivated by the DCI is transmitted belongs. For example, a PUCCH resource group for which the TCI state is updated may be determined according to a CORESET pool index (e.g., CORESETPoolIndex) in which a DCI scheduling an active MAC-CE (i.e., via a PDSCH) for a SP (semi persistent)-CSI report on the PUCCH is transmitted. For example, an ascending mapping relationship may be considered in which a PUCCH resource group with the lowest index is determined in the case of the lowest CORESET pool index, and a PUCCH resource group with the highest index is determined in the case of the highest CORESET pool index.

[0351] Of the operations in the above-mentioned embodiment 1 (embodiment 1-1 / 1-2) and embodiment 2 (embodiment 2-1 / 2-2 / 2-3), only one may be performed between the base station and the terminal, or a combination of multiple operations may be performed.

[0352] FIG. 8 illustrates a signaling procedure between a network and a terminal for a wireless signal transmission / reception method according to an embodiment of the present disclosure.

[0353] FIG. 8 illustrates signaling between a network (e.g., TRP1, TRP2) and a terminal in a multiple TRP (i.e., M-TRP or multiple cells, hereinafter, TRP may be replaced with cell) situation to which the method proposed in the present invention (e.g., any one or a combination of one or more of the detailed embodiments of Examples 1 and 2) may be applied. Here, the terminal / network is an example and may be applied instead with various devices. FIG. 8 is merely for convenience of explanation and does not limit the scope of the present disclosure. In addition, some steps illustrated in FIG. 8 may be omitted depending on the situation and / or settings, etc.

[0354] The signaling method described in FIG. 8 may be extended to signaling between multiple TRPs and multiple UEs. In the following description, the network may be a base station including multiple TRPs, or a cell including multiple TRPs. As an example, an ideal / non-ideal backhaul may be set between TRP1 and TRP2 constituting the network. In addition, the following description is described based on multiple TRPs, but this may be extended to transmission through multiple panels in the same manner. In addition, in the present disclosure, the operation of a terminal receiving a signal from TRP1 / TRP2 may be interpreted / described (or may be an operation) as the operation of the terminal receiving a signal from the network (via / using TRP1 / 2), and the operation of the terminal transmitting a signal to TRP1 / TRP2 may be interpreted / described (or may be an operation) as the operation of the terminal transmitting a signal to the network (via / using TRP1 / TRP2), or may be interpreted / described conversely.

[0355] Referring to FIG. 8, it is assumed that the UE receives configuration / DCI from a representative TRP (e.g., TRP1) in a situation where the UE is an M-TRP (or cell) (hereinafter, all TRPs may be replaced with cells / panels, or when multiple CORESETs are configured from one TRP, it can be assumed to be an M-TRP). This is merely for convenience of explanation, and it goes without saying that the method described below may be extended and applied even when the UE receives configuration / DCI from at least one TRP. As an example, the representative TRP may be a TRP that conveys / transmits a system information block (SIB) / paging / random access (RA)-related signal to the UE.

[0356] The terminal can receive configuration information from the network via / using TRP1 (and / or TRP2) (S801).

[0357] The configuration information may include information related to network configuration (e.g., TRP configuration) / information related to M-TRP-based transmission / reception (e.g., resource allocation, etc.), etc. In this case, the configuration information may be transmitted through higher layer signaling (e.g., RRC signaling, MAC-CE, etc.).

[0358] The configuration information may include configuration information related to the beam instruction / update procedure described in the proposed method above (e.g., Example 1, Example 2, and any one or a combination of one or more of the detailed embodiments for Examples 1 and 2).

[0359] For example, the configuration information may include information for configuring joint TCI and / or separate DL / UL TCI. For example, the configuration information may include a list of TCI states that provide a reference signal for QCL for a DMRS / downlink signal (e.g., CSI-RS) of a downlink channel (e.g., PDSCH, PDCCH) and / or provide a reference for determining an uplink transmit spatial filter of a DMRS / uplink signal (e.g., SRS) of an uplink channel (e.g., PUSCH, PUCCH). In the present disclosure, unless a downlink / uplink signal is specifically described, a downlink channel may be a concept that includes both downlink channels / signals, and an uplink channel may be a concept that includes both uplink channels / signals.

[0360] As yet another example, the setting information may include a CORESET setting. For example, the setting for each CORESET may include a CORESET pool index for a CORESET pool to which the CORESET belongs.

[0361] The terminal can receive downlink control information (DCI) from the network via / using TRP1 (and / or TRP2) (S802).

[0362] Here, the DCI may be transmitted on a downlink control channel (e.g., a PDCCH), and the terminal may monitor / receive the downlink control channel (e.g., a PDCCH) in one or more CORESETs set in its BWP and detect / decode the DCI.

[0363] Here, the DCI (e.g., DCI format 1_1 / 1_2) can schedule the transmission of a downlink channel (e.g., PDSCH) or an uplink channel (e.g., PUSCH) and can trigger the transmission of an uplink signal (e.g., SRS). Alternatively, the DCI may not include an uplink assignment or a downlink assignment.

[0364] Furthermore, the DCI may include a transmission configuration indication (TCI) field, and a TCI state for a downlink / uplink channel / signal may be indicated by a code point in the TCI field. Here, as described above, a TCI code point may be mapped / corresponding to one TCI state and / or to multiple TCI states. That is, since one TCI state or multiple TCI states may be indicated per TCI code point, it may be determined whether one TCI state or two TCI states in the list of TCI states are indicated according to a code point value of the TCI field in the DCI.

[0365] The terminal may perform uplink transmission (i.e., uplink channels (e.g., PUCCH, PUSCH) and / or signals (e.g., SRS)) or receive downlink transmission (i.e., downlink channels (e.g., PDSCH, PDCCH) and / or signals (e.g., CSI-RS)) to the network (S803).

[0366] Here, the terminal can perform uplink transmission or receive downlink transmission based on the above-mentioned proposed method (e.g., any one or a combination of one or more of example 1, example 2, and detailed examples of examples 1 and 2).

[0367] For example, based on the DCI indicating one TCI state in the list of TCI states, the indicated one TCI state may be applied to both uplink transmission and downlink transmission associated with a CORESET pool index of the CORESET in which the DCI is transmitted. That is, when the terminal performs uplink transmission, based on the TCI state indicated by the DCI, the terminal may use an RS in the TCI state as a reference for determining an uplink transmission spatial filter for uplink transmission. Also, when the terminal receives downlink transmission, based on the TCI state indicated by the DCI, the terminal may receive downlink transmission by assuming a QCL relationship between the RS in the TCI state and downlink transmission.

[0368] For example, when uplink transmission is a PUCCH, the indicated TCI state may be applied to all PUCCH resources in a PUCCH resource group associated with a CORESET pool index of the CORESET in which the DCI is transmitted. Here, the associated PUCCH resource group may refer to a PUCCH resource group to which a PUCCH resource indicated by a PUCCH resource indicator (PRI) field in the DCI belongs. Alternatively, the associated PUCCH resource group may refer to a PUCCH resource group to which a PUCCH resource to which a CSI report triggered by the DCI is transmitted belongs.

[0369] As yet another example, based on the DCI indicating two TCI states in the list of TCI states, the uplink or downlink transmission to which the two TCI states apply may be configured by the network (e.g., using higher layer signaling).

[0370] Alternatively, based on two TCI states in the list of TCI states being indicated by the DCI, a first TCI state of the two TCI states may be applied to one or more CORESETs having a first CORESET pool index, and a second TCI state of the two TCI states may be applied to one or more CORESETs having a second CORESET pool index, where being applied to a CORESET may mean being applied to a PDCCH (i.e., a DMRS of a PDCCH) monitored / received in the CORESET.

[0371] Alternatively, based on two TCI states in the list of TCI states indicated by the DCI, a first TCI state of the two TCI states may be applied to a first TO (or a first TO group) of uplink or downlink transmission, and a second TCI state may be applied to a second TO (or a second TO group) of the uplink or downlink transmission. That is, a TCI state may be applied for each TO (or TO group) according to a predetermined rule (e.g., mapping in ascending / descending order of TCI state index every time the index of a TO (or TO group) increases) or according to a setting by the network.

[0372] Meanwhile, although not shown in Fig. 8, the UE may receive the first DCI from the first TRP and the second DCI from the second TRP. In this case, the first DCI and the second DCI may each include a TCI field, and each TCI field may indicate one TCI state, so that a total of two TCI states may be indicated to the UE.

[0373] FIG. 9 is a diagram illustrating an operation of a terminal with respect to a wireless signal transmission and reception method according to an embodiment of the present disclosure.

[0374] Referring to FIG. 9, FIG. 9 illustrates an operation of a terminal based on the proposed method (e.g., any one or a combination of one or more of the detailed embodiments of the first and second embodiments). The illustration of FIG. 9 is for convenience of explanation and does not limit the scope of the present disclosure. Some steps illustrated in FIG. 9 may be omitted depending on the situation and / or setting. Also, the terminal in FIG. 9 is only one example and may be embodied by the device illustrated in FIG. 11. For example, the processor 102 / 202 in FIG. 11 may control the transceiver 106 / 206 to transmit and receive channels / signals / data / information, etc., and may also control the transceiver 106 / 206 to store the transmitted or received channels / signals / data / information, etc. in the memory 104 / 204.

[0375] In addition, the operations of FIG. 9 may be processed by one or more processors 102, 202 of FIG. 11, and the operations of FIG. 9 may be stored in a memory (e.g., one or more memories 104, 204 of FIG. 11) in the form of instructions / programs (e.g., instructions, executable code) for driving at least one processor (e.g., 102, 202) of FIG. 11.

[0376] Referring to FIG. 9, a terminal receives first configuration information including a list of TCI states from a base station (S901).

[0377] Here, the list of TCI states may correspond to a list of TCI states for a joint (or integrated) TCI configuration commonly applicable to uplink / downlink transmission, or may correspond to a list of TCI states for individual TCI configurations individually applicable to uplink or downlink transmission. For example, the first configuration information may include a list of TCI states providing a reference signal for a QCL for a DMRS / downlink signal (e.g., CSI-RS) of a downlink channel (e.g., PDSCH, PDCCH) and / or providing a reference for determining an uplink transmit spatial filter for a DMRS / uplink signal (e.g., SRS) of an uplink channel (e.g., PUSCH, PUCCH).

[0378] For example, the first configuration information may be included in configuration information for a PDSCH (eg, PDSCH-Config) and transmitted, or may be included in configuration information for a BWP (eg, BWP) and transmitted.

[0379] The terminal may receive second configuration information related to CORESET from the base station (S902).

[0380] Here, the second configuration information related to the CORESET may be transmitted as individual configuration information for each CORESET, and the configuration information for each CORESET may include a CORESET pool index for a CORESET pool to which the CORESET belongs.

[0381] For example, the second configuration information may be included in configuration information for a PDCCH (eg, PDCCH-Config) and transmitted, or may be included in configuration information for a BWP (eg, BWP) and transmitted.

[0382] The terminal receives downlink control information (DCI) from the base station (S903).

[0383] Here, the DCI may be transmitted on a downlink control channel (e.g., a PDCCH), and the terminal may monitor / receive the downlink control channel (e.g., a PDCCH) in one or more CORESETs set in its BWP and detect / decode the DCI.

[0384] Here, the DCI (e.g., DCI format 1_1 / 1_2) can schedule the transmission of a downlink channel (e.g., PDSCH) or an uplink channel (e.g., PUSCH) and can trigger the transmission of an uplink signal (e.g., SRS). Alternatively, the DCI may not include an uplink assignment or a downlink assignment.

[0385] Furthermore, the DCI may include a transmission configuration indication (TCI) field, and a TCI state for a downlink / uplink channel / signal may be indicated by a code point in the TCI field. Here, as described above, a TCI code point may be mapped / corresponding to one TCI state and / or to multiple TCI states. That is, since one TCI state or multiple TCI states may be indicated per TCI code point, it may be determined whether one TCI state or two TCI states in the list of TCI states are indicated according to a code point value of the TCI field in the DCI.

[0386] The terminal can perform uplink transmission (i.e., uplink channels (e.g., PUCCH, PUSCH) and / or signals (e.g., SRS)) or receive downlink transmission (i.e., downlink channels (e.g., PDSCH, PDCCH) and / or signals (e.g., CSI-RS)) to the base station (S904).

[0387] Here, the terminal can perform uplink transmission or receive downlink transmission based on the above-mentioned proposed method (e.g., any one or a combination of one or more of example 1, example 2, and detailed examples of examples 1 and 2).

[0388] For example, based on one TCI state in the list of TCI states being indicated by the DCI, the indicated one TCI state may be applied to both uplink transmission and downlink transmission associated with a CORESET pool index of the CORESET in which the DCI is transmitted. That is, when the terminal performs uplink transmission, based on the TCI state indicated by the DCI, the terminal may use an RS in the TCI state as a reference for determining an uplink transmission spatial filter for uplink transmission. Also, when the terminal receives downlink transmission, based on the TCI state indicated by the DCI, the terminal may receive downlink transmission by assuming a QCL relationship between the RS in the TCI state and downlink transmission.

[0389] For example, when uplink transmission is a PUCCH, the indicated TCI state may be applied to all PUCCH resources in a PUCCH resource group associated with a CORESET pool index of the CORESET in which the DCI is transmitted. Here, the associated PUCCH resource group may refer to a PUCCH resource group to which a PUCCH resource indicated by a PUCCH resource indicator (PRI) field in the DCI belongs. Alternatively, the associated PUCCH resource group may refer to a PUCCH resource group to which a PUCCH resource to which a CSI report triggered by the DCI is transmitted belongs.

[0390] As yet another example, based on the DCI indicating two TCI states in the list of TCI states, the uplink or downlink transmission to which the two TCI states apply may be configured by the base station (e.g., using higher layer signaling).

[0391] Alternatively, based on two TCI states in the list of TCI states being indicated by the DCI, a first TCI state of the two TCI states may be applied to one or more CORESETs having a first CORESET pool index, and a second TCI state of the two TCI states may be applied to one or more CORESETs having a second CORESET pool index, where being applied to a CORESET may mean being applied to a PDCCH (i.e., a DMRS of a PDCCH) monitored / received in the CORESET.

[0392] Alternatively, based on two TCI states in the list of TCI states indicated by the DCI, a first TCI state of the two TCI states may be applied to a first TO (or a first TO group) of uplink or downlink transmission, and a second TCI state may be applied to a second TO (or a second TO group) of the uplink or downlink transmission. That is, a TCI state may be applied for each TO (or TO group) according to a predetermined rule (e.g., mapping in ascending / descending order of TCI state index every time the index of the TO (or TO group) increases) or according to a setting by the base station.

[0393] Meanwhile, although not shown in Fig. 9, the UE may receive the first DCI from the first TRP and the second DCI from the second TRP. In this case, the first DCI and the second DCI may each include a TCI field, and each TCI field may indicate one TCI state, so that a total of two TCI states may be indicated to the UE.

[0394] FIG. 10 is a diagram illustrating an operation of a base station for a wireless signal transmission and reception method according to an embodiment of the present disclosure.

[0395] Referring to FIG. 10, FIG. 10 illustrates an operation of a base station based on the proposed method (e.g., any one or a combination of one or more of the detailed embodiments of the first and second embodiments). The illustration of FIG. 10 is for convenience of explanation and does not limit the scope of the present disclosure. Some steps illustrated in FIG. 10 may be omitted depending on the situation and / or setting. Also, the base station in FIG. 10 is only one example and may be embodied by the device illustrated in FIG. 11. For example, the processor 102 / 202 in FIG. 11 may control the transceiver 106 / 206 to transmit and receive channels / signals / data / information, etc., and may also control the transceiver 106 / 206 to store the transmitted or received channels / signals / data / information, etc. in the memory 104 / 204.

[0396] In addition, the operations of FIG. 10 may be processed by one or more processors 102, 202 of FIG. 11, and the operations of FIG. 10 may be stored in a memory (e.g., one or more memories 104, 204 of FIG. 11) in the form of instructions / programs (e.g., instructions, executable code) for driving at least one processor (e.g., 102, 202) of FIG. 11.

[0397] Referring to FIG. 10, the base station transmits first configuration information including a list of TCI states to the terminal (S1001).

[0398] Here, the list of TCI states may correspond to a list of TCI states for a joint (or integrated) TCI configuration commonly applicable to uplink / downlink transmission, or may correspond to a list of TCI states for individual TCI configurations individually applicable to uplink or downlink transmission. For example, the first configuration information may include a list of TCI states providing a reference signal for a QCL for a DMRS / downlink signal (e.g., CSI-RS) of a downlink channel (e.g., PDSCH, PDCCH) and / or providing a reference for determining an uplink transmit spatial filter for a DMRS / uplink signal (e.g., SRS) of an uplink channel (e.g., PUSCH, PUCCH).

[0399] For example, the first configuration information may be included in configuration information for a PDSCH (eg, PDSCH-Config) and transmitted, or may be included in configuration information for a BWP (eg, BWP) and transmitted.

[0400] The base station can transmit second setting information related to CORESET to the terminal (S1002).

[0401] Here, the second configuration information related to the CORESET may be transmitted as individual configuration information for each CORESET, and the configuration information for each CORESET may include a CORESET pool index for a CORESET pool to which the CORESET belongs.

[0402] For example, the second configuration information may be included in configuration information for a PDCCH (eg, PDCCH-Config) and transmitted, or may be included in configuration information for a BWP (eg, BWP) and transmitted.

[0403] The base station transmits downlink control information (DCI) to the terminal (S1003).

[0404] Here, the DCI may be transmitted on a downlink control channel (e.g., a PDCCH), and the terminal may monitor / receive the downlink control channel (e.g., a PDCCH) in one or more CORESETs set in its BWP and detect / decode the DCI.

[0405] Here, the DCI (e.g., DCI format 1_1 / 1_2) can schedule the transmission of a downlink channel (e.g., PDSCH) or an uplink channel (e.g., PUSCH) and can trigger the transmission of an uplink signal (e.g., SRS). Alternatively, the DCI may not include an uplink assignment or a downlink assignment.

[0406] Furthermore, the DCI may include a transmission configuration indication (TCI) field, and a TCI state for a downlink / uplink channel / signal may be indicated by a code point in the TCI field. Here, as described above, a TCI code point may be mapped / corresponding to one TCI state and / or to multiple TCI states. That is, since one TCI state or multiple TCI states may be indicated per TCI code point, it may be determined whether one TCI state or two TCI states in the list of TCI states are indicated according to a code point value of the TCI field in the DCI.

[0407] The base station can receive uplink transmissions (i.e., uplink channels (e.g., PUCCH, PUSCH) and / or signals (e.g., SRS)) or transmit downlink transmissions (i.e., downlink channels (e.g., PDSCH, PDCCH) and / or signals (e.g., CSI-RS)) from the terminal (S1004).

[0408] Here, the base station can receive uplink transmission or perform downlink transmission based on the above-mentioned proposed method (e.g., any one or a combination of one or more of Example 1, Example 2, and detailed embodiments of Examples 1 and 2).

[0409] For example, based on one TCI state in the list of TCI states being indicated by the DCI, the indicated one TCI state may be applied to both uplink transmission and downlink transmission associated with the CORESET pool index of the CORESET in which the DCI is transmitted. That is, when receiving uplink transmission from the UE, based on the TCI state indicated by the DCI, the RS in the TCI state may be used as a reference for determining an uplink transmission spatial filter for uplink transmission. Also, when performing downlink transmission to the UE, the downlink transmission may be performed assuming a QCL relationship between the RS in the TCI state and downlink transmission based on the TCI state indicated by the DCI.

[0410] For example, when uplink transmission is a PUCCH, the indicated TCI state may be applied to all PUCCH resources in a PUCCH resource group associated with a CORESET pool index of the CORESET in which the DCI is transmitted. Here, the associated PUCCH resource group may refer to a PUCCH resource group to which a PUCCH resource indicated by a PUCCH resource indicator (PRI) field in the DCI belongs. Alternatively, the associated PUCCH resource group may refer to a PUCCH resource group to which a PUCCH resource to which a CSI report triggered by the DCI is transmitted belongs.

[0411] As yet another example, based on the DCI indicating two TCI states in the list of TCI states, the uplink or downlink transmission to which the two TCI states apply may be configured by the base station (e.g., using higher layer signaling).

[0412] Alternatively, based on two TCI states in the list of TCI states being indicated by the DCI, a first TCI state of the two TCI states may be applied to one or more CORESETs having a first CORESET pool index, and a second TCI state of the two TCI states may be applied to one or more CORESETs having a second CORESET pool index, where being applied to a CORESET may mean being applied to a PDCCH (i.e., a DMRS of a PDCCH) monitored / received in the CORESET.

[0413] Alternatively, based on two TCI states in the list of TCI states indicated by the DCI, a first TCI state of the two TCI states may be applied to a first TO (or a first TO group) of uplink or downlink transmission, and a second TCI state may be applied to a second TO (or a second TO group) of the uplink or downlink transmission. That is, a TCI state may be applied for each TO (or TO group) according to a predetermined rule (e.g., mapping in ascending / descending order of TCI state index every time the index of the TO (or TO group) increases) or according to a setting by the base station.

[0414] Meanwhile, although not shown in Fig. 10, the first DCI may be transmitted from the first TRP to the terminal, and the second DCI may be transmitted from the second TRP. In this case, the first DCI and the second DCI may each include a TCI field, and each TCI field may indicate one TCI state, so that a total of two TCI states may be indicated to the terminal.

[0415] Apparatuses to which the present disclosure can be applied

[0416] FIG. 11 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure.

[0417] Referring to FIG. 11, a first wireless device 100 and a second wireless device 200 can transmit and receive wireless signals using various wireless access technologies (eg, LTE, NR).

[0418] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. For example, the processor 102 may process information in the memory 104 to generate a first information / signal, and then transmit a wireless signal including the first information / signal from the transceiver 106. The processor 102 may also receive a wireless signal including a second information / signal from the transceiver 106, and then store information obtained from signal processing of the second information / signal in the memory 104. The memory 104 may be coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for performing some or all of the processes controlled by the processor 102 or executing the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in the present disclosure. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 may be coupled to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be referred to as a Radio Frequency (RF) unit. In the present invention, a wireless device may mean a communication modem / circuit / chip.

[0419] The second wireless device 200 may include one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. For example, the processor 202 may process information in the memory 204 to generate a third information / signal, and then transmit a wireless signal including the third information / signal from the transceiver 206. The processor 202 may also receive a wireless signal including a fourth information / signal from the transceiver 206, and then store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be coupled to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for performing some or all of the processes controlled by the processor 202 or executing the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in the present disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to embody a wireless communication technology (e.g., LTE, NR). The transceiver 206 may be coupled to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be referred to as an RF unit. In the present invention, a wireless device may mean a communication modem / circuit / chip.

[0420] The hardware elements of the wireless device 100, 200 are described in more detail below. Without being limited thereto, one or more protocol layers may be embodied by one or more processors 102, 202. For example, one or more processors 102, 202 may embody one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. The one or more processors 102, 202 can generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information to one or more transceivers 106, 206 according to the functions, procedures, suggestions, and / or methods disclosed in this disclosure. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure.

[0421] The one or more processors 102, 202 may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The one or more processors 102, 202 may be embodied in hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be embodied in firmware or software in the form of code, instructions and / or collections of instructions.

[0422] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Also, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 by various techniques, such as wired or wireless coupling.

[0423] The one or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as referred to in the methods and / or operational flow diagrams of the present disclosure, to one or more other devices. The one or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams of the present disclosure, from one or more other devices. For example, the one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. In addition, one or more transceivers 106, 206 may be coupled to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, radio signals / channels, etc., as described, functions, procedures, suggestions, methods, and / or operation flow diagrams disclosed in the present disclosure, via the one or more antennas 108, 208. In the present disclosure, the one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may convert the received radio signals / channels, etc., from RF band signals to baseband signals for processing the received user data, control information, radio signals / channels, etc., using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, radio signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To that end, one or more of the transceivers 106, 206 may include (analog) oscillators and / or filters.

[0424] The above-described embodiments are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered as optional unless otherwise expressly stated. Each component or feature may be implemented in a form not combined with other components or features. It is also possible to combine some components and / or features to configure the embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some configurations or features of one embodiment may be included in another embodiment, or may be replaced with corresponding configurations or features of another embodiment. It is clear that claims that do not have an explicit reference relationship in the claims may be combined to configure an embodiment, or may be included as a new claim by amendment after filing.

[0425] It is obvious to those skilled in the art that the present disclosure can be embodied in other specific forms without departing from the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted as limiting in any respect, but should be considered as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the attached claims, and any modifications within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0426] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause a device or computer to perform operations according to the methods of the various embodiments, and non-transitory computer-readable media on which such software or instructions or the like can be stored and executed on a device or computer. Instructions available for programming a processing system to perform features described in the present disclosure may be stored on / in a storage medium or computer-readable storage medium, and computer program products including such storage media may be used to embody features described in the present disclosure. The storage medium may include high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, but is not limited thereto, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory optionally includes one or more storage devices that are located remotely from the processor. The memory or alternatively the non-volatile memory devices in the memory include non-transitory computer-readable storage media. The features described in this disclosure may be embodied in software and / or firmware stored on any one of a number of machine-readable media and capable of controlling the hardware of a processing system and allowing the processing system to interact with other mechanisms that utilize the results of embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0427] Here, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may include LTE, NR, and 6G as well as Narrowband Internet of Things (NB-IoT) for low power communication. At this time, for example, the NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may perform communication based on the LTE-M technology. At this time, as an example, the LTE-M technology may be an example of LPWAN technology and may be called various names such as eMTC (enhanced Machine Type Communication). For example, the LTE-M technology may be embodied by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, the wireless communication technology embodied in the wireless devices 100 and 200 of the present disclosure may include at least one of ZigBee (registered trademark), Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN), which consider low power communication, and is not limited to the above names. As an example, the ZigBee technology may generate personal area networks (PANs) related to small / low power digital communication based on various standards such as IEEE 802.15.4, and may be called various names. [Industrial Applicability]

[0428] The method proposed in this disclosure has been described mainly as being applied to 3GPP LTE / LTE-A and 5G systems, but it can be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. 1. A method performed by a terminal in a wireless communication system, the method comprising: receiving first configuration information including a list of transmission configuration indication (TCI) states from a base station, the list of TCI states providing a reference for determining a reference signal for quasi co-location (QCL) for a downlink channel and / or an uplink transmit spatial filter for an uplink channel; receiving second configuration information related to a control resource set (CORESET) from the base station, wherein a plurality of CORESETs having different CORESET pool indexes are configured according to the second configuration information; receiving downlink control information (DCI) from the base station; A method in which, based on the DCI indicating one TCI state in the list of TCI states, the indicated one TCI state is applied to uplink transmissions and downlink transmissions associated with a CORESET pool index of the CORESET in which the DCI was transmitted.

2. The method of claim 1, wherein the indicated TCI state is applied to all physical uplink control channel (PUCCH) resources in a PUCCH resource group associated with a CORESET pool index of the CORESET in which the DCI is transmitted.

3. The method of claim 2, wherein the PUCCH resource group is a PUCCH resource group to which a PUCCH resource indicated by a PUCCH resource indicator (PRI) field in the DCI belongs.

4. The method of claim 2, wherein the PUCCH resource group is a PUCCH resource group to which a PUCCH resource for transmitting a channel state information (CSI) report triggered by the DCI belongs.

5. The method of claim 1, wherein the uplink transmission and the downlink transmission associated with a CORESET pool index of the CORESET from which the DCI is transmitted include at least one of a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a CORESET, a channel state information-reference signal (CSI-RS), a PUCCH, a physical uplink shared channel (PUSCH), and a sounding reference signal (SRS).

6. Based on the DCI indicating two TCI states in the list of TCI states, The method of claim 1 , wherein the uplink or downlink transmission to which the two TCI states apply is configured by the base station.

7. Based on the DCI indicating two TCI states in the list of TCI states, 2. The method of claim 1, wherein a first TCI state of the two TCI states applies to one or more CORESETs having a first CORESET pool index, and a second TCI state applies to one or more CORESETs having a second CORESET pool index.

8. Based on the DCI indicating two TCI states in the list of TCI states, 2. The method of claim 1, wherein a first of the two TCI states applies to a first transmission occasion (TO) group of uplink or downlink transmissions and a second TCI state applies to a second TO group of the uplink or downlink transmissions.

9. The method of claim 1 , wherein a codepoint value of a TCI field in the DCI determines whether one TCI state or two TCI states in the list of TCI states are indicated.

10. A terminal for use in a wireless communication system, the terminal comprising: one or more transceivers for transmitting and receiving radio signals; one or more processors for controlling the one or more transceivers; The one or more processors: receiving first configuration information including a list of transmission configuration indication (TCI) states from a base station, where the list of TCI states provides a reference for determining a reference signal for quasi co-location (QCL) for a downlink channel and / or an uplink transmit spatial filter for an uplink channel; receiving second configuration information related to a control resource set (CORESET) from the base station, wherein a plurality of CORESETs having different CORESET pool indexes are configured according to the second configuration information; configured to receive downlink control information (DCI) from the base station; A terminal, wherein, based on the DCI indicating one TCI state in the list of TCI states, the indicated one TCI state is applied to uplink transmission and downlink transmission associated with a CORESET pool index of the CORESET in which the DCI was transmitted.

11. One or more non-transitory computer-readable media storing at least one instruction, The at least one instruction is executed by at least one processor, the apparatus comprising: receiving first configuration information including a list of transmission configuration indication (TCI) states from a base station, where the list of TCI states provides a reference for determining a reference signal for quasi co-location (QCL) for a downlink channel and / or an uplink transmit spatial filter for an uplink channel; receiving second configuration information related to a control resource set (CORESET) from the base station, wherein a plurality of CORESETs having different CORESET pool indexes are configured according to the second configuration information; and receiving downlink control information (DCI) from the base station; A computer-readable medium, comprising: a first TCI state in a list of TCI states indicated by the DCI; and a second TCI state in the list of TCI states indicated by the DCI, the second TCI state being applied to uplink transmissions and downlink transmissions associated with a CORESET pool index of the CORESET in which the DCI was transmitted.

12. 1. A processing device configured to control a terminal in a wireless communication system, the processing device comprising: At least one processor; at least one computer memory operatively coupled to the at least one processor and configured to store instructions for performing operations based on being executed by the at least one processor; The operation includes: receiving first configuration information including a list of transmission configuration indication (TCI) states from a base station, the list of TCI states providing a reference for determining a reference signal for quasi co-location (QCL) for a downlink channel and / or an uplink transmit spatial filter for an uplink channel; receiving second configuration information related to a control resource set (CORESET) from the base station, wherein a plurality of CORESETs having different CORESET pool indexes are configured according to the second configuration information; receiving downlink control information (DCI) from the base station; A processing device, in which, based on the DCI indicating one TCI state in the list of TCI states, the indicated one TCI state is applied to uplink transmissions and downlink transmissions associated with a CORESET pool index of the CORESET in which the DCI was transmitted.

13. 1. A method performed by a base station in a wireless communication system, the method comprising: transmitting first configuration information including a list of transmission configuration indication (TCI) states to the terminal, the list of TCI states providing a reference signal for quasi co-location (QCL) for a downlink channel and / or a reference for determining an uplink transmit spatial filter for an uplink channel; transmitting second configuration information related to a control resource set (CORESET) to the terminal, wherein a plurality of CORESETs having different CORESET pool indexes are configured according to the second configuration information; transmitting downlink control information (DCI) to the terminal; A method in which, based on the DCI indicating one TCI state in the list of TCI states, the indicated one TCI state is applied to uplink transmissions and downlink transmissions associated with a CORESET pool index of the CORESET in which the DCI was transmitted.

14. A base station for use in a wireless communication system, the base station comprising: one or more transceivers for transmitting and receiving radio signals; one or more processors for controlling the one or more transceivers; The one or more processors: Transmitting first configuration information including a list of transmission configuration indication (TCI) states to the terminal, where the list of TCI states provides a reference for determining a reference signal for quasi co-location (QCL) for a downlink channel and / or an uplink transmit spatial filter for an uplink channel; Transmit second configuration information related to a control resource set (CORESET) to the terminal, where a plurality of CORESETs having different CORESET pool indexes are configured according to the second configuration information; and transmitting downlink control information (DCI) to the terminal; A base station, based on the DCI indicating one TCI state in the list of TCI states, the indicated one TCI state is applied to uplink transmission and downlink transmission associated with a CORESET pool index of the CORESET in which the DCI was transmitted.

Images