Method and apparatus for transmitting or receiving downlink channels from multiple transmission reception points in a wireless communication system

Abstract

Disclosed is a method and apparatus for transmitting or receiving downlink channels from multiple transmission reception points (TRPs) in a wireless communication system. According to an embodiment of the present disclosure, a method for receiving a downlink signal by a terminal in a wireless communication system may include the steps of: repeatedly receiving a downlink control channel including the same downlink control information (DCI) from one or more TRPs at one or more transmission opportunities (TOs); and receiving a downlink signal from a single TRP based on the fact that the DCI includes control information related to downlink signal reception, the fact that a time interval between a specific TO among the one or more TOs and the reception of a downlink signal related to the DCI has a value less than a predetermined threshold, and a default transmission configuration indicator (TCI) state, wherein the default TCI state corresponds to a TCI state associated with a search space set or a control resource set (CORESET) having the lowest identifier in the latest time slot monitored by the terminal.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting or receiving a downlink channel from a plurality of transmission and reception points in the wireless communication system. Background Art

[0002] A mobile communication system has been developed to provide voice services while ensuring user mobility. However, the mobile communication system has been expanded to include data services as well as voice services, and currently, the explosive growth of services has led to a shortage of resources, and users have demanded faster services, thus requiring more advanced mobile communication systems.

[0003] The overall requirement for next-generation mobile communication systems is to support the accommodation of explosive data services, significantly increase the transmission rate per user, accommodate a significantly increased number of connected devices, provide very low end-to-end latency, and achieve high energy efficiency. To this end, various technologies have been studied, including dual connectivity, massive multiple-input multiple-output (Massive MIMO), in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and device networking. Summary of the Invention

[0004] Technical issues

[0005] The technical purpose of the present disclosure is to provide a method and device for transmitting or receiving downlink channels from multiple TRPs (MTRPs).

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

[0007] An additional technical object of the present disclosure is to provide a method and apparatus for transmitting or receiving a downlink signal from a single TRP (STRP) based on a downlink control channel transmitted from an MTRP.

[0008] An additional technical object of the present disclosure is to provide a method and apparatus for transmitting or receiving a downlink signal by applying or determining a transmission configuration indicator (TCI) for a downlink signal transmitted from a STRP based on a downlink control channel transmitted from an MTRP.

[0009] The technical objectives achieved by the present disclosure are not limited to the above-mentioned technical objectives, and other technical objectives not described herein will be clearly understood by those skilled in the relevant art from the following description.

[0010] Technical Solutions

[0011] According to one aspect of the present disclosure, a method for receiving a downlink signal by a terminal may include: repeatedly receiving a downlink control channel including the same downlink control information (DCI) from at least one transmission reception point (TRP) in at least one transmission opportunity (TO); and based on the DCI including control information related to downlink signal reception, based on the time offset between a specific TO of at least one TO and the reception timing of the downlink signal related to the DCI being less than a predetermined threshold, receiving the downlink signal from a single TRP based on a default transmission configuration indicator (TCI) state, and the default TCI state may be a TCI state related to a search space set or a control resource set (CORESET) having a lowest identifier in the latest time slot monitored by the terminal.

[0012] According to additional aspects of the present disclosure, a method for sending a downlink signal by a base station including a first TRP in a wireless communication system may include: repeatedly sending a downlink control channel including the same downlink control information (DCI) to a terminal in at least one transmission opportunity (TO) by the first TRP or by the first TRP and at least one other TRP; and sending a downlink signal to the terminal by the first TRP based on a default transmission configuration indicator (TCI) state based on the DCI including control information related to downlink signal reception, based on the time offset between a specific TO of at least one TO and the reception timing of the downlink signal related to the DCI being less than a predetermined threshold, and the default TCI state may be a TCI state related to a control resource set (CORESET) or a search space set having a lowest identifier in the latest time slot monitored by the terminal.

[0013] Technical Effects

[0014] 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.

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

[0016] According to an embodiment of the present disclosure, a method and apparatus for transmitting or receiving a downlink signal from a single TRP (STRP) based on a downlink control channel transmitted from an MTRP may be provided.

[0017] According to an embodiment of the present disclosure, a method and apparatus for transmitting or receiving a downlink signal by applying or determining a transmission configuration indicator (TCI) for a downlink signal transmitted from a STRP based on a downlink control channel transmitted from an MTRP may be provided.

[0018] According to an embodiment of the present disclosure, based on the downlink control channel transmitted from the MTRP, even when TCI information is not included in the downlink control channel, TCI associated with a downlink signal transmitted from the STRP may be clearly configured or determined.

[0019] Effects achievable by the present disclosure are not limited to the above-described effects, and those skilled in the art can clearly understand other effects not described herein through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are included as a part of the detailed description for understanding the present disclosure, provide embodiments of the present disclosure and describe technical features of the present disclosure through the detailed description.

[0021] Figure 1 The diagram shows a structure of a wireless communication system to which the present disclosure can be applied.

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

[0023] Figure 3 FIG2 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.

[0024] Figure 4 The figure illustrates physical resource blocks in a wireless communication system to which the present disclosure can be applied.

[0025] Figure 5 The diagram illustrates a time slot structure in a wireless communication system to which the present disclosure can be applied.

[0026] Figure 6 Physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the physical channels are illustrated.

[0027] Figure 7 The diagram illustrates a method for sending multiple TRPs in a wireless communication system to which the present disclosure may be applied.

[0028] Figure 8 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0029] Figure 9 is a diagram illustrating a mapping method between PDCCH transmission timing and TCI status according to an embodiment of the present disclosure.

[0030] Figure 10 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0031] Figure 11is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0032] Figure 12 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0033] Figure 13 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0034] Figure 14 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0035] Figure 15 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0036] Figure 16 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0037] Figure 17 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0038] Figure 18 is a diagram for describing the relationship between DCI and PDSCH to which the present disclosure can be applied.

[0039] Figure 19 is a diagram for describing a situation where multiple cells can be applied to the present disclosure.

[0040] Figure 20 It is a flowchart for describing a method in which a terminal according to the present disclosure receives PDSCH from a single TRP based on multiple PDCCHs.

[0041] Figure 21 It is a diagram for describing the signaling process of the network side and the terminal according to the present disclosure.

[0042] Figure 22 A block diagram of a wireless communication system according to an embodiment of the present disclosure is illustrated. DETAILED DESCRIPTION

[0043] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed 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 implemented. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the relevant art will appreciate that the present disclosure may be implemented without these specific details.

[0044] In some cases, well-known structures and devices may be omitted, or may be shown in the form of a block diagram based on the core functions of each structure and device in order to prevent ambiguity in the concepts of the present disclosure.

[0045] In the present disclosure, when an element is referred to as being "connected," "combined," or "linked" to another element, it may include an indirect connection relationship in which another element exists therebetween as well as a direct connection relationship. In addition, in the present disclosure, the terms "comprising" or "having" specify the presence of the mentioned features, steps, operations, components, and / or elements, but do not preclude the presence or addition of one or more other features, steps, operations, components, elements, and / or groups thereof.

[0046] In the present invention, terms such as "first," "second," etc. are used only to distinguish one element from another and are not used to limit the elements. Unless otherwise specified, they do not limit the order or importance of the elements. Therefore, within the scope of the present disclosure, the first element in one embodiment may be referred to as the second element in another embodiment, and similarly, the second element in one embodiment may be referred to as the first element in another embodiment.

[0047] The terms used in this disclosure are intended to describe specific embodiments and not to limit the claims. As used in the description of the embodiments and the appended claims, the singular is intended to include the plural, unless the context clearly indicates otherwise. The term "and / or" used in this disclosure may refer to one of the relevant enumerated items, or mean that it refers to and includes any and all possible combinations of two or more of them. In addition, unless otherwise indicated, the " / " between words in this disclosure has the same meaning as "and / or".

[0048] The present disclosure describes a wireless communication network or a wireless communication system, and operations performed in the wireless communication network can be performed in a process in which a device (e.g., a base station) controlling the corresponding wireless communication network controls the network and sends or receives signals, or can be performed in a process in which a terminal associated with the corresponding wireless network sends or receives signals between the network or the terminal.

[0049] In this disclosure, transmitting or receiving a channel includes the meaning of transmitting or receiving information or signals through the corresponding channel. For example, transmitting a control channel means transmitting control information or control signals through the control channel. Similarly, transmitting a data channel means transmitting data information or data signals through the data channel.

[0050] In the following, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, 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 expressed as a first communication device, and the terminal may be expressed as a second communication device. The base station (BS) may be replaced by terms such as a fixed station, a node B, an eNB (evolved node B), a gNB (next generation node B), a BTS (base transceiver system), an access point (AP), a network (5G network), an AI (artificial intelligence) system / module, an RSU (roadside unit), a robot, a drone (UAV: unmanned aerial vehicle), an AR (augmented reality) device, a VR (virtual reality) device, etc. In addition, the terminal can be fixed or mobile, and can be replaced by 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 (roadside unit), robot, AI (artificial intelligence) module, drone (UAV: unmanned aerial vehicle), AR (augmented reality) device, VR (virtual reality) device, etc.

[0051] The following description can be used for various radio access systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented through radio technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented through radio technologies such as GSM (Global System for Mobile Communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented through radio technologies such as IEEE802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802-20, E-UTRA (Evolved UTRA), etc. UTRA is part of 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 advanced version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE / LTE-A / LTE-A pro.

[0052] To make the description clearer, the description is based on the 3GPP communication system (e.g., LTE-A, NR), but the technical ideas of the present disclosure are not limited thereto. LTE means the technology after 3GPP TS (Technical Specification) 36.xxx Version 8. Specifically, the LTE technology in or after 3GPP TS 36.xxx Version 10 is called LTE-A, and the LTE technology in or after 3GPP TS 36.xxx Version 13 is called LTE-A pro. 3GPP NR means the technology in or after TS 38.xxx Version 15. LTE / NR can be referred to as a 3GPP system. "xxx" means the detailed number of the standard document. LTE / NR can generally be referred to as a 3GPP system. For the background technology, terms, abbreviations, etc. used to describe the present disclosure, reference can be made to the matters described in the standard documents disclosed before the present disclosure. For example, reference can be made to the following documents.

[0053] For 3GPP LTE, reference may be made to TS 36.211 (Physical Channels and Modulation), TS 36.212 (Multiplexing and Channel Coding), TS 36.213 (Physical Layer Procedures), TS 36.300 (General Description), and TS 36.331 (Radio Resource Control).

[0054] For 3GPP NR, you can 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 (NR and NG-RAN (Next Generation Radio Access Network) Overall Description), and TS 38.331 (Radio Resource Control Protocol Specification).

[0055] Abbreviations of terms that may be used in the present disclosure are defined as follows.

[0056] -BM: Beam Management

[0057] -CQI: Channel Quality Indicator

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

[0059] -CSI: Channel State Information

[0060] -CSI-IM: Channel State Information-Interference Measurement

[0061] -CSI-RS: Channel State Information-Reference Signal

[0062] -DMRS: Demodulation Reference Signal

[0063] -FDM: Frequency Division Multiplexing

[0064] -FFT: Fast Fourier Transform

[0065] -IFDMA: Interleaved Frequency Division Multiple Access

[0066] -IFFT: Inverse Fast Fourier Transform

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

[0068] -L1-RSRQ: Layer 1 reference signal reception quality

[0069] -MAC: Media Access Control

[0070] -NZP: Non-Zero Power

[0071] -OFDM: Orthogonal Frequency Division Multiplexing

[0072] -PDCCH: Physical Downlink Control Channel

[0073] -PDSCH: Physical Downlink Shared Channel

[0074] -PMI: Precoding Matrix Indicator

[0075] -RE: Resource Element

[0076] -RI: rank indicator

[0077] -RRC: Radio Resource Control

[0078] -RSSI: Received Signal Strength Indicator

[0079] -Rx: Receive

[0080] -QCL: Quasi-Colocated

[0081] -SINR: Signal to Interference and Noise Ratio

[0082] -SSB (or SS / PBCH block): Synchronization signal block (including PSS (Primary Synchronization Signal), SSS (Secondary Synchronization Signal) and PBCH (Physical Broadcast Channel))

[0083] -TDM: Time Division Multiplexing

[0084] -TRP: Transmit and Receive Point

[0085] -TRS: Tracking Reference Signal

[0086] -Tx: Send

[0087] -UE: User Equipment

[0088] -ZP: Zero Power

[0089] Overall system

[0090] As more communication devices require higher capacity, there has been a demand for improved mobile broadband communications compared to existing radio access technologies (RATs). In addition, large-scale MTC (machine type communication) that provides various services anytime and anywhere by connecting multiple devices and things is also one of the main issues to be considered in the next generation of communications. In addition, the design of communication systems considering services / terminals that are sensitive to reliability and latency is also discussed. Therefore, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), mMTC (massive MTC), URLLC (ultra-reliable low-latency communication), etc. is discussed, and for convenience, the corresponding technology is referred to as NR in this disclosure. NR is an expression representing an example of 5G RAT.

[0091] The new RAT system including NR uses an OFDM transmission method or a transmission method similar thereto. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system follows the parameters of the existing LTE / LTE-A as is, but may support a wider system bandwidth (e.g., 100 MHz). Alternatively, one cell may support multiple parameter sets. In other words, terminals operating according to different parameter sets may coexist in one cell.

[0092] A parameter set corresponds to one subcarrier spacing in the frequency domain. As the reference subcarrier spacing is scaled by an integer N, different parameter sets can be defined.

[0093] Figure 1 The diagram illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0094] refer to Figure 1 NG-RAN is configured with gNBs that provide the control plane (RRC) protocol side for the NG-RA (NG Radio Access) user plane (i.e., the new AS (Access Stratum) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and the UE. gNBs are interconnected via the Xn interface. In addition, gNBs are connected to the NGC (Next Generation Core) via the NG interface. More specifically, the gNB is connected to the AMF (Access and Mobility Management Power) via the N2 interface and to the UPF (User Plane Function) via the N3 interface.

[0095] Figure 2 The diagram illustrates a frame structure in a wireless communication system to which the present disclosure may be applied.

[0096] The NR system can support multiple parameter sets. Here, the parameter set can be defined by the subcarrier spacing and the cyclic prefix (CP) overhead. Here, multiple subcarrier spacings can be derived by scaling the basic (reference) subcarrier spacing by an integer N (or μ). In addition, although it is assumed that very low subcarrier spacing is not used in very high carrier frequencies, the parameter set used can be selected independently of the frequency band. In addition, various frame structures according to multiple parameter sets can be supported in the NR system.

[0097] The following describes the OFDM parameter sets and frame structures that can be considered in the NR system. The multiple OFDM parameter sets supported in the NR system can be defined as shown in Table 1 below.

[0098] [Table 1]

[0099] μ <![CDATA[Δf=2 μ ·15[kHz]]]> CP 0 15 normal 1 30 normal 2 60 Normal, Extended 3 120 normal 4 240 normal

[0100] NR supports multiple parameter sets (or subcarrier spacing (SCS)) for supporting various 5G services. For example, when the SCS is 15kHz, it supports wide areas of traditional cellular bands; when the SCS is 30kHz / 60kHz, it supports dense cities, lower latency and wider carrier bandwidth; and when the SCS is 60kHz or higher, it supports bandwidths exceeding 24.25GHz to overcome phase noise.

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

[0102] [Table 2]

[0103]

[0104] Regarding the frame structure in the NR system, the sizes of various fields in the time domain are expressed as T c =1 / (Δf max ·N f ) is a multiple of the time unit. Here, Δf max 480·10 3 Hz, and N f is 4096. Downlink and uplink transmissions are configured (organized) to have duration T f＝ 1 / (Δf max N f / 100)·T c =10ms radio frame. Here, the radio frame is configured with 10 subframes, each of which has T sf =(Δf max N f / 1000)·T c=1ms duration. In this case, there may be one frame set for uplink and one frame set for downlink. In addition, the transmission in the uplink frame numbered i from the terminal should be earlier than the corresponding downlink frame in the corresponding terminal by T TA =(N TA +N TA,offset )T c For subcarrier spacing configuration μ, the time slots in the subframe are n s μ ∈{0,...,N slot subframe,μ -1} and are numbered in increasing order in the radio frame by n s,f μ ∈{0,...,N slot frame,μ -1}. A time slot is configured with N symb slot consecutive OFDM symbols, and N symb slot Determined by CP. Slot n in a subframe s μ The beginning of the OFDM symbol n in the same subframe s μ N symb slot All terminals may not perform transmission and reception at the same time, which means that all OFDM symbols of a downlink time slot or an uplink time slot may not be used.

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

[0106] [Table 3]

[0107] μ <![CDATA[N symb slot ]]> <![CDATA[N slot frame,μ ]]> <![CDATA[N slot subframe,μ ]]> 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

[0108] [Table 4]

[0109] μ <![CDATA[N symb slot ]]> <![CDATA[N slot frame,μ ]]> <![CDATA[N slot subframe,μ ]]> 2 12 40 4

[0110] Figure 2 This is an example of μ=2 (SCS is 60kHz), see Table 3, 1 subframe can include 4 time slots. Figure 21 subframe = {1, 2, 4} slots shown in is an example, and the number of slots that can be included in 1 subframe is defined as in Table 3 or Table 4. In addition, a mini-slot may include 2, 4, or 7 symbols or more or less symbols.

[0111] Regarding the physical resources in the NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. can be considered. The following describes in detail the physical resources that can be considered in the NR system.

[0112] First, regarding antenna ports, they are defined so that the channel carrying symbols in that antenna port can be inferred from the channels carrying other symbols in the same antenna port. When large-scale properties of the channel carrying symbols in one antenna port can be inferred from the channel carrying symbols in another antenna port, the two antenna ports are said to be in a QC / QCL (quasi-co-located or quasi-co-located) relationship. In this case, the large-scale properties include at least one of delay spread, Doppler spread, frequency shift, average received power, and receive timing.

[0113] Figure 3 The diagram illustrates a resource grid in a wireless communication system to which the present disclosure may be applied.

[0114] refer to Figure 3 , which graphically depicts the resource grid configuration with N in the frequency domain RB μ N sc RB subcarriers, and one subframe is configured with 14·2 μ OFDM symbols, but not limited to this. In the NR system, the transmitted signal consists of 2 μ N symb (μ) OFDM symbols and N RB μ N sc RB Here, N RB μ ≤N RB max,μ . N RB max,μ represents the maximum transmission bandwidth, which may differ between uplink and downlink and between parameter sets. In this case, one resource grid can be configured for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element and is uniquely identified by an index pair (k, l'). Here, k = 0, ..., N RB μ N sc RB-1 is the index in the frequency domain, and l'=0,...,2 μ N symb (μ) -1 refers to the symbol position in the subframe. When referring to resource elements in a time slot, an index pair (k, l) is used. Here, l = 0, ..., N symb μ -1. The resource element (k, l') for μ and antenna port p corresponds to the complex value a k,l' (p,μ) When there is no risk of confusion or when no specific antenna port or parameter set is specified, the indices p and μ may be dropped and the complex value may be a k,l' (p) or a k,l' In addition, a resource block (RB) is defined as N in the frequency domain. sc RB =12 consecutive subcarriers.

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

[0116] -OffsetToPointA for the primary cell (PCell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping with the SS / PBCH block, which is used by the terminal for initial cell selection. It is expressed in resource blocks assuming a 15 kHz subcarrier spacing for FR1 and a 60 kHz subcarrier spacing for FR2.

[0117] -absoluteFrequencyPointA represents the frequency position of point A, expressed in ARFCN (Absolute Radio Frequency Channel Number).

[0118] For subcarrier spacing configuration μ, common resource blocks are numbered from 0 upwards in the frequency domain. The center of subcarrier 0 of common resource block 0 for subcarrier spacing configuration μ is the same as point A. Common resource block number n for subcarrier spacing configuration μ in the frequency domain CRB μ The relationship between and resource elements (k, l) is given as Equation 1 below.

[0119] [Equation 1]

[0120]

[0121] In Equation 1, k is defined relative to point A, so that k=0 corresponds to a subcarrier centered at point A. Physical resource blocks are numbered from 0 to N in a bandwidth part (BWP). BWP,i size,μ -1 numbering, and i is the number of the BWP. Physical resource block n in BWP iPRB and public resource block n CRB The relationship between is given by the following equation 2.

[0122] [Equation 2]

[0123]

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

[0125] Figure 4 The figure illustrates a physical resource block in a wireless communication system to which the present disclosure may be applied. Figure 5 The diagram illustrates a time slot structure in a wireless communication system to which the present disclosure may be applied.

[0126] refer to Figure 4 and Figure 5 , a slot includes multiple symbols in the time domain. For example, for a normal CP, 1 slot includes 7 symbols, but for an extended CP, 1 slot includes 6 symbols.

[0127] A carrier includes multiple subcarriers in the frequency domain. An RB (resource block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (bandwidth part) is defined as multiple consecutive (physical) resource blocks in the frequency domain and can correspond to a parameter set (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through activated BWPs, and only one BWP can be activated for a terminal. In the resource grid, each element is called a resource element (RE) and can map a complex symbol.

[0128] In the NR system, each component carrier (CC) can support up to 400MHz. If a terminal operating in such a wideband CC always operates with the radio frequency (FR) chip for the entire CC turned on, the terminal battery consumption may increase. Alternatively, when considering multiple application scenarios (e.g., eMBB, URLLC, Mmtc, V2X, etc.) operating in one wideband CC, different parameter sets (e.g., subcarrier spacing, etc.) can be supported in each frequency band in the corresponding CC. Alternatively, each terminal may have different capabilities for the maximum bandwidth. Taking this into account, the base station can instruct the terminal to operate only in part of the bandwidth instead of the full bandwidth of the wideband CC, and for convenience, the corresponding part of the bandwidth is defined as a bandwidth part (BWP). The BWP can be configured with continuous RBs on the frequency axis and can correspond to a parameter set (e.g., subcarrier spacing, CP length, slot / mini-slot duration).

[0129] Furthermore, even within a CC assigned to a terminal, a base station can configure multiple BWPs. For example, a BWP occupying a relatively small frequency domain can be configured in the PDCCH monitoring timeslot, while the PDSCH indicated by the PDCCH can be scheduled in a larger BWP. Alternatively, when a UE is congested in a specific BWP, other BWPs can be configured for some terminals for load balancing. Alternatively, to account for frequency-domain inter-cell interference cancellation between neighboring cells, some full-bandwidth middle spectrum can be excluded, and two edge BWPs can be configured in the same timeslot. In other words, a base station can configure at least one DL / UL BWP for a terminal associated with a wideband CC. The base station can activate at least one of the configured DL / UL BWPs at a specific time (via L1 signaling, MAC CE (Control Element), RRC signaling, etc.). Furthermore, the base station can instruct (via L1 signaling, MAC CE, RRC signaling, etc.) to switch to another configured DL / UL BWP. Alternatively, a timer can be used to switch to a specific DL / UL BWP upon expiration of the timer value. Here, the activated DL / UL BWP is defined as the active DL / UL BWP. However, when the terminal performs the initial access procedure or before establishing the RRC connection, the configuration of the DL / UL BWP may not be received, so the DL / UL BWP assumed by the terminal in these cases is defined as the initial active DL / UL BWP.

[0130] Figure 6 Physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the physical channels are illustrated.

[0131] In wireless communication systems, terminals receive information from base stations via downlinks and transmit information to base stations via uplinks. The information transmitted and received by base stations and terminals includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and receive.

[0132] When a terminal is turned on or newly enters a cell, it performs an initial cell search (S601), including synchronization with the base station. During the initial cell search, the terminal can synchronize with the base station by receiving the Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS) from the base station and obtain information such as the cell identifier (ID). The terminal can then obtain broadcast information in the cell by receiving the Physical Broadcast Channel (PBCH) from the base station. Simultaneously, the terminal can check the downlink channel status by receiving the Downlink Reference Signal (DL RS) during the initial cell search phase.

[0133] The terminal that has completed the initial cell search may obtain more detailed system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S602).

[0134] Meanwhile, when a terminal accesses a base station for the first time or has no radio resources for signal transmission, it may perform a random access (RACH) procedure on the base station (S603 to S606). For the random access procedure, the terminal may transmit a specific sequence as a preamble via a physical random access channel (PRACH) (S603 and S605), and may receive a response message to the preamble via the PDCCH and corresponding PDSCH (S604 and S606). The contention-based RACH may additionally perform a contention resolution procedure.

[0135] The terminal that then performs the above process can perform PDCCH / PDSCH reception (S607) and PUSCH (Physical Uplink Shared Channel) / PUCCH (Physical Uplink Control Channel) transmission (S608) as a general uplink / downlink signal transmission process. Specifically, the terminal receives downlink control information (DCI) via the PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format varies depending on its purpose of use.

[0136] At the same time, the control information sent 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. For the 3GPP LTE system, the terminal can send the above-mentioned CQI / PMI / RI and other control information via PUSCH and / or PUCCH.

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

[0138] [Table 5]

[0139]

[0140] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information (e.g., UL / SUL (supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), information related to transport blocks (TBs) (e.g., MCS (modulation and coding scheme), NDI (new data indicator), RV (redundancy version)), etc.), information related to HARQ (hybrid-automatic repeat and request) (e.g., process number, DAI (downlink assignment index), PDSCH-HARQ feedback timing, etc.), information related to multi-antennas (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), power control information related to PUSCH scheduling (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined.

[0141] DCI format 0_0 is used to schedule PUSCH in one cell. Information included in DCI format 0_0 is scrambled by CRC (Cyclic Redundancy Check) using C-RNTI (Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation and Coding Scheme Cell RNTI) and transmitted.

[0142] DCI format 0_1 is used to indicate scheduling or configuration grant (CG) downlink feedback information for one or more PUSCHs to the terminal in a cell. The information included in DCI format 0_1 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, SP-CSI-RNTI (semi-persistent CSI RNTI), or MCS-C-RNTI.

[0143] DCI format 0_2 is used to schedule a PUSCH in one cell. Information included in DCI format 0_2 is scrambled by CRC using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI and transmitted.

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

[0145] DCI format 1_0 is used to schedule a PDSCH in one DL cell. Information included in DCI format 1_0 is scrambled by CRC using C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.

[0146] DCI format 1_1 is used to schedule a PDSCH in one cell. Information included in DCI format 1_1 is scrambled by CRC using C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.

[0147] DCI format 1_2 is used to schedule PDSCH in one cell. Information included in DCI format 1_2 is scrambled by CRC using C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.

[0148] Operations related to multiple TRPs

[0149] The Coordinated Multi-Point (CoMP) scheme is a scheme in which multiple base stations exchange or utilize channel information (e.g., RI / CQI / PMI / LI (layer indicator)) fed back by a terminal (e.g., using the X2 interface) and cooperatively transmit it to the terminal to effectively control interference. Depending on the scheme used, CoMP can be categorized into joint transmission (JT), coordinated scheduling (CS), coordinated beamforming (CB), dynamic point selection (DPS), dynamic point blocking (DPB), etc.

[0150] The M-TRP transmission scheme in which M TRPs send data to one terminal can be mainly classified into i) eMBB M-TRP transmission, a scheme for improving the transmission rate, and ii) URLLC M-TRP transmission, a scheme for increasing the reception success rate and reducing the delay.

[0151] In addition, regarding DCI transmission, M-TRP transmission schemes can be classified into i) M-TRP transmission based on M-DCI (multiple DCIs), where each TRP transmits different DCIs, and ii) M-TRP transmission based on S-DCI (single DCI), where one TRP transmits DCI. For example, for S-DCI-based M-TRP transmission, all scheduling information about data transmitted by M TRPs should be delivered to the terminal through one DCI, which can be used in an ideal backhaul (ideal BH) environment where dynamic collaboration between two TRPs is possible.

[0152] For TDM-based URLLC M-TRP transmission, Schemes 3 / 4 are being discussed for standardization. Specifically, Scheme 4 refers to a scheme in which one TRP transmits a transport block (TB) in one time slot, and has the effect of increasing the probability of data reception by receiving the same TB from multiple TRPs in multiple time slots. Meanwhile, Scheme 3 refers to a scheme in which one TRP transmits a TB through a continuous number of OFDM symbols (i.e., a symbol group), and the TRP can be configured to transmit the same TB through different symbol groups in one time slot.

[0153] In addition, the UE can identify the PUSCH (or PUCCH) scheduled by the DCI received in different control resource sets (CORESETs) (or CORESETs belonging to different CORESET groups) as the PUSCH (or PUCCH) sent to different TRPs, or can identify the PDSCH (or PDCCH) from different TRPs. In addition, the method described below for UL transmissions (e.g., PUSCH / PUCCH) sent to different TRPs can be equivalently applied to UL transmissions (e.g., PUSCH / PUCCH) sent to different panels belonging to the same TRP.

[0154] Hereinafter, non-coherent joint transmission (NCJT) based on multiple DCIs / NCJT based on a single DCI will be described.

[0155] NCJT (Non-coherent Joint Transmission) is a scheme in which multiple transmission points (TPs) transmit data to one terminal by using the same time-frequency resources, and the TPs transmit data through different layers (i.e., through different DMRS ports) using different DMRS (Demodulation Multiplexing Reference Signals) between TPs.

[0156] TP delivers data scheduling information to the terminal receiving NCJT through DCI. Here, a scheme in which each TP participating in NCJT delivers scheduling information about the data sent by itself through DCI is called "NCJT based on multiple DCIs". Since each of the N TPs participating in NCJT transmission sends a DL grant DCI and a PDSCH to the UE, the UE receives N DCIs and N PDSCHs from the N TPs. At the same time, a scheme in which one representative TP delivers scheduling information about the data sent by itself and the data sent by different TPs (i.e., the TPs participating in NCJT) through one DCI is called "NCJT based on a single DCI". Here, N TPs send one PDSCH, but each TP sends only some layers of the multiple layers included in one PDSCH. For example, when sending 4 layers of data, TP 1 can send 2 layers to the UE, and TP 2 can send the remaining 2 layers to the UE.

[0157] By using either of the following two schemes, multiple TRPs (MTRPs) performing NCJT transmission can send DL data to the terminal.

[0158] First, the "MTRP scheme based on a single DCI" is described. The MTRP transmits one common PDSCH cooperatively, and each TRP participating in the cooperative transmission spatially divides and transmits the corresponding PDSCH to different layers (i.e., different DMRS ports) by using the same time-frequency resources. Here, the scheduling information about the PDSCH is indicated to the UE through one DCI, and which DMRS (group) port uses which QCL RS, and the QCL type information is indicated by the corresponding DCI (which is different from the DCI indicating the QCL RS and type to be commonly applied to all DMRS ports as indicated in the existing scheme). In other words, M TCI states (for example, M=2 for 2 TRP cooperative transmission) can be indicated by the TCI (Transmission Configuration Indicator) field in the DCI, and the QCL RS and type can be indicated by using M different TCI states for M DMRS port groups. In addition, the DMRS port information can be indicated by using a new DMRS table.

[0159] Next, the "multi-DCI based MTRP scheme" is described. Each MTRP transmits different DCI and PDSCH, and (part or all of) the corresponding PDSCHs overlap with each other and are transmitted in frequency-time resources. The corresponding PDSCHs may be scrambled by different scrambling IDs (identifiers), and DCI may be transmitted by CORESETs belonging to different CORESET groups. (Here, a CORESET group may be identified by an index defined in the CORESET configuration of each CORESET. For example, when index = 0 is configured for CORESET 1 and 2 and index = 1 is configured for CORESET 3 and 4, CORESET 1 and 2 are CORESET group 0, and CORESET 3 and 4 belong to CORESET group 1. In addition, when an index is not defined in a CORESET, it may be interpreted as index = 0.) When multiple scrambling IDs are configured in one serving cell or two or more CORESET groups are configured, the UE may notice that it receives data according to the multi-DCI based MTRP operation.

[0160] Alternatively, the UE may be informed by separate signaling whether to use a single DCI-based MTRP scheme or a multiple DCI-based MTRP scheme. In this example, for one serving cell, multiple CRS (cell reference signal) patterns for MTRP operation may be indicated to the UE. In this case, the PDSCH rate matching for CRS may be different depending on whether the MTRP scheme is based on a single DCI or the MTRP scheme is based on multiple DCIs (because the CRS patterns are different).

[0161] Hereinafter, the CORESET group ID described / mentioned in the present disclosure may refer to an index / identification information (e.g., ID, etc.) of a CORESET that is distinguished for each TRP / panel. In addition, a CORESET group may be a group / union of CORESETs that are distinguished by an index / identification information (e.g., ID) / CORESET group ID, etc. that is distinguished for each TRP / panel. In an example, the CORESET group ID may be specific index information defined in the CORESET configuration. In this case, the CORESET group may be configured / indicated / defined by an index defined in the CORESET configuration for each CORESET. Additionally / alternatively, the CORESET group ID may refer to an index / identification information / indicator, etc. that is used to distinguish / identify between CORESETs that are configured / associated with each TRP / panel. Hereinafter, the CORESET group ID described / mentioned in the present disclosure may be represented by being replaced with a specific index / specific identification information / specific indicator that is used to distinguish / identify between CORESETs that are configured / associated with each TRP / panel. The CORESET group ID, i.e., a specific index / specific identification information / specific indicator for distinguishing / identifying between CORESETs configured / associated with each TRP / panel, may be configured / indicated to the terminal through higher layer signaling (e.g., RRC signaling) / L2 signaling (e.g., MAC-CE) / L1 signaling (e.g., DCI), etc. In an example, it may be configured / indicated that PDCCH detection is performed per TRP / panel (i.e., per TRP / panel belonging to the same CORESET group) in units of the corresponding CORESET group. Additionally / alternatively, it may be configured / indicated that 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) are separated and managed / controlled per TRP / panel (i.e., per TRP / panel belonging to the same CORESET group) in units of the corresponding CORESET group. Additionally / alternatively, HARQ A / N (processing / retransmission) for PDSCH / PUSCH, etc. scheduled per TRP / panel may be managed per corresponding CORESET group (ie, per TRP / panel belonging to the same CORESET group).

[0162] Hereinafter, a partially overlapping NCJT will be described.

[0163] In addition, NCJT can be classified into fully overlapping NCJT in which the time-frequency resources transmitted by each TP completely overlap, and partially overlapping NCJT in which only some time-frequency resources overlap. In other words, for partially overlapping NCJT, data of both TP 1 and TP 2 is transmitted in some time-frequency resources, and data of only one TP, TP 1 or TP 2, is transmitted in the remaining time-frequency resources.

[0164] Hereinafter, a method for improving reliability in multi-TRP will be described.

[0165] As a sending and receiving method for improving reliability using transmission in multiple TRPs, the following two methods can be considered.

[0166] Figure 7 The diagram illustrates a method for multi-TRP transmission in a wireless communication system to which the present disclosure can be applied.

[0167] refer to Figure 7 (a) shows a case where layer groups transmitting the same codeword (CW) / transport block (TB) correspond to different TRPs. Here, a layer group may refer to a predetermined set of layers including one or more layers. In this case, there are the following advantages: the amount of transmission resources increases due to the number of layers, so that robust channel coding with a low coding rate can be used for the TBs, and additionally, because the multiple TRPs have different channels, the reliability of the received signal can be expected to be improved due to diversity gain.

[0168] refer to Figure 7 (b) shows an example of sending different CWs through layer groups corresponding to different TRPs. Here, it can be assumed that the TBs corresponding to CW#1 and CW#2 in the figure are the same. In other words, CW#1 and CW#2 refer to the same TBs that are transformed into different CWs by different TRPs through channel coding, etc. Therefore, it can be regarded as an example of repeatedly sending the same TB. Figure 7 (b) In the case of Figure 7 Compared with (a), the disadvantage is that the code rate corresponding to the TB is higher. However, the advantage is that the code rate can be adjusted by indicating different RV (Redundancy Version) values, or the modulation order of each CW of the coded bits generated by the same TB can be adjusted according to the channel environment.

[0169] According to the above Figure 7 (a) and Figure 7The method shown in (b) can improve the data reception probability of the terminal because the same TB is repeatedly sent through different layer groups, and each layer group is sent by a different TRP / panel. It is called the M-TRP URLLC transmission method based on SDM (spatial division multiplexing). Layers belonging to different layer groups are transmitted separately through DMRS ports belonging to different DMRS CDM groups.

[0170] In addition, the above content related to multiple TRPs is described based on the SDM (spatial division multiplexing) method using different layers, but it can be naturally extended and applied to the FDM (frequency division multiplexing) method based on different frequency domain resources (e.g., RB / PRB (sets), etc.) and / or the TDM (time division multiplexing) method based on different time domain resources (e.g., time slots, symbols, sub-symbols, etc.).

[0171] Regarding the method for URLLC based on multiple TRPs scheduled by a single DCI, the following method is discussed.

[0172] 1) Method 1 (SDM): Time and frequency resource allocation are overlapping, and there are n (n<=Ns) TCI states in a single time slot

[0173] 1-a) Method 1a

[0174] - The same TB is transmitted in one layer or one layer set at each transmission time (opportunity), and each layer or each layer set is associated with one TCI and one DMRS port set.

[0175] - Use a single codeword with one RV in all spatial layers or all layer sets. With respect to the UE, different coded bits are mapped to different layers or layer sets by using the same mapping rule.

[0176] 1-b) Method 1b

[0177] - The same TB is transmitted in one layer or one layer set at each transmission time (opportunity), and each layer or each layer set is associated with one TCI and one DMRS port set.

[0178] - Use a single codeword with one RV in each spatial layer or each layer set. The RV(s) corresponding to each spatial layer or each layer set may be the same or different.

[0179] 1-c) Method 1c

[0180] - At one transmission time (opportunity), 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.

[0181] In the case of methods 1a and 1c, the same MCS is applied to all layers or all layer sets.

[0182] 2) Method 2 (FDM): Frequency resource allocation does not overlap, and there are n (n<=Nf) TCI states in a single time slot

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

[0184] - The same single / multiple DMRS ports are associated with all non-overlapping frequency resource allocations.

[0185] 2-a) Method 2a

[0186] - A single codeword with one RV is used for all resource allocations. With respect to the UE, a common RB matching (codeword to layer mapping) is applied to all resource allocations.

[0187] 2-b) Method 2b

[0188] - A single codeword with one RV is used for each non-overlapping frequency resource allocation. The RV corresponding to each non-overlapping frequency resource allocation can be the same or different.

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

[0190] 3) Method 3 (TDM): Time resource allocation does not overlap, and there are n (n<=Nt1) TCI states in a single time slot

[0191] -Each transmission time (opportunity) of a TB has a time granularity of a mini-slot and has a TCI and an RV.

[0192] - At each transmission time (opportunity) in a time slot, a common MCS is used with single or multiple DMRS ports.

[0193] -RV / TCI can be the same or different at different transmission times (opportunities).

[0194] 4) Method 4 (TDM): n (n <= Nt2) TCI states in K (n <= K) different time slots

[0195] - Each transmission time (opportunity) of a TB has a TCI and a RV.

[0196] - Each transmission time (opportunity) across K time slots uses a common MCS with single or multiple DMRS ports.

[0197] -RV / TCI can be the same or different at different transmission times (opportunities).

[0198] Hereinafter, MTRP URLLC is described.

[0199] In the present disclosure, DL MTRP URLLC refers to multiple TRPs sending the same data (e.g., the same TB) / DCI by using different layer / time / frequency resources. For example, TRP 1 sends the same data / DCI in resource 1, and TRP2 sends the same data / DCI in resource 2. A UE configured with the DL MTRP-URLLC transmission method receives the same data / DCI by using different layer / time / frequency resources. Here, the UE is configured from the base station with which QCL RS / type (i.e., DL TCI state) should be used in the layer / time / frequency resources for receiving the same data / DCI. For example, when the same data / DCI is received in resource 1 and resource 2, the DL TCI state used in resource 1 and the DL TCI state used in resource 2 can be configured. The UE can achieve high reliability because it receives the same data / DCI through resource 1 and resource 2. This DL MTRPURLLC can be applied to PDSCH / PDCCH.

[0200] And, in the present disclosure, UL MTRP-URLLC means that multiple TRPs receive the same data / UCI (uplink control information) from any UE by using different layer / time / frequency resources. For example, TRP 1 receives the same data / DCI from the UE in resource 1, and TRP 2 receives the same data / DCI from the UE in resource 2 to share the received data / DCI through the backhaul link connected between the TRPs. UEs configured with the UL MTRP-URLLC transmission method send the same data / UCI by using different layer / time / frequency resources. In this case, the UE is configured from the base station with which Tx beam and which Tx power (i.e., UL TCI state) should be used in the layer / time / frequency resources for sending the same data / DCI. For example, when the same data / UCI is sent in resource 1 and resource 2, the UL TCI state used in resource 1 and the UL TCI state used in resource 2 can be configured. This UL MTRP URLLC can be applied to PUSCH / PUCCH.

[0201] In addition, in the present disclosure, when a specific TCI state (or TCI) is used (or mapped) when receiving data / DCI / UCI for any frequency / time / space resource (layer), its meaning is as follows. For DL, this may mean estimating the channel from the DMRS using the QCL type and QCL RS indicated by the corresponding TCI state in the frequency / time / space resource (layer), and receiving / demodulating the data / DCI based on the estimated channel. In addition, for UL, this may mean transmitting / modulating the DMRS and data / UCI in the frequency / time / space resource (layer) using the Tx beam and power indicated by the corresponding TCI state.

[0202] Here, the UL TCI state has the Tx beam and / or Tx power information of the UE, and spatial relationship information, etc. can be configured to the UE through other parameters instead of the TCI state. The UL TCI state can be directly indicated by the UL grant DCI, or it can refer to the spatial relationship information of the SRS resource indicated by the SRI (sounding resource indicator) field of the UL grant DCI. Alternatively, it can refer to the open-loop (OL) Tx power control parameter connected with the value indicated by the SRI field of the UL grant DCI (for example, j: index of open-loop parameters Po and alpha (up to 32 parameter value sets per cell), q_d: index of DL RS resource for PL (path loss) measurement (up to 4 measurements per cell), l: closed-loop power control process index (up to 2 processes per cell)).

[0203] Hereinafter, MTRP eMBB is described.

[0204] In the present disclosure, MTRP-eMBB refers to multiple TRPs that transmit different data (e.g., different TBs) using different layers / times / frequencies. A UE configured with the MTRP-eMBB transmission method receives an indication of multiple TCI states through DCI, and assumes that the data received using the QCL RS of each TCI state is different data.

[0205] On the other hand, the UE can distinguish between MTRP URLLC transmission / reception and MTRP eMBB transmission / reception by dividing the RNTI for MTRP-URLLC and the RNTI for MTRP-eMBB respectively and using them. In other words, when the CRC masking of the DCI is performed by using the RNTI for URLLC, the UE regards it as URLLC transmission, and when the CRC masking of the DCI is performed by using the RNTI for eMBB, the UE regards it as eMBB transmission. Alternatively, the base station can configure MTRP URLLC transmission / reception or TRP eMBB transmission / reception to the UE through other new signaling.

[0206] In the description of the present disclosure, for ease of description, the description is made by assuming collaborative transmission / reception between 2 TRPs, but the method proposed in the present disclosure can also be extended and applied in 3 or more TRP environments, and in addition, can also be extended and applied in multiple panel environments (i.e., by matching TRPs to panels). In addition, different TRPs can be identified as different TCI states from the UE. Therefore, when the UE receives / sends data / DCI / UCI by using TCI state 1, it refers to receiving / sending data / DCI / UCI from / to TRP 1.

[0207] Hereinafter, the method proposed in the present disclosure may be utilized when MTRP collaboratively transmits PDCCH (repeatedly transmits or partially transmits the same PDCCH). In addition, the method proposed in the present disclosure may also be used when MTRP collaboratively transmits PDSCH or collaboratively receives PUSCH / PUCCH.

[0208] In addition, in the present disclosure, when multiple base stations (ie, MTRP) repeatedly transmit the same PDCCH, this may refer to sending the same DCI through multiple PDCCH candidates, and may also refer to multiple base stations repeatedly transmitting the same DCI. Here, the same DCI may refer to two DCIs with the same DCI format / size / payload. Alternatively, although the two DCIs have different payloads, they can be considered to be the same DCI when the scheduling results are the same. For example, the TDRA (time domain resource allocation) field of the DCI relatively determines the time slot / symbol position of the data and the time slot / symbol position of A / N (ACK / NACK) based on the reception timing of the DCI, so if the DCI received at n times and the DCI received at n+1 times inform the UE of the same scheduling result, the TDRA fields of the two DCIs are different, and therefore, the DCI payloads are different. The number of repetitions R can be directly indicated by the base station or mutually agreed to the UE. Alternatively, even though two DCIs have different payloads and different scheduling results, if the scheduling result of one DCI is a subset of the scheduling result of the other DCI, they can be considered to be the same DCI. For example, when the same data is repeatedly transmitted N times via TDM, DCI 1 received before the first data indicates N data repetitions, and DCI 2 received after the first data and before the second data indicates N-1 data repetitions. The scheduled data of DCI 2 is a subset of the scheduled data of DCI 1, and since both DCIs are scheduling the same data, they can be considered to be the same DCI in this case.

[0209] In addition, in the present disclosure, when multiple base stations (ie, MTRPs) partially transmit the same PDCCH, it means that one DCI is transmitted through one PDCCH candidate, but TRP 1 transmits some resources defining such a PDCCH candidate, and TRP 2 transmits the remaining resources. One PDCCH candidate separately transmitted by multiple base stations (ie, MTRPs) can be indicated to the terminal (UE) through the configuration described below, or can be recognized or determined by the terminal.

[0210] In addition, in the present disclosure, when the UE repeatedly transmits the same PUSCH so that multiple base stations (i.e., MTRPs) can receive it, this may mean that the UE transmits the same data through multiple PUSCHs. In this case, each PUSCH can be optimized and sent to UL channels of different TRPs. For example, when the UE repeatedly transmits the same data through PUSCH 1 and 2, PUSCH 1 is transmitted by using UL TCI state 1 for TRP 1, and in this case, link adaptation such as precoder / MCS, etc. can also be scheduled / applied to the channel-optimized value for TRP 1. PUSCH 2 is transmitted by using UL TCI state 2 for TRP 2, and link adaptation such as precoder / MCS, etc. can also be scheduled / applied to the channel-optimized value for TRP 2. In this case, the repeatedly transmitted PUSCH 1 and 2 can be transmitted at different times to be TDM, FDM, or SDM.

[0211] In addition, in the present disclosure, when a UE transmits the same PUSCH separately so that multiple base stations (i.e., MTRPs) can receive it, this may mean that the UE transmits one data item via one PUSCH, but divides the resources allocated to the PUSCH, optimizes them for UL channels of different TRPs, and transmits them. For example, when a UE transmits the same data via a 10-symbol PUSCH, the data is transmitted using UL TCI state 1 for TRP 1 in the first five symbols, and in this case, link adaptation such as precoder / MCS can also be scheduled / applied to the channel-optimized values for TRP 1. The remaining data is transmitted using UL TCI state 2 for TRP 2 in the remaining five symbols, and in this case, link adaptation such as precoder / MCS can also be scheduled / applied to the channel-optimized values for TRP 2. In this example, transmission for TRP 1 and transmission for TRP 2 are time-divided by dividing one PUSCH into time resources, but can be transmitted using FDM / SDM methods.

[0212] In addition, similar to the above-mentioned PUSCH transmission, also for PUCCH, the UE can repeatedly transmit the same PUCCH, or can transmit the same PUCCH separately so that multiple base stations (ie, MTRP) receive it.

[0213] Hereinafter, the proposal of the present disclosure may be extended and applied to various channels such as PUSCH / PUCCH / PDSCH / PDCCH, etc.

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

[0215] If the method of transmitting the same DCI by using different PDCCH candidates in MTRP is extended, the PDCCH candidates that transmit the same DCI from each TRP can be transmitted using different TCI states. In this case, a specific definition of CORESET on each PDCCH candidate, a search space (SS) set configuration method, etc. are required.

[0216] Example 1)

[0217] Embodiment 1 describes a method in which multiple base stations (ie, MTRP) repeatedly transmit PDCCHs.

[0218] Embodiment 1 describes a method in which multiple base stations (ie, MTRP) repeatedly transmit PDCCHs.

[0219] When multiple base stations (i.e., MTRP) repeatedly transmit PDCCHs, the number of repeated transmissions R can be directly indicated to the UE by the base station, or can be mutually agreed upon. Here, the number of repeated transmissions R is mutually agreed upon, and the number of repeated transmissions R can be determined based on the number of TCI (Transmission Configuration Indication) states configured for repeated transmission of the same PDCCH. For example, if the base station configures r TCI states to repeatedly transmit the same PDCCH to the UE, R=r can be agreed upon. Here, for example, R=M*r can be configured, and the base station can indicate M to the UE.

[0220] When multiple base stations (i.e., MTRPs) repeatedly send the same PDCCH, TRP 1 can send DCI through PDCCH candidate 1, and TRP 2 can send DCI through PDCCH candidate 2. The mapping order of TRPs and PDCCH candidates is only for ease of description and does not limit the technical scope of the present disclosure. Each PDCCH candidate is sent by a different TRP, so each PDCCH candidate is received by using a different TCI state. Here, for PDCCH candidates sending the same DCI, part or all of the scrambling / aggregation level, CORESET, and search space (SS) set of the PDCCH may be different.

[0221] Two (or two or more) PDCCH candidates repeatedly transmitted by multiple base stations (ie, MTRP) may be identified / indicated to the UE through the following configuration.

[0222] For ease of description, the following example uses two PDCCH candidates to transmit or receive the same DCI. However, the present disclosure can be extended and applied even when the same DCI is transmitted or received via three or more PDCCH candidates. In this case, reliability can be improved. For example, TRP 1 can transmit the same DCI via PDCCH candidates 1 and 2, and TRP 2 can transmit the same DCI via PDCCH candidates 3 and 4.

[0223] In addition, for (one or more) SS sets in which multiple base stations (i.e., MTRPs) 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 the same PDCCH may not be repeatedly transmitted for the remaining DCI formats / SS / RNTI types, which may be indicated by the base station to the UE. For example, the base station may indicate to the UE that repeated transmission is performed only for format 1-0 (or 1-1) of the SS set for which both DCI formats 1-0 and 1-1 are defined. Alternatively, the base station may indicate to the UE that repeated transmission is performed only for the public SS (or UE-specific SS) among the UE-specific SS and the public SS. Alternatively, the base station may indicate to the UE that repeated transmission is performed only for the public SS (or UE-specific SS) and the common SS among the specific SS. Alternatively, the base station may specify to the UE that the same PDCCH is repeatedly transmitted only for the DCI CRC masked with a specific RNTI (e.g., RNTI excluding C-RNTI, MCS-C-RNTI, CS-RNTI).

[0224] Example 1-1) Two PDCCH candidates sending the same DCI share one (same) CORESET, but can Defined / configured in different SS collections.

[0225] Figure 8is a diagram of a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0226] refer to Figure 8 , PDCCH candidate 1 may be transmitted by using TCI state 1, and PDCCH candidate 2 may be transmitted by using TCI state 2. In addition, the same DCI may be transmitted through PDCCH candidate 1 and PDCCH candidate 2, respectively. In addition, both PDCCH candidate 1 and PDCCH candidate 2 may be (repeatedly) transmitted at specific periodic intervals in the time domain.

[0227] Each PDCCH candidate shares the same CORESET but can be defined / configured in different SS sets. In addition, TCI state 1 of the two TCI states configured for the same CORESET 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.

[0228] In the current standard, a CORESET ID is configured in an SS set, and the corresponding SS set and the CORESET are connected. According to an embodiment of the present disclosure, one CORESET can be connected (mapped) to multiple TCI states (e.g., two TCI states). In this case, information on whether or not to use which of the two TCIs of the corresponding CORESET to decode the PDCCH can be defined / configured together with the CORESET ID used in the configuration of the SS set.

[0229] In addition, the base station can inform the UE of the timing (TO: transmission timing) at which the PDCCH candidates of SS set 1 and SS set 2 corresponding to the same DCI are transmitted / received. This can be defined / referred to as a window for transmitting the same DCI. For example, the base station can indicate to the UE that SS set 1 and SS set 2 defined in the same time slot as the UE (i.e., window = 1 time slot) are SS sets for transmitting the same DCI, or it can be mutually agreed upon between the base station and the UE.

[0230] More generally, the window (eg, 1 time slot) for sending the same DCI may be indicated by the base station to the UE, or may be mutually agreed upon between the base station and the UE.

[0231] For example, such a window (e.g., n times) can be mutually agreed upon between the base station and the UE, or can be configured by the base station to the UE to begin at each TO (PDCCH candidate transmission opportunity) of a standard set (e.g., the lowest ID (identifier) SS set) defined as one of the SS sets transmitting the same DCI. Here, if the TO of the lowest ID SS set appears multiple times within a window, the windows may overlap. To prevent this, subsequent (n+1) windows can be defined / configured based on the TO of the lowest ID SS set not included in the specific (n) window. Furthermore, N windows can desirably be defined for each period of the standard set (e.g., the lowest ID SS set). Here, N can be indicated by the base station to the UE. For example, when the period is 10 slots, the SS sets are defined in the first, second, and third slots of the 10 slots, the window is 1 slot, and N is 2. Each window can be defined in the first and second slots during the period of each lowest ID SS set.

[0232] Hereinafter, a PDCCH TO and TCI mapping method in one window is described.

[0233] Figure 9 is a diagram illustrating a mapping method between PDCCH transmission timing and TCI status according to an embodiment of the present disclosure.

[0234] There are multiple PDCCH TOs in a window, and different TCI states can be mapped to each TO. Here, the following two methods can be considered through the mapping method of TO and TCI.

[0235] First, as TO increases in the window (in ascending order), TCI states can be mapped sequentially in a cyclic manner. For example, when N TOs and M TCI states are indicated in the window, the i-th TO can be mapped to the i-th TCI, and for N>M, the first TCI and the second TCI can be sequentially mapped to the M+1-th TO and the M+2-th TO, respectively. For example, Figure 9 As shown in (a), it is assumed that 6 PDCCH TOs are configured in one window and 2 TCI states are configured. In this case, in one window, the first PDCCH TO can be mapped to the first TCI state, the second PDCCH TO can be mapped to the second TCI state, the third PDCCH TO can be mapped to the first TCI state, the fourth PDCCH TO can be mapped to the second TCI state, the fifth PDCCH TO can be mapped to the first TCI state, and the sixth PDCCH TO can be mapped to the second TCI state.

[0236] Alternatively, secondly, the groups and TCI states can be sequentially mapped in a round-robin manner 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 in the window. In other words, 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, Figure 9 As shown in (b), it is assumed that 6 PDCCH TOs are configured in one window and 2 TCI states are configured. In addition, it is assumed that the first to third PDCCH TOs are grouped into a first group, and the fourth to sixth PDCCH TOs are grouped into a second group. In this case, in one window, the first TCI state can be mapped to the first to third PDCCH TOs (i.e., the first group), and the second TCI state can be mapped to the fourth to sixth PDCCH TOs (i.e., the second group).

[0237] For the general case of repeatedly transmitting PDCCH at different times (e.g., Embodiments 1-3) or transmitting PDCCH separately at different times, as well as the case in the above-mentioned Embodiment 1-1, this mapping method between TO and TCI can be applied to the mapping between TO and TCI in the same window. In other words, the above-mentioned same mapping method between TO and TCI can be applied to all cases where different PDCCH candidates (with different TCI states applied) are transmitted at different TOs in the same window.

[0238] The above-described embodiment 1-1 can be configured as a special case in embodiment 1-3 described later. In other words, for the method of configuring CORESETs 1 and 2 and SS sets 1 and 2 as in embodiment 1-3, the case where CORESETs 1 and 2 are configured to be identical (however, the CORESET IDs and TCI states defined in the CORESETs are different) is no different from embodiment 1-1 in which one CORESET, two SS sets, and two TCIs are configured. Therefore, when CORESETs 1 and 2 are configured to be identical in embodiment 1-3, the same PDCCH can be repeatedly transmitted using the same method as in embodiment 1-1.

[0239] Example 1-2) You can define / configure the send function in one (same) CORESET and one (same) SS set. Send two PDCCH candidates with the same DCI .

[0240] Figure 10 is a diagram of a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0241] refer to Figure 10, PDCCH candidate 1 may be transmitted by using TCI state 1, and PDCCH candidate 2 may be transmitted by using TCI state 2. In addition, the same DCI may be transmitted through PDCCH candidate 1 and PDCCH candidate 2, respectively. In addition, both PDCCH candidate 1 and PDCCH candidate 2 may be (repeatedly) transmitted at specific periodic intervals in the time domain.

[0242] Reference Figure 10 , each PDCCH candidate can share the same CORESET and the same SS set, and FDM can be performed on PDCCH candidates 1 and 2. PDCCH candidates 1 and 2 can be defined / configured in one SS set and one CORESET mapped to the SS set. In this case, one of the two TCI states defined / configured in the CORESET can be used in some PDCCH candidates, and the remaining TCI states can be used in the remaining PDCCH candidates. To this end, the PDCCH candidate to TCI mapping method can be referred to.

[0243] For example, when there are 4 PDCCH candidates with aggregation level = 4, the first and third candidates are mapped to TCI state 1, and the second and fourth candidates are mapped to TCI state 2, so the TCI states can be mapped alternately. Here, PDCCH candidate 1 can exist among the first and third candidates, and PDCCH candidate 2 can exist among the second and fourth candidates. Alternatively, the first and second candidates are mapped to TCI state 1, and the third and fourth candidates are mapped to TCI state 2, so the first half candidates and the second half candidates can be mapped to different TCI states. Here, PDCCH candidate 1 can exist among the first and second candidates, and PDCCH candidate 2 can exist among the third and fourth candidates.

[0244] By extending the above example, similarly for N TCI states, as the candidate index increases, the N TCI states can be cyclically mapped one after another. Alternatively, all candidates can be grouped by dividing into N adjacent candidates (adjacent candidate indices), and the N candidate groups and N TCI states can be mapped one-to-one.

[0245] In addition, in this method, the window for repeatedly transmitting the same PDCCH can be determined as each TO (transmission opportunity) of transmitting / receiving the PDCCH. In other words, PDCCH candidates 1 and 2 can be FDM-ed and repeatedly transmitted at each PDCCH TO represented in time slots n, n+P, n+2P, etc. Figure 10The diagram shows a case where the SS set period is configured as P time slots and one SS set is configured during one SS set period. In addition, SS sets can be configured in multiple (continuous) time slots within one SS set period, or multiple SS sets can be configured in one time slot.

[0246] For example, the SS set can be configured in N (continuous) time slots during each cycle through the duration field (=N) defined in the SS set. The base station and the UE can agree that the N time slots configured in this way are a window. In this case, the TCI state can be mapped to each PDCCH TO through the above-mentioned "PDCCH TO and TCI mapping method in the window". For example, for N=2, it is possible to use the same method as Figure 9 Configure the SS collection in the same way as in .

[0247] In another example, multiple SS sets can be configured in one timeslot via a higher-layer field defined in the SS set configuration (e.g., the monitoringSymbolsWithinSlot field). For example, an SS set can be defined / configured every P timeslots, and L SS sets can exist at different times in the timeslots in which the SS sets are configured. In this case, the base station and UE can agree on a window of 1 timeslot, and the TCI state can be mapped to each PDCCH TO using the "PDCCH TO and TCI mapping method in the window" described above.

[0248] In addition, the above-mentioned embodiment 1-2 can be configured as a special case of the embodiment 1-3 described later. In other words, for the method of configuring CORESETs 1 and 2 and SS sets 1 and 2 as in embodiment 1-3, the case where CORESETs 1 and 2 are configured to be the same (however, the TCI states defined in the CORESETs are different) and SS sets 1 and 2 can be configured to be the same is no different from embodiment 1-2 in which one CORESET, one SS set, and two TCI states are configured. Therefore, in this case, the same PDCCH can be repeatedly transmitted using the same method as in embodiment 1-2.

[0249] Similarly, Example 1-2 can be configured as a special case of Example 1-4. In other words, for the method of configuring CORESETs 1 and 2 and SS set 1 as in Example 1-4, the case where CORESETs 1 and 2 are configured identically (however, the TCI states defined in the CORESETs are different) is no different from Example 1-2.

[0250] In addition, embodiment 1-2 can be configured as a special case of embodiment 1-1. In other words, for the method of configuring CORESET 1 and SS sets 1 and 2 as in embodiment 1-1, the case where SS sets 1 and 2 are configured to be the same (however, the CORESET ID and TCI state of the CORESET used in each SS are different) is no different from embodiment 1-2 in which 1 CORESET, 1 SS set, and 2 TCIs are configured. Therefore, in this case, the same PDCCH can be repeatedly transmitted using the same method as in embodiment 1-2.

[0251] Embodiment 1-3) Two PDCCH candidates for sending the same DCI can be defined / configured in different CORESETs, and Furthermore, two PDCCH candidates for transmitting the same DCI may be defined / configured in different SS sets.

[0252] Figure 11 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0253] refer to Figure 11 , PDCCH candidate 1 may be transmitted by using TCI state 1, and PDCCH candidate 2 may be transmitted by using TCI state 2. In addition, the same DCI may be transmitted through PDCCH candidate 1 and PDCCH candidate 2, respectively. In addition, both PDCCH candidate 1 and PDCCH candidate 2 may be (repeatedly) transmitted at intervals of a specific period (P) in the time domain.

[0254] refer to Figure 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 such a configuration, the base station should inform the UE that the corresponding CORESET group or SS set group is configured to transmit the same DCI. For example, the ID of SS set 2 (and / or 1) for transmitting the same DCI can be additionally configured in SS set 1 (and / or 2). Alternatively, the base station can indicate to the UE that multiple SS sets are the same group, and the UE can recognize / assume that the SS sets belonging to the same group are configured to transmit the same DCI.

[0255] Since the window configuration method for sending the same DCI is the same as the configuration method in the above-mentioned embodiment 1-1, the configuration method in embodiment 1-1 can be used as it is.

[0256] Embodiment 1-4) Two PDCCH candidates for sending the same DCI are defined / configured in different CORESETs, but can be defined / configured in one (same) SS set.

[0257] Figure 12 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0258] refer to Figure 12 , PDCCH candidate 1 may be transmitted by using TCI state 1, and PDCCH candidate 2 may be transmitted by using TCI state 2. In addition, the same DCI may be transmitted through PDCCH candidate 1 and PDCCH candidate 2, respectively. In addition, both PDCCH candidate 1 and PDCCH candidate 2 may be (repeatedly) transmitted at intervals of a specific period (P) in the time domain.

[0259] refer to Figure 12 , two CORESETs with different resource blocks (RBs) can be mapped to one SS set, and candidates 1 and 2 can be defined in CORESET 1 and CORESET 2, respectively.

[0260] In addition, in this method, the window for repeatedly transmitting the same PDCCH is determined to be each TO (transmission opportunity) for transmitting / receiving the PDCCH. In other words, PDCCH candidates 1 and 2 can be FDM and repeatedly transmitted at each PDCCH TO shown in time slots n, n+P, n+2P, etc.

[0261] Figure 12 The diagram shows a case where the SS set period is configured as P time slots and one SS set is configured during one period. In addition, SS sets can be configured in multiple (continuous) time slots within one SS set period, or multiple SS sets can be configured in one time slot.

[0262] For example, the SS set may be configured in N (continuous) time slots during each cycle through the duration field (=N) defined in the SS set. The base station and the UE may agree that the N time slots configured in this manner are a window.

[0263] Hereinafter, a PDCCH TO and CORESET mapping method in a window is described.

[0264] There may be multiple PDCCH TOs in a window, and a different CORESET may be mapped to each PDCCH TO. The following two methods may be considered for mapping PDCCH TOs and CORESETs.

[0265] First, as the TO in the window increases, the CORESETs can be mapped sequentially in a cyclic manner. For example, when N TOs and M CORESETs defined in the SS set are indicated in the window, the i-th TO can be mapped to the i-th CORESET, and for N>M, the first CORESET and the second CORESET can be sequentially mapped to the M+1-th TO and the M+2-th TO in a cyclic manner. For example, Figure 9 As shown in (a), it is assumed that 6 PDCCH TOs are configured in one window and 2 CORESETs are configured. In this case, in one window, the first PDCCH TO can be mapped to the first CORESET, the second PDCCH TO can be mapped to the second CORESET, the third PDCCH TO can be mapped to the first CORESET, the fourth PDCCH TO can be mapped to the second CORESET, the fifth PDCCH TO can be mapped to the first CORESET, and the sixth PDCCH TO can be mapped to the second CORESET.

[0266] Alternatively, secondly, groups and CORESETs may be sequentially mapped cyclically by grouping adjacent floor(N / M) or ceil(N / M) TOs in a window. In other words, group i may be mapped to CORESET i. As a result, adjacent TOs included in the same group may be mapped to the same CORESET. For example, Figure 9 As shown in (b), it is assumed that 6 PDCCH TOs are configured in one window and 2 CORESETs are configured. Furthermore, it is assumed that the first to third PDCCH TOs are grouped into a first group, and the fourth to sixth PDCCH TOs are grouped into a second group. In this case, in one window, the first to third PDCCH TOs (i.e., the first group) can be mapped to the first CORESET, and the fourth to sixth PDCCH TOs (i.e., the second group) can be mapped to the second CORESET.

[0267] For the general case of repeatedly sending PDCCH at different times or sending PDCCH separately at different times and the cases in the above embodiments 1-4, this mapping method between TO and CORESET can be applied to the mapping between TO and CORESET in the same window.

[0268] In another example, multiple SS sets can be configured in one time slot through a higher-layer field defined in the SS set (e.g., the monitoringSymbolsWithinSlot field). For example, an SS set can be defined in a period of P time slots, and L SS sets can exist at different times in the time slot in which the SS set is configured. In this case, the base station and the UE can agree on a window of 1 time slot. In addition, the CORESET can be mapped using the above-mentioned "PDCCH TO and CORESET mapping method in the window".

[0269] In addition, Embodiments 1-4 can be configured as special cases of Embodiments 1-3. In other words, for the method of configuring CORESETs 1 and 2 and SS Sets 1 and 2 as in Embodiments 1-3, the case where SS Sets 1 and 2 are configured identically is no different from Proposals 1-4, which configure two CORESETs, one SS Set, and two TCIs. Therefore, in this case, the same PDCCH can be repeatedly transmitted using the same method as Proposals 1-4.

[0270] Example 2)

[0271] Embodiment 2 describes a method in which multiple base stations (ie, MTRPs) separately transmit the same PDCCH.

[0272] In addition, in the present disclosure, when multiple base stations (i.e., MTRPs) separately transmit the same PDCCH, it means that one DCI is transmitted using one PDCCH candidate, but TRP 1 performs transmission using some resources that define such PDCCH candidates, and TRP 2 performs transmission using the remaining resources. In this case, it can also be interpreted as multiple base stations transmitting the same DCI. The following configuration can be used to identify / indicate to the UE a PDCCH candidate that is separately transmitted by multiple base stations (i.e., MTRPs).

[0273] Hereinafter, for the convenience of description, it is assumed that two TRPs operate, but this assumption does not limit the technical scope of the present disclosure.

[0274] Example 2-1) Defining / configuring in one (same) CORESET the number of nodes that are sent separately by multiple base stations (i.e., MTRPs) The same / same PDCCH candidate may be sent but may be defined / configured in different SS sets.

[0275] Figure 13 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0276] refer to Figure 13 , PDCCH candidate 1 can be transmitted by using TCI state 1, and PDCCH candidate 2 can be transmitted by using TCI state 2. Furthermore, PDCCH candidate 1 and PDCCH candidate 2 can be combined to configure a single PDCCH candidate for transmitting one DCI. In addition, all PDCCH candidates generated in this manner can be transmitted (repeatedly) at intervals of a specific period (P) in the time domain.

[0277] This method can be configured similarly to the above-described embodiment 1-1, and a single PDCCH candidate can be transmitted / received by different SS sets within the same window. For example, the UE can attempt to decode a PDCCH candidate with aggregation level A1 for SS set 1 and a PDCCH candidate with aggregation level A2 for SS set 2 within the same window by assuming that they are a single PDCCH candidate with aggregation level A1+A2, rather than treating them as different PDCCH candidates. This method can support various aggregation levels in addition to existing aggregation levels.

[0278] However, because there are various aggregation levels or PDCCH candidates in each SS set, the method of generating one candidate using candidates from two SS sets without any constraints may increase the complexity of terminal implementation. To solve this problem, the candidate combination of the two SS sets that generate one PDCCH candidate can be limited. For example, the candidates in the two SS sets that generate one PDCCH candidate can be limited to the same aggregation level and / or can be limited to the same PDCCH candidate number (or index). Alternatively, for example, a standard set of two SS sets (e.g., set 1) can be configured, and one PDCCH candidate can be generated by combining the PDCCH candidates of set 1 and the PDCCH candidates of set 2 that are configured as the aggregation level of the PDCCH candidate or lower.

[0279] Embodiment 2-1 can be configured as a special case of Embodiment 2-3. In other words, for the method of configuring CORESETs 1 and 2 and SS sets 1 and 2 as in Embodiment 2-3, the case where CORESETs 1 and 2 are configured identically (however, the CORESET IDs and TCI states defined in the CORESETs are different) is no different from Embodiment 2-1, which configures one CORESET, two SS sets, and two TCIs. Therefore, in this case, the same PDCCH can be repeatedly transmitted using the same method as in Embodiment 2-1.

[0280] Example 2-2) can be defined / configured in one (same) CORESET and one (same) SS set by One PDCCH candidate transmitted separately by multiple base stations (ie, MTRPs).

[0281] PDCCH candidates defined in one CORESET and one SS set can be transmitted separately by multiple base stations. Here, some resources of the frequency / time resources configuring one PDCCH candidate can be transmitted / received using one of the two TCI states configured in the CORESET, and the remaining resources can be transmitted / received using the other TCI state.

[0282] Figure 14is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0283] Figure 14 An example is shown in which frequency resources for configuring one PDCCH candidate are divided and different TCI states are mapped. All PDCCH candidates may be (repeatedly) transmitted at intervals of a specific period (P) in the time domain.

[0284] For example, the frequency resources of the PDCCH candidates configuring aggregation level = 4 can be divided in units of control channel elements (CCEs). And, the first and third CCEs are mapped to TCI state 1, and the second and fourth CCEs are mapped to TCI state 2, so the TCI states can be mapped alternately. Alternatively, the first and second CCEs are mapped to TCI state 1, and the third and fourth CCEs are mapped to TCI state 2, so the first half CCE and the second half CCE can be mapped to different TCI states. By generalizing it, similarly for N TCI states, as the CCE index increases, the N TCIs can be mapped cyclically one by one. Alternatively, all CCEs can be divided and grouped into N adjacent CCEs (adjacent CCE indices), and the N CCE groups and N TCI states can be mapped one to one.

[0285] Because the PDCCH candidate with aggregation level = 1 may not be divided in units of CCE, the resource element group (REG) bundle size may be configured to be less than 6 REGs and can be divided in units of REG bundles. In addition, regardless of the aggregation level, the TCI state can be mapped by dividing resources in units of REG bundles. In this case, the TCI state and CCE mapping method can be similarly applied to the mapping between TCI states and REG bundles. For example, when the PDCCH candidate with aggregation level = 1 is configured with 3 REG bundles (bundle size = 2), the first and third REG bundles are mapped to TCI state 1, and the second REG bundle is mapped to TCI state 2, so the TCI states can be mapped alternately. Alternatively, the first and second REG bundles are mapped to TCI state 1, and the third REG bundle is mapped to TCI state 2, so the first half REG bundle and the second half REG bundle can be mapped to different TCI states.

[0286] Alternatively, for PDCCH candidates with aggregation level = 1, since one TRP transmits one PDCCH candidate, but different TRPs transmit different PDCCH candidates (for aggregation level = 1), diversity gain can be increased. For example, when there are 4 PDCCH candidates with aggregation level = 1, when TRP 1 transmits even / odd candidates, the even / odd candidates can be mapped to TCI state 1, and when TRP 2 transmits odd / even candidates, the odd / even candidates can be mapped to TCI state 2.

[0287] According to the current standard, when the precoder granularity configured in the CORESET is configured by continuous RBs (i.e., allContiguousRB) and wideband DMRS is configured, the UE recognizes the REG bundle in which the PDCCH candidate is configured when estimating the channel for a PDCCH candidate. In addition, the UE assumes that the DMRS to which the same precoder is applied is sent to the continuous frequency resources including the REG bundle in the CORESET. In this way, the channel estimation accuracy is improved by using the REG bundle in which the PDCCH candidate is configured and the DMRS of consecutive different REGs used for the REG bundle.

[0288] However, if the frequency resources configuring a core set are mapped to different TCI states as in this embodiment, the wideband DMRS operation method is no longer valid. This is because some of the continuous frequency resources including the REG bundle are mapped to TCI state 1, and the remaining resources are mapped to TCI state 2, so the channels for transmitting DMRS are different.

[0289] Therefore, in this case, when wideband DMRS is configured, the UE's operation should be modified as follows. When estimating the channel for one PDCCH candidate, the UE makes clear the REG bundle in which the PDCCH candidate is configured. In addition, the UE can assume that DMRS to which the same precoder is applied is transmitted to the continuous frequency resources including the REG bundle "among the frequency resources mapped to the same TCI state and the REG bundle" in the CORESET. Even when multiple TRPs are used as described later Figure 15The UE operation proposed above can also be applied in configuring wideband DMRS when the time resources configuring one PDCCH candidate are sent separately as in . In addition, this method can also be extended and applied to the case of the above-mentioned embodiment 1-2. For the case of embodiment 2-4 described later, one PDCCH candidate is sent through two CORESETs, so that the UE can figure out the REG bundle configuring the PDCCH candidate, and assume that the DMRS to which the same precoder is applied is sent to the continuous frequency resources including the REG bundle in the CORESET to which the REG bundle belongs. For example, if the PDCCH candidate is configured with 3 REG bundles, when estimating the channel of bundle i (i=1,2,3), the UE can assume that the DMRS to which the same precoder is applied is sent to the continuous frequency resources including the bundle in the CORESET to which bundle i belongs.

[0290] Figure 15 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0291] Figure 15 The case where different TCI states are mapped by dividing the time resources for configuring one PDCCH candidate is shown. All PDCCH candidates can be (repeatedly) transmitted at intervals of a specific period (P) in the time domain.

[0292] Figure 15 This is an example of defining a CORESET as a CORESET duration of two symbols. Furthermore, the two symbols configuring one PDCCH candidate may be mapped to different TCI states. In this case, the mapping between TCI and symbols may be defined / configured similarly to the TCI and CCE mapping method described above.

[0293] For the mapping between REG and REG bundle and between REG bundle and CCE, the resources of PDCCH candidates can be configured by applying the existing method as is. However, when estimating the channel through the actual DMRS, the existing REG bundle may not be used as is. This is because the symbols configuring the REG bundle are mapped to different TCIs. Therefore, when estimating the channel through the actual DMRS, the UE can reconfigure the REG bundle using only the symbols mapped to the same TCI state among the symbols configuring the existing REG bundle, and perform channel estimation in units of the reconfigured REG bundle.

[0294] In addition, in this method, the window for separately transmitting the same PDCCH is determined for each TO (Transmission Opportunity) in which the PDCCH is transmitted / received. In other words, some resources configuring one PDCCH candidate are transmitted / received using TCI state 1 for each PDCCH TO shown in time slots n, n+P, and n+2P, and the remaining resources are transmitted / received using TCI state 2. In other words, two TRPs are transmitted separately.

[0295] In addition, Example 2-2 can be configured as a special case of Example 2-3. In other words, for the method of configuring CORESETs 1 and 2 and SS sets 1 and 2 as in Example 2-3, the case where CORESETs 1 and 2 are configured to be the same (however, the TCI states defined in the CORESETs are different) and SS sets 1 and 2 can be configured to be the same is no different from Example 2-2 in which 1 CORESET, 1 SS set, and 2 TCI states are configured. Therefore, in this case, the same PDCCH can be separately transmitted by the same method as in Example 2-2. Similarly, Example 2-2 can be configured as a special case of Example 2-4. For the method of configuring CORESETs 1 and 2 and SS set 1 as in Proposal 2-4, the case where CORESETs 1 and 2 are configured to be the same (however, the TCI states defined in the CORESETs are different) is no different from Example 2-2. In addition, Example 2-2 can be configured as a special case of Example 2-1. In other words, for the method of configuring CORESET 1 and SS sets 1 and 2 as in Example 2-1, the case where SS sets 1 and 2 are configured to be the same (however, the CORESET ID and TCI state of the CORESET used in each SS are different) is no different from Example 2-2 in which 1 CORESET, 1 SS set, and 2 TCIs are configured. Therefore, in this case, the same PDCCH can be repeatedly transmitted using the same method as in Example 2-2.

[0296] Embodiment 2-3) It is possible to define / configure in multiple CORESETs the transmission of data separately by multiple base stations (ie, MTRP). A PDCCH candidate may be defined / configured in multiple SS sets.

[0297] Figure 16 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0298] refer to Figure 16 , CORESET 1 may be mapped to SS set 1, and CORESET 2 may be mapped to SS set 2. In addition, one PDCCH candidate may be transmitted / received through different SS sets existing in the same window.

[0299] 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 in the same window are one PDCCH candidate with aggregation level = A1 + A2 instead of treating them as different PDCCH candidates. Since embodiment 2-3 differs from embodiment 2-1 above only in the mapping between CORESET and SS set, the detailed proposal of proposal 2-1 can be applied as is.

[0300] Here, the base station may indicate to the UE that multiple SS sets (eg, SS sets 1 and 2) are the same group, and the UE may recognize / assume that the SS sets belonging to the same group are configured to separately transmit the same DCI (and / or the same PDCCH candidate).

[0301] Example 2-4) Defining / Configuring a Multiple CORESET Separately Transmitted by Multiple Base Stations (i.e., MTRP) PDCCH candidates, however, can be defined / configured in one SS set.

[0302] Figure 17 is a diagram illustrating a method of transmitting and receiving downlink control information according to an embodiment of the present disclosure.

[0303] refer to Figure 17 , two CORESETs with different RB resources can be mapped to one SS set. Furthermore, one PDCCH candidate can be generated by combining the PDCCH candidates of CORESET 1 and the PDCCH candidates of CORESET 2. For example, TRPs 1 and 2 can transmit PDCCHs through CORESET 1 and 2, respectively, and the UE can combine the PDCCH candidate with aggregation level A1 in CORESET 1 and the PDCCH candidate with aggregation level A2 in CORESET 2 to assume it is one PDCCH candidate with aggregation level A1+A2 and attempt decoding.

[0304] However, because there are various aggregation levels or PDCCH candidates in each CORESET, the method of generating one candidate using the candidates of two CORESETs without any constraints increases the complexity of terminal implementation. To solve this problem, the PDCCH candidate combination of the two CORESETs that generates one PDCCH candidate can be restricted. Such restrictions can be similarly applied to the method of restricting the PDCCH candidate combination of the two SS sets in the method of the above-mentioned embodiment 2-1. In other words, embodiment 2-4 is similar to embodiment 2-1, so the detailed proposal of embodiment 2-1 can be applied. However, embodiment 2-4 generates one PDCCH candidate by aggregating multiple multiplexed PDCCH candidates to frequency resources instead of time resources, so it can be modified and applied accordingly.

[0305] In addition, this method determines the window in which the same PDCCH is separately transmitted for each TO (Transmission Opportunity) in which the PDCCH is transmitted / received. In other words, PDCCH candidate 1 can be transmitted / received using TCI state 1 in some resources (by CORESET 1) of the resources in which one PDCCH candidate is configured for each PDCCH TO shown in time slots n, n+P, and n+2P, and PDCCH candidate 2 can be transmitted / received using TCI state 2 in the remaining resources (by CORESET 2). In other words, two TRPs divide the PDCCH candidates into PDCCH candidate 1 and PDCCH candidate 2 and transmit them.

[0306] In addition, embodiment 2-4 can be configured as a special case of embodiment 2-3. In other words, for the method of configuring CORESETs 1 and 2 and SS sets 1 and 2 as in embodiment 2-3, the case where SS sets 1 and 2 are configured identically is no different from embodiment 2-4, which configures two CORESETs, one SS set, and two TCIs. Therefore, in this case, the PDCCH can be transmitted separately using the same method as embodiment 2-4.

[0307] In addition, for an SS set in which multiple base stations (i.e., MTRPs) separately transmit the same PDCCH (i.e., for the above-mentioned embodiments 2-1 to 2-4), the UE may be instructed to separately transmit the same PDCCH only for some DCI formats / SS types / RNTIs defined in the SS set, and for the remaining DCI formats / SS types / RNTIs, the same PDCCH from one TRP is transmitted as in the existing method. For example, for an SS set that defines both DCI formats 1-0 and 1-1, separate transmission may be indicated only for format 1-0 (or 1-1). Alternatively, separate transmission may be indicated only for a common SS (or UE-specific SS) among a UE-specific SS and a common SS. Alternatively, the same PDCCH may be separately transmitted only for a DCI CRC masked with a specific RNTI (e.g., RNTI excluding C-RNTI, MCS-C-RNTI, CS-RNTI).

[0308] The base station may inform the UE through higher layer signaling whether a plurality of base stations will transmit the same PDCCH separately (the case of the above embodiment 2) or repeatedly transmit the same PDCCH (the case of the above embodiment 1).

[0309] Hereinafter, the method proposed in the present disclosure can be applied to the case where multiple base stations (i.e., MTRP) repeatedly send the same PDCCH (the case of the above-mentioned embodiment 1) and the case where multiple base stations (i.e., MTRP) separately send the same PDCCH (the case of the above-mentioned embodiment 2).

[0310] In the present disclosure, when multiple channels (i.e., i) multiple PDCCH candidates for repeated transmission, ii) multiple combined PDCCH candidates or multiple PDCCH candidates before combining) are TDMed, TO (or PDCCH TO) may refer to each channel transmitted at a different time, when multiple channels are FDMed, it may refer to each channel transmitted to a different frequency / RB, or when multiple channels are SDMed, it may refer to each channel transmitted to a different layer / beam / DMRS port. One TCI state may be mapped to each TO.

[0311] When the same channel is repeatedly transmitted (for example, in the case of embodiment 1), the complete DCI / data / uplink control information (UCI) can be sent to one TO, and the receiving end can increase the reception success rate by receiving multiple TOs. When a channel is sent separately to multiple TOs (for example, in the case of embodiment 2), part of the DCI / data / UCI is sent to one TO, and only when the receiving end should receive all multiple TOs, it can receive the complete DCI / data / UCI by collecting the partitioned DCI / data / UCI.

[0312] Example 3)

[0313] This embodiment is about a case where one same DCI is repeatedly transmitted from multiple TRPs (MTRPs) through a downlink control channel (eg, PDCCH) and TCI information is not included in the one same DCI.

[0314] When the TCI field is not included in one DCI transmitted from a single TRP (STRP) that is not the same DCI / PDCCH repeatedly transmitted from an MTRP, the TCI state of the PDSCH scheduled by the DCI may follow the TCI state associated with the CORESET that received the DCI.

[0315] When TCI information is included in DCI repeatedly transmitted from the MTRP, a TCI state associated with a downlink data channel (eg, PDSCH) scheduled by the DCI may be clearly determined based on the TCI information included in the DCI.

[0316] Meanwhile, when TCI information is not included in DCI repeatedly transmitted from the MTRP, a method of determining a TCI state associated with a downlink data channel scheduled by the DCI is not clearly defined.

[0317] Hereinafter, various examples for resolving the ambiguity problem are described. In particular, a method for determining TCI information to be applied to a downlink data channel (e.g., PDSCH) transmitted from a single TRP (STRP) is described when TCI is not included in DCI repeatedly transmitted from an MTRP.

[0318] The following examples assume that there are multiple CORESETs associated with one same DCI (or downlink control channel) transmitted from the MTRP and each TCI information is associated with each CORESET, or that there is one CORESET associated with one same DCI (or downlink control channel) and multiple TCI information is associated with one CORESET. In other words, they assume that when one same DCI is transmitted from the MTRP via the downlink control channel, multiple TCI information is preconfigured or predefined based on the CORESET associated with the downlink control channel transmission.

[0319] For example, a higher layer parameter ControlResourceSet IE (information element) may be used to configure a time / frequency control resource set (CORESET). For example, a control resource set (CORESET) may be related to 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 a CORESET pool for a CORESET (e.g., CORESETPoolIndex), a time / frequency resource configuration for the CORESET, or CORESET-related TCI information. For example, the index of the CORESET pool (e.g., CORESETPoolIndex) may be configured to 0 or 1. In the above examples of the present disclosure, a CORESET group may correspond to a CORESET pool, and a CORESET group ID may correspond to a CORESET pool index (e.g., CORESETPoolIndex). The ControlResourceSet (i.e., CORESET) may be configured through higher layer signaling (e.g., RRC signaling).

[0320] In addition, in the following examples, a CORESET identifier or CORESET ID may include a search space set (SS set) identifier or SS set ID. In other words, one CORESET may include one or more SSs, and one or more SSs may be defined as an SS set.

[0321] In addition, in the following example, when one same DCI (or downlink control channel (e.g., PDCCH)) is transmitted from the MTRP, the SFN (Single Frequency Network) method includes an operation in which the MTRP simultaneously transmits the same DCI (or PDCCH), and the non-SFN method includes an operation in which the MTRP repeatedly transmits the same DCI (or PDCCH) in different time resources (in a predetermined order). For example, in the SFN method, a plurality of TCI information may be associated with one CORESET, and in the non-SFN method, each TCI information may be associated with each CORESET in a plurality of CORESETs. It is assumed that the following example can be applied to both the SFN method and the non-SFN method, and the terminal can obtain a plurality of TCI information associated with (one or more) CORESETs associated with one DCI (or PDCCH) transmitted from the MTRP.

[0322] In the following description, for the sake of clarity, the term "repeated transmission of the same DCI (or PDCCH) from the MTRP" is mainly used, and repeated transmission of the same DCI / PDCCH from the MTRP can include both the SFN method and the non-SFN method. In addition, it should be understood that repeated transmission of the same DCI / PDCCH from the MTRP also includes a method in which the MTRP transmits the same DCI / PDCCH separately or transmits one DCI / PDCCH separately.

[0323] In addition, unless otherwise specifically limited, repeated transmission of the same DCI / PDCCH may include repeated transmission from MTRP and repeated transmission from a single TRP (STRP).

[0324] In addition, when the same DCI / PDCCH is repeatedly transmitted, the terminal can increase the DCI / PDCCH reception / decoding success rate through two methods (eg, a soft combining method and a multi-opportunity method).

[0325] First, in the soft combining method, the UE can increase the decoding success rate by soft combining multiple identical PDCCHs received (i.e., stored in the memory / buffer). This is a method similar to the method of increasing the decoding success rate by soft combining the initial PDSCH received by the UE and the retransmitted PDSCH when retransmitting the PDSCH. For such a UE, the base station can notify the UE of the PDCCH TO (or window) in which the same PDCCH is repeatedly transmitted, and the UE can perform soft combining on the indicated PDCCH TO.

[0326] Secondly, in the multi-opportunity method, the UE can independently decode each of the multiple PDCCHs without performing soft combining. In this case, the benefits may not be obtained through soft combining, but the implementation of the UE is simplified and only at least one of the multiple received PDCCHs needs to be successfully decoded, so the reception success rate can be increased. The base station does not need to notify the UE of the repeated PDCCH TO (or window) that sends the same PDCCH, and the UE can independently decode each PDCCH TO. For example, the base station sends the same PDCCH to PDCCH TO 1 and TO 2, but the UE can decode TO 1 and TO 2 separately without knowing that the same PDCCH is sent to TO 1 and TO 2. If the UE successfully decodes the PDCCH at TO 1 and TO 2, the UE can know that the scheduling information included in the DCI of TO 1 overlaps with the scheduling information included in the DCI of TO 2. In this case, the UE can know that the same DCI is repeatedly sent at TO 1 and TO 2 after the DCI decoding is successful. The UE can ignore or discard the remaining DCI except for one DCI. If the UE successfully decodes the DCI only at TO 1, it may not know that the DCI is sent at TO 2, and conversely, if the UE successfully decodes the DCI only at TO 2, it may not know that the DCI is sent at TO 1.

[0327] In other words, in the following examples, the method of repeatedly transmitting the same DCI / PDCCH from the MTRP is not limited to the SFN method or the non-SFN method and the method of performing reception / decoding for one or more DCI / PDCCHs in the terminal is not limited to the soft combining method or the multi-opportunity method.

[0328] Example 3-1

[0329] In the case of repeated DCI / PDCCH transmissions from an MTRP, there are multiple TCI states associated with the CORESET that receives the same DCI. In addition, one TCI state is associated with a PDSCH transmitted from a single TRP (STRP). Here, when PDSCH transmission from an STRP is scheduled by the same DCI repeatedly transmitted from an MTRP and TCI information is not included in the same DCI, it is unclear which TCI state among the multiple TCI states associated with the CORESET associated with the repeatedly transmitted DCI / PDCCH will be applied to the STRP PDSCH transmission.

[0330] For example, DCI repeatedly transmitted from the MTRP is transmitted through one CORESET, but there are two TCIs in the CORESET, so the same DCI can be received in both TCI state 1 and TCI state 2. Alternatively, the same DCI repeatedly transmitted from the MTRP can be received by CORESET 1 using TCI state 1 and CORESET 2 using TCI state 2.

[0331] As a more specific example, in the soft combining method, when DCI decoding is successful, there are multiple TCI states connected to multiple PDCCH TOs (ie, PDCCH candidates) to be soft combined.

[0332] In the multi-opportunity method, the UE independently decodes the repeatedly transmitted PDCCH TOs, so it may succeed or fail to decode at the target BLER (block error rate) at each PDCCH TO. For example, if the same DCI / PDCCH is transmitted twice using TCI state 1 in slot 1 and TCI state 2 in slot 2, the UE may experience one of the following three situations.

[0333] - Case 1: DCI decoding in time slot 1 succeeds, and DCI decoding in time slot 2 fails

[0334] - Case 2. DCI decoding in time slot 1 fails, and DCI decoding in time slot 2 succeeds

[0335] - Case 3. DCI decoding is successful in time slot 1 and DCI decoding is successful in time slot 2

[0336] In case 1, the UE may recognize TCI state 1 as CORESET TCI and use it for PDSCH reception. In case 2, the UE may recognize TCI state 2 as CORESET TCI and use it for PDSCH reception. In case 3, the UE recognizes both TCI states 1 and 2 as CORESET TCI, making it unclear which TCI will be used for PDSCH reception. In other words, the UE determines the PDSCH TCI as TCI state 1 or 2 differently depending on the situation, and the base station may not be able to clearly determine which TCI state will be used to transmit the PDSCH because it does not know whether it belongs to case 1, 2, or 3.

[0337] Example 3-1-1

[0338] In the soft combining method, the base station and the UE can predetermine and pre-share the reception of the PDSCH by using a specific TCI state among multiple TCI states associated with DCI reception. This method can be applied to the case where the MTRP repeatedly transmits the same DCI / PDCCH, and can also be applied to the case where the MTRP transmits the same DCI / PDCCH separately. Here, the repeated transmission of the same DCI / PDCCH from the MTRP can include both the SFN method and the non-SFN method.

[0339] For example, a particular TCI state may be defined as the first TCI state, the last TCI state, the lowest (or highest) indexed TCI state, or the TCI state associated with the lowest (or highest) indexed CORESET among multiple TCIs.

[0340] In the multi-opportunity method, the TCI state to be used for PDSCH reception can be configured separately from the CORESET TCI state in the CORESET. For example, when the same DCI is transmitted by CORESET 1 and CORESET 2, the PDSCH TCI State field can be defined in CORESET 1 and CORESET 2, respectively, and configured to have the same value of TCI State 1. As a result, for the above-mentioned cases 1, 2, and 3, the UE can receive the PDSCH by using TCI State 1. Alternatively, if there is no PDSCH TCI State field in the CORESET, the PDSCH can be received by using the TCI state of that CORESET, and if there is a PDSCH TCI State field, the PDSCH can be received by using that value. For example, if the PDSCH TCI State field is not configured in CORESET 1 using TCI State 1 and the PDSCH TCI state is configured to TCI State 1 in CORESET 2 using TCI State 2, the PDSCH can be received by using TCI State 1 for the above-mentioned cases 1, 2, and 3.

[0341] Example 3-1-2

[0342] In the multi-opportunity method, if the base station configures or indicates to the UE a set of PDCCH TOs that repeatedly transmit the same DCI and the UE successfully receives even one DCI in the corresponding set, the PDSCH can be received by using the TCI state for a specific PDCCH TO in the set. For example, the set of PDCCH TOs can be configured to the UE through higher layer (e.g., RRC) signaling, and the UE can know in advance the number of TOs and the order of each TO in the TO set.

[0343] For example, as mentioned above Figure 8and Figure 11 In the case where the PDCCH TOs are TDMed in a window, the PDCCH TOs in the window may form a set. In other words, when the UE configures the window to the UE, the UE may receive a configuration or indication of a set of PDCCH TOs. In this case, regardless of which PDCCH TO in the window receives DCI, the TCI state for a specific PDCCH TO may always be used for PDSCH reception. For example, a specific PDCCH TO may be the first TO (or first transmitted) in the time domain or the last TO transmitted in the time domain in the TO set.

[0344] As an additional example, when PDCCH TO is Figure 10 When FDM is performed at the same time in a PDCCH TO, a PDCCH TO using TCI state 1 and a PDCCH TO using TCI state 2 may form a set. In this case, regardless of which PDCCH TO in the set receives DCI, the TCI state used for a specific PDCCH TO may always be used for PDSCH reception. For example, a specific PDCCH TO may be the first TO (or use the first TCI state) or the last TO (or use the last TCI state) in the TO set.

[0345] As an additional example, when PDCCH TO is Figure 12 When FDM is performed at the same time in a CORESET 1, the PDCCH TOs of CORESET 1 and the PDCCH TOs of CORESET 2 defined at the same time may form a set. In this case, regardless of which PDCCH TO in the set receives DCI, the TCI state for a specific PDCCH TO may always be used for PDSCH reception. For example, a specific PDCCH TO may be the first ID (or corresponding to the lowest CORESET ID (or SS set ID)) or the last TO (or corresponding to the highest CORESET ID (or SS set ID)) in the TO set.

[0346] Example 3-1-3

[0347] In the multi-opportunity method, if the base station configures or instructs the UE to repeatedly transmit a set of PDCCH TOs of the same DCI and the UE successfully receives even one DCI in the corresponding set, the PDSCH can be received by using a specific TCI state.

[0348] For example, the specific TCI state may be indicated by the base station to the UE through MAC CE or RRC signaling.

[0349] As an additional example, a specific TCI state may be determined as a default TCI state (or default beam). For example, the TCI state of the CORESET configured with the lowest CORESET ID (or SS set ID) in the latest slot of the configured search space may be determined as the default TCI state.

[0350] Here, the default TCI state may be defined as a TCI state used when the time until the UE receives the PDSCH after receiving the DCI (ie, DCI to PDSCH time) is less than a specific threshold reported by the UE to the base station as its capability.

[0351] In more detail, the determination of the default TCI state (or default beam) may be defined as follows.

[0352] For both cases when tci-PresentInDCI is set to "enabled" and tci-PresentInDCI is not configured in RRC connected mode, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, the UE may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with the RS relative to the QCL parameters of the PDCCH quasi-co-location indication for the CORESET associated with the monitored search space with the lowest CORESET-ID in the latest timeslot in which one or more CORESETs within the active BWP of the serving cell are monitored by the UE.

[0353] Here, the latest slot may correspond to a latest slot in which a PDCCH monitoring opportunity (MO) exists among slots before the DCI is received.

[0354] Example 3-2

[0355] This embodiment includes a new method regarding the time reference for determining the default TCI state (or default beam) when the same DCI / PDCCH is repeatedly transmitted (i.e., when the terminal can receive / detect multiple identical DCI / PDCCHs at different time locations).

[0356] In the following, for clarity of description, the description is made by assuming that the same DCI / PDCCH is repeatedly transmitted from the MTRP, but the scope of the present disclosure is not limited thereto. In other words, this embodiment can be applied to the case where the same DCI / PDCCH is repeatedly transmitted from the MTRP, and can also be applied to the case where the same DCI / PDCCH is repeatedly transmitted from a single TRP (STRP).

[0357] Furthermore, this embodiment can be applied to both cases where the TCI field is included in the DCI and cases where the TCI field is not included in the DCI. In other words, this embodiment includes a method for clearly determining the default TCI state based on the relationship between the DCI and the PDSCH timing, regardless of whether the TCI field is included in the DCI.

[0358] Figure 18 is a diagram for describing the relationship between DCI and PDSCH to which the present disclosure can be applied.

[0359] The same DCI / PDCCH can be transmitted at different times (e.g., time slot 1 and time slot 2) through repeated transmission of the same DCI / PDCCH. In other words, DCI 1 in time slot 1 and DCI 2 in time slot 2 can include the same information. For example, DCI 1 may include information scheduling a PDSCH to be transmitted in time slot M, and DCI 2 may also include information scheduling a PDSCH to be transmitted in time slot M in the same manner.

[0360] The DCI / PDCCH in slot 1 may be transmitted in CORESET 1, and the DCI / PDCCH in slot 2 may be transmitted in CORESET 2. CORESET 1 and CORESET 2 may belong to the same CORESET pool or may belong to different CORESET pools. The DCI / PDCCH may or may not include a TCI field.

[0361] When the DCI / PDCCH does not include the TCI field, the TCI state associated with the CORESET associated with the DCI / PDCCH can be applied to the PDSCH scheduled by the corresponding DCI / PDCCH. If the PDSCH in time slot M is a PDSCH transmitted from a single TRP (STRP), it is necessary to define which of the TCI state associated with the DCI / PDCCH in time slot 1 or the TCI state associated with the DCI / PDCCH in time slot 2 will be applied to the PDSCH in time slot M.

[0362] As described above, when the time from the UE receiving the DCI until the UE receives the PDSCH (i.e., the DCI to PDSCH time) is less than a specific threshold value reported by the UE to the base station as its capability, the TCI state for the PDSCH may be determined to be the default TCI state (or default beam) regardless of whether the TCI field is included in the DCI. For example, the default TCI state (or default beam) may be determined to be the TCI state of the CORESET configured with the lowest CORESET ID (or SS set ID) in the latest slot in which the search space is configured.

[0363] For example, when the same DCI / PDCCH is repeatedly transmitted, the terminal may attempt DCI decoding separately at multiple PDCCH TOs. For example, with the multi-opportunity method, if the same DCI / PDCCH is transmitted twice by using TCI state 1 in slot 1 and by using TCI state 2 in slot 2, the UE may experience one of the following three situations.

[0364] Case 1: DCI decoding in slot 1 (e.g., the first symbol of slot 1) succeeds, and DCI decoding in slot 2 (e.g., the first symbol of slot 2) fails

[0365] - Case 2. DCI decoding in slot 1 (e.g., the first symbol of slot 1) fails, and DCI decoding in slot 2 (e.g., the first symbol of slot 2) succeeds

[0366] - Case 3. DCI decoding in slot 1 (e.g., the first symbol of slot 1) is successful, and DCI decoding in slot 2 (e.g., the first symbol of slot 2) is successful

[0367] Because the repeatedly transmitted DCI / PDCCH schedules the same PDSCH, when the same DCI / PDCCH is sent at different times via TDM, the DCI to PDSCH time (i.e., the time from the last received symbol of the DCI to the first symbol of the PDSCH) may be different in each of the above cases 1, 2, and 3.

[0368] If the first symbol of the PDSCH is the first symbol of slot 3, the UE may determine the DCI to PDSCH time as 28 symbols and 14 symbols in Cases 1 and 2, respectively. Because both the case where the DCI to PDSCH time is 14 symbols and the case where the DCI to PDSCH time is 28 symbols exist in Case 3, it is unclear which value should be selected and compared with a predetermined threshold (e.g., timeDurationForQCL).

[0369] For example, assuming that the predetermined threshold for determining the default TCI state is 20 symbols, the DCI to PDSCH time for PDCCH TO 1 (e.g., 28 symbols) is greater than the predetermined threshold, but the DCI to PDSCH time for PDCCH TO 2 (e.g., 14 symbols) is less than the predetermined threshold. In this case, the UE receives the PDSCH by using a different TCI state than the default TCI state in case 1 (e.g., based on the TCI field included in the DCI or based on the CORESET TCI associated with the PDCCH), but the UE receives the PDSCH by using the default TCI state in case 2. In case 3, the UE may not be able to clearly determine whether the PDSCH is received using the default TCI state or a different TCI state.

[0370] Because the base station may not know which of situations 1, 2, and 3 the UE is in, it is unclear which TCI state the base station should select to apply to PDSCH transmission.

[0371] In other words, for DCI / PDCCHs that schedule the same PDSCH but are received at different times, there is a problem in which TCI state (or beam) is applied to the same PDSCH.

[0372] Example 3-2-1

[0373] According to this embodiment, when the terminal successfully receives / decodes even one DCI among the set of PDCCH TOs configured or indicated by the base station, it can determine whether to apply the default TCI state (or default beam) based on the specific PDCCH TO configured or indicated by the base station by comparing the DCI to PDSCH time with a predetermined threshold.

[0374] For example, in the multi-opportunity method, when the base station configures or instructs the UE to repeatedly send a set of PDCCH TOs for the same DCI and the UE successfully receives even one DCI in the corresponding set, it can determine whether to apply the default beam (default TCI state) based on the specific PDCCH TO in the set by calculating the DCI to PDSCH time and comparing it with the threshold.

[0375] For example, if Figure 8 or Figure 11If the PDCCH TOs are TDMed in the window, the PDCCH TOs in the window can form a set. In other words, when the base station configures the window for the UE, the UE can receive a configuration or indication of a set of PDCCH TOs. In this case, no matter which PDCCH TO in the window receives DCI, the time between the DCI that should be received at a specific PDCCH TO and the PDSCH scheduled by the DCI can be calculated and compared with a threshold to determine whether to apply the default beam (or default TCI state).

[0376] Here, the specific PDCCH TO that is the basis for the DCI-to-PDSCH time calculation may be the last PDCCH TO in the set (eg, the TO that was transmitted last in chronological order).

[0377] In this case, in all of the above cases 1, 2, and 3, the DCI-to-PDSCH time calculated based on the last DCI / PDCCH in chronological order is 14 symbols and is less than 20 symbols (a predetermined threshold), so the terminal can clearly determine that the default TCI state (or default beam) will be applied to all cases 1, 2, and 3. In addition, although the base station may not know which of cases 1, 2, and 3 will occur, it can apply and transmit the default TCI state (or default beam) to the PDSCH based on the timing of the last transmitted DCI / PDCCH.

[0378] Example 3-2-2

[0379] When the same DCI / PDCCH is repeatedly transmitted, the base station can configure each difference between the timing of the PDSCH scheduled by the corresponding DCI and the timing of the DCI / PDCCH to be less than (or greater than) a threshold. Accordingly, regardless of whether the terminal successfully receives / decodes some of the multiple DCI / PDCCHs, the DCI-to-PDSCH time can be calculated based on the timing of the corresponding DCI / PDCCH and compared with a predetermined threshold to clearly determine whether to apply the default beam.

[0380] For example, when MTRP repeatedly transmits the same PDCCH via TDM, it is possible to calculate a threshold (e.g., a second threshold) adjusted by adding a predetermined value (e.g., alpha) to a threshold reported by the UE (e.g., a first threshold) and ensure that the DCI-to-PDSCH time of multiple PDCCH TOs is less than (or greater than) the second threshold. Such a second threshold can also be derived by the UE in the same manner as the base station. Here, the value of alpha can be a value predetermined based on the SCS, or a value indicated by the base station to the UE. In addition, the value of alpha can be a positive or negative number.

[0381] For example, assuming that the UE reports to the base station a first threshold of 20 symbols and an alpha value of 20 symbols, the base station and the UE may determine the second threshold to be 40 (=20+20) symbols. Therefore, the DCI-to-PDSCH times of 28 symbols and 14 symbols for each of PDCCH TOs 1 and 2 are both less than the second threshold, so the UE and the base station may apply the default beam without distinguishing between cases 1, 2, and 3.

[0382] If the threshold is not adjusted, the base station may schedule PDSCH for all PDCCH TOs that repeatedly transmit the same DCI so that the time from each DCI to PDSCH will be less than or greater than the threshold (i.e., the first threshold). If the PDSCH is scheduled to be greater than the threshold of all multiple PDCCH TOs, the average DCI to PDSCH time may increase to increase the latency. If the PDSCH is scheduled to be less than the threshold of all multiple PDCCH TOs, there is a problem of reduced scheduling flexibility because all PDCCH TOs should be scheduled within the threshold.

[0383] Therefore, by restrictively applying the threshold adjustment only for whether the default beam (or default TCI state) is applied, the flexibility of PDSCH scheduling can be guaranteed, the delay can be prevented from being extended, and the ambiguity about whether the default beam is applied to PDSCH can be resolved.

[0384] Example 3-2-2

[0385] When the same DCI / PDCCH is repeatedly transmitted, it can be defined that the PDSCH is always transmitted or received by applying the default TCI state (or default beam).

[0386] For example, when MTRP repeatedly transmits the same PDCCH through TDM, regardless of the comparison result between the DCI to PDSCH time and / or the predetermined threshold, the base station can always transmit the PDSCH by using the default beam, and the UE can always receive the PDSCH by using the default beam. To this end, the base station can directly or indirectly instruct the UE to repeatedly transmit the same DCI / PDCCH (for example, window configuration, etc.). Therefore, in all of the above cases 1, 2, and 3, the UE can always receive the PDSCH by using the default beam, thereby removing ambiguity.

[0387] Example 3-2-4

[0388] When the same DCI / PDCCH is repeatedly transmitted, one PDSCH transmission timing (ie, PDSCH time scheduling) scheduled by the corresponding DCI may be configured to be smaller than (or larger than) a predetermined threshold for all PDCCH TOs.

[0389] For example, when MTRP repeatedly transmits the same PDCCH via TDM, for all PDCCH TOs transmitting the same DCI, the base station may schedule the time of each DCI to PDSCH to be less than or greater than a predetermined threshold. In other words, for PDCCH TOs transmitting the same DCI, the UE may not expect that the DCI to PDSCH time of some TOs is greater than the threshold and the DCI to PDSCH time of other TOs is less than or equal to the threshold.

[0390] Example 3-2-5

[0391] When the same DCI / PDCCH is repeatedly transmitted, when the DCI to PDSCH time is greater than a predetermined threshold for even one PDCCH TO among them, the default TCI state (or default beam) may not be applied, and when the TCI field is included in the DCI, the PDSCH (and PDSCH DMRS) may be received according to the TCI state indicated by the TCI field included in the DCI.

[0392] At the PDSCH reception timing, the UE can be considered to have completed decoding of DCI / PDCCH for which the DCI-to-PDSCH time is configured to be greater than a threshold. In other words, for DCI received at a PDCCH TO greater than a predetermined threshold, there is sufficient processing time, so if the corresponding DCI is successfully decoded and the TCI field is included in the corresponding DCI, the UE can perform PDSCH reception by using it. Therefore, in the case of not applying the default beam, the TCI state indicated by the DCI can be applied.

[0393] For the above-mentioned cases 1 and 2, there is no difference between the base station and the terminal in the operation of applying the TCI included in the DCI of PDCCH TO 1 to the PDSCH. Meanwhile, for case 2, the base station may apply the TCI state of the TCI field included in the DCI to the PDSCH transmission based on PDCCH TO 1, but since the DCI / PDCCH blind decoding at PDCCH TO 1 fails, the UE may attempt PDSCH reception by applying the default TCI state based on PDCCH TO 2. In this case, due to the difference between the base station and the UE for the TCI applied to the PDSCH, the UE may fail in PDSCH reception / decoding and additional operations such as PDSCH retransmission may occur, but this case is assumed to be an exception, and the complexity of UE implementation can be reduced by removing the ambiguity of the UE operation as to whether the default beam is applied.

[0394] The examples below the above-mentioned embodiment 3-2 can be applied to the case where the MTRP transmits the same DCI / PDCCH separately, and can also be applied to the case where the MTRP repeatedly transmits the same DCI / PDCCH and the UE performs a soft combining method. In other words, when the problem of whether a predetermined threshold value (or a comparison result with a predetermined threshold value) is satisfied for multiple PDCCH TOs is different because DCI / PDCCH transmission from MTRP or STRP is performed at different timings (PDCCH TOs), the examples below the embodiment 3-2 can be applied.

[0395] Example 3-3

[0396] According to the current standard, a CORESET pool can be configured for eMBB MTRP PDSCH transmission. For example, CORESET0, 1, 2, and 3 are configured, CORESET 0 and 1 are configured as pool 0, and the rest are configured as pool 2, so that the UE recognizes that different TRPs use CORESETs in different pools. For a PDSCH scheduled by a CORESET in CORESET pool 0 and a PDSCH scheduled by a CORESET in CORESET pool 1, frequency / time resources may partially or completely overlap, and the two PDSCHs have different data / TBs (i.e., different PDSCHs), so resource efficiency may be increased to achieve higher throughput. For example, a CORESET pool may correspond to a CORESET group.

[0397] On the other hand, for URLLC MTRP PDCCH, the same DCI can be transmitted via multiple CORESETs, and in this case, the PDSCHs scheduled by the multiple CORESETs are one PDSCH with one data. This is because DCI is repeatedly transmitted to improve the PDCCH reception success rate, but ultimately, there is one data scheduled by the DCI. In the multi-opportunity method, the UE can independently identify / decode the DCI transmitted by each CORESET without having to identify the PDCCH TO set or window in which the same DCI is repeatedly transmitted. In this case, if the eMBB MTRP PDSCH is configured together, a complex problem arises. When the frequency / time resources of the PDSCHs scheduled by multiple CORESETs completely overlap, it is ambiguous whether the corresponding PDSCHs are different PDSCHs transmitting different data / TBs or one PDSCH with one data.

[0398] Example 3-3-1

[0399] When the corresponding CORESETs are configured as different CORESET groups (when the corresponding CORESETs are configured as different CORESET pools), if the frequency / time resources of the PDSCHs scheduled by the CORESETs completely / partially overlap, the UE recognizes the corresponding PDSCHs as multiple (independent) different PDSCHs. In other words, independent data can be received by independently decoding each PDSCH. When the corresponding CORESETs are configured as the same CORESET group (when the corresponding CORESETs are configured as the same CORESET pool), if the frequency / time resources of the PDSCHs scheduled by the CORESETs completely / partially overlap, the UE recognizes the corresponding PDSCHs as the same PDSCH. In other words, the received DCI can be recognized as the same DCI scheduling the same PDSCH, and the remaining DCIs except one DCI can be ignored or discarded.

[0400] Although multiple DCIs transmitted through multiple core sets schedule one PDSCH, the frequency / time resources of the PDSCHs scheduled by each DCI may not completely overlap, and in some cases may only partially overlap. For example, when DCI 1 is transmitted through core set 1 in slot 1, DCI 2 (scheduling the same data as that scheduled by DCI 1) is transmitted through core set 2 in slot 10, and the same scheduled PDSCH is repeatedly transmitted in slots 9 and 11, DCI 1 schedules the same PDSCH to be repeatedly transmitted in slots 9 and 11 because it is received before the PDSCH is transmitted, and DCI 2 schedules it to be repeated once in slot 11 because it is received while the PDSCH is being repeatedly transmitted. The UE recognizes DCI 1, which has more scheduling information, as the final DCI and discards DCI 2. Such operation is described in LTE Release 15 as follows.

[0401] For the serving cell, if the UE is configured with the higher layer parameter blindSubframePDSCH-Repetitions, the UE shall drop any PDCCH / EPDCCH used for PDSCH data transmission in a subframe in which the UE is receiving a PDSCH assigned by a PDCCH / EPDCCH with DCI format 1A scrambled by a C-RNTI CRC in the UE-specific search space. (for subframe-TTI level PDSCH repetition)

[0402] For the serving cell, if the UE is configured with the higher layer parameter blindSlotSubslotPDSCH-Repetitions, the UE shall drop any PDCCH / SPDCCH used for PDSCH data transmission in the slot / subslot in which the UE is receiving PDSCH assigned by PDCCH / SPDCCH with DCI format 7-1A / 7-1B / 7-1C / 7-1D / 7-1E / 7-1F / 7-1G scrambled by C-RNTI CRC (for short TTI level PDSCH repetition)

[0403] Even when multiple DCIs schedule one PDSCH, but the resources of the PDSCHs scheduled by each DCI only partially overlap, it can be determined whether to identify each PDSCH as the same PDSCH or as different independent PDSCHs according to whether the CORESET groups (pools) are the same or different, and when it is identified as the same PDSCH, the UE can identify the DCI with more scheduling information (e.g., DCI 1) as the final DCI and discard the other DCIs.

[0404] Example 3-3-2

[0405] When multiple DCIs indicate the same DMRS CDM group / port, they can be identified as the same PDSCH, and when different identical DMRS CDM groups / ports are indicated, they can be identified as different independent PDSCHs. Alternatively, when the values of MCS / HARQ process number / RV / NDI, etc. are the same, they can be identified as the same PDSCH, and when they are different, they can be identified as different PDSCHs.

[0406] Example 3-3-2

[0407] A specific field in the DCI (e.g., a 1-bit field) may be configured to indicate whether the PDSCH scheduled by the DCI is an independent PDSCH or the same PDSCH as other DCI re-scheduled PDSCHs. Alternatively, by extending the field to N bits, the UE may be informed whether the PDSCH scheduled by the DCI is an independent PDSCH or the same PDSCH as other DCI re-scheduled PDSCHs, as well as the total number of re-scheduled DCIs in this case.

[0408] As an additional example, configuration information about linking on repeated transmissions of the same DCI / PDCCH can be provided to the terminal. For example, the base station can configure or indicate to the UE a set of PDCCH TOs that repeatedly transmit the same DCI. For example, the set of PDCCH TOs can be configured to the UE through higher layer (e.g., RRC) signaling, and based on it, the UE can know in advance the number of TOs in the TO set and the order of each TO.

[0409] Examples 3-4

[0410] In Example 3-2, for repeated transmission of the same DCI / PDCCH, various examples are described for resolving ambiguity regarding the possibility of a case where the time between the DCI / PDCCH and one PDSCH scheduled by it (e.g., DCI to PDSCH time) is different.

[0411] Similarly, for various operations based on time definitions with DCI / PDCCH timing (or PDCCH TO) (PDSCH reception, PUSCH transmission, APCSI reporting, AP CSI-RS reception, BWP switching, etc.), the corresponding times may be different due to repeated transmissions of the same DCI / PDCCH. In this case, ambiguity may arise as to which DCI / PDCCH timing is the basis for the operation.

[0412] For example, for the time from DCI to PDSCH, one DCI can schedule one PDSCH. When the time given from DCI to PDSCH transmission / reception opportunity is less than a predetermined threshold, the UE can receive the PDSCH by using the default beam. To this end, the UE can report the predetermined threshold as the UE capability value to the base station.

[0413] For DCI to PUSCH time, one DCI can schedule one PUSCH. When the time given from DCI to PDSCH transmission / reception opportunity is less than a specific value (e.g., N2), the UE may not send PUSCH. To prevent this, the base station can schedule the time given from the DCI reception opportunity to the PUSCH transmission opportunity as a specific value N2 or greater. In order to determine the above-mentioned specific value N2, the UE can report the value of N2' to the base station, the value of d can be determined according to the PUSCH DMRS pattern, and it can be calculated by N2=N2'+d.

[0414] The UE PUSCH preparation procedure time associated therewith may be defined as follows.

[0415] - if the first uplink symbol in a PUSCH allocation for a transport block defined by slot offset K2 and the start and length indicator SLIV of the scheduling DCI, including DM-RS and including the effect of timing advance, is no earlier than symbol L2, where L2 is defined as the time starting T after the end of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH is received proc，2 =max((N2+d 2，1 )(2048+144)·κ2 -μ ·T C d 2，2 ), the UE shall send a transport block after the next uplink symbol with its CP starting.

[0416] - N2 is based on μ from Tables 6.4-1 and 6.4-2 for UE processing capabilities 1 and 2, respectively, where μ corresponds to the maximum T proc,2 (μ DL ,μ UL ), where μ DL corresponds to the downlink subcarrier spacing of the PDCCH with which the DCI carrying the scheduling PUSCH is transmitted, and μ UL corresponds to the subcarrier spacing of an uplink channel with which the PUSCH is to be transmitted, and κ is defined as a predetermined constant value.

[0417] - If the first symbol of the PUSCH allocation consists of only DM-RS, then d 2,1 =0, otherwise d 2,1 =1.

[0418] - If the UE is configured with multiple active component carriers, the first uplink symbol in the PUSCH allocation further includes the effect of the timing difference between the component carriers.

[0419] - If the DCI is scheduled to trigger the switching of BWP, then d 2,2 Equal to the switching time, otherwise d 2,2 =0.

[0420] - For UEs supporting capability 2 on a given cell, if the higher layer parameter processingType2Enabled in PUSCH-ServingCellConfig is configured for the cell and is set to enabled, the processing time according to UE processing capability 2 applies,

[0421] If the PUSCH indicated by the DCI overlaps with one or more PUCCH channels, the transport block is multiplexed, otherwise the transport block is sent on the PUSCH indicated by the DCI.

[0422] - Otherwise, the UE may ignore the scheduling DCI.

[0423] -T proc,2 The value of is used in both normal and extended cyclic prefix cases.

[0424] [Table 6]

[0425] μ <![CDATA[PUSCH preparation time N2 [symbols]]]> 0 10 1 12 2 23 3 36

[0426] [Table 7]

[0427] μ <![CDATA[PUSCH preparation time N2 [symbols]]]> 0 5 1 5.5 2 For frequency range 1 it is 11

[0428] For DCI to AP (non-periodic) CSI reporting time, a DCI can trigger AP CSI / beam reporting. When the time given from DCI to AP CSI / beam reporting is less than a specific value Z, the UE may ignore the corresponding DCI, or may not report CSI, or may report CSI that has not been updated (or calculated).

[0429] For DCI to AP CSI-RS time, one DCI can trigger AP CSI / beam reporting and configure the AP CSI-RS as its channel / interference measurement resource. When the time given from DCI to AP CSI-RS reception is less than a specific value, the UE does not perform measurement using the QCL RS (Type D) of the AP CSI-RS and performs measurement using the default beam. Here, the specific value can be determined as the minimum value 48 and the value reported by the UE to the base station as the UE capability.

[0430] For the switching time from DCI to BWP, the scheduled PDSCH / PUSCH and the BWP to be used for PDCCH / PUCCH / PDSCH / PUSCH transmission and reception can be dynamically changed through the BWP indicator field of a DCI (e.g., DCI format 1-1 or 0-1). When the BWP is changed by the BWP indicator field, the time given from the reception timing of the DCI in which the corresponding BWP indicator field is transmitted to the reception timing of the PDSCH / PUSCH scheduled by the corresponding DCI should be greater than a specific value. The UE can report a specific value to the base station as the value of the UE capability. In addition, the UE may not transmit and receive all PDCCH / PDSCH / PUCCH / PUSCH from the timing after receiving the DCI including the BWP indicator until the reception timing of the PDSCH / PUSCH scheduled by the corresponding DCI.

[0431] For the above operations such as PDSCH reception, PUSCH transmission, AP CSI reporting, AP CSI-RS reception, BWP switching, etc., the DCI reception timing can be a reference.

[0432] If the same DCI / PDCCH is transmitted at different times, there are multiple reception opportunities for the same DCI. For example, if TRP 1 transmits the same DCI in slot 1 and TRP 2 transmits it in slot 2, the UE receives the corresponding DCI in slot 1 and slot 2. Therefore, there is a problem of unclearness as to which DCI is used to determine the time from DCI to PDSCH reception / PUSCH transmission opportunity, the time from DCI to AP CSI / beam report transmission opportunity, the time from DCI to AP CSI-RS reception opportunity, or the time from the reception opportunity of DCI that transmits the BWP indicator to the reception opportunity of the PDSCH / PUSCH scheduled by the corresponding DCI.

[0433] Example 3-4-1

[0434] When the same DCI / PDCCH is sent from MTRP or STRP at different times, the base station can indicate a specific DCI / PDCCH to the UE as a reference PDCCH, and the base station and the UE can predetermine and pre-share the reference PDCCH to be applied as the DCI reception opportunity. Alternatively, the reference PDCCH can be determined without signaling between the base station and the UE based on predefined rules. For example, the reference PDCCH can be defined as the last (or latest) transmitted PDCCH among multiple identical PDCCHs that are TDM and transmitted.

[0435] For example, information indicating the order of repeated transmissions may be included in the DCI. The base station may configure the DCI corresponding to the last transmission as the reference DCI, or may configure the i-th (1<=i<=N) DCI as the reference DCI. Here, the number of DCI / PDCCH repeated transmissions (N) may be indicated to the UE by the base station through higher layer signaling.

[0436] In addition, for repeatedly transmitted (or separately transmitted) PDCCHs, a scrambling sequence may be applied differently to each PDCCH. Therefore, a PDCCH to which a specific scrambling sequence is applied may be defined as a reference PDCCH.

[0437] In addition, for repeatedly transmitted (or separately transmitted) PDCCHs, the RNTI of the CRC mask may be applied differently to each PDCCH. Therefore, a PDCCH CRC-masked with a specific RNTI may be defined as a reference PDCCH.

[0438] The reference PDCCH thus determined can be used to determine DCI reception timings during repeated transmissions of the same DCI / PDCCH. For example, the DCI reception timings for DCI to PDSCH, DCI to PUSCH, DCI to AP CSI reporting, DCI to AP CSI-RS, and DCI to BWP switching can be determined based on the reference PDCCH. For other operations, one of multiple DCI reception timings can also be determined using the reference PDCCH.

[0439] Examples 3-5

[0440] For repeated transmissions of the same DCI / PDCCH, multiple default TCI states (default beams) can be determined based on the DCI to PDSCH time. When a PDSCH from a single TRP (STRP) is scheduled with the same DCI for repeated transmissions, it becomes unclear which of the multiple default beams will be applied to the PDSCH.

[0441] For example, as in Figure 18 In the example of , when the same DCI / PDCCH is repeatedly transmitted through TDM, TRP 1 may transmit PDCCH (e.g., DCI 1) through a CORESET (e.g., CORESET 0) belonging to CORESET pool 0, and TRP 2 may transmit PDCCH (e.g., DCI 2) through a CORESET (e.g., CORESET 1) belonging to CORESET pool 1.

[0442] exist Figure 18 In the example of , when the DCI to PDSCH time is less than a specific threshold reported by the UE as a capability for both DCI 1 and DCI 2, if the UE has the capability of receiving 2 default beams simultaneously, the UE can find the default beam 1 among the 2 CORESETs belonging to CORESET pool 1, and find the default beam 2 among the 2 CORESETs belonging to CORESET pool 2.

[0443] Whether the PDSCH is transmitted from STRP or MTRP can be indicated by the base station or can be understood by the UE as follows. For example, it can be determined that when there are two or more TCI states of the PDSCH indicated by the DCI, it is MTRP transmission, and otherwise, it is STRP transmission. Alternatively, although there is one TCI state of the PDSCH indicated by the DCI, when the TCI state values indicated by DCI 1 and DCI2 are different, it can be determined as MTRP transmission. Alternatively, when the DMRS ports indicated by DCI 1 and DCI 2 are defined by different CDM groups, it can be determined as MTRP transmission and when defined by the same CDM group, it can be determined as STRP transmission.

[0444] If in Figure 18 In the example above, if PDSCH is sent from MTRP, both default beams are valid.

[0445] If in Figure 18 In the example of transmitting PDSCH from STRP, only either one of the default beams 1 and 2 may be valid for STRP PDSCH. In this case, the UE should determine which of the two default beams is the valid default beam. Figure 18 In the example in which the UE receives PDSCH, the same problem may occur even when receiving AP CSIRS instead of PDSCH. That is, when the time from DCI to AP CSIRS is less than a specific threshold based on the UE capability report, the same problem may also occur and can be solved in the same way by the proposals of the following embodiments.

[0446] Example 3-5-1

[0447] The base station may indicate to the UE what is the valid default beam for STRP PDSCH reception among multiple default beams.

[0448] For example, the base station may indicate one of default beam 1 and default beam 2 to the UE through the TCI field of the DCI and alternatively, it may indicate the valid default beam through higher layer control information such as RRC and / or MAC CE.

[0449] Alternatively, when the UE can receive multiple default beams, multiple reception operation modes for operating by using at least one of the multiple default beams may be defined, and the base station may enable one of the multiple reception operation modes and indicate it to the UE. For example, the base station may enable one of a mode for performing channel (i.e., data channel and / or control channel) reception by using multiple default beams, a mode for performing channel reception by using one default beam, a mode for receiving the channel by using default beam 1, and a mode for receiving the channel by using default beam 2, so that the UE operates in the enabled mode.

[0450] Example 3-5-2

[0451] The base station may predefine or preconfigure a specific default beam among a plurality of default beams to the UE as a valid default beam to be used for STRP PDSCH reception.

[0452] For example, when the same DCI / PDCCH is repeatedly transmitted via TDM, the default beam corresponding to the CORESET pool of the last (ie, latest) received / transmitted PDCCH (eg, DCI 2) may be pre-determined and pre-shared to be configured as the valid default beam.

[0453] Alternatively, simply, one of the default beam 1 and the default beam 2 may be pre-determined as the effective default beam. For example, the effective default beam may be determined as the default beam 1, which is the default beam based on the CORESET configuration with a small CORESET pool index, or as the default beam 2, which is the default beam based on the CORESET configuration with a large CORESET pool index.

[0454] Example 3-5-3

[0455] Whether the PDSCH scheduled by repeated transmission of the same DCI / PDCCH is a STRP PDSCH or a MTRP PDSCH can be semi-statically configured to the UE. For example, the base station can indicate the STRP PDSCH or the MTRP PDSCH to the UE through higher layer signaling.

[0456] For example, when STRP PDSCH is scheduled by DCI 1 and DCI 2, one default beam determined without dividing CORESET pool indexes associated with DCI 1 and DCI 2 may be determined as a valid default beam.

[0457] Example 3-5-4

[0458] Whether the PDSCH scheduled by repeated transmission of the same DCI / PDCCH is a STRP PDSCH or an MTRP PDSCH can be configured to the UE in a semi-static manner (eg, through higher layer signaling).

[0459] For example, when the same DCI / PDCCH is repeatedly transmitted through TDM, the PDSCH can be received by using the default beam corresponding to the CORESET pool of the last (ie, most recent) received / transmitted PDCCH (e.g., DCI 2). Unlike embodiment 3-5-2, in the case where there is no preconfigured / predefined valid default beam between the base station and the UE, the UE can receive the PDSCH by using the default beam associated with the CORESET associated with the last received DCI / PDCCH.

[0460] Alternatively, simply one of the default beam 1 or the default beam 2 may be pre-determined as the valid default beam. Alternatively, the base station may indicate the default beam for STRP PDSCH transmission to the UE.

[0461] Examples 3-6

[0462] As in the above-mentioned embodiments 3-2, 3-4, and 3-5, when the same DCI is TDM-transmitted and repeatedly transmitted to a plurality of PDCCHs (or transmitted separately to a plurality of PDCCHs), an ambiguous problem arises in determining the default beam of the DCI.

[0463] To solve this problem, the base station and the UE may predetermine and pre-share that only a specific PDCCH among TDMed PDCCHs is used for default beam determination, and other PDCCHs do not affect the default beam determination.

[0464] The specific PDCCH may be indicated by the base station to the UE or may be predetermined as the last (or latest) received / transmitted PDCCH or may be predetermined as the first received / transmitted PDCCH. For example, if two TRPs repeatedly transmit the same DCI to slots 1 and 2 and only use the PDCCH sent to slot 2 for default beam determination, the UE may determine the default beam by assuming that the PDCCH for slot 1 does not exist and only the PDCCH for slot 2 exists.

[0465] Examples 3-7

[0466] When the same DCI / PDCCH is repeatedly transmitted, the UE can increase the reception success rate by performing soft combining on the PDCCH. The UE can report whether to perform this soft combining to the base station in advance as capability information. The base station can then configure a different redundancy version for each PDCCH and notify the UE of this information to improve soft combining performance.

[0467] Because the UE receives multiple DCI / PDCCHs and performs soft combining for the corresponding PDCCHs, the computational complexity becomes higher than when decoding a single PDCCH. Therefore, the PDCCH decoding time may increase and in this case, the parameters determined based on the PDCCH decoding time may be affected. For example, such parameters may be timeDurationForQCL associated with the DCI to PDSCH time, Z related to the DCI to AP CSI reporting time, N2 related to the DCI to PUSCH time, etc.

[0468] Example 3-7-1

[0469] A UE (e.g., a UE operating in frequency range 2) stores a DL signal during the timeDurationForQCL time after receiving a PDCCH with DL control information (e.g., DCI formats 1-0, 1-1, 1-2) by using a default beam and designs the timeDurationForQCL by considering the PDCCH decoding time.

[0470] When the PDCCH decoding time increases due to repeated DCI / PDCCH transmission, but the value of timeDurationForQCL remains unchanged, the UE should perform more operations for PDCCH decoding during the same time, so the burden on the UE implementation increases. Therefore, when soft combining is performed on multiple PDCCHs, timeDurationForQCL can be increased. For example, the value of timeDurationForQCL reported by the UE to the base station can be determined as follows, and this value can be increased.

[0471] The above-mentioned timeDurationForQCL may be defined as the minimum number of OFDM symbols required by the UE to perform PDCCH reception and apply spatial QCL information received in the DCI for PDSCH processing.

[0472] In addition, timeDurationForQCL may be related to UE capabilities, and the UE may send a specific value to the base station via a capability report. For example, for SCS 60 kHz, the specific value may be 7, 14, or 28 symbols, or for SCS 120 kHz, it may be 14 or 28 symbols.

[0473] For example, apart from the existing timeDurationForQCL parameter, the UE may additionally report a new parameter (e.g., timeDurationForQCL2) to the base station that takes soft combining into account. Therefore, when the UE applies soft combining to multiple PDCCHs, the default beam may be determined based on the timeDurationForQCL2 parameter.

[0474] As an additional example, when soft combining is applied to multiple PDCCHs, the UE may update the value of timeDurationForQCL by adding the time of alpha (e.g., 1 or 2 symbols) to the existing timeDurationForQCL and determine the default beam based on the updated timeDurationForQCL. For example, the alpha value may be predefined, or may be configured to the UE by the base station, or the alpha value applied by the UE may be reported to the base station.

[0475] The increment (e.g., alpha) of the timeDurationForQCL value described above may vary depending on the number of PDCCHs for which soft combining is performed (i.e., the number of PDCCHs transmitted repeatedly or separately). For example, as the number of PDCCHs for which soft combining is performed increases, the amount of computation increases, and thus a larger increment may be applied. For example, for soft combining of two PDCCHs, the increment value may be configured as 1 symbol, and for soft combining of four PDCCHs, the increment value may be configured as 2 symbols.

[0476] Additionally, the increment may be configured differently depending on the SCS. For example, the increment size may increase as the SCS becomes higher.

[0477] For example, based on at least one of the number of PDCCHs or SCSs that are repeatedly transmitted, the value of timeDurationForQCL (or a new parameter or increment) may be determined or configured.

[0478] As an additional example, when scheduling information for AP CSI-RS is included in the DCI / PDCCH, similar to the case of PDSCH reception, the UE can store the DL signal using the default beam for a specific period of time after receiving the DCI / PDCCH. In other words, after PDCCH reception, the UE can receive the DL signal by applying the default beam during the beamSwitchTiming time reported by the UE. When multiple PDCCHs are processed through soft combining, the beamSwitchTiming can be increased.

[0479] Such beamSwitchTiming can be defined as the minimum number of OFDM symbols between the DCI triggering of the aperiodic CSI-RS and the aperiodic CSI-RS transmission. Such beamSwitchingTiming can be delivered to the base station via the UE capability report. In addition, the corresponding beamSwitchTiming value can be pre-configured according to the SCS supported by the UE.

[0480] In addition, for beamSwitchTiming, a value (or a new parameter or increment) of beamSwitchTiming may be determined or configured based on at least one of the number of repeatedly transmitted PDCCHs or SCSs.

[0481] Example 3-7-2

[0482] A UE (eg, a UE operating in frequency range 2) may desire to schedule a PUSCH after a specific time (eg, PUSCH preparation time N2) after receiving a PDCCH with UL control information (eg, DCI formats 0-0, 0-1, 0-2).

[0483] For DCI / PDCCH that schedules PUSCH before PUSCH preparation time, UE ignores the corresponding DCI / PDCCH and does not perform PUSCH transmission. UE can report the value of N2' as UE capability to the base station, and the value of N2 can be calculated according to N2=N2'+d 2,1 - is determined. Here, d 2,1 -Can be determined to be 0 or 1 or greater based on parameters such as UL DMRS configuration. For example, the value of N2 can be determined based on the processing capability of the UE and can be related to the PUSCH preparation time. In addition, N2 can be configured in symbol units.

[0484] For example, according to the DMRS configuration and SCS, the value of N2' can be configured as shown in Table 8.

[0485] [Table 8]

[0486]

[0487] The value of N2 is designed by considering the PDCCH decoding time, so this value can be increased when soft combining is performed on multiple PDCCHs.

[0488] For example, separately from the existing N2', the UE may additionally report a new parameter N2' considering soft combining to the base station. When soft combining of multiple PDCCHs is applied, N2 may be determined based on N2' instead of N2'.

[0489] As an additional example, when soft combining is applied, the UE may update the value of N2' by adding a time alpha (e.g., 1 or 2 symbols) to the existing N2', and may determine N2 based on the updated N2'. For example, the alpha value may be predefined, or may be configured to the UE by the base station, or the alpha value applied by the UE may be reported to the base station.

[0490] In addition, the increment (e.g., alpha) of the value of N2' (or N2) may vary depending on the number of PDCCHs for which soft combining is performed (i.e., the number of PDCCHs transmitted repeatedly or separately). As the number of PDCCHs increases, the amount of calculation increases, so a larger increment may be applied. For example, for soft combining of two PDCCHs, the increment value may be configured as 1 symbol, and for soft combining of four PDCCHs, the increment value may be configured as 2 symbols.

[0491] Additionally, the increment may be configured differently depending on the SCS. For example, the increment size may increase as the SCS becomes higher.

[0492] For example, based on at least one of the number of PDCCHs or SCSs that are repeatedly transmitted, a value of N-2 (or a new parameter or increment) may be determined or configured.

[0493] Example 3-7-3

[0494] A UE (eg, a UE operating in frequency range 2) may desire to schedule a PUSCH for aperiodic CSI reporting after a specific time (eg, Z) after receiving a PDCCH with UL control information (eg, DCI formats 0-0, 0-1, 0-2).

[0495] For DCI / PDCCH that schedules PUSCH before Z time, the UE may ignore the corresponding DCI / PDCCH and may not perform PUSCH (i.e., AP CSI feedback) transmission or may perform PUSCH transmission without including AP CSI feedback or may report CSI that is not updated (or calculated).

[0496] The UE can report the value of Z to the base station as a capability. In the examples in Tables 9 and 10 below, Z1, Z2, and Z3 are all values related to Z, and depending on the CSI reporting configuration conditions, one of Z1, Z2, and Z3 can be determined as Z. Tables 9 and 10 can be applied to different CSI calculation delay requirements and represent the value of the symbol unit.

[0497] [Table 9]

[0498] μ <![CDATA[Z1]]> <![CDATA[Z1']]> 0 10 8 1 13 11 2 25 21 3 43 36

[0499] [Table 10]

[0500] μ <![CDATA[Z1]]> <![CDATA[Z1']]> <![CDATA[Z2]]> <![CDATA[Z2']]> <![CDATA[Z3]]> <![CDATA[Z3']]> 0 22 16 40 37 22 <![CDATA[X1]]> 1 33 30 72 69 33 <![CDATA[X2]]> 2 44 42 141 140 <![CDATA[min(44,X3+KB1)]]> <![CDATA[X3]]> 3 97 85 152 140 <![CDATA[min(97,X4+KB2)]]> <![CDATA[X4]]>

[0501] Z, Z' and μ are defined as follows.

[0502] - where M is the number of updated CSI reports, (Z(m), Z'(m)) corresponds to the mth updated CSI report and is defined as follows.

[0503] - When L=0 CPU is occupied and the CSI to be transmitted is a single CSI and corresponds to a wideband frequency granularity, wherein the CSI corresponds to a maximum of 4 CSI-RS ports in a single resource in the absence of a CRI report, and wherein CodebookType is set to "typeI-SinglePanel" or wherein reportQuantity is set to "cri-RI-CQI", if the CSI is triggered without a PUSCH with a transport block or HARQ-ACK or both, then (Z1, Z1') of Table 9, or

[0504] - if the CSI to be transmitted corresponds to wideband frequency granularity, where the CSI corresponds to a maximum of 4 CSI-RS ports in a single resource in the absence of CRI reporting and where CodebookType is set to "typeI-SinglePanel" or where reportQuantity is set to "cri-RI-CQI", then (Z1, Z1') of Table 10, or

[0505] - If the CSI to be transmitted corresponds to wideband frequency granularity, where reportQuantity is set to "ssb-Index-SINR", or reportQuantity is set to "cri-SINR", then (Z1, Z1') of Table 10, or

[0506] - If reportQuantity is set to "cri-RSRP" or "ssb-Index-RSRP", where X μ According to the UE reported capabilities beamReportTiming and KB l is based on the beamSwitchTiming capability reported by the UE, then (Z3, Z3') in Table 10, or

[0507] - Otherwise, (Z2, Z2') of Table 10.

[0508] - μ in Tables 9 and 10 corresponds to min(μ PDCCH ,μ CSI-RS ,μ UL), where μ PDCCH corresponds to the subcarrier spacing of the PDCCH with which the DCI is transmitted, and μ UL corresponds to the subcarrier spacing of the PUSCH with which the CSI report is to be sent and μ CSI-RS Corresponds to the minimum subcarrier spacing of the aperiodic CSI-RS triggered by DCI.

[0509] The value of Z is designed by considering the PDCCH decoding time, and thus an increased Z value may be applied when soft combining of multiple PDCCHs associated with DCI / PDCCH repetition transmission is performed.

[0510] For example, separately from parameter Z, the UE may additionally report a new parameter Z (e.g., Z ) that takes soft combining into account when soft combining is applied to multiple PDCCHs associated with DCI / PDCCH repetition transmission. -1 ”, Z2”, Z3”) and apply Z” instead of Z.

[0511] As an additional example, when soft combining is applied, the UE may update the value of Z by adding a time alpha (e.g., 1 or 2 symbols) to the existing Z and apply the updated Z. For example, the alpha value may be predefined or may be configured to the UE by the base station, or the alpha value applied by the UE may be reported to the base station.

[0512] In addition, the increment (e.g., alpha) of the Z value may vary depending on the number of PDCCHs for which soft combining is performed (i.e., the number of PDCCHs transmitted repeatedly or separately). As the number of PDCCHs increases, the amount of calculation increases, so a larger increment may be applied. For example, for soft combining of two PDCCHs, the increment value may be configured as 1 symbol, and for soft combining of four PDCCHs, the increment value may be configured as 2 symbols.

[0513] Additionally, the increment may be configured differently depending on the SCS. For example, the increment size may increase as the SCS becomes higher.

[0514] For example, based on at least one of the number of PDCCHs or SCSs that are repeatedly transmitted, the value of Z (or a new parameter or increment) can be determined or configured.

[0515] Examples 3-8

[0516] When the same DCI / PDCCH is repeatedly transmitted in multiple component carriers or multiple serving cells, ambiguity may arise regarding the determination of the default TCI state (or default beam).

[0517] Figure 19 is a diagram for describing a case of multiple cells to which the present disclosure can be applied.

[0518] exist Figure 19 In the example shown in FIG1 , TRP 1 transmits DCI 1 and data based on it (e.g., PDSCH) with a subcarrier spacing of 120 kHz in the Scell (secondary cell), and transmits DCI 2 with a subcarrier spacing of 60 kHz in the Pcell (primary cell). DCI 2 is the same DCI as DCI 1 and includes scheduling information about the PDSCH of TRP 1.

[0519] The default beam segment (e.g., the segment where the DCI to PDSCH time is less than a predetermined offset (e.g., timeDurationForQCL)) can be configured differently in different serving cells. For example, the default beam segment for DCI 1 (3 time slots in SCell) and the default beam segment for DCI 2 (8 time slots in PCell) can be configured differently. In this case, the PDSCH exists outside the default beam segment based on DCI 1, but exists within the default beam segment based on DCI 2. Therefore, when the UE receives the PDSCH, it is unclear whether the default beam will be applied.

[0520] In this case, the solution to the case where the same DCI (PDCCH TO) is repeatedly transmitted at different times in the above-mentioned embodiment 3-2 can be extended and applied to the case where the same DCI (PDCCH TO) is repeatedly transmitted at different times in multiple cells. For example, when DCI / PDCCH is repeatedly transmitted in multiple cells, it can be determined whether to apply the default TCI based on a specific (e.g., last received) DCI (PDCCH TO) by comparing with a predetermined threshold, or the default TCI can be configured to be applied to all DCIs (PDCCH TO) by increasing the predetermined threshold, or the default TCI can be configured to be applied at all times, or all of the multiple DCIs (PDCCH TO) can be configured to be less than or greater than the predetermined threshold, or if even one of the multiple DCIs (PDCCH TO) is greater than the predetermined threshold, the TCI of the PDSCH can be determined based on the TCI field included in the DCI without applying the default TCI.

[0521] Example 3-8-1

[0522] When the same DCI / PDCCH is repeatedly transmitted in multiple cells, the individual default beam segments for each DCI / PDCCH may be determined, and a final default beam segment corresponding to the union of the individual default beam segments may be determined. The final default beam segment may be determined as the default beam segment that last exists (or ends last, or ends closest to the timing of the PDSCH scheduled by the DCI) in the time domain among the individual default beam segments. Figure 19 In the example, the default beam segment based on DCI 2 can be determined as the final default beam segment.

[0523] As an additional example, when the same DCI / PDCCH is repeatedly transmitted in multiple cells, individual default beam segments for each DCI / PDCCH may be determined and a final default beam segment corresponding to the intersection of the individual default beam segments may be determined. The final default beam segment may be determined as the default beam segment that exists for the shortest time in the time domain among the individual default beam segments (or ends first, or ends at the timing farthest from the PDSCH scheduled by the DCI). Figure 19 In the example, the default beam segment based on DCI 1 can be determined as the final default beam segment.

[0524] When the same DCI / PDCCH is transmitted in multiple cells, the above-mentioned example of whether to apply the default beam related to PDSCH scheduling can be extended and applied to the examples of Embodiments 3-4 for PUSCH scheduling, CSI reporting, CSI-RS reception, and BWP switching. For example, the time period related to DCI / PDCCH in Embodiments 3-4 (e.g., DCI to PDSCH time, DCI to PUSCH time, DCI to AP CSI reporting time, DCI to AP CSI-RS time, DCI to BWP switching time, etc.) can be determined based on a specific thing (i.e., reference PDCCH) of the same DCI / PDCCH repeatedly transmitted in multiple cells. In addition, when multiple time reference values exist based on the number of SCS and / or DCI / PDCCH repeated transmissions in each of the multiple cells, the time base compared with the time period related to DCI / PDCCH in Embodiments 3-4 (e.g., timeDurationForQCL, N2, Z, beamSwitchTiming, etc.) can be determined based on their union or intersection.

[0525] For example, Examples 3-2 and 3-8 propose a default beam determination method for the case where DCI schedules PDSCH, but they can also be applied to the default beam determination method for the case where DCI schedules AP CSI-RS. However, unlike the PDSCH default beam based on timeDurationForQCL, the AP CSIRS default beam can be determined based on beamSwitchTiming.

[0526] The various examples in the present disclosure described above mainly describe sending the same DCI / PDCCH through two TCI states, but this is only for the convenience of description and does not limit the scope of the present invention. In other words, the examples of the present disclosure are about a method for clearly determining the TCI state to be applied to the STRP PDSCH scheduled by the corresponding DCI even for a case where the same DCI / PDCCH is associated with 2 or more different TCI states in one or more serving cells from one or more TRPs (for example, a case where the TCI state associated with the CORESET associated with the DCI (or the default TCI state) is different).

[0527] Figure 20 It is a flowchart for describing a method in which a terminal according to the present disclosure receives a PDSCH from a single TRP based on multiple PDCCHs.

[0528] In step S2010, the terminal may repeatedly receive a downlink control channel (eg, PDCCH) including the same DCI from one or more TRPs at one or more transmission opportunities (TOs).

[0529] For example, a plurality of PDCCHs including repeatedly received DCI may be received in resources different from one or more of time resources or frequency resources.

[0530] For example, the same DCI may be repeatedly sent from the STRP, or the same DCI may be repeatedly (or separately) sent from the MTRP.

[0531] In step S2020, the terminal may receive a downlink data channel from a single TRP (STRP).

[0532] Here, when the time interval (e.g., DCI to PDSCH time) between a specific TO of one or more TOs and a downlink data channel (e.g., PDSCH) scheduled by the same DCI is less than a predetermined threshold (e.g., timeDurationForQCL), the terminal can receive PDSCH based on the default TCI state (e.g., refer to Example 3-2).

[0533] Here, the default TCI state may be the TCI state associated with the CORESET (or SS set) having the lowest identifier in the latest timeslot monitored by the terminal (refer to the description of the default TCI state in embodiments 3-1 and 3-2).

[0534] In addition, a specific TO may be the last TO in the time domain among one or more TOs, or all TOs among one or more TOs may be configured to be less than or greater than or equal to a predetermined threshold (refer to the detailed example in Example 3-2).

[0535] In addition, when the time interval between one or more TOs and the downlink data channel reception time is equal to or greater than a predetermined threshold (i.e., when the default TCI state is not applied), and when the TCI field is not included in the DCI (i.e., when the TCI state associated with the CORESET associated with the DCI is applied to PDSCH reception), and when there are multiple TCI states associated with the CORESET, the downlink data channel can be received based on a specific preconfigured TCI state among the multiple TCI states (refer to Example 3-1).

[0536] Here, a specific preconfigured TCI state can be determined based on the first TO in the time domain, the TO using the lowest indexed TCI state, or the TO corresponding to the CORESET (or SS set) with the lowest identifier (refer to the detailed example in Example 3-1).

[0537] In addition, when all time intervals between multiple TOs and downlink data channel reception are less than a predetermined threshold (i.e., when the default TCI state is applied) and when multiple TOs belong to different CORESET pools and multiple default TCI states are determined accordingly, the downlink data channel can be received based on a specific default TCI state preconfigured among the multiple default TCI states (refer to Examples 3-5).

[0538] In addition, the last downlink control channel in the time domain can be configured as a reference downlink control channel among the downlink control channels received at multiple TOs, and based on the reception timing of the reference downlink control channel, the time interval between one or more of the uplink data channel transmission timing, the aperiodic channel state information (CSI) reporting timing, the aperiodic CSI reference signal (RS) reception timing or the bandwidth part (BWP) switching time can be determined (refer to Examples 3-4).

[0539] In addition, based on the multiple service cells configured for the terminal, among the time intervals between one or more TOs and the downlink data channel reception time for the multiple service cells, the default TCI state can be determined based on the time interval ending at the latest or earliest opportunity (refer to Example 3-8).

[0540] In addition, a modified value of a terminal capability parameter associated with a decoding time of multiple downlink control channels including the repeatedly received same DCI may be sent to the network side (refer to embodiment 3-7).

[0541] Figure 21 It is a diagram for describing the signaling process of the network side and the terminal according to the present disclosure.

[0542] Figure 21 Indicates signaling between a network side (e.g., a first TRP and a second TRP) and a terminal (UE) in the case of multiple TRPs to which various embodiments of the present disclosure (Embodiment 1, 2, and / or 3) can be applied (in the following description, TRP can be replaced with a base station and a cell). Here, the UE / network side is only an example and can be replaced by using the above description or Figure 22 The various equipment substitutions described were applied. Figure 21 It is only for the convenience of description and does not limit the scope of the present disclosure. In addition, it can be omitted according to the situation and / or configuration. Figure 21 Some of the steps shown in .

[0543] refer to Figure 21 , for ease of description, consider the signaling between 2 TRPs and UE, but it goes without saying that the corresponding signaling method can be extended and applied to signaling between multiple TRPs and multiple UEs. In the following description, the network side can be a base station including multiple TRPs, and can be a cell including multiple TRPs. In the example, an ideal / non-ideal backhaul can be configured between the first TRP and the second TRP configuring the network side. In addition, the following description is described based on multiple TRPs, but it can be equally extended and applied to transmission through multiple panels. In addition, in the present disclosure, the operation of the terminal receiving a signal from the first TRP and / or the second TRP may include the operation of the terminal receiving a signal from the network side (through / using the first TRP and / or the second TRP), and the operation of the terminal sending a signal to the first TRP and / or the second TRP may include the operation of the terminal sending a signal to the network side (through / using the first TRP and / or the second TRP).

[0544] Figure 21The example represents signaling when the terminal receives multiple DCIs in the case of M-TRP (or the case where multiple CORESETs are configured from one TRP can also be assumed to be M-TRP) (for example, when each TRP repeatedly sends the same DCI to the UE (or sends the same DCI separately)).

[0545] Although Figure 21 Not shown, the UE may transmit UE capabilities including capability information related to the execution of the operations proposed in the above-mentioned embodiments 1, 2 and / or 3 to the network side through / utilizing TRP 1 (and / or TRP 2). For example, as described in embodiments 3-7, etc., the UE capabilities may include timing-related information (e.g., timeDurationForQCL, Z, N2, etc.) considering soft combining. For example, parameters related to timeDurationForQCL, Z, N2, etc. considering soft combining may be redefined. Alternatively, specific parameters (e.g., alpha) added to existing parameters may be configured / defined, and for soft combining, timing related to data transmission and reception may be determined by further considering specific parameters. In other words, depending on whether soft combining is applied, the values of timeDurationForQCL, Z, N2, etc. applied when the UE sends and receives data may be different.

[0546] The UE may receive configuration information S2105 about transmission and reception based on multiple TRPs from the network side through / using TRP 1 (and / or TRP 2). 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), and the like. In this case, the configuration information may be sent through higher layer signaling (e.g., RRC signaling, MAC-CE, etc.). In addition, when the configuration information is predefined or preconfigured, the corresponding steps may be omitted. For example, the configuration information may include configuration related to the TCI state mapping method / method described in the above-mentioned embodiments 1, 2, and / or 3, etc. In addition, for example, the configuration information may include information related to the configuration of the transmission timing described in embodiments 1, 2, and / or 3, information related to TCI mapping, information related to repeated transmission of a control channel (e.g., PDCCH) (e.g., whether to perform retransmission, the number of retransmissions, etc.), and the like. For example, as described in the detailed example of Embodiment 3 above, by considering the repeated / partitioned transmission of the control channel (e.g., PDCCH), the configuration information may include a default beam-related configuration, reference control channel information associated with the beam and / or spatial relationship RS, etc.

[0547] For example, the UE ( Figure 22 100 / 200) from the network side ( Figure 22The operation of receiving the configuration information related to the transmission and reception based on multiple TRPs can be performed by the following method. Figure 22 For example, refer to Figure 22 , 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 multiple TRPs, and one or more transceivers 106 can receive configuration information related to transmission and reception based on multiple TRPs from the network side.

[0548] The UE may receive a first DCI and first data scheduled by the first DCI from the network side through / using TRP 1 (S1910). In addition, the UE may receive a second DCI and second data scheduled by the second DCI from the network side through / using TRP 2, or may receive the second data scheduled by the first DCI without the second DCI, or may receive only the second DCI scheduling the first data (S1920). For example, data of a single TRP (e.g., first data of TRP 1 or second data of TRP 2) may be scheduled by the first DCI and the second DCI repeatedly transmitted from TRP 1 and TRP 2.

[0549] For example, the first DCI (and the second DCI) may include the same (indication) information about the TCI state as in the above-mentioned embodiments 1, 2, and / or 3, resource allocation information about the DMRS and / or data (i.e., space / frequency / time resources), etc. For example, the first DCI (and the second DCI) may include information related to repeated transmission of a control channel (e.g., PDCCH) (e.g., a specific DCI format / SS / RNTI, etc.), indication information related to the configuration of a transmission opportunity (TO), information related to the mapping between 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 above-mentioned embodiments 1, 2, and / or 3. For example, the TCI state mapping with the TO of the control channel may be configured based on the configuration of the CORESET / SS set in the window in which the DCI is received, etc. For example, a set of TOs of the PDCCH may be configured.

[0550] DCI (e.g., first DCI and second DCI) and data (e.g., first data and second data) can be transmitted via a control channel (e.g., PDCCH, etc.) and a data channel (e.g., PDSCH, etc.), respectively. For example, a control channel (e.g., PDCCH) can be transmitted repeatedly, and the same control channel can be transmitted separately. In addition, step S2110 and step S2120 can be performed simultaneously, or either can be performed earlier than the other.

[0551] For example, the default TCI state (default beam) may be configured to be mapped by comparing the time between DCI (eg, first DCI and / or second DCI) and data (eg, first data and / or second data) with a specific threshold.

[0552] For example, as described in the detailed example of the third embodiment above, the beam / spatial relationship RS DCI (e.g., the first DCI and / or the second DCI) to be applied when receiving data (e.g., the first data and / or the second data) can be determined by comparing the interval (offset value) between the DCI (e.g., the first DCI and / or the second DCI) and the data (e.g., the first data and / or the second data) with a specific value. For example, when the interval (offset value) is less than the specific value, the default beam / spatial relationship RS can be applied, and when it is greater than the specific value, the beam / spatial relationship RS can be determined based on the TCI state indicated / configured by the DCI (e.g., the first DCI and / or the second DCI). For example, when a control channel (e.g., a PDCCH) is repeatedly transmitted, a reference PDCCH / DCI can be determined by an indication / configuration on the network side or a predefined rule, and the above operation can be performed based on the reference PDCCH / DCI. For example, the DCI (e.g., the first DCI and / or the second DCI) may include PDSCH / PUCCH / PUSCH related scheduling information / AP CSI report related information / AP CSIRS related information / BWP related information, etc. For example, whether it is M-TRP / S-TRP can be configured based on the DCI (e.g., the first DCI and / or the second DCI). In an example, whether it is M-TRP / S-TRP can be configured based on the number of TCI states / TCI state values / DMRS port related configurations included in the DCI (e.g., the first DCI and / or the second DCI). For example, the DCI (e.g., the first DCI and / or the second DCI) may include default beam related information.

[0553] For example, as described in Example 3-8, when the same DCI is repeatedly sent in different TRPs, the default beam can be determined based on the union or intersection of the default beam information related to each DCI.

[0554] For example, the time / frequency resources for receiving the first data and the second data may overlap, and the first data and the second data may be identified as different data / TBs when corresponding to one of the following situations: i) when scheduling is performed through different CORESET groups (pools), ii) when different DMRS CDM groups / ports are configured, iii) when different MCS / HARQ process numbers / RV / NDI are configured, or iv) when indication is performed through a specific field in DCI.

[0555] For example, the UE ( Figure 22 100 / 200) from the network side ( Figure 22 The operation of receiving DCI (eg, first DCI and / or second DCI) and / or data (eg, first data and / or second data) may be performed by the following method. Figure 22 For example, refer to Figure 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., the first DCI and / or the second DCI) and / or data (e.g., the first DCI and / or the second DCI), and one or more transceivers 106 can receive DCI (e.g., the first DCI and / or the second DCI) and / or data (e.g., the first data and / or the second data) from the network side.

[0556] The UE may decode the data (e.g., first data and / or second data) received from the network side by / using TRP1 (and / or TRP2) S2130. For example, the UE may perform decoding and / or channel estimation for the data based on the above-mentioned embodiments 1, 2, and / or 3. For example, according to the definition of the candidate of the control channel (e.g., PDCCH) (e.g., defined based on CORESET / SS set), decoding and / or channel estimation for the data may be performed by applying aggregation level / TCI state mapping.

[0557] For example, the UE ( Figure 22 The operation of decoding the first data and / or the second data can be performed by the following method. Figure 22 For example, refer to Figure 22 , one or more processors 102 may control one or more memories 104 etc. to perform operations of decoding the first data and / or the second data.

[0558] The UE may send HARQ-ACK information (e.g., ACK information, NACK information, etc.) about the first data and / or the second data to the network side through / using TRP 1 and / or TRP 2 (S1940 and S2145). In this case, HARQ-ACK information about each of the first data or the second data may be sent to each TRP. In addition, the HARQ-ACK information about the first data and the second data may be combined into one. In addition, the UE may be configured to send HARQ-ACK information only to a representative TRP (e.g., TRP 1), and may omit HARQ-ACK information transmission to other TRPs (e.g., TRP 2).

[0559] For example, as described in the detailed example of Embodiment 3, the beam / spatial relationship RS to be applied when transmitting HARQ-ACK information (e.g., ACK information, NACK information, etc.) can be determined by comparing the interval (offset value) between the DCI (e.g., the first DCI and / or the second DCI) and the HARQ-ACK information (e.g., ACK information, NACK information, etc.) with a specific value. For example, when the interval (offset value) is less than the specific value, the default beam / spatial relationship RS can be applied, and when it is greater than the specific value, the beam / spatial relationship RS can be determined based on the TCI state indicated / configured by the DCI (e.g., the first DCI and / or the second DCI). For example, when a control channel (e.g., a PDCCH) is repeatedly transmitted, a reference PDCCH / DCI can be determined by an indication / configuration on the network side or a predefined rule, and the above operation can be performed based on the reference PDCCH / DCI. For example, the above steps are described based on HARQ-ACK information (eg, ACK information, NACK information, etc.), but the configuration of beam / spatial relationship RS can also be applied to uplink channels (eg, PUCCH / PUSCH).

[0560] For example, the UE ( Figure 22 100 / 200) from the network side ( Figure 22 The operation of sending HARQ-ACK information about the first data and / or the second data can be performed by Figure 22 For example, refer to Figure 22 , one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104 to send HARQ-ACK information about the first data and / or the second data, and one or more transceivers 106 can send HARQ-ACK information about the first data and / or the second data to the network side.

[0561] The above network side / UE signaling and operations can be performed by the devices described below (e.g., Figure 22 For example, the network side (eg, TRP 1 / TRP 2) may correspond to a first wireless device, and the UE may correspond to a second wireless device, and in some cases, the opposite situation may be considered.

[0562] For example, the network side / UE signaling and operations described above may be processed by one or more processors (eg, 102, 202), and the network side / UE signaling and operations described above may be used to operate Figure 22 The instructions / programs (eg, instructions, executable codes) of at least one processor (eg, 102, 202) are stored in a memory (eg, Figure 22 in one or more memories (e.g., 104, 204)).

[0563] General devices to which the present disclosure can be applied

[0564] Figure 22 is a diagram illustrating a block diagram of a wireless communication system according to an embodiment of the present disclosure.

[0565] refer to Figure 22 , the first wireless device 100 and the second wireless device 200 can send and receive wireless signals through a variety of radio access technologies (e.g., LTE, NR).

[0566] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operational flowcharts included in this disclosure. For example, the processor 102 may generate first information / signals by processing information in the memory 104 and then transmit a wireless signal including the first information / signal through the transceiver 106. In addition, the processor 102 may receive a wireless signal including second information / signals through the transceiver 106 and then store information obtained by signal processing of the second information / signals 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 including commands for executing all or part of the processes controlled by the processor 102 or for executing the descriptions, functions, processes, proposals, methods, and / or operational flowcharts included in this 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 send and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used in conjunction with an RF (radio frequency) unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0567] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operational flowcharts included in this disclosure. For example, the processor 202 may generate third information / signals by processing information in the memory 204, and then transmit a wireless signal including the third information / signals through the transceiver 206. In addition, the processor 202 may receive a wireless signal including fourth information / signals through the transceiver 206, and then store information obtained through signal processing of the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including commands for executing all or part of the processes controlled by the processor 202 or for executing the descriptions, functions, processes, proposals, methods, and / or operational flowcharts included in this disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver 206 may be connected to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used in conjunction with an RF unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0568] In the following, the hardware elements of the wireless device 100, 200 will be described in more detail. Without limitation, 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 PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) according to the descriptions, functions, processes, proposals, methods, and / or operational flow charts included in the present disclosure. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flow charts included in the present disclosure. One or more processors 102, 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, processes, proposals, and / or methods disclosed in the present disclosure to provide them to one or more transceivers 106, 206. The one or more processors 102, 202 may receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flow diagrams included in the present disclosure.

[0569] The one or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. In an example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) may be included in the one or more processors 102, 202. The descriptions, functions, processes, proposals, methods, and / or operational flowcharts included in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, etc. The firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operational flowcharts included in this disclosure may be included in the one or more processors 102, 202 or may be stored in one or more memories 104, 204 and driven by the one or more processors 102, 202. The descriptions, functions, processes, proposals, methods, and / or operational flowcharts included in this disclosure may be implemented in firmware or software in the form of code, commands, and / or command sets.

[0570] The one or more memories 104, 204 may be connected to the one or more processors 102, 202 and may store data, signals, messages, information, programs, codes, instructions, and / or commands in various forms. The one or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, a hard drive, registers, cash memory, a computer-readable storage medium, and / or a combination thereof. The one or more memories 104, 204 may be located internally and / or externally to the one or more processors 102, 202. Furthermore, the one or more memories 104, 204 may be connected to the one or more processors 102, 202 via a variety of technologies, such as wired or wireless connections.

[0571] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, and the like mentioned in the methods and / or operational 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, and the like mentioned in the descriptions, functions, processes, proposals, methods, and / or operational 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. In addition, 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. In addition, one or more transceivers 106, 206 can be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 can be configured to transmit and receive user data, control information, wireless signals / channels, etc. mentioned in the description, functions, processes, proposals, methods and / or operational flowcharts, etc. included in this disclosure through one or more antennas 108, 208. In the present invention, one or more antennas can be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 can convert received wireless signals / channels, etc. from RF band signals to baseband signals using one or more processors 102, 202 to process received user data, control information, wireless signals / channels, etc. One or more transceivers 106, 206 can convert user data, control information, wireless signals / channels, etc. processed by using one or more processors 102, 202 from baseband signals to RF band signals. Therefore, one or more transceivers 106, 206 can include (analog) oscillators and / or filters.

[0572] The above-mentioned embodiments are elements and features of the present disclosure combined in a predetermined form. Unless otherwise explicitly mentioned, each element or feature should be considered optional. Each element or feature can be implemented in a form not combined with other elements or features. In addition, the embodiments of the present disclosure may include combined elements and / or features. The order of the operations described in the embodiments of the present disclosure may be changed. Some elements or features of an embodiment may be included in other embodiments, or may be replaced with corresponding elements or features of other embodiments. It is clear that an embodiment may include a combined claim without an explicit dependency relationship in the claim, or may be included as a new claim by modification after application.

[0573] It is clear to those skilled in the art that the present disclosure can be implemented in other specific forms without exceeding the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted restrictively in every aspect, but should be considered as illustrative. The scope of the present invention should be determined by the reasonable interpretation of the appended claims, and all changes within the equivalent range of the present disclosure are included within the scope of the present invention.

[0574] The scope of the present disclosure includes software or machine executable commands (e.g., operating systems, applications, firmware, programs, etc.) that perform operations in accordance with the methods of various embodiments in a device or computer, and non-transitory computer-readable media that store such software or commands, etc. and that can be executed in a device or computer. Commands that can be used to program a processing system that performs the features described in this disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in this disclosure can be implemented by using a computer program product that includes such a storage medium. The storage medium may include high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, but is not limited thereto, and it may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory optionally includes one or more storage devices located away from the processor. The memory or, alternatively, the non-volatile memory device in the memory includes a non-transitory computer-readable storage medium. The features described in this disclosure may be stored in any machine-readable medium to control the hardware of a processing system and may be integrated into software and / or firmware that allows the processing system to utilize the results from embodiments of the present disclosure and interact with other mechanisms. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0575] Here, the wireless communication technologies implemented in the wireless devices 100 and 200 of the present disclosure may include narrowband IoT for low-power communication, as well as LTE, NR, and 6G. Here, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented in standards such as LTE Cat. NB1 and / or LTE Cat. NB2, and is not limited to the aforementioned names. Additionally or alternatively, the wireless communication technologies implemented in the wireless devices 100 and 200 of the present disclosure may perform communications based on LTE-M technology. Here, in the examples, 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 any one of the following various standards, including 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 aforementioned names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may include at least one of ZigBee, Bluetooth, and a low-power wide area network (LPWAN) considering low-power communication, and is not limited to the above-mentioned names. In an example, the ZigBee technology may generate a PAN (Personal Area Network) 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.

[0576] Industrial Applicability

[0577] The method proposed in the present invention is mainly described by taking the application in 3GPP LTE / LTE-A and 5G systems as an example, but can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method for receiving a downlink channel by a terminal in a wireless communication system, the method comprising: receiving, in a plurality of transmission opportunities TO, a plurality of physical downlink control channels (PDCCHs) including downlink control information (DCI) having the same information according to a plurality of search space sets associated with at least one control resource set (CORESET) pool index; as well as Based on the DCI including scheduling information related to a downlink channel, and based on a time offset between a last specific TO in the time domain of the plurality of TOs and a reception timing of the downlink channel related to the DCI being less than a predetermined threshold: Receiving the downlink channel associated with a single CORESET pool index based on a transmission configuration indicator (TCI) state associated with the CORESET with the lowest identifier in the latest timeslot monitored by the terminal.

2. The method according to claim 1, wherein: Based on the DCI including scheduling information related to a downlink channel, the time offset is equal to or greater than the predetermined threshold, the DCI does not include a TCI field, and a CORESET associated with the DCI including the scheduling information related to the downlink channel is associated with a plurality of TCI states: The downlink channel is received based on a first TCI state among the plurality of TCI states.

3. The method according to claim 1, wherein: Based on the DCI including scheduling information related to a downlink channel, the time offset is equal to or greater than the predetermined threshold, the DCI does not include a TCI field, and a plurality of CORESETs are associated with the DCI: The downlink channel is received based on a TCI state of a CORESET having a lowest identifier among the plurality of CORESETs.

4. The method according to claim 1, wherein: Based on the DCI including control information related to uplink transmission, the time offset is determined based on the PDCCH candidate that ends last in the time domain of the multiple TOs.

5. The method according to claim 4, wherein: The uplink transmission includes at least one of a physical uplink shared channel (PUSCH) transmission or an aperiodic CSI report.

6. The method according to claim 1, wherein: The downlink channel is a physical downlink shared channel PDSCH.

7. A terminal for receiving a downlink channel in a wireless communication system, the terminal comprising: at least one transceiver; as well as at least one processor connected to the at least one transceiver, Wherein, the at least one processor is configured to: Receiving, by the at least one transceiver, a plurality of physical downlink control channels (PDCCHs) including downlink control information (DCI) having the same information in a plurality of transmission opportunities (TOs) according to a plurality of search space sets associated with at least one control resource set (CORESET) pool index; as well as Based on the DCI including scheduling information related to a downlink channel, and based on a time offset between a last specific TO in the time domain of the plurality of TOs and a reception timing of the downlink channel related to the DCI being less than a predetermined threshold: Receiving, by the at least one transceiver, the downlink channel associated with a single CORESET pool index based on a transmission configuration indicator (TCI) state associated with a CORESET having a lowest identifier in a latest timeslot monitored by the terminal.

8. The terminal according to claim 7, wherein: Based on the DCI including scheduling information related to a downlink channel, the time offset is equal to or greater than the predetermined threshold, the DCI does not include a TCI field, and a CORESET associated with the DCI including the scheduling information related to the downlink channel is associated with a plurality of TCI states: The downlink channel is received based on a first TCI state among the plurality of TCI states.

9. The terminal according to claim 7, wherein: Based on the DCI including scheduling information related to a downlink channel, the time offset is equal to or greater than the predetermined threshold, the DCI does not include a TCI field, and a plurality of CORESETs are associated with the DCI: The downlink channel is received based on a TCI state of a CORESET having a lowest identifier among the plurality of CORESETs.

10. The terminal according to claim 7, wherein: Based on the DCI including control information related to uplink transmission, the time offset is determined based on the PDCCH candidate that ends last in the time domain of the multiple TOs.

11. The terminal according to claim 10, wherein: The uplink transmission includes at least one of a physical uplink shared channel (PUSCH) transmission or an aperiodic CSI report.

12. The terminal according to claim 7, wherein: The downlink channel is a physical downlink shared channel PDSCH.

13. A processing unit configured to control a terminal receiving a downlink channel in a wireless communication system, the processing unit comprising: at least one processor; as well as at least one computer memory operatively connected to the at least one processor and storing instructions for performing operations upon execution by the at least one processor, The operations include: Receiving, in a plurality of transmission opportunities TO, a plurality of physical downlink control channels (PDCCHs) including downlink control information (DCI) having the same information according to a plurality of search space sets associated with at least one control resource set (CORESET) pool index; and Based on the DCI including scheduling information related to a downlink channel, and based on a time offset between a last specific TO in the time domain of the plurality of TOs and a reception timing of the downlink channel related to the DCI being less than a predetermined threshold: Receiving the downlink channel associated with a single CORESET pool index based on a transmission configuration indicator (TCI) state associated with the CORESET with the lowest identifier in the latest timeslot monitored by the terminal. 14 . A non-transitory medium, readable by at least one processor and storing at least one instruction for causing the at least one processor to execute the method according to claim 1 .

Images