Method and device for transmitting / receiving downlink channel from multiple transmission / reception points in wireless communication system

Abstract

A method and apparatus for transmitting or receiving a downlink channel from multiple transmitting and receiving points in a wireless communication system are disclosed. A method for a terminal to receive a downlink channel in a wireless communication system according to one embodiment of the present disclosure comprises: receiving a downlink control channel based on two or more transmission configuration indicator (TCI) states associated with one or more control resource sets (CORESET); and receiving a downlink data channel based on two or more TCI states associated with one or more CORESETs based on the fact that the downlink control information (DCI) received through the downlink control channel does not include TCI information, wherein the two or more TCI states may be mapped to the downlink data channel based on a predetermined mapping method.

Description

Technology Field

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for transmitting or receiving a downlink channel from multiple transmitting and receiving points in a wireless communication system. Background Technology

[0002] Mobile communication systems were developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded their scope to include data services as well as voice. Currently, due to the explosive increase in traffic leading to resource shortages and users demanding higher-speed services, more advanced mobile communication systems are required.

[0003] The requirements for next-generation mobile communication systems largely include the ability to accommodate explosive data traffic, a dramatic increase in transmission rates per user, a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To achieve this, various technologies are being researched, such as dual connectivity, massive multiple input multiple output (MMIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking. The problem to be solved

[0004] The technical problem of the present disclosure is to provide a method and apparatus for transmitting or receiving a downlink channel from multiple TRPs (MTRPs).

[0005] An additional technical objective of the present disclosure is to provide a method and apparatus for transmitting or receiving a downlink data channel based on a downlink control channel transmitted from MTRP.

[0006] An additional technical objective of the present disclosure is to provide a method and apparatus for transmitting or receiving a downlink data channel based on a transmission configuration indicator (TCI) based on a downlink control channel transmitted from the MTRP.

[0007] The technical problems to be solved in this disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this disclosure belongs from the description below. means of solving the problem

[0008] A method for a terminal to receive a downlink channel in a wireless communication system according to one aspect of the present disclosure comprises: receiving a downlink control channel based on two or more transmission configuration indicator (TCI) states associated with one or more control resource sets (CORESET); and receiving a downlink data channel based on two or more TCI states associated with one or more CORESETs based on the fact that the downlink control information (DCI) received through the downlink control channel does not include TCI information, wherein the two or more TCI states may be mapped to the downlink data channel based on a predetermined mapping method.

[0009] A terminal receiving a downlink channel in a wireless communication system according to an additional aspect of the present disclosure comprises: one or more transceivers; and one or more processors connected to the one or more transceivers, wherein the one or more processors are configured to receive a downlink control channel through the transceivers based on two or more transmission configuration indicator (TCI) states associated with one or more control resource sets (CORESET); and, based on the fact that the downlink control information (DCI) received through the downlink control channel does not include TCI information, the two or more TCI states associated with the one or more CORESETs are configured to receive a downlink data channel through the transceivers, and the two or more TCI states may be mapped to the downlink data channel based on a predetermined mapping method. Effects of the invention

[0010] According to an embodiment of the present disclosure, a method and apparatus for transmitting or receiving a downlink channel from multiple TRPs (MTRPs) may be provided.

[0011] According to an embodiment of the present disclosure, a method and apparatus for transmitting or receiving a downlink data channel based on a downlink control channel transmitted from MTRP may be provided.

[0012] According to an embodiment of the present disclosure, a method for transmitting or receiving a downlink data channel based on a transmission configuration indicator (TCI) based on a downlink control channel transmitted from MTRP may be provided.

[0013] According to an embodiment of the present disclosure, based on a downlink control channel transmitted from the MTRP, even if TCI information is not included in the downlink control information (DCI), the TCI associated with the downlink data channel can be clearly set or determined.

[0014] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below. Brief explanation of the drawing

[0015] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and explain the technical features of the present disclosure together with the detailed description. FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied. FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure may be applied. FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure may be applied. FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure may be applied. FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure may be applied. FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure may be applied, and a general method of transmitting and receiving signals using these channels. FIG. 7 illustrates a multiple TRP transmission method in a wireless communication system to which the present disclosure may be applied. FIG. 8 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure. FIG. 9 is a diagram illustrating a mapping method between a PDCCH transmission occasion and a TCI state according to one embodiment of the present disclosure. FIG. 10 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure. FIG. 11 is a drawing illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure. FIG. 12 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure. FIG. 13 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure. FIG. 14 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure. FIG. 15 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure. FIG. 16 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure. FIG. 17 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure. FIG. 18 is a flowchart illustrating a method for a terminal to receive a downlink channel according to the present disclosure. FIG. 19 is a diagram illustrating the signaling procedure of a network side and a terminal according to the present disclosure. FIG. 20 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure. Specific details for implementing the invention

[0016] Hereinafter, preferred embodiments according to 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 represent the only embodiment in which the present disclosure may be practiced. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the art will know that the present disclosure may be practiced without such specific details.

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

[0018] In the present disclosure, when a component is described as being “connected,” “combined,” or “joined” with another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, in the present disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, actions, elements, components, and / or groups thereof.

[0019] In the present disclosure, terms such as "first," "second," etc. are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor do they limit the order or importance of the components unless specifically stated otherwise. Accordingly, within the scope of the present disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and likewise, a second component in one embodiment may be referred to as a first component in another embodiment.

[0020] The terms used in this disclosure are for the description of specific embodiments and are not intended to limit the claims. As used in the description of embodiments and in the appended claims, the singular form is intended to include the plural form unless the context clearly indicates otherwise. The term "and / or" as used in this disclosure may refer to any one of the related enumerated items, or refers to and includes any and all possible combinations of two or more of them. Additionally, the " / " between words in this disclosure has the same meaning as "and / or" unless otherwise noted.

[0021] The present disclosure describes a wireless communication network or a wireless communication system, and operations performed in the wireless communication network may be performed in the process of controlling the network and transmitting or receiving signals by a device (e.g., a base station) governing the wireless communication network, or in the process of transmitting or receiving signals with or between the network and terminals by a terminal connected to the wireless network.

[0022] In the present disclosure, transmitting or receiving a channel includes the meaning of transmitting or receiving information or a signal through said channel. For example, transmitting a control channel means transmitting control information or a signal through the control channel. Similarly, transmitting a data channel means transmitting data information or a signal through the data channel.

[0023] In the following, the downlink (DL) refers to communication from a base station to a terminal, and the uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter may be part of the base station, and the receiver may be part of the terminal. In the uplink, the transmitter may be part of the terminal, and the receiver may be part of the base station. The base station may be referred to as the first communication device, and the terminal as the second communication device. The term base station (BS) may be replaced by terms such as 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 (roadside unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.In addition, the terminal may be fixed or mobile and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, RSU (road side unit), robot, AI (Artificial Intelligence) module, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device.

[0024] The following technologies can be used in various wireless access systems such as CDMA, FDMA, TDMA, OFDMA, and SC-FDMA. CDMA can be implemented using wireless technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented using wireless technologies such as GSM (Global System for Mobile Communications), GPRS (General Packet Radio Service), and EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented using wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is part of the UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) using 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.

[0025] For clarity of explanation, the description is based on 3GPP communication systems (e.g., LTE-A, NR), but the technical scope of this disclosure is not limited thereto. LTE refers to technology from 3GPP Technical Specification (TS) 36.xxx Release 8 onwards. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onwards is referred to as LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onwards is referred to as LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onwards. LTE / NR may be referred to as a 3GPP system. "xxx" indicates a specific standard document number. LTE / NR may be collectively referred to as a 3GPP system. Regarding background technology, terms, abbreviations, etc. used in the description of this disclosure, reference may be made to matters described in standard documents published prior to this disclosure. For example, the following documents may be referenced.

[0026] For 3GPP LTE, refer 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).

[0027] For 3GPP NR, you may refer 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 Specification).

[0028] Abbreviations of terms that may be used in this disclosure are defined as follows.

[0029] - BM: Beam management

[0030] - CQI: Channel quality indicator

[0031] - CRI: Channel State Information - Reference Signal Resource Indicator

[0032] - CSI: Channel state information

[0033] - CSI-IM: Channel state information - interference measurement

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

[0035] - DMRS: demodulation reference signal

[0036] - FDM: Frequency Division Multiplexing

[0037] - FFT: Fast Fourier Transform

[0038] - IFDMA: Interleaved frequency division multiple access

[0039] - IFFT: Inverse Fast Fourier Transform

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

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

[0042] - MAC: Medium Access Control

[0043] - NZP: Non-zero power

[0044] - OFDM: Orthogonal Frequency Division Multiplexing

[0045] - PDCCH: Physical downlink control channel

[0046] - PDSCH: Physical downlink shared channel

[0047] - PMI: Precoding Matrix Indicator

[0048] - RE: resource element

[0049] - RI: Rank indicator

[0050] - RRC: Radio Resource Control

[0051] - RSSI: Received signal strength indicator

[0052] - Rx: Reception

[0053] - QCL: quasi co-location

[0054] - SINR: Signal to interference and noise ratio

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

[0056] - TDM: Time Division Multiplexing

[0057] - TRP: transmission and reception point

[0058] - TRS: Tracking Reference Signal

[0059] - Tx: transmission

[0060] - UE: User equipment

[0061] - ZP: Zero Power

[0062] General System

[0063] As more communication devices require greater communication capacity, the need for enhanced mobile broadband communication compared to existing radio access technology (RAT) is emerging. Furthermore, 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 designs that take into account services and terminals sensitive to reliability and latency are being discussed. As such, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), and URLLC (Ultra-Reliable and Low Latency Communication) is being discussed, and for convenience, this technology is referred to as NR in this specification. NR is an expression representing an example of 5G RAT.

[0064] A new RAT system including NR uses an OFDM transmission method or a similar transmission method. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Or, a single cell may support multiple numerologies. That is, terminals operating with different numerologies can coexist within a single cell.

[0065] Numerology corresponds to a single subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing to an integer N.

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

[0067] Referring to FIG. 1, the NG-RAN consists of gNBs that provide NG-RA (NG-Radio Access) 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 endpoints for the UE. The gNBs are interconnected via Xn interfaces. The gNBs are also connected to the NGC (New Generation Core) via NG interfaces. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Function) via N2 interfaces and to the UPF (User Plane Function) via N3 interfaces.

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

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

[0070] Below, we examine the OFDM numerologies and frame structures that can be considered in NR systems. Many OFDM numerologies supported in NR systems can be defined as shown in Table 1 below.

[0071] μ Δf=2 μ ·15 [kHz] CP 0 15 Normal 1 30 common 2 60 General, Extended 3 120 common 4 240 common

[0072] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, if the SCS is 15 kHz, it supports a wide area in traditional cellular bands; if the SCS is 30 kHz / 60 kHz, it supports dense-urban environments, lower latency, and wider carrier bandwidth; and if the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise. NR frequency bands are defined by two types of frequency ranges (FR1 and FR2). FR1 and FR2 can be configured as shown in Table 2 below. Additionally, FR2 may refer to millimeter wave (mmW).

[0073] Frequency Range Designation Corresponding frequency range Subcarrier Spacing FR1 410MHz - 7125MHz 15, 30, 60kHz FR2 24250MHz - 52600MHz 60, 120, 240kHz

[0074] Regarding the frame structure in an NR system, the magnitude of various fields in the time domain is T c =1 / (Δf max ·N f It is expressed as a multiple of the time unit of ). Here, Δf max =480·10 3 Hz and N f = 4096. Downlink and uplink transmission is T f =1 / (Δf max N f / 100)·T c It is organized into radio frames having an interval of = 10ms. Here, each radio frame is T sf =(Δf max N f / 1000)·T c=1ms It consists of 10 subframes having the interval. In this case, there may be one set of frames for the uplink and one set of frames for the downlink. Additionally, the transmission at uplink frame number i from the terminal is T before the start of the corresponding downlink frame at the terminal. TA =(N TA +N TA,offset )T c Must start previously. For a subcarrier spacing configuration μ, the slots are n within the subframe. s μ ∈{0,..., N slot subframe,μ Numbered in increasing order of {-1}, and n within the wireless frame s,f μ ∈{0,..., N slot frame,μ Numbers are assigned in increasing order of {-1}. One slot is N symb slot It consists of consecutive OFDM symbols of, and N symb slot is determined by CP. Slot n in the subframe s μ The start is OFDM symbol n in the same subframe. s μ N symb slot It is aligned temporally with the start of. Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in the downlink slot or uplink slot can be utilized. Table 3 shows the number of OFDM symbols per slot (N) in a standard CP. symb slot ), number of slots per wireless frame (N slot frame,μ ), number of slots per subframe (N slot subframe,μTable 4 shows the number of OFDM symbols per slot, the number of slots per wireless frame, and the number of slots per subframe in the extended CP.

[0075] μ N symb slot N slot frame,μ N slot subframe,μ 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

[0076] μ N symb slot N slot frame,μ N slot subframe,μ 2 12 40 4

[0077] Figure 2 is an example of the case where μ=2 (SCS is 60kHz). Referring to Table 3, one subframe can contain four slots. The slots in Figure 2, 1 subframe={1,2,4}, are examples, and the number of slot(s) that can be included in one subframe is defined as in Table 3 or Table 4. Additionally, a mini-slot can contain 2, 4, or 7 symbols, or more or fewer symbols. Regarding physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc., may be considered. Below, the physical resources that can be considered in an NR system will be examined in detail.

[0078] First, regarding antenna ports, an antenna port is defined such that the channel carrying a symbol on the antenna port can be inferred from the channel carrying another symbol on the same antenna port. If the large-scale property of the channel carrying a symbol on one antenna port can be inferred from the channel carrying a symbol on another antenna port, the two antenna ports can be said to be in a QC / QCL (quasi-co-located or quasi-co-location) relationship. Here, the large-scale property includes 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 may be applied.

[0080] Referring to Fig. 3, the resource grid N in the frequency domain RB μ N sc RB It consists of subcarriers, and one subframe is 14.2 μ It is described by way of example as being composed of OFDM symbols, but is not limited thereto. In an NR system, the transmitted signal is N RB μ N sc RB One or more resource grids composed of subcarriers and 2 μ N symb (μ) It is described by the OFDM symbols of. Here, N RB μ ≤ N RB max,μ It is. The above N RB max,μrepresents the maximum transmission bandwidth, which can vary not only between numerologies but also between uplink and downlink. In this case, a single resource grid can be established for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is referred to as a resource element, and the index pair (k, It is uniquely identified by ). Here, k=0,...,N RB μ N sc RB -1 is an index in the frequency domain, and =0,...,2 μ N symb (μ) -1 refers to the location of a symbol within a subframe. When referring to resource elements in a slot, an index pair (k,l) is used. Here, l=0,...,N symb μ It is -1. Resource factor (k) for μ and antenna port p ) is a complex value It corresponds to. If there is no risk of confusion or if a specific antenna port or numerology is not specified, the indices p and μ may be dropped, and the resulting complex value is or This can be. In addition, the resource block (RB) is N in the frequency domain. sc RB =12 is defined by consecutive subcarriers.

[0081] Point A serves as a common reference point for the resource block grid and is acquired as follows.

[0082] - OffsetToPointA for the Primary Cell (PCell) downlink represents 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 a 15 kHz subcarrier interval for FR1 and a 60 kHz subcarrier interval for FR2.

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

[0084] Common resource blocks are numbered from 0 upward 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 in the frequency domain CRB μ The relationship between the resource element (k,l) and the subcarrier spacing setting μ is given as Equation 1 below.

[0085]

[0086] In Equation 1, k is defined relative to point A such that k=0 corresponds to a subcarrier centered at point A. Physical resource blocks range from 0 to N within the bandwidth part (BWP). BWP,i size,μ Numbers are assigned up to -1, and i is the BWP number. Physical resource block n in BWP i PRB and common resource block n CRB The relationship between them is given by the following mathematical formula 2.

[0087]

[0088] N BWP,i start,μ is a common resource block where 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 may be applied. FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure may be applied.

[0090] Referring to FIGS. 4 and 5, a slot contains multiple symbols in the time domain. For example, in the case of a standard CP, one slot contains 7 symbols, but in the case of an extended CP, one slot contains 6 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 can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication is performed through the active BWPs, and only one BWP can be active for a single terminal. In the resource grid, each element is referred to as a Resource Element (RE) and can be mapped to a single complex symbol.

[0092] NR systems can support up to 400 MHz per Component Carrier (CC). If a terminal operating in such a wideband CC always keeps its radio frequency (RF) chip turned on for the entire CC, the terminal's battery consumption may increase. Alternatively, considering various use cases operating within a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different numerologies (e.g., subcarrier spacing) may be supported for each frequency band within that CC. Or, the capability regarding maximum bandwidth may vary by terminal. Taking this into account, the base station may instruct the terminal to operate only on a portion of the bandwidth rather than the entire bandwidth of the wideband CC, and for convenience, this portion of bandwidth is defined as the bandwidth part (BWP). A BWP can consist of consecutive RBs on the frequency axis and can correspond to a single numerology (e.g., subcarrier spacing, CP length, slot / mini-slot interval).

[0093] Meanwhile, the base station may configure multiple BWPs within a single CC configured for a terminal. For example, a BWP occupying a relatively small frequency range may be configured in the PDCCH monitoring slot, and the PDSCH indicated by the PDCCH may be scheduled on a larger BWP. Alternatively, if UEs are concentrated on a specific BWP, some terminals may be configured to a different BWP for load balancing. Or, considering frequency domain inter-cell interference cancellation between neighboring cells, a portion of the spectrum in the middle of the total bandwidth may be excluded, and both BWPs may be configured within the same slot. That is, the base station may configure at least one DL / UL BWP for a terminal associated with a broadband CC. The base station may activate at least one DL / UL BWP among the DL / UL BWP(s) configured at a specific time (by L1 signaling, MAC CE (Control Element), or RRC signaling, etc.). Additionally, the base station may instruct a switch to another configured DL / UL BWP (by L1 signaling, MAC CE, RRC signaling, etc.). Alternatively, a switch to a defined DL / UL BWP may occur based on a timer when the timer value expires. In this case, the activated DL / UL BWP is defined as the active DL / UL BWP. However, since the terminal may not receive the configuration for the DL / UL BWP in situations such as when the terminal is performing the initial access process or before the RRC connection is set up, the DL / UL BWP assumed by the terminal in such situations is defined as the initial active DL / UL BWP.

[0094] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure may be applied, and a general method of transmitting and receiving signals using these channels.

[0095] In a wireless communication system, a terminal receives information from a base station via the downlink and transmits information to the base station via the uplink. The information transmitted and received by the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.

[0096] When the terminal is powered on or enters a new cell, it performs an initial cell search operation, 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). Subsequently, the terminal receives a Physical Broadcast Channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, during the initial cell search phase, the terminal receives a Downlink Reference Signal (DL RS) to check the downlink channel status.

[0097] A terminal that has completed initial cell search can obtain more specific system information by receiving a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH) according to the information carried on the PDCCH (S602).

[0098] Meanwhile, when a terminal first connects to a base station or when there are no wireless resources available for signal transmission, the terminal may perform a Random Access Procedure (RACH) with respect to the base station (steps S603 to S606). To do this, the terminal transmits a specific sequence as a preamble through a Physical Random Access Channel (PRACH) (S603 and S605), and may receive a response message for the preamble through a PDCCH and a corresponding PDSCH (S604 and S606). In the case of a contention-based RACH, a Contention Resolution Procedure may additionally be performed.

[0099] A terminal that has performed the procedure described above may subsequently 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 its format varies depending on its purpose of use.

[0100] Meanwhile, control information transmitted by the terminal to the base station via the uplink or received by the terminal from the base station includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In the case of a 3GPP LTE system, the terminal may transmit the aforementioned control information, such as CQI / PMI / RI, via PUSCH and / or PUCCH.

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

[0102] DCI format conjugation 0_0 Scheduling of PUSCH within a single cell 0_1 Scheduling of one or multiple PUSCHs within a single cell, or instruction to the UE regarding cell group (CG) downlink feedback information 0_2 Scheduling of PUSCH within a single cell 1_0 Scheduling of PDSCH within a single DL cell 1_1 Scheduling of PDSCH within a single cell 1_2 Scheduling of PDSCH within a single cell

[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.), 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.), multi-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 DCI format may be predefined. DCI format 0_0 is used for PUSCH scheduling in a single cell. The information contained in DCI format 0_0 is transmitted after being scrambled with a cyclic redundancy check (CRC) by a C-RNTI (Cell RNTI: Cell Radio Network Temporary Identifier), a CS-RNTI (Configured Scheduling RNTI), or a MCS-C-RNTI (Modulation Coding Scheme Cell RNTI).

[0104] DCI format 0_1 ​​is used to instruct a terminal on the scheduling of one or more PUSCHs in a cell, or configured grant (CG) downlink feedback information. The information contained in DCI format 0_1 ​​is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI.

[0105] DCI format 0_2 is used for scheduling PUSCH in a single cell. The information contained in DCI format 0_2 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0106] 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 DCI format may be predefined.

[0107] DCI format 1_0 is used for scheduling PDSCH in a single DL cell. The information contained in DCI format 1_0 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0108] DCI format 1_1 is used for PDSCH scheduling in a single cell. The information contained in DCI format 1_1 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0109] DCI format 1_2 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_2 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0110] Multi-TRP related operations

[0111] Coordinated Multi-Point (CoMP) is a method of effectively controlling interference by having multiple base stations exchange (e.g., RI / CQI / PMI / LI (layer indicator), etc.) channel information received as feedback from a terminal with one another (e.g., using an X2 interface) or utilize it to cooperatively transmit to the terminal. Depending on the method used, CoMP can be classified into Joint Transmission (JT), Coordinated Scheduling (CS), Coordinated Beamforming (CB), Dynamic Point Selection (DPS), and Dynamic Point Blocking (DPB).

[0112] The M-TRP transmission method, in which M TRPs transmit data to a single terminal, can be broadly classified into i) eMBB M-TRP transmission, which is a method to increase the transmission rate, and ii) URLLC M-TRP transmission, which is a method to increase the reception success rate and reduce latency.

[0113] In addition, from the perspective of DCI transmission, M-TRP transmission methods can be classified into i) M-DCI (multiple DCI) based M-TRP transmission, where each TRP transmits different DCIs, and ii) S-DCI (single DCI) based M-TRP transmission, where a single TRP transmits a DCI. For example, in the case of S-DCI based M-TRP transmission, since all scheduling information for the data transmitted by the M TRP must be delivered to the terminal through a single DCI, it can be used in an ideal backhaul (ideal BH) environment where dynamic cooperation between two TRPs is possible.

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

[0115] Additionally, the UE may recognize a PUSCH (or PUCCH) scheduled by the DCI received from a different control resource set (CORESET: control resource set) (or a CORESET belonging to a different CORESET group) as a PUSCH (or PUCCH) transmitted to a different TRP, or as a PDSCH (or PDCCH) of a different TRP. Furthermore, the method for UL transmissions transmitted to different TRPs (e.g., PUSCH / PUCCH) described below can be applied in the same way to UL transmissions transmitted to different panels belonging to the same TRP (e.g., PUSCH / PUCCH).

[0116] Below, we examine multi-DCI-based non-coherent joint transmissions (NCJT) and single-DCI-based NCJTs.

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

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

[0119] Multiple TRPs (MTRP) that perform NCJT transmission can perform DL data transmission to a terminal using either of the following two methods.

[0120] First, we examine the 'single DCI-based MTRP method.' In MTRP, a single common PDSCH is transmitted collaboratively, and each TRP participating in the collaborative transmission spatially divides the PDSCH into different layers (i.e., different DMRS ports) using the same time-frequency resources for transmission. At this time, scheduling information for the PDSCH is instructed to the UE via a single DCI, and this DCI indicates which DMRS (group) port utilizes which QCL RS and QCL type information (this differs from the existing method of instructing the QCL RS and type that applies commonly to all DMRS ports indicated in the DCI). That is, M TCI states are indicated through the TCI (Transmission Configuration Indicator) field within the DCI (for example, M=2 in the case of 2 TRP collaborative transmission), and QCL RS and types can be indicated using M different TCI states for each of the M DMRS port groups. Additionally, DMRS port information can be indicated using a new DMRS table.

[0121] Next, we examine the 'multiple DCI based MTRP method'. MTRP transmits different DCIs and PDSCHs, and these PDSCHs are transmitted overlapping (partially or entirely) on frequency-time resources. These PDSCHs are scrambled using different scrambling IDs (identifiers), and these DCIs can be transmitted through Coresets belonging to different Coreset groups. (Here, a Coreset group can be identified by an index defined within the Coreset settings of each Coreset. For example, if Coresets 1 and 2 are set to index = 0 and Coresets 3 and 4 are set to index = 1, then Coresets 1 and 2 belong to Coreset group 0, and Coresets 3 and 4 belong to Coreset group 0. Also, if no index is defined within a Coreset, it can be interpreted as index = 0.) If multiple scrambling IDs are set in a single serving cell or if two or more Coreset groups are set, the UE can recognize that it is receiving data through multiple DCI-based MTRP operations.

[0122] Alternatively, whether it is a single DCI-based MTRP method or a multiple DCI-based MTRP method can be indicated to the UE through separate signaling. For example, multiple CRS (cell reference signal) patterns may be indicated to the UE for MTRP operation for a single serving cell. In this case, the PDSCH rate matching for the CRS may differ depending on whether it is a single DCI-based MTRP method or a multiple DCI-based MTRP method (since the CRS patterns are different).

[0123] Hereinafter, the CORESET group ID described or mentioned in this specification may refer to an index / identification information (e.g., ID) for distinguishing CORESETs for each TRP / panel. Furthermore, a CORESET group may be a group / union of CORESETs distinguished by the index / identification information (e.g., ID) for distinguishing CORESETs for each TRP / panel, or by the said CORESET group ID. For example, the CORESET group ID may be specific index information defined within a CORESET configuration. In this case, the CORESET group may be set / indicated / defined by an index defined within the CORESET configuration for each CORESET. And / or, the CORESET group ID may refer to an index / identification information / indicator, etc. for distinguishing / identifying CORESETs set / associated with each TRP / panel. Hereinafter, the CORESET group ID described or mentioned in this disclosure may be replaced and expressed with a specific index, specific identification information, or specific indicator for distinguishing or identifying between CORESETs set or associated with each TRP / panel. The said CORESET group ID, that is, the specific index, specific identification information, or specific indicator for distinguishing or identifying between CORESETs set or associated with each TRP / panel, may be set or instructed to the terminal through higher layer signaling (e.g., RRC signaling), L2 signaling (e.g., MAC-CE), L1 signaling (e.g., DCI), etc. For example, PDCCH detection may be set or instructed to be performed for each TRP / panel (i.e., for each TRP / panel belonging to the same CORESET group) on a CORESET group basis.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) within the corresponding CORESET group. 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) within the corresponding CORESET group may be managed.

[0124] Below, we examine partially overlapping NCJPs.

[0125] In addition, NCJTs can be classified into fully overlapped NCJTs, where the time-frequency resources transmitted by each TP completely overlap, and partially overlapped NCJTs, where only some time-frequency resources overlap. That is, in the case of a partially overlapped NCJT, data from both TP 1 and TP 2 is transmitted in some time-frequency resources, while data from only one of the TPs, either TP 1 or TP 2, is transmitted in the remaining time-frequency resources.

[0126] Below, we examine methods for improving reliability in Multi-TRP.

[0127] The following two methods can be considered as transmission and reception methods to improve reliability using transmission in multiple TRPs.

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

[0129] 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 may refer to a set of layers consisting of one or more layers. In this case, the amount of transmission resources increases due to the number of layers, which has the advantage of allowing robust channel coding with a low code rate for the TB. Additionally, since the channels differ from the multiple TRPs, the reliability of the received signal can be expected to improve based on diversity gain.

[0130] Referring to Fig. 7(b), an example is shown of transmitting different CWs through 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 identical. That is, CW #1 and CW #2 each represent the same TB that has been converted into different CWs through channel coding, etc., by different TRPs. Therefore, this can be viewed as an example of repeated transmission of the same TB. In the case of Fig. 7(b), compared to Fig. 7(a) mentioned earlier, there may be a disadvantage in that the code rate corresponding to the TB is high. However, it has the advantage of being able to adjust the code rate by indicating different RV (redundancy version) values ​​for the encoded bits generated from the same TB depending on the channel environment, or to adjust the modulation order of each CW.

[0131] According to the method exemplified in FIGS. 7(a) and 7(b) above, the same TB is repeatedly transmitted through different layer groups, and as each layer group is transmitted by different TRPs / panels, the probability of data reception by the terminal can be increased. This is referred to as the SDM (Spatial Division Multiplexing) based M-TRP URLLC transmission method. Layers belonging to different layer groups are each transmitted through DMRS ports belonging to different DMRS CDM groups.

[0132] In addition, although the above description regarding multiple TRPs was explained based on the spatial division multiplexing (SDM) method using different layers, it goes without saying that this can be extended and applied to the frequency division multiplexing (FDM) method based on different frequency domain resources (e.g., RB / PRB (set), etc.) and / or the time division multiplexing (TDM) method based on different time domain resources (e.g., slot, symbol, sub-symbol, etc.).

[0133] Regarding techniques for multi-TRP-based URLLCs scheduled by a single DCI, the following techniques are being discussed.

[0134] 1) Technique 1 (SDM): Time and frequency resource allocations overlap, and n (n<=Ns) TCI states within a single slot

[0135] 1-a) Technique 1a

[0136] - At each transmission occasion, the same TB is transmitted from one layer or set of layers, and each layer or set of layers is associated with one set of TCI and one DMRS port(s).

[0137] - A single codeword with a single RV is used in all spatial layers or a set of all layers. From the UE perspective, different coded bits are mapped to different layers or a set of layers using the same mapping rules.

[0138] 1-b) Technique 1b

[0139] - At each transmission occasion, the same TB is transmitted from one layer or set of layers, and each layer or set of layers is associated with one set of TCI and one set of DMRS ports.

[0140] - A single codeword with a single RV is used in each spatial layer or in the set of each layer. The RV(s) corresponding to each spatial layer or the set of each layer may be the same or different.

[0141] 1-c) Technique 1c

[0142] - At one transmission occasion, the same TB having one DMRS port associated with multiple TCI state indices is transmitted in one layer, or the same TB having multiple DMRS ports associated one-to-one with multiple TCI state indices is transmitted in one layer.

[0143] In the case of the aforementioned techniques 1a and 1c, the same MCS is applied to all layers or all sets of layers.

[0144] 2) Technique 2 (FDM): Frequency resource allocations do not overlap, and there are n (n<=Nf) TCI states within a single slot.

[0145] - Each non-overlapping frequency resource allocation is associated with one TCI state.

[0146] - The same single / multiple DMRS port(s) are associated with all non-overlapping frequency resource allocations.

[0147] 2-a) Technique 2a

[0148] - A single codeword with a single RV is used for all resource allocations. From the UE's perspective, common RB matching (mapping of codewords to layers) is applied in all resource allocations.

[0149] 2-b) Technique 2b

[0151] A single codeword with a single RV is used for each non-overlapping frequency resource allocation. The RVs corresponding to each non-overlapping frequency resource allocation may be the same or different.

[0152] For the aforementioned technique 2a, the same MCS is applied to all non-overlapping frequency resource allocations.

[0153] 3) Technique 3 (TDM): Time resource allocations do not overlap, and n (n<=Nt1) TCI states within a single slot

[0154] - Each transmission occasion of TB has mini-slot time granularity and has one TCI and one RV.

[0155] - A common MCS is used with a single or multiple DMRS port(s) at every transmission occasion within the slot.

[0157] The RV / TCI may be the same or different at different transmission occasions.

[0158] 4) Technique 4 (TDM): n (n<=Nt2) TCI states in K (n<=K) different slots

[0159] - Each transmission occasion of TB has one TCI and one RV.

[0160] - All transmission occasions across K slots use a common MCS with a single or multiple DMRS port(s).

[0161] - RV / TCI can be the same or different at different transmission occasions.

[0162] Below, we will examine MTRP URLLC.

[0163] In the present disclosure, DL MTRP-URLLC means that multiple TRPs transmit the same data (e.g., the same TB) / DCI using different layer / time / frequency resources. For example, TRP 1 transmits the same data / DCI from resource 1, and TRP 2 transmits the same data / DCI from resource 2. A UE configured with the DL MTRP-URLLC transmission method receives the same data / DCI using different layer / time / frequency resources. At this time, the UE is configured by the base station to use which QCL RS / type (i.e., DL TCI state) in the layer / time / frequency resource receiving the same data / DCI. For example, if the same data / DCI is received from resource 1 and resource 2, the DL TCI state used in resource 1 and the DL TCI state used in resource 2 may be configured. Since the UE receives the same data / DCI through Resource 1 and Resource 2, high reliability can be achieved. This DL MTRP URLLC can be applied to PDSCH / PDCCH.

[0164] In addition, in the present disclosure, UL MTRP-URLLC means that multiple TRPs receive the same data / UCI (uplink control information) from a single UE using different layer / time / frequency resources. For example, TRP 1 receives the same data / UCI from the UE at resource 1, and TRP 2 receives the same data / UCI from the UE at resource 2, and then the received data / UCI is shared through a connected backhaul link between the TRPs. A UE configured with the UL MTRP-URLLC transmission method transmits the same data / UCI using different layer / time / frequency resources. At this time, the UE is configured by the base station to use which Tx beam and which Tx power (i.e., UL TCI state) in the layer / time / frequency resource transmitting the same data / UCI. For example, if the same data / UCI is transmitted from resource 1 and resource 2, the UL TCI state used by resource 1 and the UL TCI state used by resource 2 may be set. These UL MTRP URLLCs can be applied to PUSCH / PUCCH.

[0165] Additionally, in the present disclosure, the meaning of using (or mapping) a specific TCI state (or TCI) when receiving data / DCI / UCI for a certain frequency / time / space resource (layer) is as follows. In the case of DL, it may mean estimating a channel from DMRS using the QCL type and QCL RS indicated by the corresponding TCI state in that frequency / time / space resource (layer), and receiving / demodulating data / DCI based on the estimated channel. Additionally, in the case of UL, it may mean transmitting / modulating DMRS and data / UCI using the Tx beam and / or power indicated by the corresponding TCI state in that frequency / time / space resource.

[0166] Here, the UL TCI state contains the UE's Tx beam and / or Tx power information, and instead of the TCI state, spatial relation info, etc., may be set for the UE through other parameters. The UL TCI state may be directly indicated by the UL grant DCI, or it may refer to the spatial relation info of the SRS resource indicated through the sounding resource indicator (SRI) field of the UL grant DCI. Alternatively, it may refer to the open loop (OL) transmission power control parameter (OL Tx power control parameter) connected to the value indicated through the SRI field of the UL grant DCI (e.g., j: index for open loop parameters Po and alpha (maximum 32 parameter value sets per cell), q_d: index of the DL RS resource for path loss (PL) measurements (maximum 4 measurements per cell), l: index for closed loop power control process (maximum 2 processes per cell)).

[0167] Below, we will examine MTRP eMBB.

[0168] In the present disclosure, MTRP-eMBB means that multiple TRPs transmit different data (e.g., different TB) using different layer / time / frequency. A UE configured with the MTRP-eMBB transmission method is instructed to have multiple TCI states via DCI, and it is assumed that the data received using the QCL RS of each TCI state is different data.

[0169] Meanwhile, the UE can determine whether it is an MTRP URLLC transmission / reception or an MTRP eMBB transmission / reception by using separate RNTIs for MTRP-URLLC and MTRP-eMBB. That is, if the DCI is CRC masked using the URLLC RNTI, the UE considers it a URLLC transmission, and if the DCI is CRC masked using the eMBB RNTI, the UE considers it an eMBB transmission. Alternatively, the base station may set the UE to receive an MTRP URLLC transmission / reception or an MTRP eMBB transmission / reception through other new signaling.

[0170] In the description of the present disclosure, cooperative transmission / reception between 2 TRPs is assumed for convenience of explanation; however, the method proposed in the present disclosure can be extended to environments with three or more TRPs, and can also be extended to environments with multiple panels (i.e., by mapping TRPs to panels). Furthermore, different TRPs may be recognized as different TCI states by the UE. Therefore, when a UE receives / transmits data / DCI / UCI using TCI state 1, it means that it has received / transmitted data / DCI / UCI from / to TRP 1.

[0171] The methods proposed in the present disclosure may be utilized in situations where the MTRP cooperatively transmits PDCCH (transmitting the same PDCCH repeatedly or splitting it for transmission). Additionally, the methods proposed in the present disclosure may also be utilized in situations where the MTRP cooperatively transmits PDSCH or cooperatively receives PUSCH / PUCCH.

[0172] In addition, in the present disclosure, the meaning that multiple base stations (i.e., MTRP) repeatedly transmit the same PDCCH may mean that the same DCI was transmitted through multiple PDCCH candidates, or that multiple base stations repeatedly transmit the same DCI. Here, the term "same DCI" may refer to two DCIs that have the same DCI format, size, and payload. Alternatively, even if the payloads of the two DCIs are different, they may be considered the same DCI if the scheduling results are identical. For example, since the time domain resource allocation (TDRA) field of a DCI determines the relative positions of the data slot / symbol and the A / N (ACK / NACK) slot / symbol based on the time of reception of the DCI, if the DCI received at time n and the DCI received at time n+1 provide the same scheduling result to the UE, the TDRA fields of the two DCIs will differ, and consequently, the DCI payloads will inevitably differ. The number of repetitions R may be directly instructed by the base station to the UE or mutually agreed upon. Alternatively, even if the payloads of two DCIs are different and their scheduling results are not identical, they can be considered the same DCI if the scheduling result of one DCI is a subset of the scheduling result of another DCI. For example, if the same data is TDMed and transmitted N times, DCI 1, received before the first data, indicates N repetitions of the data, and DCI 2, received after the first data and before the second data, indicates N-1 repetitions of the data. The scheduling data of DCI 2 becomes a subset of the scheduling data of DCI 1, and since both DCIs are scheduling for the same data, this case can also be considered the same DCI.

[0173] In addition, in the present disclosure, the statement that multiple base stations (i.e., MTRPs) share and transmit the same PDCCH means that one DCI is transmitted through one PDCCH candidate, wherein TRP 1 transmits some of the resources defined by the PDCCH candidate and TRP 2 transmits the remaining resources. A single PDCCH candidate that is shared and transmitted by multiple base stations (i.e., MTRPs) may be indicated to a terminal (UE) or recognized or determined by the terminal through a configuration described below.

[0174] Additionally, in the present disclosure, the meaning that a UE repeatedly transmits the same PUSCH for reception by multiple base stations (i.e., MTRP) may mean that the UE has transmitted the same data through multiple PUSCHs. In this case, each PUSCH may be transmitted optimized for the UL channels of different TRPs. For example, when a UE repeatedly transmits the same data through PUSCH 1 and 2, PUSCH 1 is transmitted using UL TCI state 1 for TRP 1, and link adaptations such as a precoder / MCS may also be scheduled / applied with values ​​optimized for the channel of TRP 1. PUSCH 2 is transmitted using UL TCI state 2 for TRP 2, and link adaptations such as a precoder / MCS may also be scheduled / applied with values ​​optimized for the channel of TRP 2. In this case, the repeatedly transmitted PUSCH 1 and 2 may be transmitted at different times and thus TDM, FDM, or SDM.

[0175] In addition, in the present disclosure, the meaning of a UE dividing and transmitting the same PUSCH so that it is received by multiple base stations (i.e., MTRPs) may mean that the UE transmits one data through a single PUSCH, but divides the resources allocated to that PUSCH to optimize transmission to the UL channels of different TRPs. For example, when a UE transmits the same data through a 10-symbol PUSCH, the data is transmitted using UL TCI state 1 for TRP 1 in the first 5 symbols, and at this time, link adaptation values ​​such as precoder / MCS may also be scheduled / applied to the channel of TRP 1. In the remaining 5 symbols, the remaining data is transmitted using UL TCI state 2 for TRP 2, and at this time, link adaptation values ​​such as precoder / MCS may also be scheduled / applied to the channel of TRP 2. In the above example, a single PUSCH was divided into time resources to perform TDM transmission to TRP 1 and transmission to TRP 2, but other methods may be used for transmission in FDM / SDM manner.

[0176] In addition, similar to the PUSCH transmission described earlier, PUCCH can also be transmitted repeatedly or divided and transmitted so that the UE can receive the same PUCCH at multiple base stations (i.e., MTRP).

[0177] The proposal of the present disclosure can be extended and applied to various channels such as PUSCH / PUCCH / PDSCH / PDCCH.

[0178] MTRP (Multi-TRP)-URLLC is a technique in which the same data is transmitted by multiple TRPs (MTRP: Multiple TRP) using different layer / time / frequency resources. Here, the data transmitted from each TRP is transmitted using a different TCI state for each TRP.

[0179] If this is extended to a method where the MTRP transmits the same DCI using different PDCCH candidates, the PDCCH candidates from each TRP to which the same DCI is transmitted may be transmitted using different TCI states. Here, specific definitions regarding the CORESET and the method of setting the search space (SS) set for each PDCCH candidate are required.

[0180] Example 1)

[0181] In Example 1, a method is described in which multiple base stations (i.e., MTRP) repeatedly transmit PDCCH.

[0182] In Example 1, a method is described in which multiple base stations (i.e., MTRP) repeatedly transmit PDCCH.

[0183] When multiple base stations (i.e., MTRP) repeatedly transmit a PDCCH, the number of repeated transmissions R can be directly instructed by the base station to the UE, or mutually agreed upon. Here, if the number of repeated transmissions R is mutually agreed upon, the number of repeated transmissions R can be determined based on the number of TCI (Transmission Configuration Indication) states set for repeatedly transmitting the same PDCCH. For example, if the base station has set r TCI states to repeatedly transmit the same PDCCH to the UE, it can be agreed that R=r. Here, for example, R is set as M*r, and the base station can instruct M to the UE.

[0184] When multiple base stations (i.e., MTRPs) repeatedly transmit the same PDCCH, TRP 1 transmits the DCI through PDCCH candidate 1, and TRP 2 transmits the same DCI through PDCCH candidate 2. The mapping order between TRPs and PDCCH candidates is for convenience of explanation only and does not limit the technical scope of the present disclosure. Since each PDCCH candidate is transmitted by a different TRP, each PDCCH candidate is received using a different TCI state. Here, PDCCH candidates transmitting the same DCI may differ in some or all of the scrambling / aggregation level, CORESET, and Search space (SS) set of the PDCCH.

[0185] Two (or more than two) PDCCH candidates that are repeatedly transmitted by multiple base stations (i.e., MTRP) can be recognized / instructed to the UE through the following configuration.

[0186] For the convenience of explanation below, the case where the same DCI is transmitted / received through two PDCCH candidates has been described as an example, but the proposal of the present disclosure can be extended to cases where the same DCI is transmitted / received through three or more PDCCH candidates. In this case, reliability can be further increased. For example, TRP 1 may transmit the same DCI through PDCCH candidates 1 and 2, and TRP 2 may transmit the same DCI through PDCCH candidates 3 and 4.

[0187] Additionally, for SS set(s) in which multiple base stations (i.e., MTRP) repeatedly transmit the same PDCCH, the same PDCCH may be repeatedly transmitted only for some DCI formats / SS / RNTI types defined in the SS set, and not for others, and the base station may instruct the UE to do so. For example, for an SS set in which both DCI format 1-0 and 1-1 are defined, the base station may instruct the UE to repeat only for format 1-0 (or 1-1). Or, the base station may instruct the UE to repeat only for the common SS (or UE-specific SS) among the UE-specific SS and common SS. Or, the base station may instruct the UE to repeat only for DCIs CRC-masked with specific RNTIs (e.g., RNTIs excluding C-RNTI, MCS-C-RNTI, CS-RNTI).

[0188] Example 1-1) Two PDCCH candidates transmitting the same DCI may share one (same) CORESET but be defined / configured in different SS sets.

[0189] FIG. 8 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure.

[0190] Referring to FIG. 8, PDCCH candidate 1 can be transmitted using TCI state 1, and PDCCH candidate 2 can be transmitted using TCI state 2. Additionally, the same DCI can be transmitted through PDCCH candidate 1 and PDCCH candidate 2, respectively. Furthermore, both PDCCH candidate 1 and PDCCH candidate 2 can be transmitted (repeatedly) at specific intervals (P) in the time domain.

[0191] Each PDCCH candidate can be defined / configured in different SS sets while sharing the same CORESET. Also, among the two TCI states configured in the same CORESET, TCI state 1 can be used in SS Set 1 where PDCCH candidate 1 exists, and TCI state 2 can be used in SS Set 2 where PDCCH candidate 2 exists.

[0192] In current standards, a CORESET ID is set within an SS set, and the SS set is linked to the CORESET. According to an embodiment of the present disclosure, a single CORESET may be linked (mapped) to a plurality of TCI states (e.g., two TCI states). In this case, within the configuration for the SS set, not only the CORESET ID but also information regarding which of the two TCIs of the CORESET should be used to decode the PDCCH may be defined / set.

[0193] Additionally, the base station may inform the UE of when the PDCCH candidate of SS set 1 and the PDCCH candidate of SS set 2 corresponding to the same DCI are transmitted or received (TO: Transmission occasion). This can be defined or referred to as the window in which the same DCI is transmitted. For example, the base station may indicate to the UE that SS set 1 and SS set 2 defined in the same single slot (i.e., window = 1 slot) are SS sets in which the same DCI is transmitted, or this may be mutually agreed upon between the base station and the UE.

[0194] More generally, the window (e.g., 1 slot) in which the same DCI is transmitted may be instructed to the UE by the base station, or may be mutually agreed upon between the base station and the UE.

[0195] For example, this window (e.g., time n) may be mutually agreed upon between the base station and the UE, or set by the base station to the UE, to start at every TO (time when a PDCCH candidate is transmitted) of a reference set (e.g., the lowest ID (Identifier) ​​SS set) among the SS sets defined to transmit the same DCI. Here, since windows may overlap if the TO of the lowest ID SS set appears multiple times within a single window, to prevent this, the next (n+1) window may be defined / set based on the TO of the lowest ID SS set that is not included within a specific (n) window. Additionally, preferably, N windows may be defined for each period of a reference set (e.g., lowest ID SS set). Here, N can be instructed by the base station to the UE. For example, if the period is 10 slots, and SS sets are defined in the 1st, 2nd, and 3rd slots out of the 10 slots, and the window is 1 slot and N=2, then windows may be defined in the 1st and 2nd slots, respectively, during each period of the lowest ID SS set.

[0196] Below, the PDCCH TO and TCI mapping method within a single window is described.

[0197] FIG. 9 is a diagram illustrating a mapping method between a PDCCH transmission occasion and a TCI state according to one embodiment of the present disclosure.

[0198] Multiple PDCCH TOs exist within a single window, and different TCI states can be mapped to each TO. Here, the following two methods can be considered for mapping TOs to TCIs.

[0199] First, as the number of TOs within the window increases (in ascending order), the TCI states can be mapped sequentially in a circular manner. For example, if N TOs and M TCI states are indicated within the window, the i-th TO is mapped to the i-th TCI, and if N > M, for the M+1 and M+2th TOs, respectively, the first (1 st ) TCI, second(2 nd TCIs can be mapped sequentially. For example, as shown in FIG. 9(a), assume a case where six PDCCH TOs are set within one window and two TCI states are set. In this case, within one window, the first PDCCH TO is mapped to the first TCI state, the second PDCCH TO is mapped to the second TCI state, the third PDCCH TO is mapped to the first TCI state, the fourth PDCCH TO is mapped to the second TCI state, the fifth PDCCH TO is mapped to the first TCI state, and the sixth PDCCH TO is mapped to the second TCI state.

[0200] Alternatively, secondly, by grouping adjacent floor(N / M) (floor(x) is the largest integer not greater than x) or ceil(N / M) (ceil(x) is the smallest integer not less than x) TOs within the window, the group and the TCI state can be mapped sequentially in a circular manner. That is, group i can be mapped to CORESET i. As a result, adjacent TOs included in the same group can be mapped to the same TCI. For example, as shown in FIG. 9(b), assume a case where 6 PDCCH TOs are set and 2 TCI states are set within a single window. Then, assume that the 1st to 3rd PDCCH TOs are grouped into the 1st group, and the 4th to 6th PDCCH TOs are grouped into the 2nd group. In this case, within a single window, the first to third PDCCH TOs (i.e., the first group) may be mapped to the first TCI state, and the fourth to sixth PDCCH TOs (i.e., the second group) may be mapped to the second TCI state.

[0201] This mapping method between TO and TCI can be applied to the mapping between TO and TCI within the same window not only in the case of Example 1-1 described above, but also in general cases where PDCCH is transmitted repeatedly at different times (e.g., Example 1-3) or divided and transmitted at different times. In other words, the mapping method between the same TO and TCI described above can be applied to all cases where different PDCCH candidates (to which different TCI states are applied) are transmitted from different TOs within the same window.

[0202] The previously described Example 1-1 can be configured as a special case of Example 1-3 described below. That is, in the method of configuring CORESET 1 and 2 and SS set 1 and 2 as in Example 1-3, if CORESET 1 and 2 are configured identically (provided that the TCI state and CORESET ID defined in the CORESET are different), it is no different from Example 1-1, where one CORESET, two SS sets, and two TCIs are configured. Therefore, in the case where CORESET 1 and 2 are configured identically in Example 1-3, the same PDCCH can be repeatedly transmitted in the same manner as in Example 1-1.

[0203] Example 1-2) Two PDCCH candidates transmitting the same DCI can be defined / configured in one (same) CORESET and one (same) SS set.

[0204] FIG. 10 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure.

[0205] Referring to FIG. 10, PDCCH candidate 1 can be transmitted using TCI state 1, and PDCCH candidate 2 can be transmitted using TCI state 2. Additionally, the same DCI can be transmitted through PDCCH candidate 1 and PDCCH candidate 2, respectively. Furthermore, both PDCCH candidate 1 and PDCCH candidate 2 can be transmitted (repeatedly) at specific intervals (P) in the time domain.

[0206] Referring to Fig. 10, each PDCCH candidate may share the same CORESET and SS set, and PDCCH candidates 1 and 2 may be FDMed. Both PDCCH candidates 1 and 2 may be defined / configured within a single SS set and a single CORESET mapped to that SS set. In this case, one of the two TCI states defined / configured within the CORESET may be used for some PDCCH candidates and the remaining TCI state may be used for the remaining PDCCH candidates. Regarding this, the previously mentioned PDCCH candidate to TCI mapping method may be referenced.

[0207] For example, if there are 4 PDCCH candidates with aggregation level = 4, the TCI states can be mapped alternately, such that the 1st and 3rd candidates are mapped to TCI state 1 and the 2nd and 4th candidates are mapped to TCI state 2. Here, PDCCH candidate 1 exists among the 1st and 3rd candidates, and PDCCH candidate 2 exists among the 2nd and 4th candidates. Alternatively, the candidates in the first half and the candidates in the second half can be mapped to different TCI states, such that the 1st and 2nd candidates are mapped to TCI state 1 and the 3rd and 4th candidates are mapped to TCI state 2. Here, PDCCH candidate 1 exists among the 1st and 2nd candidates, and PDCCH candidate 2 exists among the 3rd and 4th candidates.

[0208] Extending the above example, for N TCI states, N TCI states can be mapped one by one in a circular manner as the candidate index increases. Alternatively, the entire pool of candidates can be divided into N equal groups of adjacent candidates (adjacent candidate indices), and N candidate groups and N TCI states can be mapped 1:1.

[0209] In addition, in this method, the window in which the same PDCCH is repeatedly transmitted can be determined for every transmission occasion (TO) in which the PDCCH is transmitted or received. That is, for every PDCCH TO appearing in slots n, n+P, n+2P, etc., PDCCH candidate 1 and 2 can be FDMed and repeatedly transmitted. Figure 10 illustrates a case where the SS set period is set to P slot, and one SS set is set during one SS set period. Additionally, SS sets can be set in multiple (consecutive) slots within one SS set period, or multiple SS sets can be set in a single slot.

[0210] For example, an SS set can be configured for N (consecutive) slots during each period through a duration field (=N) defined within the SS set. The base station and the UE can agree on these N slots configured in this way as a single window. In this case, a TCI state can be mapped to each PDCCH TO through the 'PDCCH TO and TCI mapping method within the window' described earlier. For example, when N=2, the SS set can be configured in the form shown in Fig. 9 above.

[0211] As another example, multiple SS sets can be configured within a single slot through a higher-level field defined within the SS set configuration (e.g., the monitoringSymbolsWithinSlot field). For instance, an SS set is defined / configured with a P slot cycle, and L SS sets may exist at different times within the slot where the SS set is configured. In this case, the base station and the UE agree on a window of 1 slot, and a TCI state can be mapped to each PDCCH TO through the previously described "PDCCH TO and TCI mapping method within the window."

[0212] In addition, the previously described Example 1-2 can be configured as a special case of Example 1-3 described below. That is, in the method of configuring CORESET 1 and 2 and SS set 1 and 2 as in Example 1-3, if CORESET 1 and 2 are configured identically (provided that the TCI state defined in CORESET is different) and SS set 1 and 2 are configured identically, it is no different from Example 1-2, where one CORESET, one SS set, and two TCI states are configured. Therefore, in this case, the same PDCCH can be repeatedly transmitted in the same manner as in Example 1-2.

[0213] In addition, similar to the above, Example 1-2 can be set as a special case of Example 1-4. That is, regarding the method of setting CORESET 1, 2 and SS set 1 as in Example 1-4, if CORESET 1 and 2 are set identically (provided that the TCI state defined in CORESET is different), it is no different from Example 1-2.

[0214] In addition, Example 1-2 can be configured as a special case of Example 1-1. That is, in the method of configuring CORESET 1 and SS sets 1 and 2 as in Example 1-1, if SS sets 1 and 2 are configured identically (provided that the TCI state and CORESET ID of the CORESET used in each SS are different), it is no different from Example 1-2, where one CORESET, one SS set, and two TCIs are configured. Therefore, in this case, the same PDCCH can be repeatedly transmitted in the same manner as in Example 1-2.

[0215] Example 1-3) Two PDCCH candidates transmitting the same DCI may be defined / configured in different CORESETs and may be defined / configured in different SS sets.

[0216] FIG. 11 is a drawing illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure.

[0217] Referring to FIG. 11, PDCCH candidate 1 can be transmitted using TCI state 1, and PDCCH candidate 2 can be transmitted using TCI state 2. Additionally, the same DCI can be transmitted through PDCCH candidate 1 and PDCCH candidate 2, respectively. Furthermore, both PDCCH candidate 1 and PDCCH candidate 2 can be transmitted (repeatedly) at specific intervals (P) in the time domain.

[0218] Referring to FIG. 11, CORESET 1 is mapped to SS set 1, CORESET 2 is mapped to SS set 2, PDCCH candidate 1 is transmitted through CORESET 1 and SS set 1, and PDCCH candidate 2 is transmitted through CORESET 2 and SS set 2. For this configuration, the base station must inform the UE that the corresponding CORESET group or SS set group is configured for transmitting the same DCI. For example, the ID of SS set 2 (and / or 1) used for transmitting the same DCI may be additionally configured within SS set 1 (and / or 2). Alternatively, the base station may indicate to the UE that multiple SS sets belong to the same group, and the UE may recognize / assume that the SS sets belonging to the same group are configured for transmitting the same DCI.

[0219] Since the window setting method in which the same DCI is transmitted is the same as the setting method of Example 1-1 described above, the setting method of Example 1-1 can be used as is.

[0220] Example 1-4) Two PDCCH candidates transmitting the same DCI may be defined / configured in different CORESETs, but may be defined / configured in one (same) SS set.

[0221] FIG. 12 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure.

[0222] Referring to FIG. 12, PDCCH candidate 1 can be transmitted using TCI state 1, and PDCCH candidate 2 can be transmitted using TCI state 2. Additionally, the same DCI can be transmitted through PDCCH candidate 1 and PDCCH candidate 2, respectively. Furthermore, both PDCCH candidate 1 and PDCCH candidate 2 can be transmitted (repeatedly) at specific intervals (P) in the time domain.

[0223] Referring to Fig. 12, two CORESETs with different resource block (RB) resources are mapped to one SS set, and candidate 1 and 2 can be defined in CORESET 1 and CORESET 2, respectively.

[0224] In addition, in this method, the window in which the same PDCCH is repeatedly transmitted is determined by each TO (transmission occasion) in which the PDCCH is transmitted / received. That is, for every PDCCH TO appearing in slot n, n+P, n+2P, etc., PDCCH candidate 1 and 2 can be FDMed and repeatedly transmitted.

[0225] FIG. 12 illustrates a case where the SS set cycle is set to P slot and one SS set is set during one cycle. Additionally, SS sets may be set in multiple (consecutive) slots within one SS set cycle, or multiple SS sets may be set in a single slot.

[0226] For example, an SS set can be configured for N (consecutive) slots during each period through a duration field (=N) defined within the SS set. The base station and the UE can agree to designate these N configured slots as a single window.

[0227] The mapping method between PDCCH TO and CORESET within the window is described below.

[0228] Multiple PDCCH TOs can exist within a single window, and a different CORESET can be mapped to each PDCCH TO. The following two methods can be considered for the mapping between PDCCH TO and CORESET.

[0229] First, as the number of TOs within the window increases, CORESETs can be mapped sequentially in a circular manner. For example, if N TOs within the window and M CORESETs defined in their SS set are indicated, the i-th TO is mapped to the i-th CORESET, and if N > M, for the M+1 and M+2th TOs, respectively, the first (1 st ) CORESET, second(2 nd ) CORESETs can be mapped sequentially in a circular manner. For example, as shown in FIG. 9(a), assume a case where six PDCCH TOs are set and two CORESETs are set within one window. In this case, within one window, the first PDCCH TO is mapped to the first CORESET, the second PDCCH TO is mapped to the second CORESET, the third PDCCH TO is mapped to the first CORESET, the fourth PDCCH TO is mapped to the second CORESET, the fifth PDCCH TO is mapped to the first CORESET, and the sixth PDCCH TO is mapped to the second CORESET.

[0230] Alternatively, secondly, by grouping adjacent floor (N / M) or ceil (N / M) TOs within a window, the group and CORESET can be mapped sequentially in a circular manner. That is, group i can be mapped to CORESET i. As a result, adjacent TOs included in the same group can be mapped to the same CORESET. For example, as shown in FIG. 9(b), assume a case where 6 PDCCH TOs are set and 2 CORESETs are set within a single window. Then, assume that the 1st to 3rd PDCCH TOs are grouped into the 1st group, and the 4th to 6th PDCCH TOs are grouped into the 2nd group. In this case, within a single window, the 1st to 3rd PDCCH TOs (i.e., the 1st group) can be mapped to the 1st CORESET, and the 4th to 6th PDCCH TOs (i.e., the 2nd group) can be mapped to the 2nd CORESET.

[0231] This mapping method between TO and CORESET can be applied to the mapping between TO and CORESET within the same window not only in the case of Examples 1-4 described above, but also in general cases where PDCCH is transmitted repeatedly at different times or divided and transmitted at different times.

[0232] As another example, multiple SS sets can be configured in a single slot through upper-layer fields defined within the SS set (e.g., the monitoringSymbolsWithinSlot field). For example, an SS set is defined with a P slot period, and L SS sets may exist at different times within the slot where the SS set is configured. In this case, the base station and the UE can agree on a window of 1 slot. Then, the CORESET can be mapped through the aforementioned 'PDCCH TO and CORESET mapping method within the window'.

[0233] In addition, Example 1-4 can be configured as a special case of Example 1-3. That is, in the method of configuring CORESET 1,2 and SS set 1,2 as in Example 1-3, if SS set 1 and 2 are configured identically, it is no different from Proposal 1-4, in which two CORESETs, one SS set, and two TCIs are configured. Therefore, in this case, the same PDCCH can be repeatedly transmitted in the same manner as in Proposal 1-4.

[0234] Example 2)

[0235] In Example 2, a method is described in which multiple base stations (i.e., MTRP) share and transmit the same PDCCH.

[0236] In the present disclosure, the statement that multiple base stations (i.e., MTRPs) share and transmit the same PDCCH means that a single DCI is transmitted through a single PDCCH candidate, wherein TRP 1 transmits the PDCCH candidate in some defined resources and TRP 2 transmits it in the remaining resources. In this case, it can also be interpreted as multiple base stations transmitting the same DCI. A single PDCCH candidate that multiple base stations (i.e., MTRPs) share and transmit can be recognized / instructed to the UE through the following settings.

[0237] For the convenience of the following description, it is assumed that two TRPs are in operation, but this assumption does not limit the technical scope of the present disclosure.

[0238] Example 2-1) A single / identical PDCCH candidate that is divided and transmitted by multiple base stations (i.e., MTRP) is defined / configured in a single (identical) CORESET, but can be defined / configured in different SS sets.

[0239] FIG. 13 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure.

[0240] Referring to FIG. 13, PDCCH candidate 1 can be transmitted using TCI state 1, and PDCCH candidate 2 can be transmitted using TCI state 2. Additionally, PDCCH candidate 1 and PDCCH candidate 2 can be combined to form a single PDCCH candidate in which a single DCI is transmitted. Furthermore, all PDCCH candidates generated in this way can be transmitted (repeatedly) at specific intervals (P) in the time domain.

[0241] This method can be configured in a manner similar to the previously described Example 1-1, and a single PDCCH candidate can be transmitted / received through different SS sets existing within the same window. For example, the UE may attempt decoding by assuming that the PDCCH candidate with aggregation level=A1 of SS set 1 and the PDCCH candidate with aggregation level=A2 of SS set 2 within the same window are a single PDCCH candidate with aggregation level=A1+A2, rather than treating them as different PDCCH candidates. Through this method, various aggregation levels other than the existing aggregation levels can be supported.

[0242] However, since the aggregation level or PDCCH candidate varies in each SS set, the method of generating a single candidate from candidates of two SS sets without any constraints can increase the complexity of terminal implementation. To address this, restrictions can be placed on the combination of candidates from two SS sets that generate a single PDCCH candidate. For example, the candidates from two SS sets that generate a single PDCCH candidate can be restricted to the same aggregation level and / or to the same PDCCH candidate number (or index). Alternatively, for example, a reference set (e.g., set 1) can be set among the two SS sets, and a single PDCCH candidate can be generated by combining a PDCCH candidate from set 1 with a PDCCH candidate from set 2 that is set to an aggregation level equal to or lower than that PDCCH candidate.

[0243] Example 2-1 can be configured as a special case of Example 2-3. That is, in the method of configuring CORESET 1 and 2 and SS set 1 and 2 as in Example 2-3, if CORESET 1 and 2 are configured identically (provided that the TCI state and CORESET ID defined in CORESET are different), it is no different from Example 2-1, in which one CORESET, two SS sets, and two TCIs are configured. Therefore, in this case, the same PDCCH can be repeatedly transmitted in the same manner as in Example 2-1.

[0244] Example 2-2) A single PDCCH candidate that is divided and transmitted by multiple base stations (i.e., MTRP) can be defined / configured in one (identical) CORESET and one (identical) SS set.

[0245] Multiple base stations can share and transmit PDCCH candidates defined in a single CORESET and a single SS set. Here, some of the frequency / time resources constituting a single PDCCH candidate are transmitted / received using one of the two TCI states configured within the CORESET, while the remaining resources can be transmitted / received using the other TCI state.

[0246] FIG. 14 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure.

[0247] Figure 14 shows an example where frequency resources constituting a single PDCCH candidate are divided and mapped to different TCI states. All PDCCH candidates can be transmitted (repeatedly) at specific intervals (P) in the time domain.

[0248] For example, the frequency resources constituting a PDCCH candidate with aggregation level = 4 can be divided into control channel elements (CCEs). Then, TCI states can be mapped alternately, such that the 1st and 3rd CCEs are mapped to TCI state 1 and the 2nd and 4th CCEs are mapped to TCI state 2. Alternatively, the first half of the CCEs and the latter half of the CCEs can be mapped to different TCI states, such that the 1st and 2nd CCEs are mapped to TCI state 1 and the 3rd and 4th CCEs are mapped to TCI state 2. Generalizing this, for N TCI states, N TCIs can be mapped circularly one by one as the CCE index increases. Alternatively, the entire set of CCEs can be grouped into N equal parts by adjacent CCEs (adjacent CCE indices), and N CCE groups and N TCI states can be mapped 1:1.

[0249] In the case of a PDCCH candidate with Aggregation level = 1, since it cannot be divided into CCE units, the resource element group (REG) bundle size is set to less than 6 REGs, and it can be divided into REG bundle units. Additionally, regardless of the aggregation level, resources can be divided into REG bundle units and TCI states can be mapped. In this case, the mapping method between the TCI state and the REG bundle can be applied in the same way as the above TCI state and CCE mapping method. For example, if a PDCCH candidate with aggregation level = 1 consists of 3 REG bundles (bundle size = 2), the TCI states can be mapped alternately by mapping TCI state 1 to the 1st and 3rd REG bundles and TCI state 2 to the 2nd REG bundle. Alternatively, the first and second REG bundles may be mapped to TCI state 1 and the third REG bundle may be mapped to TCI state 2, so that the first half of the REG bundles and the second half of the REG bundles are mapped to different TCI states.

[0250] Alternatively, in the case of a PDCCH candidate with Aggregation level = 1, diversity gain can be increased by one TRP transmitting one PDCCH candidate, while different TRPs transmit different PDCCH candidates (of Aggregation level = 1). For example, when there are 4 PDCCH candidates with Aggregation level = 1, TRP 1 transmits an even / odd candidate so that the even / odd candidate is mapped to TCI state 1, and conversely, TRP 2 transmits an odd / even candidate so that the odd / even candidate is mapped to TCI state 2.

[0251] According to the current standard, when a wideband DMRS is configured by setting the precoder granularity within a CORESET to consecutive RBs (i.e., allContiguousRBs), the UE identifies the REG bundle constituting the PDCCH candidate when estimating the channel for that PDCCH candidate. The UE then assumes that DMRS with the same precoder applied is transmitted for contiguous frequency resources containing that REG bundle within the CORESET. In this way, by utilizing not only the REG bundle constituting the PDCCH candidate but also the DMRS of other REGs following that REG bundle, the accuracy of channel estimation is improved.

[0252] However, as in the present embodiment, if the frequency resources constituting a CORESET are mapped to different TCI states, the wideband DMRS operation method is no longer valid. This is because some of the contiguous frequency resources containing the REG bundle are mapped to TCI state 1, and the remaining portions are mapped to TCI state 2, so the channels through which the DMRS is transmitted are different.

[0253] Therefore, in this case, if wideband DMRS is configured, the UE's operation must be modified as follows. When the UE estimates the channel for a single PDCCH candidate, it identifies the REG bundle constituting that PDCCH candidate. Then, the UE can assume that within the CORESET, DMRS with the same precoder applied is transmitted for contiguous frequency resources containing that REG bundle, "among frequency resources mapped to the same TCI state as that REG bundle." Even when multiple TRPs divide and transmit the time resources constituting a single PDCCH candidate, as shown in Fig. 15 described later, the UE operation proposed above can be applied when wideband DMRS is configured. Furthermore, this method can be extended and applied in the same manner to the case of the above-described Embodiment 1-2. In the case of Example 2-4 described below, since one PDCCH candidate is transmitted through two CORESETs, the UE can identify the REG bundle constituting the PDCCH candidate and assume that DMRS with the same precoder applied is transmitted for contiguous frequency resources containing the REG bundle in the CORESET to which the REG bundle belongs. For example, if the PDCCH candidate consists of three REG bundles, when estimating the channel of bundle i (i=1,2,3), the UE can assume that DMRS with the same precoder applied is transmitted for contiguous frequency resources containing the bundle in the CORESET to which bundle i belongs.

[0254] FIG. 15 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure.

[0255] Figure 15 shows a case where different TCI states are mapped by dividing the time resources constituting a single PDCCH candidate. All PDCCH candidates can be transmitted (repeatedly) at specific intervals (P) in the time domain.

[0256] FIG. 15 is an example in which a single CORESET is defined as the CORESET duration of two symbols. Additionally, two symbols constituting a single PDCCH candidate can be mapped to different TCI states. In this case, the mapping between the TCI and the symbol can be defined / configured in a manner similar to the TCI and CCE mapping method described above.

[0257] The mapping between REG and REG bundle, and between REG bundle and CCE, can be configured by applying the existing method to the PDCCH candidate resources. However, when actually estimating channels through DMRS, the existing REG bundle may not be used as is. This is because the symbols constituting the REG bundle are mapped to different TCIs. Therefore, when estimating channels through DMRS, the UE can reconstruct the REG bundle using only the symbols among those constituting the existing REG bundle that are mapped to the same TCI state, and perform channel estimation on the reconstructed REG bundle basis.

[0258] In addition, in this method, the window in which the same PDCCH is divided for transmission is determined for each transmission occasion (TO) when the PDCCH is sent or received. That is, for each PDCCH TO appearing in slots n, n+P, and n+2P, some of the resources constituting a single PDCCH candidate are transmitted or received using TCI state 1, while the remaining resources are transmitted or received using TCI state 2. In other words, the transmission is divided between two TRPs.

[0259] In addition, Example 2-2 can be configured as a special case of Example 2-3. That is, regarding the method of configuring CORESET 1 and 2 and SS set 1 and 2 as in Example 2-3, if CORESET 1 and 2 are configured identically (provided that the TCI state defined in CORESET is different) and SS set 1 and 2 are configured identically, it is no different from Example 2-2, where one CORESET, one SS set, and two TCIs are configured. Therefore, in this case, the same PDCCH can be divided and transmitted in the same manner as in Example 2-2. Similarly, Example 2-2 can be configured as a special case of Example 2-4. Regarding the method of configuring CORESET 1 and 2 and SS set 1 as in Proposal 2-4, if CORESET 1 and 2 are configured identically (provided that the TCI state defined in CORESET is different), it is no different from Example 2-2. In addition, Example 2-2 can be configured as a special case of Example 2-1. That is, in the method of setting CORESET 1 and SS sets 1 and 2 as in Example 2-1, if SS 1 and 2 are set identically (provided that the TCI state and CORESET ID of the CORESET used in each SS are different), it is no different from Example 2-2, where one CORESET, one SS set, and two TCIs are set. Therefore, in this case, the same PDCCH can be repeatedly transmitted in the same manner as in Example 2-2.

[0260] Example 2-3) A single PDCCH candidate that is divided and transmitted by multiple base stations (i.e., MTRP) may be defined / configured in multiple CORESETs and may be defined / configured in multiple SS sets.

[0261] FIG. 16 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure.

[0262] Referring to FIG. 16, CORESET 1 can be mapped to SS set 1, and CORESET 2 can be mapped to SS set 2. Also, one PDCCH candidate can be transmitted / received through different SS sets existing within the same window.

[0263] For example, the UE may attempt decoding by assuming that the PDCCH candidate of aggregation level=A1 of SS set 1 and the PDCCH candidate of aggregation level=A2 of SS set 2 within the same window are a single PDCCH candidate of aggregation level=A1+A2, rather than treating them as different PDCCH candidates. Since Example 2-3 differs from Example 2-1 described above only in the mapping between CORESET and SS set, the detailed proposed method of Proposal 2-1 can be applied as is.

[0264] Here, the base station indicates to the UE that multiple SS sets (e.g., SS sets 1 and 2) are in the same group, and the UE can recognize / assume that the SS sets belonging to the same group are configured to share and transmit the same DCI (and / or the same PDCCH candidate).

[0265] Example 2-4) A single PDCCH candidate that is divided and transmitted by multiple base stations (i.e., MTRP) may be defined / configured in multiple CORESETs, but may be defined / configured in a single SS set.

[0266] FIG. 17 is a diagram illustrating a method for transmitting and receiving downlink control information according to one embodiment of the present disclosure.

[0267] Referring to Fig. 17, two CORESETs with different RB resources can be mapped to a single SS set. Additionally, a single PDCCH candidate can be generated by combining a PDCCH candidate from CORESET 1 and a PDCCH candidate from CORESET 2. For example, TRP 1 and 2 transmit PDCCH through CORESET 1 and 2, respectively, and the UE can attempt decoding by assuming a single PDCCH candidate of aggregation level=A1+A2 by combining a PDCCH candidate of aggregation level=A1 from CORESET 1 and a PDCCH candidate of aggregation level=A2 from CORESET 2.

[0268] However, since the aggregation level or PDCCH candidate varies in each CORESET, the method of generating a single candidate from candidates of two CORESETs without any constraints increases the complexity of terminal implementation. To solve this, the combination of PDCCH candidates from two CORESETs that generate a single PDCCH candidate can be limited. This limitation can be applied similarly to the method of limiting the combination of PDCCH candidates from two SS sets in the method of Example 2-1 described above. That is, since Example 2-4 is similar to Example 2-1, the detailed proposed methods of Example 2-1 can be applied. However, since Example 2-4 generates a single PDCCH candidate by aggregating multiple PDCCH candidates that are multiplexed on frequency resources instead of time resources, it can be modified and applied accordingly.

[0269] In addition, in this method, the window in which the same PDCCH is divided and transmitted is determined for each transmission occasion (TO) when the PDCCH is sent or received. That is, for each PDCCH TO appearing in slots n, n+P, and n+2P, PDCCH candidate 1 may be transmitted / received using TCI state 1 (via CORESET 1) from some of the resources constituting a single PDCCH candidate, and PDCCH candidate 2 may be transmitted / received using TCI state 2 (via CORESET 2) from the remaining resources. In other words, the two TRPs divide the PDCCH candidate into PDCCH candidate 1 and PDCCH candidate 2 for transmission.

[0270] In addition, Example 2-4 can be configured as a special case of Example 2-3. That is, in the method of configuring CORESET 1,2 and SS set 1,2 as in Example 2-3, if SS set 1 and 2 are configured identically, it is no different from Example 2-4, where two CORESETs, one SS set, and two TCIs are configured. Therefore, in this case, PDCCH can be divided and transmitted in the same manner as in Example 2-4.

[0271] Additionally, for SS set(s) in which multiple base stations (i.e., MTRPs) divide and transmit the same PDCCH (i.e., in the case of Examples 2-1 to 2-4 described above), the UE may be instructed to divide and transmit the same PDCCH only for some DCI formats / SS types / RNTIs defined in the SS set, and to transmit the remainder from a single TRP in the conventional manner. For example, for an SS set in which both DCI format 1-0 and 1-1 are defined, the UE may be instructed to divide and transmit only for format 1-0 (or 1-1). Or, among the UE-specific SS and common SS, the UE may be instructed to divide and transmit only for the common SS (or UE-specific SS). Or, the UE may be instructed to divide and transmit only for DCIs CRC-masked with specific RNTIs (e.g., RNTIs excluding C-RNTI, MCS-C-RNTI, CS-RNTI).

[0272] A base station can inform the UE through higher layer signaling whether multiple base stations will divide and transmit the same PDCCH (case of Example 2 described above) or transmit it repeatedly (case of Example 1 described above).

[0273] The method proposed in the present disclosure below can be applied to both cases where multiple base stations (i.e., MTRP) repeatedly transmit the same PDCCH (case 1 of the embodiment described above) and cases where they divide and transmit the same PDCCH (case 2 of the embodiment described above).

[0274] In the present disclosure, TO (or PDCCH TO) may refer to each channel transmitted at different times when multiple channels (e.g., i) multiple PDCCH candidates in the case of repeated transmission, ii) combined multiple PDCCH candidates or multiple PDCCH candidates before combination in the case of split transmission), each channel transmitted to different frequencies / RBs in the case of FDM, and each channel transmitted to different layers / beams / DMRS ports in the case of SDM. One TCI state may be mapped to each TO.

[0275] When the same channel is transmitted repeatedly (e.g., Case 1 of Example 1), a complete DCI / data / uplink control information (UCI) is transmitted to one TO, and the receiving end can receive multiple TOs to increase the reception success rate. When a channel is divided and transmitted to multiple TOs (e.g., Case 2 of Example 2), a part of the DCI / data / UCI is transmitted to one TO, and the receiving end must receive all multiple TOs to collect the fragmented DCI / data / UCI and receive the complete DCI / data / UCI.

[0276] Example 3)

[0277] Before describing the present embodiment, a method for explicitly indicating the TCI in the DCI transmitted via the PDCCH to support multi-TRP (or multi-panel) transmission will be described.

[0278] To support multi-TRP (or multi-panel) transmission, single PDCCH-based and multi-PDCCH-based methods may be applied. The single PDCCH-based method can support various transmission methods for URLLC services as well as eMBB services. To support the single PDCCH-based method, the TCI information included in the DCI may indicate multiple TCI states together. For example, there exists a TCI state pool configured by an RRC message, and one or more TCI state candidates to be applied to actual PDSCH transmission from this pool may be selected and indicated to the terminal via a MAC-CE message. Additionally, the functionality of this MAC-CE message can be extended to link multiple TCI states to a single TCI codepoint. Accordingly, if the TCI information indicated by the base station via the DCI indicates multiple TCI states, the terminal can utilize each TCI state for PDSCH reception by mapping or applying it to different PDSCH transmission resources according to the PDSCH transmission settings. Here, the PDSCH transmission resource can be configured as a combination of one or more of time resources (e.g., symbol, symbol set, slot, slot set, etc.), frequency resources (e.g., RB, RB set, etc.), or spatial resources (e.g., layer, antenna port, beam, RS, etc.).

[0279] As such, a single PDCCH-based multi-TRP / panel transmission method may include expanding the TCI states indicated by the TCI information included in the DCI to multiple states. To apply this, there is a restriction that TCI states must always be signaled only through the DCI.

[0280] Meanwhile, in cases where TCI information is not included in the DCI (i.e., no separate TCI is indicated via the DCI) and QCL type-D (i.e., QCL between antenna ports for beamforming related to channel characteristics of spatial Rx parameters) is applied, if a PDSCH is assigned after a predetermined time (e.g., scheduling offset), the TCI of the PDSCH may follow the TCI of the CORESET to which the PDSCH was transmitted (i.e., a pre-configured TCI for the CORESET) to which the DCI scheduling the PDSCH is transmitted. If the PDSCH is assigned before the aforementioned predetermined time, a default TCI (e.g., the TCI state associated with the CORESET or search space set having the lowest identifier in the latest slot monitored by the terminal) may be applied, regardless of whether TCI information is included in the DCI. Additionally, the above scheduling offset may correspond to the time required for DCI decoding and beam switching, and may be defined based on the terminal capability reported by the terminal.

[0281] If the DCI does not include TCI information, applying the TCI of the CORESET associated with the PDCCH transmitting the DCI to the PDSCH scheduled by that DCI can be useful when the PDSCH transmission beam does not change relative to the PDCCH transmission beam. However, this method is defined only for single-PDCCH-based single-TRP / panel transmissions and is not defined for single-PDCCH-based multi-TRP / panel transmissions. Therefore, there is ambiguity regarding how to determine the TCI to be applied to the transmission or reception of downlink data channels (e.g., PDSCH) from multi-TRP / panels.

[0282] In addition, to enhance the reliability of the PDCCH transmission itself, the transmission of a single PDCCH (or DCI) from multiple TRPs / panels may be supported. Accordingly, multiple QCL RSs (or TCI states) may be applied to a single PDCCH / DCI transmission (i.e., for the same QCL parameter).

[0283] For example, the same PDCCH / DCI may be transmitted repeatedly from the MTRP, or a single PDCCH / DCI may be divided and transmitted by the MTRP. Accordingly, each TCI may be mapped to a different time / frequency / space resource for the resource to transmit the PDCCH (e.g., CORESET, search space, CCE, etc.). Alternatively, a single PDCCH may be transmitted by multiple TRPs over the same time / frequency / space resource (e.g., a single frequency network (SFN) method).

[0284] In the following description, TCI may include the meaning of QCL reference signal (RS) information or QCL type-D RS information.

[0285] In addition, time / frequency / space resource units mapped to different TCIs are referred to as transmission opportunities (TO).

[0286] In the following examples, it is assumed that there are multiple CORESETs associated with a single identical DCI (or downlink control channel) transmitted from the MTRP, and that one TCI information is associated with each CORESET, or that there is one CORESET associated with the single identical DCI (or downlink control channel), and that multiple TCI information is associated with the one CORESET. That is, it is assumed that when a single identical DCI is transmitted from the MTRP through the downlink control channel, multiple TCI information is pre-set or pre-defined based on the CORESET associated with the downlink control channel transmission.

[0287] For example, the upper-level parameter ControlResourceSet IE (information element) can be used to set a time / frequency control resource set (CORESET). For example, the control resource set (CORESET) may be associated with the detection and reception of downlink control information. The ControlResourceSet IE may include one or more of the following: a CORESET-related ID (e.g., controlResourceSetID), an index of the CORESET pool for the CORESET (e.g., CORESETPoolIndex), a time / frequency resource setting for the CORESET, or TCI information associated with the CORESET. For example, the index of the CORESET pool (e.g., CORESETPoolIndex) may be set to 0 or 1. In the examples of the present disclosure described above, a CORESET group may correspond to a CORESET pool, and a CORESET group ID may correspond to a CORESET pool index (e.g., CORESETPoolIndex). A ControlResourceSet (i.e., CORESET) can be configured via upper-level signaling (e.g., RRC signaling).

[0288] Additionally, in the following examples, the CORESET identifier or CORESET ID may include a search space set (SS set) identifier or SS set ID. That is, a single CORESET may include one or more SSs, and one or more SSs may be defined as an SS set.

[0289] In addition, in the following examples, when the same DCI (or downlink control channel (e.g., PDCCH)) is transmitted from the MTRP, the single frequency network (SFN) method includes the operation of the MTRP simultaneously transmitting the same DCI (or PDCCH), and the non-SFN method includes the operation of the MTRP repeatedly transmitting the same DCI (or PDCCH) at different time resources (in a predetermined order). For example, in the SFN method, multiple TCI information may be associated with one CORESET, and in the non-SFN method, one TCI information may be associated with each of multiple CORESETs. The following examples are applicable to both the SFN method and the non-SFN method, and it is assumed that the terminal can obtain multiple TCI information associated with CORESET(s) associated with a single DCI (or PDCCH) transmitted from the MTRP.

[0290] For clarity, the term "repeated transmission of a single identical DCI (or PDCCH) from MTRP" is primarily used in the following description, and repeated transmission of a single identical DCI / PDCCH from MTRP may include both SFN and non-SFN methods. Furthermore, repeated transmission of a single identical DCI / PDCCH from MTRP should be understood to include methods in which MTRP transmits the same DCI / PDCCH individually or divides and transmits a single DCI / PDCCH.

[0291] Additionally, repeated transmissions of the same DCI / PDCCH may include repeated transmissions from MTRP and repeated transmissions from a single TRP (STRP), unless specifically limited.

[0292] That is, in the following examples, the method of repeated transmission of the same DCI / PDCCH from MTRP is not limited to the SFN method or the non-SFN method.

[0293] The present embodiment includes various examples for clearly determining the TCI state to be applied to a downlink data channel (e.g., PDSCH) scheduled by a single identical DCI when the same DCI is repeatedly transmitted through a downlink control channel (e.g., PDCCH).

[0294] The following examples may apply when TCI information is not included in the PDCCH / DCI scheduling the PDSCH, or when a Type-D QCL exists for the PDCCH / DCI.

[0295] Additionally or alternatively, the following examples may apply when the time from the time of receiving the PDCCH / DCI to the time of receiving the PDSCH scheduled by the said PDCCH / DCI (i.e., scheduling offset) is greater than or equal to a predetermined threshold (i.e., when sufficient time is given for DCI decoding and beaming so that the default TCI is not applied). For example, the time of receiving the PDCCH / DCI may correspond to the last time of receiving the PDCCH / DCI (or PDCCH TO) in the case of a PDCCH / DCI transmitted from multiple time resources in the time domain. For example, the time of receiving the PDSCH may correspond to the first time of receiving the PDSCH (or PDSCH TO) in the case of a PDSCH transmitted from multiple time resources in the time domain.

[0296] Example 3-1

[0297] The present embodiment includes examples in which, when multiple TCIs are set in a single CORESET, the multiple TCIs are mapped / applied based on a predetermined mapping method for each PDSCH TO of the PDSCH scheduled through the CORESET (i.e., the DCI transmitted through the PDCCH transmitted from the CORESET).

[0298] In the following examples, a plurality of TCIs are primarily described as being mapped / applied to PDCCH and / or PDSCH alternately or sequentially as an example of a predetermined mapping method, but the scope of the present disclosure is not limited thereto. For example, in the following description, a predetermined mapping method may include a method in which a plurality of TCI states are cyclically mapped sequentially in ascending order of the indices of a plurality of PDCCH TOs and / or a plurality of PDSCH TOs (i.e., a cyclic mapping method). Additionally, the predetermined mapping method may include a method in which a plurality of PDCCH TOs and / or a plurality of PDSCH TOs are grouped into a plurality of TO groups, and a plurality of TCI states are sequentially mapped in ascending order of the indices of the TO groups (i.e., a sequential mapping method). Furthermore, the predetermined mapping method may include a method in which a plurality of PDCCH TOs and / or a plurality of PDSCH TOs are grouped into a plurality of TO groups, and a plurality of TCI states are cyclically mapped sequentially in ascending order of the indices of the TO groups for each TO group (i.e., a hybrid mapping method). That is, the above-mentioned predetermined mapping method may include one or more of a cyclic mapping method, a sequential mapping method, or a hybrid mapping method.

[0299] If MTRP transmission for PDCCH is not applied (e.g., PDCCH / DCI repeated transmission by STRP), the terminal may assume that for the PDCCH transmitted from the corresponding CORESET, only one specific TCI among the plurality of TCIs set for the corresponding CORESET is applied. For example, the specific TCI may be the first TCI, the TCI with the lowest index, the last TCI, or the TCI with the highest index. In this case, the TCI applied to the PDSCH (i.e., the one applied by the base station to the PDSCH transmission, or the one assumed by the terminal to the PDSCH reception) may follow the specific TCI.

[0300] If MTRP transmission is applied to a PDCCH, the terminal may assume that the plurality of TCIs configured for the corresponding CORESET are applied to the PDCCH transmitted from the corresponding CORESET based on a predetermined mapping method (e.g., one or more of cyclic, sequential, or hybrid mapping methods) according to a predetermined criterion. For example, the plurality of TCIs may be applied based on a predetermined mapping method (e.g., one or more of cyclic, sequential, or hybrid mapping methods) based on an index related to MTRP. For example, the plurality of TCIs may be applied based on a predetermined mapping method (e.g., one or more of cyclic, sequential, or hybrid mapping methods) based on the order of TO for the PDCCH. The TCI applied to the PDCCH may be mapped or configured based on the TCI applied to the PDCCH as described above. In other words, the plurality of TCIs may be applied to the PDCCH based on a predetermined mapping method (e.g., one or more of cyclic, sequential, or hybrid mapping methods) according to a predetermined criterion.

[0301] Here, whether MTRP transmission is applied to the PDCCH can be distinguished based on the base station's settings / instructions regarding whether multiple TCIs are applied to the PDCCH transmission and / or the base station's settings / instructions that the number of TOs for the PDCCH is 2 or more. For example, in the case of a setting / instruction that only one TCI is applied to the PDCCH transmission and / or a setting / instruction that the number of TOs for the PDCCH is 1, the terminal may assume STRP PDCCH transmission.

[0302] In this embodiment, a plurality of TCIs to be applied to a PDSCH scheduled through at least a CORESET may be configured / instructed through the CORESET. The configuration / instruction operation includes being configured / instructed to a terminal through an RRC, MAC-CE, and / or DCI.

[0303] When multiple TCIs are associated with and configured / instructed in CORESET, for STRP PDCCH transmission, only one of the multiple TCIs is a value applied to PDCCH and / or PDSCH, and the remaining TCI(s) may be value(s) applied to PDCCH and / or PDSCH transmission from MTRP.

[0304] For example, in the case of STRP PDCCH transmission, a specific TCI to be applied to the PDCCH and / or PDSCH among a plurality of TCIs configured for the CORESET may be indicated / configured to the terminal through one or more signaling methods such as RRC, MAC-CE, or DCI, or may be predefined between the base station and the terminal without separate signaling.

[0305] For example, in the case of MTRP PDCCH transmission, multiple TCIs (TCI set) configured for CORESET may be applied to PDCCH and PDSCH. Here, the configuration of the TCI set applied to PDCCH transmission and the configuration of the TCI set applied to PDSCH transmission may be the same or different. For example, if three TCIs are configured for CORESET, two of the three TCIs may be applied to PDCCH transmission configured with two TOs, and all three TCIs may be configured or predefined to be applied to PDSCH transmission configured with four TOs.

[0306] This embodiment is applicable not only to transmission methods that increase reliability (e.g., operations that repeatedly transmit the same data per TO) but also to transmission methods that increase throughput by transmitting different data for each TO. For example, each PDSCH TO may be configured to be distinguished by different spatial resources (e.g., layers, antenna ports, etc.) within the same time-frequency resource, and different TCIs may be applied to each distinguished spatial resource (e.g., layer groups, antenna port groups, etc.).

[0307] Control information that must be reliably transmitted to terminals, such as system information, can also be transmitted through a specific CORESET. Due to the absence of feedback information from the terminal, it may be difficult for the base station to determine which TRP combination is preferred by the terminal. Additionally, since this information is transmitted at a sufficiently low MCS, the application of MTRP PDSCH transmission may be unnecessary.

[0308] In addition, multiple search spaces may be configured for the CORESET. Through this CORESET, the base station can send control information of various uses / forms to the terminal. Accordingly, according to the present embodiment, multiple TCIs (i.e., TCIs to which PDCCH and / or PDSCH are applied) may be configured for the CORESET, and for a PDCCH that satisfies a specific condition, a specific TCI among the multiple TCIs may be applied. The PDCCH that satisfies the specific condition may be one or more of the following: a PDCCH that includes a specific DCI format, such as a fallback DCI (e.g., DCI format 1-0); a PDCCH that is CRC-masked by a specific RNTI, such as an RNTI excluding C(Cell)-RNTI (e.g., SI(System Information)-RNTI, MCS-C-RNTI, CS-RNTI, etc.); or a PDCCH that is transmitted through a specific search space, such as a common search space.

[0309] Example 3-1-1

[0310] For a PDSCH scheduled by a PDCCH / DCI transmitted in a CORESET where multiple TCIs are configured, if the PDCCH / DCI is based on a specific DCI format, a specific search space, or a specific RNTI, only one specific TCI among the multiple TCIs may be applied to the transmission / reception of the PDCCH / DCI. For example, the specific TCI may be the first TCI, the TCI with the lowest index, the last TCI, or the TCI with the highest index.

[0311] Example 3-1-2

[0312] As an alternative (or supplementary) method to Example 1-1, a specific CORESET may be defined to operate based only on a single TCI.

[0313] For example, the maximum number of TCIs that can be set can be defined differently depending on the CORESET. For instance, a specific set of CORESETs (i.e., one or more CORESETs) can set at most one TCI.

[0314] For example, a specific CORESET set may include one or more of CORESET 0 (i.e., a CORESET that is configured by a Master Information Block (MIB) provided through a PBCH and monitored by a PDCCH containing information for scheduling a System Information Block 1 (SIB1)), a CORESET with a common search space configured, or a CORESET with a search space configured for base station responses to a BFRQ (beam failure recovery request) and / or PRACH.

[0315] Example 3-2

[0316] According to the examples described in the aforementioned Examples 3-1, 3-1-1 and / or 3-1-2, multiple TCIs may be set / instructed for a single CORESET in order to set / instruct multiple TCIs applicable to PDSCH.

[0317] When MTRP transmission is performed for PDCCH, a PDCCH transmitted through one CORESET may be transmitted on multiple TOs, and PDCCH / DCI may be repeatedly transmitted through multiple CORESETs.

[0318] For example, the same PDSCH TO group may be scheduled by a DCI transmitted through PDCCH #1 transmitted from CORESET #1 and a DCI transmitted through PDCCH #2 transmitted from CORESET #2 (the same DCI as the DCI of PDCCH #1). Alternatively, when PDCCH / DCI is transmitted separately, the same PDSCH TO group may be scheduled by a first part of the PDCCH (or first part of the DCI) transmitted through CORESET #1 and a second part of the PDCCH (or second part of the DCI) transmitted through CORESET #2.

[0319] In such cases, the terminal may not successfully receive a specific PDCCH among the PDCCHs that are repeatedly transmitted through multiple CORESETs. In such cases, the terminal may be instructed through separate signaling which combination of CORESETs will participate in / use the repeated transmission of the PDCCH. In the following description, CORESETs that establish such combination relationships are referred to as 'paired CORESETs'.

[0320] According to the present embodiment, when multiple PDSCH TOs (for the same data) are scheduled through multiple CORESET / PDCCH / DCIs, the TCI to be applied to each PDSCH TO can be determined based on the TCI values ​​set for the paired CORESETs.

[0321] For example, assume that CORESET#1 and CORESET#2 are configured as paired CORESETS, and that TCI A and TCI B are configured for each CORESET via RRC / MAC-CE signaling. Additionally, assume that the base station (repeatedly) transmits PDCCH(s) to a specific terminal via CORESET#1 and CORESET#2 to improve PDCCH reliability, and that a PDSCH that is transmitted four times is scheduled by the DCI(s) included in the PDCCH(s). A terminal that has successfully received / decoded at least one of the two PDCCH TOs can obtain information about the four PDSCH TOs.

[0322] For example, a terminal that has successfully received DCI from both PDCCH TOs can obtain TCI information (i.e., TCI A and TCI B) set for CORESET#1 and CORESET#2, where the PDCCH TOs were received, and apply TCI A and TCI B to each PDCCH TO based on a predetermined mapping method (e.g., one or more of cyclic, sequential, or hybrid mapping methods).

[0323] For example, a terminal that has successfully received DCI only from CORESET#1 or the first PDCCH TO can obtain the TCI information set for CORESET#1 (i.e., TCI A) and know that it must apply the set {TCI A, TCI B} through the pairing relationship between CORESET#1 and CORESET#2.

[0324] For example, a terminal that has successfully received DCI only from CORESET#2 or the second PDCCH TO can obtain the TCI information set for CORESET#2 (i.e., TCI B) and know that it must apply the set {TCI A, TCI B} through the pairing relationship between CORESET#2 and CORESET#1.

[0325] In the case of a terminal that has successfully received DCI in only some of the multiple PDCCH TOs, it may be able to acquire the TCI set itself, but it may not be able to clearly determine the order in which the TCIs within the TCI set are applied to the PDSCH TOs. For example, if the order of applying TCIs to the PDSCH is set to apply them starting from the TCI of the CORESET that successfully received the DCI, then depending on whether the terminal successfully receives the DCI from the first PDCCH TO, the order of TCIs applied to the four PDSCH TOs becomes {A, B, A, B} or {B, A, B, A}. In this case, there is a problem in that the terminal cannot clearly determine the order of TCIs applied by the base station to the PDSCH TOs.

[0326] Therefore, the base station needs to instruct / set the terminal to apply PDSCH TO starting from the TCI corresponding to which CORESET (or in what order), or define which TCI to apply to PDSCH TO in what order according to a predefined rule.

[0327] Example 3-2-1

[0328] In determining the order of applying TCIs for each PDSCH TO among the multiple TCIs configured for a CORESET, the order in which TCIs are applied to the paired CORESETs (or from which CORESET) may be separately indicated via RRC / MAC-CE / DCI signaling, or they may be applied according to a predefined rule. Here, the predefined rule may be defined based on the configuration order of the paired CORESETs and / or the order of the IDs (or indices) of the paired CORESETs. Here, the order may be ascending, descending, ascending cycling, or descending cycling.

[0329] For example, if paired CORESETs are configured in the order of CORESET#1 and CORESET#2, the TCI information configured for CORESET#1 (e.g., TCI A) and the TCI information configured for CORESET#2 (e.g., TCI B) can be applied to PDSCH TO based on a predetermined mapping method (e.g., in the order A, B, A, B) according to the configuration order of the paired CORESETs.

[0330] Alternatively, regardless of the configuration order of the paired CORESETs, the TCI information configured for CORESET#1 (e.g., TCI A) and the TCI information configured for CORESET#2 (e.g., TCI B) based on the ID (or index) order of the paired CORESETs may be applied to PDSCH TO based on a predetermined mapping method (e.g., in the order A, B, A, B).

[0331] In this case, even if the terminal succeeds in receiving DCI only from the second PDCCH TO, it may apply a predetermined mapping method (e.g., one or more of cyclic, sequential, or hybrid mapping methods) based on the pairing relationship to the PDSCH TO, rather than starting from the TCI information set for CORESET#2 (e.g., TCI B).

[0332] Alternatively, based on a predetermined mapping method (e.g., one or more of cyclic, sequential, or hybrid mapping methods), the TCI information of the DCI that was successfully received may be applied. For example, if DCI reception is successful only in the second PDCCH TO, the TCI information set for CORESET#2 (e.g., TCI B) may be applied to the PDSCH TO based on a predetermined mapping method (e.g., B, A, B, A). In this case, the order of TCIs actually applied by the base station to the PDSCH TO may be the same or different from the order of TCIs assumed by the terminal, but the complexity of the terminal implementation may be reduced.

[0333] The detailed examples of the aforementioned Example 3 can be applied not only when the PDSCH TO is transmitted over resources distinguished in the time / frequency / space resource domain, but also to the transmission of an SFN method for a single PDSCH TO.

[0334] For example, as in Example 3-1, multiple TCIs configured for a single CORESET can be indicated / configured to establish a QCL relationship with the PDSCH DMRS port(s) scheduled through the CORESET.

[0335] As an additional example, as in Example 3-2, multiple TCIs configured for CORESETs belonging to a paired CORESET can be indicated / configured to establish a QCL relationship with the PDSCH DMRS port(s) scheduled through the CORESETs.

[0336] For example, if the DMRS ports indicated via DCI belong to multiple (e.g., 2) CDM groups, a QCL relationship may be established between the TCI states set for the CORESET(s) that received the DCI and the CDM groups to which the DMRS ports are transmitted. That is, each TRP can cooperatively transmit data (e.g., PDSCH) through DMRS ports belonging to different CDM groups. Here, PDSCH TO is SDM and can be transmitted simultaneously over the same time / frequency resource.

[0337] Alternatively, if the DMRS ports indicated via DCI belong to a single CDM group and the PDSCHs are configured to be FDM / TDM and repeatedly transmitted, a QCL relationship based on the TCI state can be established for the FDM / TDM PDSCH TOs.

[0338] In the various examples of the present disclosure described above, the same DCI / PDCCH is primarily described as being transmitted through two TCI states, but this is for convenience of explanation only and does not limit the scope of the present disclosure. That is, the examples of the present disclosure include a method for clearly determining the TCI state to be applied to the PDSCH scheduled by the said DCI, even in cases where the same DCI / PDCCH is associated with two or more different TCI states on one or more serving cells from one or more TRPs (e.g., cases where the TCI states associated with the CORESET associated with the DCI are different).

[0339] FIG. 18 is a flowchart illustrating a method for a terminal to receive a downlink channel according to the present disclosure.

[0340] In step S1810, the terminal may receive a downlink control channel based on two or more TCI states associated with one or more CORESETs. Here, the DCI received through the downlink control channel may not include TCI information.

[0341] For example, two or more TCI states may be set for a single CORESET, or one TCI state may be set for each of multiple CORESETs. For example, two or more TCI states may include multiple TCI states set for multiple paired CORESETs.

[0342] For example, the downlink control channel transmitted from a single TRP may be received based on a specific preset TCI state among two or more TCI states associated with one or more CORESETs. Here, the downlink control channel may be associated with one or more of DCI format 1-0, C-RNTI, or common search space. Alternatively, the downlink control channel transmitted from multiple TRPs may be received based on two or more TCI states associated with one or more CORESETs.

[0343] For example, for a CORESET associated with one or more of CORESETs, at most one TCI state may be set, such as CORESET 0, a common search space, a search space associated with BFRQ, or a search space associated with PRACH.

[0344] In step S1820, the terminal may receive a downlink data channel transmitted from multiple TRPs based on two or more TCI states associated with one or more CORESETs. Here, the two or more TCI states may be applied to the downlink data channel based on a predetermined mapping method (e.g., one or more of cyclic, sequential, or hybrid mapping methods).

[0345] For example, the reception time of the downlink data channel can be set after a predetermined offset from the reception time of the downlink control channel.

[0346] For example, the mapping relationship between the plurality of TCI states and the TO of the downlink data channel may be pre-set through one or more of upper layer signaling, MAC-CE, or DCI, or determined based on pre-defined criteria. Here, the pre-defined criteria may include mapping the plurality of TCI states to the transmission opportunity (TO) of the downlink data channel based on a predetermined mapping method (e.g., one or more of cyclic, sequential, or hybrid mapping methods) based on one or more of the setting order of the plurality of paired CORESETs or the order of the CORESET identifiers of the plurality of paired CORESETs.

[0347] FIG. 19 is a diagram illustrating the signaling procedure of a network side and a terminal according to the present disclosure.

[0348] FIG. 19 illustrates signaling between a network side (e.g., a first TRP and a second TRP) and a terminal (UE) in a situation where various examples of the present disclosure (Examples 1, 2 and / or 3) may be applied to a plurality of TRPs (wherein in the following description, TRP may be replaced with a base station or a cell). Here, the UE / Network side is merely an example and may be replaced with various devices as described in the foregoing description or in relation to FIG. 20. FIG. 19 is for convenience of explanation only and does not limit the scope of the present disclosure. Additionally, some step(s) shown in FIG. 19 may be omitted depending on the situation and / or settings, etc.

[0349] Referring to FIG. 19, signaling between two TRPs and a UE is considered for the sake of convenience of explanation, but it goes without saying that the signaling method can be extended and applied to signaling between multiple TRPs and multiple UEs. In the following description, the Network side may be a single base station containing multiple TRPs, or a single Cell containing multiple TRPs. For example, an ideal / non-ideal backhaul may be established between the first TRP and the second TRP constituting the Network side. Furthermore, although the following description is based on multiple TRPs, this can be similarly extended and applied to transmission through multiple panels. Additionally, in the present disclosure, the operation of a terminal receiving a signal from a first TRP and / or a second TRP may include the operation of the terminal receiving a signal from a Network side (through / using the first TRP and / or the second TRP), and the operation of the terminal transmitting a signal to the first TRP and / or the second TRP may include the operation of the terminal transmitting a signal to the Network side (through / using the first TRP and / or the second TRP).

[0350] The example in FIG. 19 shows signaling when a terminal receives multiple DCIs in an M-TRP situation (or when multiple CORESETs are set from a single TRP can also be assumed to be M-TRP) (e.g., when each TRP transmits the same DCI repeatedly (or divides the same DCI) to the UE).

[0351] The UE can receive configuration information for transmission and reception based on Multiple TRPs from the Network side via / using TRP 1 (and / or TRP 2) (S1905). The configuration information may include information related to the configuration of the network side (i.e., TRP configuration), resource information related to transmission and reception based on Multiple TRPs (resource allocation), etc. At this time, the configuration information may be transmitted via upper layer signaling (e.g., RRC signaling, MAC-CE, etc.). Additionally, if the configuration information is predefined or configured, the corresponding step may be omitted. For example, the configuration information may include settings related to the TCI state mapping method / method described in the aforementioned embodiments 1, 2, and / or 3. Additionally, for example, the above-mentioned configuration information may include information related to the configuration of transmission occasions described in Examples 1, 2, and / or 3, information related to TCI mapping, and information related to repeated transmission of a control channel (e.g., PDCCH) (e.g., whether repeated transmission occurs, number of repeated transmissions, etc.). For example, as described in the detailed examples of Example 3 above, the above-mentioned configuration information may include information related to MTRP transmission (e.g., multiple TO configurations, information related to the application of multiple TCIs), information related to repeated transmission (e.g., combinations of CORESETs), etc. For example, the configuration related to the TCI state mapping method / scheme may include information on the number of applicable TCIs per CORESET, information related to a specific TCI state to be applied in specific cases (e.g., STRP, specific DCI Format, specific SS, specific RNTI, etc.). For example, based on the above-mentioned configuration information, multiple TCI states may be configured in a single CORESET.

[0352] For example, the operation of the UE (100 / 200 in FIG. 20) of step S2105 described above receiving configuration information related to transmission and reception based on the Multiple TRP from the Network side (100 / 200 in FIG. 20) can be implemented by the device of FIG. 20 to be described below. For example, referring to FIG. 20, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc. to receive configuration information related to transmission and reception based on the Multiple TRP, and one or more transceivers 106 can receive configuration information related to transmission and reception based on the Multiple TRP from the Network side.

[0353] The UE can receive a first DCI and a first data scheduled by the first DCI through / using TRP 1 from the Network side (S1910). Additionally, the UE can receive a second data scheduled by a second DCI and a second DCI 2 through / using TRP 2 from the Network side, receive Data 2 which is a second data scheduled by the first DCI without a second DCI, or receive only the second DCI that schedules the first data (S1920). For example, data of a single TRP (e.g., the first data of TRP 1, or the second data of TRP 2) may be scheduled by the first DCI and the second DCI that are repeatedly transmitted from TRP 1 and TRP 2.

[0354] For example, the first DCI (and the second DCI) may include (instruction) information regarding the TCI state described in the aforementioned Examples 1, 2, and / or 3, resource allocation information for DMRS and / or data (i.e., spatial / frequency / time resources), etc. For example, the DCI (e.g., the first DCI and / or the second DCI) may include information related to the repeated transmission of PDCCH / PDSCH (e.g., CORESET information related to repeated transmission), instruction information related to the setting of the transmission occasion (TO), information related to the mapping of the TO and the TCI state (e.g., mapping order, etc.). In this case, the first data and the second data may be transmitted and received based on the TCI state mapping method described in the detailed examples of Example 3.

[0355] DCI (e.g., first DCI and second DCI) and data (e.g., first data and second data) may be transmitted through a control channel (e.g., PDCCH, etc.) and a data channel (e.g., PDSCH, etc.), respectively. For example, the control channel (e.g., PDCCH) may be transmitted repeatedly, or the same control channel may be divided and transmitted. Additionally, steps S2110 and S2120 may be performed simultaneously, or one may be performed earlier than the other.

[0356] For example, the operation of the UE (100 / 200 of FIG. 20) of steps S2110 and S2120 receiving a DCI (e.g., a first DCI and / or a second DCI) and / or data (e.g., a first data and / or a second data) from the Network side (100 / 200 of FIG. 20) can be implemented by the device of FIG. 20, which will be described below. For example, referring to FIG. 2, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc. to receive DCI (e.g., a first DCI and / or a second DCI) and / or data (e.g., a first data and / or a second data), and one or more transceivers 106 can receive DCI (e.g., a first DCI and / or a second DCI) and / or data (e.g., a first data and / or a second data) from the Network side.

[0357] The UE can decode data received from the Network side via / using TRP 1 (and / or TRP 2) (e.g., first data and / or second data) (S1930). For example, the UE can perform channel estimation and / or decoding of data based on the above-described embodiments 1, 2, and / or 3.

[0358] For example, the operation of the UE (100 / 200 of FIG. 20) in step S2130 decoding the first data and / or the second data can be implemented by the device of FIG. 20, which will be described below. For example, referring to FIG. 20, one or more processors 102 can control one or more memories 104, etc. to perform the operation of decoding the first data and / or the second data.

[0359] The UE may transmit HARQ-ACK information (e.g., ACK information, NACK information, etc.) for the first data and / or the second data to the Network side through / using TRP 1 and / or TRP 2 (S1940, S2145). In this case, HARQ-ACK information for each of the first data or the second data may be transmitted to each TRP. Additionally, HARQ-ACK information for the first data and the second data may be combined into one. Furthermore, the UE may be configured to transmit only HARQ-ACK information to a representative TRP (e.g., TRP 1), and the transmission of HARQ-ACK information to other TRPs (e.g., TRP 2) may be omitted.

[0360] For example, the operation of the UE (100 / 200 of FIG. 20) in step S2140 / S2145 transmitting HARQ-ACK information for the first data and / or the second data from the Network side (100 / 200 of FIG. 20) can be implemented by the device of FIG. 20, which will be described below. For example, referring to FIG. 20, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc. to transmit HARQ-ACK information for the first data and / or the second data, and one or more transceivers 106 can transmit HARQ-ACK information for the first data and / or the second data to the Network side.

[0361] The aforementioned Network side / UE signaling and operation may be implemented by a device to be described below (e.g., the device of FIG. 20). For example, the Network side (e.g., TRP 1 / TRP 2) may correspond to the first wireless device and the UE may correspond to the second wireless device, and in some cases, the opposite case may also be considered.

[0362] For example, the above-described Network side / UE signaling and operation may be processed by one or more processors of FIG. 20 (e.g., 102, 202), and the above-described Network side / UE signaling and operation may be stored in memory (e.g., one or more memories of FIG. 20 (e.g., 104, 204)) in the form of an instruction / program (e.g., instruction, executable code) for driving at least one processor of FIG. 20 (e.g., 102, 202).

[0363] General devices to which the present disclosure may be applied

[0364] FIG. 20 is a drawing illustrating a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0365] Referring to FIG. 20, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR).

[0366] The first wireless device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memory (104) and / or transceivers (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation included in the present disclosure. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the signal processing of the second information / signal in the memory (104). The memory (104) may be connected 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 containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the descriptions, functions, procedures, proposals, methods, and / or sequence diagrams of operation included in the present disclosure. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be combined with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0367] The second wireless device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation included in the present disclosure. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or sequences of operation included in the present disclosure. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with an RF unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0368] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement 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 Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation included in the present disclosure. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation included in the present disclosure. One or more processors (102, 202) may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., a baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation included in the present disclosure.

[0369] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For 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 one or more processors (102, 202). Descriptions, functions, procedures, proposals, methods, and / or flowcharts of operations included in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences included in the present disclosure may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences included in the present disclosure may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0370] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0371] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of the present disclosure to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., included in the present disclosure from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation included in the present disclosure through one or more antennas (108, 208). In the present disclosure, one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0372] The embodiments described above are combinations of the components and features of the present disclosure in a specific form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, it is possible to construct embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment. It is obvious that embodiments may be constructed by combining claims that are not explicitly related in the claims, or that they may be included as new claims by amendment after filing.

[0373] It is obvious to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential features of the present disclosure. Accordingly, the detailed description set forth above should not be interpreted restrictively in all respects and should be considered exemplary. The scope of the present disclosure shall be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are included within the scope of the present disclosure.

[0374] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that enable operations according to the methods of various embodiments to be executed on a device or computer, and a non-transitory computer-readable medium on which such software or instructions, etc. are stored and executable on a device or computer. Instructions that may be used to program a processing system to perform the features described in the present disclosure may be stored on or within a storage medium or a computer-readable storage medium, and the features described in the present disclosure may be implemented using a computer program product comprising such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, 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 may optionally include one or more storage devices located remotely from the processor(s). Memory or alternatively, non-volatile memory device(s) within memory comprises a non-transient computer-readable storage medium. The features described in this disclosure may be stored in any one of the machine-readable media and integrated into software and / or firmware that can control the hardware of a processing system and allow the processing system to interact with other mechanisms utilizing results according to the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0375] Here, the wireless communication technology implemented in the wireless device (100, 200) of this specification may include LTE, NR, and 6G, as well as Narrowband Internet of Things for low-power communication. For example, 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, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in 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 names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) with consideration for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0376] Although the method proposed in this disclosure has been described with an example applied to 3GPP LTE / LTE-A and 5G systems, it can be applied to various wireless communication systems in addition to 3GPP LTE / LTE-A and 5G systems.

Claims

Claim 1 A method comprising: a step of receiving a physical downlink control channel (PDCCH) containing downlink control information (DCI) from a control resource set (CORESET) based on two transmission configuration indicator (TCI) states by a terminal; and a step of i) setting a single frequency network (SFN) scheme for the PDCCH and also setting an SFN scheme for a physical downlink shared channel (PDSCH) for the terminal, ii) the time offset between the reception of the DCI and the PDSCH scheduled based on the DCI is greater than or equal to a predetermined threshold, and iii) receiving the PDSCH from a network by the terminal based on two TCI states identical to the two TCI states for the CORESET, based on the fact that the DCI does not contain a TCI field. Claim 2 delete Claim 3 In claim 1, the method wherein the DCI is DCI format 1_0. Claim 4 delete Claim 5 A method according to claim 1, wherein the TCI state is associated with one or more Quasi Co-Location Reference Signals (QCL RS). Claim 6 A terminal comprises: one or more transceivers; and one or more processors connected to the one or more transceivers, wherein the one or more processors: receive a physical downlink control channel (PDCCH) containing downlink control information (DCI) from a control resource set (CORESET) through the one or more transceivers based on two transmission configuration indicator (TCI) states; and the terminal is configured to receive the PDSCH from a network through the one or more transceivers based on two TCI states identical to the two TCI states for the CORESET, based on i) the terminal being configured to have a single frequency network (SFN) scheme set for the PDCCH and also to have a single frequency network scheme set for a physical downlink shared channel (PDSCH), ii) the time offset between the reception of the DCI and the PDSCH scheduled based on the DCI being greater than or equal to a predetermined threshold, and iii) the terminal being configured to receive the PDSCH from a network through the one or more transceivers based on two TCI states identical to the two TCI states for the CORESET, based on the fact that the DCI does not contain a TCI field. Claim 7 A base station comprising: one or more transceivers; and one or more processors connected to the one or more transceivers, wherein the one or more processors: transmit a physical downlink control channel (PDCCH) containing downlink control information (DCI) from a control resource set (CORESET) to a terminal through the one or more transceivers based on two transmission configuration indicator (TCI) states; and i) a single frequency network (SFN) scheme is configured for the PDCCH to the terminal and also a single frequency network scheme is configured for the physical downlink shared channel (PDSCH), ii) the time offset between the reception of the DCI at the terminal and the PDSCH scheduled based on the DCI is greater than or equal to a predetermined threshold, and iii) the PDSCH is configured to transmit to the terminal through the one or more transceivers based on two TCI states identical to the two TCI states for the CORESET, based on the fact that the DCI does not contain a TCI field.

Images