Methods and devices for transmission and reception based on default spatial parameters in wireless communication systems

Abstract

A method and apparatus for transmitting and receiving based on default spatial parameters in a wireless communication system are disclosed. According to one embodiment of this disclosure, a method for a terminal to receive downlink transmissions from a base station in a wireless communication system includes the steps of: receiving from the base station setting information regarding at least one of spatial parameters set for a control resource set (CORESET) or spatial parameters set for at least one code point; receiving downlink control information (DCI) from the base station in a first time unit; and receiving downlink transmissions from the base station based on at least one default spatial parameter in a second time unit, wherein the at least one code point does not include code points for which multiple spatial parameters are set, and at least one default spatial parameter can be determined based on at least one of multiple spatial parameters set for CORESET.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to methods and apparatus for transmission and reception based on default spatial parameters in wireless communication systems. Background Technology

[0002] A mobile communication system has been developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded to include data and voice services, and the current explosive growth in these services has led to resource shortages. Users are demanding faster services and therefore require more advanced mobile communication systems.

[0003] The overall requirements for next-generation mobile communication systems should be able to support the capacity for explosive data traffic, significantly increased per-user transmission rates, a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To this end, various technologies have been investigated, including dual connectivity, 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 problem of this disclosure is to provide a method and apparatus for transmission and reception based on multiple default spatial parameters in a wireless communication system over a predetermined duration.

[0006] An additional technical problem of this disclosure is to provide a method and apparatus for transmission and reception in a wireless communication system based on at least one of spatial parameters configured for a predetermined code point or for a set of control resources, and based on a plurality of default spatial parameters.

[0007] The technical objectives achieved through this disclosure are not limited to those described above, and those skilled in the art will clearly understand from the following description other technical objectives not described herein.

[0008] Technical solution

[0009] A method for a terminal to receive downlink transmission from a base station in a wireless communication system according to one aspect of the present disclosure includes: receiving configuration information from the base station for at least one of spatial parameters configured for at least one code point or for at least one spatial parameter configured for a control resource set (CORESET); receiving downlink control information (DCI) from the base station in a first time unit; receiving downlink transmission from the base station in a second time unit based on at least one default spatial parameter; and determining at least one default spatial parameter based on at least one of the multiple spatial parameters configured for CORESET, since at least one code point does not include a code point configured with multiple spatial parameters.

[0010] According to another aspect of this disclosure, a method for performing downlink transmission by a base station in a wireless communication system includes: sending configuration information to a terminal for at least one of spatial parameters configured for at least one code point or for at least one spatial parameter configured for a control resource set (CORESET); sending downlink control information (DCI) to the terminal in a first time unit; and sending downlink transmission to the terminal in a second time unit based on at least one default spatial parameter; and determining at least one default spatial parameter based on at least one spatial parameter among multiple spatial parameters configured for CORESET, since at least one code point does not include a code point configured with multiple spatial parameters.

[0011] Technical effect

[0012] According to embodiments of this disclosure, a transmission and reception method and apparatus based on a plurality of default spatial parameters can be provided in a wireless communication system for a predetermined duration.

[0013] According to embodiments of this disclosure, a method and apparatus for transmission and reception in a wireless communication system based on at least one of spatial parameters configured for a predetermined code point or spatial parameters configured for a control resource set, and based on multiple default spatial parameters, can be provided.

[0014] The effects achievable by this disclosure are not limited to those described above, and those skilled in the art can clearly understand other effects not described herein through the following description. Attached Figure Description

[0015] The accompanying drawings, included as part of the detailed description for understanding this disclosure, provide embodiments of the disclosure and describe the technical features of the disclosure through detailed description.

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

[0017] Figure 2 The diagram illustrates the frame structure applicable to wireless communication systems disclosed herein.

[0018] Figure 3 The diagram illustrates a resource grid that can be applied to a wireless communication system according to this disclosure.

[0019] Figure 4 The diagram illustrates physical resource blocks in a wireless communication system that can be applied according to this disclosure.

[0020] Figure 5 The diagram illustrates a time slot structure applicable to wireless communication systems according to this disclosure.

[0021] Figure 6The diagram illustrates a physical channel used in a wireless communication system to which this disclosure can be applied, as well as general signal transmission and reception methods using that physical channel.

[0022] Figure 7 The diagram illustrates multiple TRP transmission methods applicable to wireless communication systems using this disclosure.

[0023] Figure 8 This is a diagram illustrating downlink reception operation based on a terminal's default beam, according to embodiments of this disclosure.

[0024] Figure 9 This is a diagram illustrating downlink transmission operation based on a base station's default beam, according to embodiments of this disclosure.

[0025] Figure 10 This is a diagram illustrating downlink transmission and reception operations based on various examples of this disclosure, according to default space parameters.

[0026] Figure 11 This is a diagram illustrating an example of signaling between the network side and the terminal to which embodiments of this disclosure may be applied.

[0027] Figure 12 The figure shows a block diagram of a wireless communication system according to an embodiment of the present disclosure. Detailed Implementation

[0028] In the following, embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed with reference to the drawings is intended to describe exemplary embodiments of the present disclosure and not to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the art will recognize that the present disclosure may be practiced without these specific details.

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

[0030] In this disclosure, when an element is referred to as “connected,” “combined,” or “linked” to another element, it can include both indirect and direct connections between the two elements. Furthermore, in this disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, operations, components, and / or elements, but do not exclude the presence or addition of one or more other features, stages, operations, components, elements, and / or groups thereof.

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

[0032] The terminology used in this disclosure is for the purpose of describing particular embodiments and not for limiting the claims. As used in the description of the embodiments and the appended claims, the singular forms are intended to include the plural forms unless the context clearly indicates otherwise. The term “and / or” as used in this disclosure may refer to one of the associated enumerations, or is intended to refer to and include any and all possible combinations of two or more of them. Furthermore, unless otherwise stated, the “ / ” between words in this disclosure has the same meaning as “and / or”.

[0033] This disclosure describes a wireless communication network or wireless communication system, and operations performed in the wireless communication network can be performed during the process of a device (e.g., a base station) controlling the network and transmitting or receiving signals, or during the process of a terminal associated with the corresponding wireless network transmitting or receiving signals between the network or between the terminal.

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

[0035] In the following text, downlink (DL) refers to communication from a base station to a terminal, while uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter can be part of the base station, and the receiver can be part of the terminal. In the uplink, the transmitter can be part of the terminal, and the receiver can be part of the base station. A base station can be referred to as a first communication device, and a terminal can be referred to as a second communication device. A base station (BS) can be replaced by terms such as fixed station, Node B, eNB (evolved Node B), gNB (next-generation Node B), BTS (Base Transceiver System), Access Point (AP), Network (5G network), AI (Artificial Intelligence) system / module, RSU (Roadside Unit), robot, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, terminals 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) equipment, M2M (Machine-to-Machine) equipment, D2D (Device-to-Device) equipment, vehicles, RSU (Roadside Unit), robots, AI (Artificial Intelligence) modules, drones (UAVs), AR (Augmented Reality) equipment, VR (Virtual Reality) equipment, etc.

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

[0037] To make the description clearer, it is based on 3GPP communication systems (e.g., LTE-A, NR), but the technical ideas of this disclosure are not limited thereto. LTE refers to technology from 3GPP TS (Technical Specification) version 8 onwards. Specifically, LTE technology in or after 3GPP TS 36.xxx version 10 is referred to as LTE-A, and LTE technology in or after 3GPP TS 36.xxx version 13 is referred to as LTE-A pro. 3GPP NR refers to technology in or after TS 38.xxx version 15. LTE / NR can be referred to as a 3GPP system. "xxx" refers to the detailed number of the standard document. LTE / NR is generally referred to as a 3GPP system. For background technology, terminology, abbreviations, etc., used to describe this disclosure, reference can be made to the matters described in the standard documents previously published. For example, the following documents can be consulted.

[0038] For 3GPP LTE, please refer to TS 36.211 (Physical Channels and Modulation), TS 36.212 (Multiplexing and Channel Compilation), TS 36.213 (Physical Layer Procedures), TS 36.300 (General Description), and TS 36.331 (Radio Resource Control).

[0039] For 3GPP NR, you can refer to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Compilation), TS 38.213 (Physical Layer Procedures for Control), TS 38.214 (Physical Layer Procedures for Data), TS 38.300 (General Description of NR and NG-RAN (Next Generation Radio Access Network)), and TS 38.331 (Radio Resource Control Protocol Specification).

[0040] The abbreviations of terms that may be used in this disclosure are defined as follows.

[0041] -BM: Beam Management

[0042] -CQI: Channel Quality Indicator

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

[0044] -CSI: Channel State Information

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

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

[0047] -DMRS: Demodulation Reference Signal

[0048] -FDM: Frequency Division Multiplexing

[0049] -FFT: Fast Fourier Transform

[0050] -IFDMA: Interleaved Frequency Division Multiple Access

[0051] -IFFT: Inverse Fast Fourier Transform

[0052] -L1-RSRP: Layer 1 Reference Signal Received Power

[0053] -L1-RSRQ: Layer 1 Reference Signal Receive Quality

[0054] -MAC: Media Access Control

[0055] -NZP: Non-zero power

[0056] -OFDM: Orthogonal Frequency Division Multiplexing

[0057] -PDCCH: Physical Downlink Control Channel

[0058] -PDSCH: Physical Downlink Shared Channel

[0059] -PMI: Precoding Matrix Indicator

[0060] -RE: Resource Element

[0061] -RI: Rank indicator

[0062] -RRC: Radio Resource Control

[0063] -RSSI: Received Signal Strength Indicator

[0064] -Rx: Receive

[0065] -QCL: Quasi-co-location

[0066] -SINR: Signal-to-Noise Ratio

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

[0068] -TDM: Time Division Multiplexing

[0069] -TRP: Sending and Receiving Point

[0070] -TRS: Tracking Reference Signal

[0071] -Tx: Send

[0072] -UE: User Equipment

[0073] -ZP: Zero Power

[0074] Overall System

[0075] With more communication devices requiring higher capacity, there has been a demand for improved mobile broadband communications compared to existing radio access technologies (RATs). Furthermore, massive MTC (machine-type communication) that provides various services anytime, anywhere by connecting multiple devices and things is also one of the main issues to be considered in next-generation communications. In addition, communication system designs considering services / terminals sensitive to reliability and latency are 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 technologies are referred to as NR in this disclosure. NR is an example expression representing 5G RAT.

[0076] New RAT systems, including those for NR, use OFDM or similar transmission methods. These new RAT systems can follow OFDM parameters different from those used in LTE. Alternatively, the new RAT systems can follow existing LTE / LTE-A parameters as is, but can support wider system bandwidths (e.g., 100MHz). Alternatively, a single cell can support multiple parameter sets. In other words, terminals operating according to different parameter sets can coexist in a single cell.

[0077] The parameter set corresponds to a subcarrier spacing in the frequency domain. Different parameter sets can be defined as the reference subcarrier spacing is scaled by an integer N.

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

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

[0080] Figure 2 The diagram illustrates a frame structure in a wireless communication system to which this disclosure can be applied.

[0081] NR systems can support multiple parameter sets. These parameter sets can be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings can be derived by scaling the basic (reference) subcarrier spacing by an integer N (or μ). Furthermore, while it is assumed that very low subcarrier spacings are not used at very high carrier frequencies, the parameter set used can be selected independently of the frequency band. Moreover, various frame structures based on multiple parameter sets can be supported in NR systems.

[0082] The OFDM parameter sets and frame structures that can be considered in an NR system are described below. Several OFDM parameter sets supported in an NR system can be defined as shown in Table 1 below.

[0083] [Table 1]

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

[0085] NR supports multiple sets of parameters (or subcarrier spacing (SCS)) to support various 5G services. For example, a 15kHz SCS supports wide-area coverage of traditional cellular bands; a 30kHz / 60kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidth; and a 60kHz or higher SCS supports bandwidths exceeding 24.25GHz to overcome phase noise.

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

[0087] [Table 2]

[0088] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410MHz–7125MHz 15, 30, 60kHz FR2 24250MHz–52600MHz 60, 120, 240kHz

[0089] Regarding the frame structure in the NR system, the size of various fields in the time domain is expressed as T. c =1 / (Δf) max ·N f The multiple of the time unit. Here, Δf max 480·10 3 Hz, and N f The value is 4096. Downlink and uplink transmissions are configured (organized) to have a duration T. f＝ 1 / (Δf max N f / 100)·T c A radio frame of 10 ms. Here, the radio frame is configured with 10 subframes, each with a T... sf =(Δf max N f / 1000)·T c=1ms duration. In this case, there may be one frame set for the uplink and one frame set for the downlink. Furthermore, the transmission in the i-th uplink frame from the terminal should be T seconds earlier than the corresponding downlink frame in the corresponding terminal. TA =(N TA +N TA,offset )T c Begin. For the subcarrier spacing configuration μ, the time slots are arranged in n-order within the subframe. s μ ∈{0,...,N slot subframe,μ The numbers are numbered in ascending order from -1, and in the radio frames, they are numbered in n... s,f μ ∈{0,...,N slot frame,μ The time slot is configured with N in ascending order of -1. symb slot N consecutive OFDM symbols, and N symb slot The time slot n in the subframe is determined based on the CP. s μ The start of the OFDM symbol n in the same subframe s μ N symb slot The start dates are arranged in time. Not all terminals may perform transmission and reception simultaneously, meaning that all OFDM symbols in either the downlink or uplink time slots may not be available.

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

[0091] [Table 3]

[0092] μ <![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

[0093] [Table 4]

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

[0095] Figure 2 This is an example of μ=2 (SCS is 60kHz), see Table 3. One subframe can include 4 time slots. Figure 2The subframe = {1, 2, 4} slot shown is an example; the number of slots that can be included in a subframe is defined in Table 3 or Table 4. Additionally, micro-slots can include 2, 4, or 7 symbols, or more or fewer symbols.

[0096] Regarding physical resources in an NR system, factors such as antenna ports, resource grids, resource elements, resource blocks, and carrier components can be considered. The following sections will describe these physical resources in detail.

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

[0098] Figure 3 The illustration shows a resource grid in a wireless communication system to which this disclosure can be applied.

[0099] refer to Figure 3 The diagram illustrates the resource grid configuration with N in the frequency domain. RB μ N sc RB There are 14.2 subcarriers, and one subframe is configured with 14.2 μ The number of OFDM symbols is not limited to this. In an NR system, the transmitted signal consists of 2 OFDM symbols. μ N symb (μ) Each OFDM symbol and configuration has N RB μ N sc RB It is described by one or more resource grids of N subcarriers. Here, N RB μ ≤N RB max,μ N RB max,μ This represents the maximum transmission bandwidth, which may differ between uplink and downlink, and between parameter sets. In this case, each μ and antenna port p can be configured with a resource grid. Each element of the resource grid used for μ and antenna port p is called a resource element and is indexed by a pair of... Unique identifier. Here, k = 0, ..., N RB μ N sc RB-1 is the index in the frequency domain, and Refers to the symbol position within a subframe. When referencing resource elements within a time slot, the index pair (k, l) is used. Here, l = 0,...,N symb μ -1. Resource element used for μ and antenna port p. Corresponding to complex values When there is no risk of confusion, or when a specific antenna port or parameter set is not specified, the indices p and μ may be discarded, and the complex values ​​may then be... or Furthermore, a resource block (RB) is defined as N in the frequency domain. sc RB = 12 consecutive subcarriers.

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

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

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

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

[0104] [Equation 1]

[0105]

[0106] In Equation 1, k is defined relative to point A such that k = 0 corresponds to a subcarrier centered at point A. Physical resource blocks range from 0 to N in the bandwidth portion (BWP). BWP,i size,μ -1 is the number, and i is the number of the BWP. The physical resource block n in BWP i. PRB and public resource block n CRB The relationship between them is given by the following equation 2.

[0107] [Equation 2]

[0108]

[0109] N BWP,i start,μ It is a public resource block relative to public resource block 0 in BWP.

[0110] Figure 4 The diagram illustrates physical resource blocks in a wireless communication system to which this disclosure can be applied. Furthermore, Figure 5 The diagram illustrates a time slot structure in a wireless communication system to which this disclosure can be applied.

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

[0112] A carrier comprises 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 Component) is defined as multiple consecutive (physical) resource blocks in the frequency domain and may correspond to a set of parameters (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication can be performed through active BWPs, and only one BWP can be active for a given terminal. In the resource grid, each element is called a resource element (RE) and can be mapped to a complex number of symbols.

[0113] In NR systems, 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 always on, terminal battery consumption may increase. Alternatively, when considering multiple application scenarios operating within a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different sets of parameters (e.g., subcarrier spacing, etc.) can be supported in each band of the corresponding CC. Alternatively, each terminal may have different capabilities for the maximum bandwidth. With this in mind, the base station can instruct the terminal to operate only in a portion of the bandwidth, rather than the full bandwidth of the wideband CC, and for convenience, the corresponding portion of the bandwidth is defined as the bandwidth portion (BWP). The BWP can be configured with consecutive RBs on the frequency axis and can correspond to a set of parameters (e.g., subcarrier spacing, CP length, slot / microslot duration).

[0114] Simultaneously, even within a single CC configured for a terminal, the base station can configure multiple BWPs. For example, a BWP occupying a relatively small frequency domain can be configured in the PDCCH monitoring slot, and PDSCH indicated by the PDCCH can be scheduled in a larger BWP. Alternatively, when a UE is congested in a particular BWP, other BWPs can be configured for some terminals for load balancing. Alternatively, considering inter-cell interference cancellation in the frequency domain between neighboring cells, some intermediate spectrum of the full bandwidth can be excluded, and two edge BWPs can be configured in the same time slot. In other words, the base station can configure at least one DL / UL BWP for a terminal associated with a broadband CC. The base station can activate at least one DL / UL BWP among the configured DL / UL BWPs at a specific time (via L1 signaling, MAC CE (control element), or RRC signaling, etc.). Furthermore, the base station can instruct a handover to other configured DL / UL BWPs (via L1 signaling, MAC CE, or RRC signaling, etc.). Alternatively, based on a timer, a handover to a specific DL / UL BWP can be performed when the timer value expires. Here, the active DL / UL BWP is defined as the active DL / UL BWP. However, when the terminal performs the initial access procedure or before establishing an RRC connection, it may not receive configuration information about the DL / UL BWP. Therefore, in these cases, the DL / UL BWP assumed by the terminal is defined as the initially active DL / UL BWP.

[0115] Figure 6 The illustration shows a physical channel used in a wireless communication system to which this disclosure can be applied, as well as general signal transmission and reception methods using the physical channel.

[0116] In wireless communication systems, terminals receive information from base stations via downlink and transmit information to base stations via uplink. The information sent and received by base stations and terminals includes data and various control information, and various physical channels exist depending on the type / purpose of the information they send and receive.

[0117] When a terminal is powered on or enters a new cell, it performs an initial cell search (S601), including synchronization with the base station. For the initial cell search, the terminal synchronizes with the base station by receiving the primary synchronization signal (PSS) and secondary synchronization signal (SSS) from the base station, and obtains information such as the cell identifier (ID). Then, the terminal obtains broadcast information within the cell by receiving the physical broadcast channel (PBCH) from the base station. Simultaneously, the terminal checks the downlink channel state by receiving the downlink reference signal (DL RS) during the initial cell search phase.

[0118] The terminal that has completed the initial cell search can obtain more detailed system information by receiving the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH) based on the information carried in the PDCCH (S602).

[0119] Simultaneously, when a terminal first accesses a base station or when there are no radio resources available for signal transmission, it can perform a random access (RACH) procedure (S603 to S606) with the base station. For the random access procedure, the terminal can send a specific sequence as a preamble via the Physical Random Access Channel (PRACH) (S603 and S605), and can receive response messages to the preamble via the PDCCH and the corresponding PDSCH (S604 and S606). Contention-based RACH can additionally execute a contention resolution procedure.

[0120] The terminal that subsequently performs the above process can execute 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 PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format varies depending on its intended use.

[0121] Meanwhile, 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 (acknowledgment / non-acknowledgment) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. For 3GPP LTE systems, the terminal can send the aforementioned control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

[0122] Table 5 shows examples of DCI format in the NR system.

[0123] [Table 5]

[0124]

[0125] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information (e.g., UL / SUL (Supplemental UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), information related to transport blocks (TB) (e.g., MCS (Modulation Compilation and 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 multiple antennas (e.g., DMRS sequence initialization information, antenna ports, CSI requests, etc.), power control information related to PUSCH scheduling (e.g., PUSCH power control, etc.), and control information included in each DCI format can be predefined.

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

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

[0128] DCI format 0_2 is used to schedule PUSCH in a cell. The information included in DCI format 0_2 is CRC scrambled and transmitted via C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0129] 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 (TB) (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 (sound reference signal) request, etc.), information related to PUCCH scheduling regarding PDSCH (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format can be predefined.

[0130] DCI format 1_0 is used to schedule PDSCH in a DL cell. The information included in DCI format 1_0 is CRC scrambled and transmitted via C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0131] DCI format 1_1 is used to schedule PDSCH in a cell. The information included in DCI format 1_1 is CRC scrambled and transmitted via C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0132] DCI format 1_2 is used to schedule PDSCH in a cell. The information contained in DCI format 1_2 is CRC scrambled and transmitted via C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0133] Operations related to multiple TRPs

[0134] Coordinated Multipoint (CoMP) schemes refer to a method in which multiple base stations effectively control interference by exchanging (e.g., using the X2 interface) or utilizing channel information fed back by terminals (e.g., RI / CQI / PMI / LI (layer indicators)) and cooperating in transmitting it to the terminals. Depending on the scheme used, CoMP can be classified into Joint Transmission (JT), Coordinated Scheduling (CS), Coordinated Beamforming (CB), Dynamic Point Selection (DPS), Dynamic Point Blocking (DPB), etc.

[0135] M-TRP transmission schemes that send data from M TRPs to a terminal can be mainly classified into i) eMBB M-TRP transmission, a scheme used to improve the transmission rate, and ii) URLLC M-TRP transmission, a scheme used to increase the success rate of reception and reduce latency.

[0136] Furthermore, regarding DCI transmission, M-TRP transmission schemes can be classified into i) M-TRP transmission based on M-DCI (multiple DCIs), where each TRP sends a different DCI, and ii) M-TRP transmission based on S-DCI (single DCI), where only one TRP sends the DCI. For example, for S-DCI-based M-TRP transmission, all scheduling information regarding data sent by M TRPs should be delivered to the terminal via a single DCI. This can be used in an ideal backhaul (ideal BH) environment, where dynamic cooperation between two TRPs is possible.

[0137] For TDM-based URLLC M-TRP transmission, schemes 3 and 4 are being discussed for standardization. Specifically, scheme 4 refers to a scheme where a TRP transmits a transport block (TB) in one time slot, and it 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 where a TRP transmits a TB through a consecutive number of OFDM symbols (i.e., symbol groups), and the TRP can be configured to transmit the same TB through different symbol groups in one time slot.

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

[0139] The following text will describe incoherent joint transport (NCJT) based on multiple DCIs / NCJT based on a single DCI.

[0140] NCJT (Noncoherent Joint Transmission) is a scheme in which multiple transmission points (TPs) send data to a terminal using the same time and frequency resources. The TPs send data between each other using different DMRS (Demodulation Multiplexing Reference Signals) through different layers (i.e., through different DMRS ports).

[0141] The TP delivers data scheduling information to the receiving terminal via DCI. Here, the scheme where each TP participating in NCJT delivers scheduling information about its own transmitted data via DCI is called "multi-DCI-based NCJT". Since each of the N TPs participating in NCJT transmission sends a DL license DCI and a PDSCH to the UE, the UE receives N DCIs and N PDSCHs from the N TPs. Simultaneously, the scheme where a representative TP delivers scheduling information about data transmitted by itself and data transmitted by different TPs (i.e., TPs participating in NCJT) via a single DCI is called "single-DCI-based NCJT". Here, N TPs transmit one PDSCH, but each TP's transmission includes only some of the multiple layers in a single PDSCH. For example, when transmitting 4 layers of data, TP 1 can transmit 2 layers to the UE, and TP 2 can transmit the remaining 2 layers to the UE.

[0142] Multiple TRPs (MTRPs) performing NCJT transmissions can send DL data to the terminal by using either of the following two schemes.

[0143] First, the “MTRP scheme based on a single DCI” is described. MTRPs cooperatively transmit a common PDSCH, and each TRP participating in the cooperative transmission spatially partitions and sends its corresponding PDSCH to different layers (i.e., different DMRS ports) using the same time and frequency resources. Here, a single DCI indicates to the UE scheduling information regarding the PDSCH, and which DMRS(group) port uses which QCL RS, as well as the QCL type information, is indicated by the corresponding DCI (which is different from the DCI indicating that the QCL RS and type will be applied to all DMRS ports as indicated in the existing scheme). In other words, M TCI states (e.g., 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. Additionally, DMRS port information can be indicated by using a new DMRS table.

[0144] Next, the "Multi-DCI-based MTRP Scheme" is described. Each MTRP transmits different DCIs and PDSCHs, and the corresponding PDSCHs (partially or entirely) overlap and are transmitted in frequency-time resources. The corresponding PDSCHs can be scrambled using different scrambling IDs (identifiers), and DCIs can be transmitted using CORESETs belonging to different CORESET groups. (Here, CORESET groups can be identified by an index defined in the CORESET configuration for each CORESET. For example, when index = 0 is configured for CORESETs 1 and 2 and index = 1 is configured for CORESETs 3 and 4, CORESETs 1 and 2 are in CORESET group 0, and CORESETs 3 and 4 belong to CORESET group 1. Furthermore, when no index is defined in a CORESET, it can be interpreted as index = 0.) When multiple scrambling IDs are configured in a serving cell or two or more CORESET groups are configured, the UE can be aware that it is receiving data according to the Multi-DCI-based MTRP operation.

[0145] Alternatively, the MTRP scheme based on a single DCI or the MTRP scheme based on multiple DCIs can be indicated to the UE via separate signaling. In the example, for a serving cell, multiple CRS (Cell Reference Signal) patterns can be indicated to the UE for MTRP operation. In this case, the PDSCH rate matching for the CRS can differ 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).

[0146] In the following, the CORESET group ID described / mentioned in this disclosure may refer to index / identification information (e.g., ID, etc.) used to distinguish CORESETs for each TRP / panel. Alternatively, a CORESET group may be a group / union of CORESETs distinguished by index / identification information (e.g., ID) / CORESET group ID, etc., used to distinguish CORESETs for each TRP / panel. In the example, the CORESET group ID may be specific index information defined in the CORESET configuration. In this case, the CORESET group can be configured / indicated / defined by an index defined in the CORESET configuration for each CORESET. Additionally / alternatively, the CORESET group ID may refer to index / identification information / indicators, etc., used to distinguish / identify CORESETs associated with each TRP / panel configuration. In the following, the CORESET group ID described / mentioned in this disclosure may be replaced by a specific index / specific identification information / specific indicator used to distinguish / identify CORESETs associated with each TRP / panel configuration. The CORESET group ID can be configured / indicated to the terminal via higher-level signaling (e.g., RRC signaling) / L2 signaling (e.g., MAC-CE) / L1 signaling (e.g., DCI), i.e., a specific index / specific identification information / specific indicator used to distinguish / identify CORESETs configured / associated with each TRP / panel. In the example, it can be configured / indicated that PDCCH detection will be performed on a per-TRP / panel basis (i.e., per TRP / panel belonging to the same CORESET group) at the corresponding CORESET group level. Additionally / alternatively, it can 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 on a per-TRP / panel basis (i.e., per TRP / panel belonging to the same CORESET group) at the corresponding CORESET group level (i.e., per TRP / panel belonging to the same CORESET group). Additional / alternative locations can manage HARQ A / N (processing / retransmission) for PDSCH / PUSCH, etc., scheduled per TRP / panel, according to the corresponding CORESET group (i.e., by TRP / panel belonging to the same CORESET group).

[0147] The partially overlapping NCJT will be described below.

[0148] Furthermore, NCJTs can be classified into fully overlapping NCJTs, where the time and frequency resources transmitted by each TP completely overlap, and partially overlapping NCJTs, where only some time and frequency resources overlap. In other words, for partially overlapping NCJTs, data from both TP 1 and TP 2 are transmitted in some time and frequency resources, and data from only one of TP 1 or TP 2 is transmitted in the remaining time and frequency resources.

[0149] The following section describes methods for improving reliability in multiple TRPs.

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

[0151] Figure 7 The illustration shows a method for multi-TRP transmission that can be applied to a wireless communication system according to the present disclosure.

[0152] refer to Figure 7 (a) illustrates the case where layer groups transmitting the same codeword (CW) / transmission block (TB) correspond to different TRPs. Here, a layer group can refer to a predetermined set of layers comprising one or more layers. In this case, there are advantages: the amount of transmission resources increases due to the number of layers, allowing robust channels with low compilation rates to be compiled for the TB; and additionally, since multiple TRPs have different channels, improved reliability of the received signal can be expected based on diversity gain.

[0153] refer to Figure 7 (b) illustrates an example of transmitting 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 TB being transformed into different CWs by different TRPs through channel compilation, etc. Therefore, this can be seen as an example of repeatedly transmitting the same TB. Figure 7 In the case of (b), with Figure 7 (a) The disadvantage is that the code rate is higher corresponding to the TB. However, the advantage is that the code rate can be adjusted by indicating different RV (redundant version) values, or the modulation order of each CW generated from the same TB can be adjusted according to the channel environment.

[0154] 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 transmitted through different layer groups, and each layer group is transmitted by a different TRP / panel. It is called the SDM (Space Division Multiplexing) based M-TRP URLLC transmission method. Layers belonging to different layer groups are transmitted separately through DMRS ports belonging to different DMRS CDM groups.

[0155] Furthermore, the above content related to multiple TRPs is described based on the SDM (Space Division Multiplexing) method using different layers, but it can be naturally extended and applied to FDM (Frequency Division Multiplexing) methods based on different frequency domain resources (e.g., RB / PRB (sets) etc.) and / or TDM (Time Division Multiplexing) methods based on different time domain resources (e.g., time slots, symbols, sub-symbols etc.).

[0156] Regarding methods for URLLC based on multiple TRPs scheduled by a single DCI, the following approaches are discussed.

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

[0158] 1-a) Method 1a

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

[0160] - Use a single codeword with one RV in all spatial layers or all layer sets. Regarding UE, map different compiled bits to different layers or layer sets using the same mapping rules.

[0161] 1-b) Method 1b

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

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

[0164] 1-c) Method 1c

[0165] - In a transmission time (timing), send the same TB with a DMRS port associated with multiple TCI status indices in a layer, or send the same TB with multiple DMRS ports associated one-to-one with multiple TCI status indices in a layer.

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

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

[0168] - Each non-overlapping frequency resource allocation is associated with a TCI state.

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

[0170] 2-a) Method 2a

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

[0172] 2-b) Method 2b

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

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

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

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

[0177] - At each transmission time (opportunity) within a time slot, the common MCS is used with one or more DMRS ports.

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

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

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

[0181] - Each transmission time (opportunity) across K time slots uses a common MCS with one or more DMRS ports.

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

[0183] The MTRP URLLC is described below.

[0184] In this disclosure, DL MTRP URLLC refers to multiple TRPs transmitting the same data (e.g., the same TB) / DCI using different tier / time / frequency resources. For example, TRP 1 transmits the same data / DCI in resource 1, and TRP 2 transmits the same data / DCI in resource 2. A UE configured with the DL MTRP-URLLC transmission method receives the same data / DCI using different tier / time / frequency resources. Here, the base station configures the UE to use which QCL RS / type (i.e., DL TCI state) should be used in the tier / time / frequency resources for receiving the same data / DCI. For example, when receiving the same data / DCI 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.

[0185] Furthermore, in this disclosure, UL MTRP-URLLC refers to multiple TRPs receiving the same data / UCI (uplink control information) from any UE 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, sharing the received data / DCI via a backhaul link connected between the TRPs. UEs configured with the UL MTRP-URLLC transmission method transmit the same data / UCI using different layer / time / frequency resources. In this case, the base station configures the UE for which Tx beam and which Tx power (i.e., UL TCI state) should be used in the layer / time / frequency resources for transmitting the same data / DCI. For example, when transmitting the same data / UCI 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.

[0186] Additionally, in this 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 can refer to estimating the channel from the DMRS in that frequency / time / space resource (layer) using the QCL type and QCL RS indicated by the corresponding TCI state, and receiving / demodulating data / DCI based on the estimated channel. For UL, this can refer to transmitting / modulating DMRS and data / UCI in that frequency / time / space resource (layer) using the Tx beam and power indicated by the corresponding TCI state.

[0187] Here, the UL TCI state contains the UE's Tx beam and / or Tx power information, and can be configured with spatial relationship information, etc., through other parameters, instead of the TCI state. The UL TCI state can be directly indicated by the UL-permitted DCI, or it can refer to the spatial relationship information of the SRS resources indicated by the SRI (Probe Resource Indicator) field of the UL-permitted DCI. Alternatively, it can refer to the open-loop (OL) Tx power control parameters connected to the values ​​indicated by the SRI field of the UL-permitted DCI (e.g., j: index of open-loop parameters Po and alpha (up to 32 parameter value sets per cell), q_d: index of DL RS resources used for PL (path loss) measurement (up to 4 measurements per cell), l: index of closed-loop power control process (up to 2 processes per cell)).

[0188] The MTRP eMBB is described below.

[0189] In this disclosure, MTRP-eMBB refers to multiple TRPs transmitting different data (e.g., different TBs) using different layers / times / frequency. A UE configured with the MTRP-eMBB transmission method receives indications about multiple TCI states via DCI, and it is assumed that the data received using the QCL RS for each TCI state is different.

[0190] On the other hand, the UE can distinguish between MTRP URLLC and MTRP eMBB transmissions / receives by separately assigning RNTIs for MTRP-URLLC and RNTIs for MTRP-eMBB. In other words, when DCI CRC masking is performed using the RNTI for URLLC, the UE treats it as a URLLC transmission, and when DCI CRC masking is performed using the RNTI for eMBB, the UE treats it as an eMBB transmission. Alternatively, the base station can configure MTRP URLLC or MTRP eMBB transmissions / receives to the UE via additional signaling.

[0191] In the description of this disclosure, for ease of description, it is described by assuming cooperative transmission / reception between two TRPs. However, the method proposed in this disclosure can also be extended and applied in environments with three or more TRPs, and additionally, it can also be extended and applied in multiple panel environments (i.e., by matching TRPs to panels). Furthermore, different TRPs can be identified as having different TCI states than the UE. Therefore, when the UE receives / transmits data / DCI / UCI using TCI state 1, it means receiving / transmitting data / DCI / UCI from / to TRP 1.

[0192] In the following description, the method proposed in this disclosure can be used when MTRP cooperatively sends PDCCH (repeatedly or partially sending the same PDCCH). Additionally, the method proposed in this disclosure can also be used when MTRP cooperatively sends PDSCH or cooperatively receives PUSCH / PUCCH.

[0193] Furthermore, in this disclosure, when multiple base stations (i.e., MTRPs) repeatedly transmit the same PDCCH, this can refer to transmitting the same DCI through multiple PDCCH candidates, and it can also refer to multiple base stations repeatedly transmitting the same DCI. Here, the same DCI can refer to two DCIs having the same DCI format / size / payload. Alternatively, although two DCIs have different payloads, they can be considered the same DCI when the scheduling result is the same. For example, the TDRA (Time Domain Resource Allocation) field of the DCI determines the time slot / symbol position of the data and the time slot / symbol position of A / N (ACK / NACK) based on the timing of the DCI reception. Therefore, if a DCI received at n timings and a DCI received at n+1 timings notify 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 upon by them to the UE. Alternatively, even though two DCIs have different payloads and different scheduling results, they can be considered the same DCI if the scheduling result of one DCI is a subset of the scheduling result of the other 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 becomes a subset of the scheduled data of DCI 1, and since the two DCIs are scheduling the same data, they can be considered the same DCI in this case.

[0194] Furthermore, in this disclosure, when multiple base stations (i.e., MTRPs) partially transmit the same PDCCH, it means that a 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. For example, when PDCCH candidates corresponding to aggregation level m1+m2 are partially transmitted through TRP 1 and TRP 2, the PDCCH candidates can be divided into PDCCH candidate 1 corresponding to aggregation level m1 and PDCCH candidate 2 corresponding to aggregation level m2, and TRP 1 can transmit PDCCH candidate 1 and TRP 2 can transmit PDCCH candidate 2 to different time / frequency resources. After the UE receives PDCCH candidate 1 and PDCCH candidate 2, it can generate a PDCCH candidate corresponding to aggregation level m1+m2 and attempt DCI decoding.

[0195] Additionally, when the same DCI is partially sent to multiple PDCCH candidates, there are two possible implementation methods.

[0196] According to the first method, the DCI payload (i.e., control information bits and CRC) can be encoded by a single channel encoder (e.g., a polar encoder), and the resulting compiled bits can be partially transmitted by multiple TRPs. In this case, for each compiled bit transmitted by a TRP, either all the DCI payload can be encoded, or only a portion of the DCI payload can be encoded.

[0197] According to the second method, the DCI payload (i.e., control information bits and CRC) can be divided into multiple DCI parts (e.g., two, a first DCI and a second DCI), and each part can be encoded by a channel encoder (e.g., a polar encoder). Subsequently, TRP1 can send the encoded bits corresponding to the first DCI, and TRP2 can send the encoded bits corresponding to the second DCI.

[0198] In summary, when multiple base stations (MTRPs) partially / repeatedly transmit the same PDCCH across multiple MOs, the following meanings can be included.

[0199] For example, the compiled DCI bits encoding all DCI content of the corresponding PDCCH can be repeatedly sent for each base station (STRP), and the same compiled DCI bits can be repeatedly sent for each MO.

[0200] Alternatively, the compiled DCI bits that encode all DCI content of the corresponding PDCCH can be divided into multiple parts, and different parts can be sent for each base station (STRP) via each MO.

[0201] Alternatively, the DCI content of the corresponding PDCCH can be divided into multiple parts, and the different parts can be encoded separately for each base station (STRP) and can be transmitted through each MO.

[0202] Whether PDCCH is transmitted repeatedly or partially, it can be understood that PDCCH is transmitted multiple times across multiple transmission times (TOs). TO can refer to a specific time / frequency resource unit (RB) for transmitting the PDCCH. For example, when PDCCH is transmitted multiple times across time slots 1, 2, 3, and 4 (through a specific set of RBs), TO can refer to each time slot. Alternatively, when PDCCH is transmitted multiple times across RB sets 1, 2, 3, and 4 (within a specific set of RBs), TO can refer to each RB set. Alternatively, when PDCCH is transmitted multiple times across different time and frequency resources, TO can refer to each combination of time and frequency resources.

[0203] Additionally, the TCI states used for DMRS channel estimation can be configured differently based on the TOs. It can be assumed that TOs with different TCI state configurations are transmitted by different TRPs / panels. When multiple base stations transmit PDCCH repeatedly or partially, this might refer to transmitting PDCCH across multiple TOs, and the union of the TCI states configured for the corresponding TOs includes at least two TCI states. For example, when transmitting PDCCH across TOs 1, 2, 3, 4, TCI states 1, 2, 3, 4 can be configured for each of TOs 1, 2, 3, 4, which could mean that TRP i cooperatively transmits PDCCH in TO i.

[0204] Additionally, in this disclosure, when a UE repeatedly transmits the same PUSCH so that multiple base stations (i.e., MTRPs) can receive it, this can refer to the UE transmitting the same data through multiple PUSCHs. In this case, each PUSCH can be optimized and transmitted to the UL channel of a different TRP. For example, when the UE repeatedly transmits the same data through PUSCH 1 and 2, PUSCH 1 is transmitted using UL TCI state 1 for TRP 1, and in this case, link adaptation such as precoder / MCS can also be scheduled / applied to channel-optimized values ​​for TRP 1. PUSCH 2 is transmitted using UL TCI state 2 for TRP 2, and link adaptation such as precoder / MCS can also be scheduled / applied to channel-optimized values ​​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.

[0205] Additionally, in this disclosure, when a UE transmits the same PUSCH separately so that multiple base stations (i.e., MTRPs) can receive it, this could mean that the UE transmits one data through a single PUSCH, but it partitions the resources allocated to that PUSCH, optimizes them for the UL channels of different TRPs, and transmits them accordingly. For example, when the UE transmits the same data through a 10-symbol PUSCH, the data is transmitted in the first 5 symbols using UL TCI state 1 for TRP 1, and in this case, link adaptation such as precoder / MCS can also be scheduled / applied to channel-optimized values ​​for TRP 1. The remaining data is transmitted in the remaining 5 symbols using UL TCI state 2 for TRP 2, and in this case, link adaptation such as precoder / MCS can also be scheduled / applied to channel-optimized values ​​for TRP 2. In this example, a PUSCH is partitioned into time resources for TDM processing of transmissions for TRP 1 and for TRP 2, but it can be transmitted using FDM / SDM methods.

[0206] In addition, similar to the PUSCH transmission described above, the UE can repeatedly send the same PUCCH, or it can send the same PUCCH separately, so that multiple base stations (i.e., MTRPs) can receive it.

[0207] In the following text, the proposals of this disclosure can be extended and applied to various channels, such as PUSCH / PUCCH / PDSCH / PDCCH, etc.

[0208] The proposals in this disclosure can be extended and applied to situations where various uplink / downlink channels are repeatedly transmitted to different time / frequency / spatial resources and situations where various uplink / downlink channels are partially transmitted to different time / frequency / spatial resources.

[0209] Control Resource Set (CORESET)

[0210] Predetermined resources for monitoring downlink control channels (e.g., PDCCH) can be defined based on control channel elements (CCE), resource element groups (REG), and control resource sets (CORESET). Furthermore, predetermined resources can be defined as resources not used for DMRS associated with downlink control channels.

[0211] CORESET corresponds to time-frequency resources used to attempt to decode control channel candidates using one or more search spaces (SS). For example, CORESET is defined as a resource in which a terminal can receive PDCCH but the base station does not necessarily transmit PDCCH within the CORESET.

[0212] In the time-frequency domain, the size and location of a CORESET can be configured semi-statically by the network. In the time domain, a CORESET can be located within any symbol in a timeslot. For example, the duration of a CORESET can be defined as up to two or three symbol durations. In the frequency domain, a CORESET can be located at any frequency within the active bandwidth portion (BWP) of the carrier bandwidth. The frequency size of a CORESET can be defined as a multiple of six RB units of the carrier bandwidth (e.g., 400 MHz) or less. The time-frequency location and size of a CORESET can be configured via RRC signaling.

[0213] The first CORESET (or CORESET 0) can be configured by a Master Information Block (MIB) provided via the PBCH. The MIB can be obtained from the network by the terminal during the initial access procedure, and the terminal can monitor the PDCCH, including information from the Scheduling System Information Block 1 (SIB1), within CORESET 0 configured by the MIB. After the terminal is configured for connection, one or more additional CORESETs can be configured via RRC signaling. Identifiers can be assigned to each of the multiple CORESETs. Multiple CORESETs can overlap.

[0214] A PDSCH in a time slot can also be positioned before or after the start of a PDCCH in a CORESET. Furthermore, unused CORESET resources can be reused for PDSCH. For this purpose, reserved resources are defined, which may overlap with CORESETs. For example, one or more reserved resource candidates can be configured, and each reserved resource candidate can be configured by a bitmap in a time resource unit and a bitmap in a frequency resource unit. Whether a configured reserved resource candidate is active (or whether it can be used for PDSCH) can be dynamically indicated or configured semi-statically via DCI.

[0215] A CCE-to-REG mapping can be defined for each CORESET. Here, one REG corresponds to one OFDM symbol and one RB (i.e., 12 subcarriers). One CCE can correspond to six REGs. The CCE-to-REG mappings for different CORESETs can be the same or configured differently. Mappings can be defined on a REG bundle basis. A REG bundle can correspond to a set of REGs for which the terminal assumes consistent precoding will be applied. The CCE-to-REG mapping may or may not include interleaving. For example, when interleaving is not applied, a REG bundle configured with six consecutive REGs can form a CCE. When interleaving is applied, the size of the REG bundle can be 2 or 6 when the duration of the CORESET is 1 or 2 OFDM symbols, and the size of the REG bundle can be 3 or 6 when the duration of the CORESET is 3 OFDM symbols. A block interleaver can be applied to distribute different REG bundles across the frequency domain and map them to CCEs. The number of rows of the block interleaver can be variably configured for various frequency diversity.

[0216] To enable a terminal to receive the PDCCH, channel estimation using PDCCH DMRS can be performed. The PDCCH can use a single antenna port (e.g., antenna port index 2000). The PDCCH DMRS sequence is generated across the entire common resource block in the frequency domain, but it can be transmitted only within the resource block associated with the PDCCH. Furthermore, the terminal may not know the location of the common resource block before obtaining system information during initial access; therefore, for CORESET 0 configured via the MIB provided through the PBCH, the PDCCH DMRS sequence can be generated from the first resource block of CORESET 0. The PDCCH DMRS can be mapped to every four subcarriers in the REG. The terminal can perform channel estimation using PDCCH DMRS on a REG-by-REG basis.

[0217] Quasi-co-located (QCL)

[0218] Define antenna ports such that the channel transmitting symbols in the same antenna port can be inferred from the channels transmitting other symbols in the same antenna port. When the properties of the channel carrying symbols from one antenna port can be inferred from the channel carrying symbols from another antenna port, the two antenna ports can be said to be in a QC / QCL (quasi-co-location or quasi-co-addressable) relationship.

[0219] Here, channel attributes include at least one of delay spread, Doppler spread, frequency / Doppler shift, average received power, receive timing / average delay, or spatial Rx parameters. Here, spatial Rx parameters refer to spatial (Rx) channel characteristic parameters, such as the angle of arrival.

[0220] The terminal can be configured at a list of up to M TCI state configurations in the higher-level parameter PDSCH-Config to decode the PDSCH based on the detected PDCCH with the expected DCI for the corresponding terminal and a given serving cell. M depends on the UE capability.

[0221] Each TCI state includes parameters for configuring the quasi-co-address relationship between one or two DL reference signals and the ports of the PDSCH DM-RS (demodulation reference signal).

[0222] The quasi-co-address relationship is configured by the higher-level parameter qcl-Type1 for the first DL RS and qcl-Type2 (if configured) for the second DL RS. The QCL types are different for the two DL RSs, regardless of whether they reference the same or different DL RSs.

[0223] The QCL type corresponding to each DL RS is given by the higher-level parameter qcl-Type of QCL-Info and can take one of the following values.

[0224] - "QCL-TypeA": {Doppler frequency shift, Doppler spread, average delay, delay spread}

[0225] - "QCL-TypeB": {Doppler frequency shift, Doppler spread}

[0226] - "QCL-TypeC": {Doppler frequency shift, average delay}

[0227] - "QCL-TypeD": {Space Rx parameter}

[0228] For example, when the target antenna port is a specific NZP CSI-RS, the corresponding NZP CSI-RS antenna port can be quasi-co-located with a specific TRS for QCL-Type A and quasi-co-located with a specific SSB for QCL-Type D. The terminal receiving this instruction / configuration can receive the corresponding NZP CSI-RS by using the Doppler delay value measured in the QCL-Type A TRS and by applying the Rx beam to receive the QCL-Type D SSB to receive the corresponding NZP CSI-RS.

[0229] The UE can receive activation commands via MAC CE signaling, which is used to map up to 8 TCI states to code points in the DCI field "Transmission Configuration Indication".

[0230] When a HARQ-ACK corresponding to the PDSCH carrying the activation command is sent in time slot n, it can be sent from time slot n+3N.slot subframe,μ +1 is applied to the mapping between the code points indicating the TCI state and the DCI field "Transmission Configuration Indication". After receiving the initial higher-layer configuration for the TCI state before the UE receives the activation command, for QCL-Type A, and if applicable, for QCL-Type D, the UE may assume that the DMRS port of the serving cell's PDSCH is quasi-co-configured with the SS / PBCH block determined during the initial access procedure.

[0231] When a higher-layer parameter indicating the presence of a TCI field in the DCI configured for the UE (e.g., tci-PresentInDCI) is set to enable a CORESET for scheduling PDSCH, the UE may assume the presence of a TCI field in the DCI format 1_1 of the PDCCH transmitted in the corresponding CORESET. When tci-PresentInDCI is not configured for a CORESET for scheduling PDSCH, or when PDSCH is scheduled by DCI format 1_0 and the time offset between the reception of the DL DCI and the corresponding PDSCH is equal to or greater than a predetermined threshold (e.g., timeDurationForQCL), to determine the PDSCH antenna port QCL, the UE may assume the same TCI state or QCL assumption for PDSCH as the TCI state or QCL assumption applied to the CORESET for PDCCH transmission. Here, the predetermined threshold may be based on reported UE capabilities.

[0232] When the parameter tci-PresentInDCI is enabled, the TCI field in the DCI of the scheduled CC (component carrier) can indicate the active TCI state of the scheduled CC or DL ​​BWP. When scheduling PDSCH via DCI format 1_1, the UE can use the TCI state to determine the PDSCH antenna port QCL based on the value of the "Transmission Configuration Indication" field of the detected PDCCH with DCI.

[0233] When the time offset between the reception of DL DCI and the corresponding PDSCH is equal to or greater than a predetermined threshold (e.g., timeDurationForQCL), the UE may assume that the DMRS port of the serving cell's PDSCH is quasi-co-located with the RS of the TCI state for the QCL type parameter given by the indicated TCI state.

[0234] When configuring a single-slot PDSCH for a UE, the indicated TCI state can be based on the active TCI state of the slot with the scheduled PDSCH.

[0235] When a multi-slot PDSCH is configured for a UE, the indicated TCI state can be based on the active TCI state of the first slot with the scheduled PDSCH, and the UE can expect that the active TCI state across slots with the scheduled PDSCH is the same.

[0236] When configuring a CORESET associated with a search space set used for cross-carrier scheduling for a UE, the UE may expect the tci-PresentInDCI parameter to be set to enabled for the corresponding CORESET. When configuring one or more TCI states for a serving cell scheduled by a search space set including QCL-TypeD, the UE may expect the time offset between the reception of a PDCCH detected in the search space set and the corresponding PDSCH to be equal to or greater than a predetermined threshold (e.g., timeDurationForQCL).

[0237] When the parameter tci-PresentInDCI is enabled and when tci-PresentInDCI is not configured in RRC connection mode, the UE can assume that the DMRS port of the serving cell's PDSCH is quasi-co-located with the RS quasi-co-located for the QCL parameter, which is used to indicate the PDCCH QCL of the CORESET associated with the monitored search space with the lowest CORESET-ID in the most recent slot monitored by the UE in one or more CORESETs in the active BWP of the serving cell.

[0238] In this scenario, when the QCL-TypeD of the PDSCH DMRS differs from that of the PDCCH DMRS and they overlap in at least one symbol, the UE can expect that reception of the PDCCH associated with the corresponding CORESET will be prioritized. This can also be applied to in-band CA (carrier aggregation) (when the PDSCH and CORESET exist in different CCs). When any configured TCI state does not include QCL-TypeD, different QCL assumptions can be derived from the TCI state indicated for the scheduled PDSCH, regardless of the time offset between the reception of the DL DCI and the corresponding PDSCH.

[0239] For periodic CSI-RS resources of a configured NZP-CSI-RS-ResourceSet that includes the higher-level parameter trs-Info, the UE can anticipate the TCI state to indicate one of the following QCL types.

[0240] - With QCL-Type C of the SS / PBCH block, and if applicable, with QCL-Type D of the same SS / PBCH block, or

[0241] - QCL-TypeC with the SS / PBCH block, and, if applicable, QCL-TypeD with the CSI-RS resource in the NZP-CSI-RS-ResourceSet configuration that includes repeating higher-level parameters.

[0242] For non-periodic CSI-RS resources in a configuration NZP-CSI-RS-ResourceSet that includes the higher-layer parameter trs-Info, the UE can anticipate the TCI state to indicate QCL-Type A with the periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet that includes the higher-layer parameter trs-Info, and, if applicable, QCL-Type D with the same periodic CSI-RS resources.

[0243] For CSI-RS resources of an NZP-CSI-RS-ResourceSet configured without higher-level parameter trs-Info and without higher-level parameter duplication, the UE can expect the TCI state to indicate one of the following QCL types.

[0244] - With the CSI-RS resource of the NZP-CSI-RS-ResourceSet, which includes the higher-level parameter trs-Info, and, if applicable, with the QCL-TypeD of the same CSI-RS resource, or

[0245] - With the CSI-RS resource of the NZP-CSI-RS-ResourceSet, which includes the higher-level parameter trs-Info, and, if applicable, with the QCL-TypeD of the SS / PBCH block, or

[0246] - The QCL-TypeA of the CSI-RS resource in the NZP-CSI-RS-ResourceSet with a configuration that includes the higher-level parameter trs-Info, and, if applicable, the QCL-TypeD of the CSI-RS resource in the NZP-CSI-RS-ResourceSet with a configuration that repeats the higher-level parameter, or

[0247] - When QCL-TypeD is not applicable, use QCL-TypeB for the CSI-RS resources in the NZP-CSI-RS-ResourceSet, which includes the higher-level parameter trs-Info.

[0248] For CSI-RS resources in an NZP-CSI-RS-ResourceSet that includes configurations with repeated higher-level parameters, the UE can anticipate the TCI state to indicate one of the following QCL types.

[0249] - With the CSI-RS resource of the NZP-CSI-RS-ResourceSet, which includes the higher-level parameter trs-Info, and, if applicable, with the QCL-TypeD of the same CSI-RS resource, or

[0250] - The QCL-TypeA of the CSI-RS resource in the NZP-CSI-RS-ResourceSet with a configuration that includes the higher-level parameter trs-Info, and, if applicable, the QCL-TypeD of the CSI-RS resource in the NZP-CSI-RS-ResourceSet with a configuration that repeats the higher-level parameter, or

[0251] - QCL-TypeC with the SS / PBCH block, and QCL-TypeD with the same SS / PBCH block, if applicable.

[0252] For DMRS of PDCCH, the UE may expect TCI status to indicate one of the following QCL types.

[0253] - With the CSI-RS resource of the NZP-CSI-RS-ResourceSet, which includes the higher-level parameter trs-Info, and, if applicable, with the QCL-TypeD of the same CSI-RS resource, or

[0254] - The QCL-TypeA of the CSI-RS resource in the NZP-CSI-RS-ResourceSet with a configuration that includes the higher-level parameter trs-Info, and, if applicable, the QCL-TypeD of the CSI-RS resource in the NZP-CSI-RS-ResourceSet with a configuration that repeats the higher-level parameter, or

[0255] - The QCL-TypeA of the CSI-RS resource of the NZP-CSI-RS-ResourceSet configured without higher-level parameter trs-Info and without higher-level parameter duplication, and, if applicable, the QCL-TypeD of the same CSI-RS resource.

[0256] For DMRS of PDSCH, the UE may expect the TCI state to indicate one of the following QCL types.

[0257] - With the CSI-RS resource of the NZP-CSI-RS-ResourceSet, which includes the higher-level parameter trs-Info, and, if applicable, with the QCL-TypeD of the same CSI-RS resource, or

[0258] - The QCL-TypeA of the CSI-RS resource in the NZP-CSI-RS-ResourceSet with a configuration that includes the higher-level parameter trs-Info, and, if applicable, the QCL-TypeD of the CSI-RS resource in the NZP-CSI-RS-ResourceSet with a configuration that repeats the higher-level parameter, or

[0259] - The QCL-TypeA of the CSI-RS resource of the NZP-CSI-RS-ResourceSet configured without higher-level parameter trs-Info and without higher-level parameter duplication, and, if applicable, the QCL-TypeD of the same CSI-RS resource.

[0260] Downlink transmission and reception based on default spatial parameters

[0261] In the following description, the term "spatial parameters" may refer to beam transmission and reception-related parameters for downlink reception or uplink transmission of a terminal.

[0262] For example, spatial parameters related to downlink transmission and reception may include QCL information, which is applied to the physical channel for transmitting and receiving downlink control information or data, or assumed by the terminal. QCL information may include QCL RS information, and can be configured according to QCL type (e.g., QCL type A / B / C / D). For example, downlink control information (DCI) can be transmitted and received via PDCCH, and spatial parameters related to DCI transmission and reception may include QCL reference information, TCI status information, etc., for one or more PDCCH DMRS antenna ports. Similarly, downlink data can be transmitted and received via PDSCH, and spatial parameters related to downlink data transmission and reception may include QCL reference information, TCI status information, etc., for one or more PDSCH DMRS antenna ports.

[0263] However, in this disclosure, the terminology for spatial parameters is not limited to QCL information and may include spatial parameters applied to uplink transmissions (e.g., spatial relationship information (spatial relationship info) related to the uplink transmission beam). For example, uplink control information (UCI) can be transmitted and received via PUCCH and / or PUSCH, and spatial parameters related to UCI transmission and reception may include PRI (PUCCH resource indicator) related to PUCCH / PUSCH transmission and reception, associated spatial relationship information, or QCL reference RS, etc.

[0264] In addition, spatial parameters can be configured individually for downlink or uplink, or they can be integrated and configured for both downlink and uplink.

[0265] Alternatively, spatial parameters can also be defined or configured as a set of spatial parameters including at least one spatial parameter. In the following text, at least one spatial parameter is collectively referred to as a spatial parameter for simplicity.

[0266] In the following description, the terms used for spatial parameters of downlink / uplink transmission and reception may be replaced by various terms such as spatial relation information, beam, transmit beam, receive beam, TCI status, QCL RS, QCL reference RS, etc., and in some examples, these terms may be used instead of default spatial parameters for description.

[0267] Additionally, spatial parameters configured as default among spatial parameters can be referred to as default spatial parameters. When a specific spatial parameter is configured as default, it may include pre-configured / defined conditions to be applied to situations that meet predetermined conditions (e.g., when a separate configuration / indication for the spatial parameter is not available to the terminal, etc.).

[0268] Default spatial parameters can be replaced by terms such as default spatial relationship information, default beam, default transmit beam, default receive beam, default TCI status, etc., and in some examples, these terms can be used instead of default spatial parameters for description.

[0269] Additionally, in this disclosure, reference signals (RSs) are used as a term encompassing physical layer signals / channels such as synchronization signals and / or SS / PBCH blocks, as well as various types of RSs defined in the standard. Furthermore, beams may correspond to RS configurations / resources.

[0270] Figure 8 This is a diagram illustrating downlink reception operation based on a terminal's default beam, according to embodiments of this disclosure.

[0271] In S810, the terminal can receive configuration information for spatial parameters from the base station.

[0272] Configuration information for spatial parameters may include at least one of spatial parameters configured for a predetermined code point or spatial parameters configured for a control resource set.

[0273] For example, a spatial parameter can be a TCI state. However, the scope of this disclosure is not limited to TCI states, but includes various other examples of spatial parameters as described above.

[0274] Additionally, the predetermined code point can be a TCI code point. However, the scope of this disclosure is not limited to TCI code points, but includes code points of various formats mapped to at least one spatial parameter. At least one TCI code point can be pre-configured for the terminal. A TCI code point can be mapped to one TCI state, or it can be mapped to multiple TCI states. Furthermore, at least one TCI code point can include at least one code point mapped to one TCI state and can include at least 0 code points mapped to multiple TCI states. When the DCI includes a Transmission Configuration Indicator (TCI) field, a specific (at least one) code point can be indicated by that field, thus allowing the terminal to determine one or more TCI states mapped to the specific (at least one) code point.

[0275] Additionally, at least one TCI state can be pre-configured for a control resource set (CORESET). At least one CORESET can be configured for a terminal, and at least one TCI state can be configured for each CORESET.

[0276] In S820, the terminal can receive the first PDCCH in the first CORESET within the first time unit.

[0277] For example, a time unit can be a time slot. However, the scope of this disclosure is not limited to time slots, and can include various time-domain units, including symbols, symbol groups, time slot groups, sub-time slots, subframes, subframe groups, frames, etc.

[0278] Processing the first PDCCH received by the terminal and checking the spatial parameter information (e.g., TCI field) included in the DCI takes time. In other words, it is assumed that the terminal may not know the spatial parameters indicated by the DCI for a predetermined duration (e.g., the higher-layer parameter timeDurationForQCL). Therefore, the terminal may receive / buffer downlink transmissions based on default spatial parameters instead of those indicated by the DCI for the predetermined duration (e.g., timeDurationForQCL). Thus, the duration for which default spatial parameters or default beaming are applied can be referred to as the default spatial parameter duration or default beaming duration.

[0279] In S830, the terminal can perform downlink reception based on the first default space parameters during the first duration.

[0280] The first duration begins in the first time unit and may end after a pre-configured / predefined predetermined time length (e.g., timeDurationForQCL). For example, when the time offset between the first time unit (the reception time of PDCCH / DCI in S820) and the second time unit (the reception time of downlink transmission in S830) is equal to or less than a threshold within the predetermined time length (e.g., timeDurationForQCL), downlink reception may be performed based on the first default spatial parameters.

[0281] When at least one code point pre-configured for a terminal includes a specific code point configured with multiple spatial parameters, a first default spatial parameter can be determined based on the multiple spatial parameters configured for the specific code point.

[0282] When at least one code point pre-configured for the terminal does not include a code point configured with multiple spatial parameters, the first default spatial parameter can be determined based on the spatial parameters configured for the first CORESET.

[0283] In S840, during the second duration, the terminal can perform downlink reception based on the second default spatial parameters.

[0284] The second duration begins in the second time unit and can end in the time unit where the first duration ends. The second time unit can have a later time domain location than the first time unit. Additionally, at least one second CORESET can be configured in the second time unit.

[0285] When at least one second CORESET includes a specific CORESET with multiple space parameters configured, the second default space parameter can be determined based on the multiple space parameters configured for the specific CORESET.

[0286] When at least one second CORESET does not include a CORESET with multiple spatial parameters configured, the second default spatial parameter can be determined based on the multiple spatial parameters configured in the predetermined code point.

[0287] Summarizing S830 and S840 above, the default spatial parameters for downlink transmission and reception can be determined or updated within a predetermined duration (e.g., the duration during which the offset between the first time unit and the time unit in which the terminal receives downlink transmission from the base station is equal to or less than a predetermined threshold (e.g., timeDurationForQCL)). In other words, the default spatial parameters determined in S830 can be updated as in S840. For example, the default spatial parameters can be determined or updated based on whether a CORESET configuring multiple spatial parameters is included in at least one CORESET associated with the search space monitored by the terminal in the "latest time unit" and whether a code point configuring multiple spatial parameters is included in a predetermined code point.

[0288] Figure 9 This is a diagram illustrating downlink transmission operation based on a base station's default beam, according to embodiments of this disclosure.

[0289] In the S910, the base station can send configuration information for spatial parameters to the terminal.

[0290] Configuration information for spatial parameters may include at least one of spatial parameters configured for a predetermined code point or spatial parameters configured for a control resource set. Due to its specific description and... Figure 8 S810 in the text overlaps and is therefore omitted.

[0291] In S920, the base station can send the first PDCCH to the terminal in the first CORESET within the first time unit. Due to its specific description and... Figure 8 S820 overlaps in the text and is therefore omitted.

[0292] In S930, the base station can perform downlink transmission based on a first default spatial parameter within a first duration. Due to its specific description and... Figure 8 S830 overlaps in the text and is therefore omitted.

[0293] In S940, the base station can perform downlink reception based on a second default spatial parameter during a second duration. Due to its specific description and... Figure 8 S840 overlaps in the text and is therefore omitted.

[0294] In the example above, the terminal can receive / buffer downlink transmissions based on default spatial parameters for a predetermined duration, and the default spatial parameters can be determined / updated according to the example above. Additionally, the base station can perform downlink transmissions based on the default spatial parameters for the determined duration.

[0295] In the above example, downlink transmissions may include at least one of data scheduled by the DCI of the PDCCH (e.g., PDSCH) or aperiodic (AP) CSI-RS associated with a CSI report triggered by the DCI of the PDCCH. However, this disclosure is not limited to PDSCH / AP CSI-RS and may include various downlink transmissions with applied default spatial parameters for transmission and reception.

[0296] In the various examples described above and below, when the downlink transmission is AP CSI-RS, the example timeDurationForQCL of the higher-layer parameter associated with the length of the first / second duration can be replaced with beamSwitchTiming reported by the terminal when the downlink transmission is PDSCH.

[0297] For example, for each aperiodic CSI-RS resource in the CSI-RS resource set associated with each CSI trigger state, the UE can receive an indication of QCL configuration for one or more QCL RS sources and one or more QCL types via qcl-info (a higher-layer signaling that includes a reference list of TCI states for the aperiodic CSI-RS resources associated with the CSI trigger state). When a state included in the list is configured as a reference for an RS associated with QCL-TypeD, the corresponding RS can be an SS / PBCH block located in the same or different CC / DL BWPs, or it can be a periodically or semi-persistently configured CSI-RS resource located in the same or different CC / DL BWPs.

[0298] Here, when the reported value of a predetermined threshold related to the beam switching time (e.g., beamSwitchTiming) reported by the UE is one of {14, 28, 48}, and the scheduling offset between the last symbol of the PDCCH carrying the DCI trigger and the first symbol of the aperiodic CSI-RS resource of the NZP-CSI-RS-ResourceSet configured without the higher-level parameter trs-info is less than the threshold, or when the reported value is one of {224, 336} and the scheduling offset is less than 48, the following operation can be performed.

[0299] If an additional DL signal exists with a TCI state indicated in the same symbol as CSI-RS, the UE can apply the QCL assumptions of the other DL signal even when an aperiodic CSI-RS is received. The other DL signal can correspond to a PDSCH scheduled with an offset equal to or greater than the timeDurationForQCL threshold, an aperiodic CSI-RS scheduled with an offset equal to or greater than the value of the beamSwitchTiming threshold reported by the UE when it is one of {14, 28, 48}, an aperiodic CSI-RS scheduled with an offset equal to or greater than the value of the beamSwitchTiming threshold reported by the UE when it is one of {224, 336}, a periodic CSI-RS, or a semi-persistent CSI-RS.

[0300] If no other DL signal has a TCI state indicated in the same symbol as CSI-RS, when an aperiodic CSI-RS is received, the UE may apply the QCL assumption for the CORESET associated with the search space of the monitoring that has the lowest controlResourceSetId in the latest time slot of at least one CORESET monitored in the active BWP of the serving cell.

[0301] When the reported value of a predetermined threshold associated with the beam switching time (e.g., beamSwitchTiming) reported by the UE is one of {14, 28, 48}, and the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI and the first symbol of the aperiodic CSI-RS resource is equal to or greater than the threshold, or when the reported value is one of {224, 336}, and the scheduling offset is equal to or greater than 48, the UE may expect to apply the QCL assumption of the indicated TCI state to the aperiodic CSI-RS resource of the CSI triggering state indicated by the CSI triggering field of the DCI.

[0302] In other words, for a predetermined duration (e.g., timeDurationForQCL or beamSwitchTiming) from the PDCCH / DCI reception time, the terminal can receive / buffer downlink transmissions based on default spatial parameters, and can... Figure 8 The examples above and the specific examples described below clearly demonstrate how default spatial parameters are determined / updated. The base station can also perform downlink transmissions based on the default spatial parameters expected by the terminal.

[0303] The following describes specific examples of this disclosure regarding downlink transmission and reception operations based on default space parameters.

[0304] Figure 10This is a diagram illustrating downlink transmission and reception operations based on various examples of this disclosure, according to the default space parameters.

[0305] refer to Figure 10 (a) describes the determination of default space parameters for the case where PDCCH is sent from a single TRP (i.e., STRP) and PDSCH from the STRP is scheduled via the corresponding PDCCH.

[0306] After receiving the PDCCH in the terminal, PDCCH decoding requires a specific time period. Therefore, within this specific time period, the PDCCH can be received based on a default beam and stored in a buffer. This default beam can be determined as the beam configured for the CORESET with the lowest ID in the latest time slot configured for the CORESET. Alternatively, the specific time period can be determined using the RRC parameter called timeDurationForQCL.

[0307] exist Figure 10 In (a), an example of scheduling PDSCH via PDCCH / DCI is shown in 5 time slots (time slots 0 to 4). When one TRP sends PDCCH and another TRP sends PDSCH, the terminal can be configured with a TCI state for receiving PDCCH and a TCI state for receiving PDSCH.

[0308] The TCI state used for receiving PDSCH can be configured in two ways. The first method determines the TCI state for receiving PDSCH based on the TCI state of the CORESET configured for the PDCCH / DCI that schedules the PDSCH. The second method determines the TCI state for receiving PDSCH based on the TCI state indicated by the TCI field in the DCI that schedules the PDSCH.

[0309] For the second method, among at least one TCI code point configured by a higher layer, a specific (at least one) code point can be indicated by the TCI field in the DCI. At least one TCI code point with multiple TCI states configured can be included among at least one TCI code point that can be indicated by the TCI field, and one TCI state can be configured for each of the remaining (one or more) TCI code points. In this case, it is unclear to the terminal whether one or more TCI states configured for PDSCH reception (i.e., indicated by the TCI field in the DCI) exist when DCI decoding is not completed for the default spatial parameter duration. Therefore, the terminal can assume STRP PDSCH only when one TCI state is configured for each of all (configured by a higher layer) TCI code points. Otherwise (i.e., when including even one TCI code point with multiple TCI states configured among the (configured by a higher layer) TCI code points), the terminal can assume MTRP PDSCH (e.g., PDSCH NCJT transmission). Alternatively, for the second method, the base station can be configured with a third factor that can indicate to the terminal whether it is STRP PDSCH or MTRP PDSCH.

[0310] exist Figure 10 The shaded slots in the example can include the duration of the default spatial parameter. For example, when the value of the timeDurationForQCL parameter is configured to 28 OFDM symbols and the PDCCH is transmitted in slot 0, the terminal can receive downlink signals based on the default spatial parameter up to some symbols in slot 2, which is 28 symbols from the start of PDCCH reception.

[0311] exist Figure 10 In (a), if the latest time slot for configuring a CORESET is time slot 0 and only one CORESET is configured at this time, the spatial parameters configured for the corresponding CORESET (e.g., one or more TCI states) can be ultimately determined as the default spatial parameters. PDSCH can be transmitted in time slot 4, and the terminal can complete DCI decoding in time slot 4; therefore, the spatial parameters for downlink reception can be determined and applied based on one or more TCI states indicated by the TCI field of the DCI.

[0312] Example 1

[0313] This embodiment is an example of determining at least one default space parameter from among a plurality of default space parameter candidates configured for CORESET for a predetermined duration (e.g., the duration of the default space parameter) to be applied to downlink transmission and reception.

[0314] refer to Figure 10(b) describes the determination of default space parameters for the case where PDCCHs are sent from multiple TRPs (i.e., MTRPs) and PDSCHs from a single TRP (i.e., STRP) are scheduled by the corresponding PDCCHs.

[0315] and Figure 10 The examples of STRP PDCCH and STRP PDSCH in (a) differ, and ambiguity may occur in the determination of default spatial parameters when sending PDCCH via MTRP. For example, for MTRP PDCCH transmission, two TCI states can be configured for a CORESET. In this case, the spatial parameters configured for the CORESET with the lowest ID in the latest slot can be two: one corresponding to the first TCI state and the other corresponding to the second TCI state.

[0316] Figure 10 (b) illustrates the case of MTRP PDCCH transmission configured with two TCI states for the CORESET corresponding to the PDCCH. A TCI state can be configured / indicated for the terminal's PDSCH reception, thus enabling STRP PDSCH transmission and reception. Regarding the duration of the shadow default spatial parameter, the terminal may encounter ambiguity about which of the two spatial parameters configured for the CORESET should be used for receiving and buffering downlink signals.

[0317] To address this issue, the base station and the terminal can make a pre-commitment to determine a predetermined TCI state as the default spatial parameter among multiple TCI states configured for the CORESET with the lowest ID for the latest time slot. For example, a predetermined TCI state could be the first, second, or last TCI state among multiple TCI states. Alternatively, a predetermined TCI state can be configured / indicated by the base station to the terminal via RRC signaling.

[0318] The maximum number of spatial parameters (or receive beams) that a terminal can apply when receiving downlink transmissions can be reported to the base station in advance as UE capability information. For example, some terminals may have the capability to receive downlink signals by applying at most one spatial parameter (e.g., by one receive beam), while other terminals may have the capability to receive downlink signals by applying up to multiple spatial parameters (e.g., by two receive beams). In this disclosure, the former is referred to as a 1Rx beam UE or a 1Rx default beam UE, and the latter is referred to as a 2Rx beam UE or a 2Rx default beam UE.

[0319] During the duration of the default spatial parameter, an example of determining one of the multiple spatial parameters configured for CORESET as the default spatial parameter can be applied to a 1Rx beam UE.

[0320] For 2Rx-beamed UEs, even when two TCI states are configured for a CORESET, downlink signals can be received using the two spatial parameters / beams corresponding to the two TCI states without determining one of them as the default spatial parameter. Therefore, a 2Rx-beamed UE can receive downlink signals based on two default spatial parameters by using all two TCI states configured for the CORESET with the lowest ID in the latest time slot.

[0321] exist Figure 10 In (b), the case of MTRP PDCCH scheduling STRP PDSCH is used as an example, but it is not limited to this, and the above example can also be applied to the case of MTRP PDCCH scheduling MTRP PDSCH.

[0322] Example 2

[0323] This embodiment is an example of determining at least one default space parameter among a plurality of default space parameter candidates configured for a predetermined code point or a plurality of default space parameter candidates configured for CORESET for application to downlink transmission and reception within a predetermined duration (e.g., the duration of a default space parameter).

[0324] refer to Figure 10 (c) describes the determination of default space parameters for the case where a PDCCH is sent from a single TRP (i.e., STRP) and PDSCHs from multiple TRPs (i.e., MTRPs) are scheduled via the corresponding PDCCHs. For example, a PDSCH scheduled via a DCI can be sent from multiple TRPs via the NCJT method. To this end, code points configuring multiple TCI states can be included in at least one TCI code point configured for the terminal, and the specific code point configured for the multiple TCI states for PDSCH reception can be indicated by the TCI field in the DCI.

[0325] exist Figure 10 In (c), an example of scheduling PDSCH via PDCCH / DCI is shown in 5 time slots (time slots 0 to 4). When one TRP sends PDCCH and multiple TRPs send PDSCH, the terminal can be configured with one TCI state for receiving PDCCH and multiple TCI states for receiving PDSCH.

[0326] The TCI state used to receive PDSCH can be determined based on the TCI state configured for the CORESET corresponding to the PDCCH / DCI that schedules the PDSCH, or it can be determined based on the TCI state indicated by the TCI field in the DCI that schedules the PDSCH. For the latter, during the default spatial parameter duration, the terminal can assume STRP PDSCH only when one TCI state is configured for each of all TCI code points (configured by higher layers), and when the TCI code points (configured by higher layers) include even one TCI code point with multiple configured TCI states, the terminal can assume MTRP PDSCH (e.g., PDSCH NCJT transmission). Alternatively, the base station can configure a third factor that can indicate to the terminal whether it is STRP PDSCH or MTRP PDSCH.

[0327] exist Figure 10 In (c), the 1Rx beam UE can determine the default spatial parameters based on a TCI state configured for the latest slot of the configured CORESET with the lowest ID during the duration of the default spatial parameters.

[0328] exist Figure 10 In (c), the 2Rx beam UE can determine the default spatial parameters based on multiple TCI states configured for one of one or more code points (e.g., the code point with the lowest ID / index) among multiple TCI states configured in the pre-configured TCI code points during the duration of the default spatial parameters.

[0329] In this scenario, during the default space parameter duration, when other additional CORESETs are configured / exist, the following limitations may apply: at least one of the multiple TCI states configured for a specific codepoint (e.g., the codepoint with the lowest ID / index) should be configured for the additional CORESET. Additionally, when multiple TCI states are configured for an additional CORESET, the following limitation may apply: these multiple TCI states should be configured identically to the multiple TCI states configured for a specific codepoint (e.g., the codepoint with the lowest ID / index).

[0330] The following describes an example of this disclosure for removing such restrictions and applying default space parameters more flexibly.

[0331] Figure 10(d) illustrates the case where there are CORESETs (hereinafter, CORESET M) configured with multiple spatial parameters (e.g., 2 TCI states) within the shaded area (e.g., the default spatial parameter duration). When at least one CORESET M exists within the default spatial parameter duration, the default spatial parameter can be determined (or updated) based on the TCI state of the CORESET M with the lowest ID in the latest time slot among them.

[0332] Figure 10 Example of (d) Figure 10 The example in (c) is the same, except that the CORESETM is additionally configured to have two TCI states in slot 1. In other words, as referenced... Figure 10 As described in (c), after receiving the PDCCH in slot 0, multiple default spatial parameters can be determined based on the TCI code points. Subsequently, when a CORESET M configured with two TCI states appears in slot 1, the default spatial parameters can be determined / updated based on the two TCI states configured for the corresponding CORESET M, starting from the time when the corresponding CORESET M was configured.

[0333] Therefore, one or more TCI states configured for the additional CORESET configuration and one or more TCI states configured for the TCI code points can be configured differently during the duration of the default spatial parameters. The terminal can update the default spatial parameters based on one or more TCI states configured for the additional CORESET.

[0334] As an additional example, if the terminal is configured with the higher-level parameter enableTwoDefaultTCI-States (i.e., when configured to perform downlink reception via the 2Rx default beam for the terminal (which is different from the UE capability report)), then when there is an SFN CORESET (i.e., a CORESET with two TCI states configured) among the CORESETs present in the latest time slot, the terminal can determine the default spatial parameters for PDSCH reception / buffering based on the two TCI states configured for the corresponding SFN CORESET.

[0335] As an additional example, when the CORESET with the lowest ID in the latest time slot (among one or more time slots of the CORESET) is an SFN CORESET (i.e., a CORESET configured with two TCI states), the terminal can determine the default space parameters for PDSCH reception / buffering based on the two TCI states configured for the corresponding SFN CORESET.

[0336] According to Example 2, the default space parameters can be determined differently depending on whether an SFNCORESET exists in one or more CORESETs in the latest time slot, or depending on whether the CORESET with the lowest ID in the latest time slot is an SFN CORESET.

[0337] Example 3

[0338] This embodiment is an additional example of determining, within a predetermined duration (e.g., the duration of the default space parameter), at least one default space parameter among a plurality of default space parameter candidates configured for a predetermined code point or a plurality of default space parameter candidates configured for CORESET, for application to downlink transmission and reception.

[0339] According to embodiments 1 and 2 above, when multiple TCI states are configured for the CORESET with the lowest ID in the latest time slot during the duration of the default spatial parameters, the 2Rx beam UE can determine the default spatial parameters based on multiple corresponding TCI states.

[0340] refer to Figure 10 (e) describes the determination of default space parameters for the case where PDCCH is sent from multiple TRPs (i.e., MTRPs) and PDSCH from multiple TRPs (i.e., MTRPs) is scheduled via the corresponding PDCCH.

[0341] exist Figure 10 In (e), an example of scheduling PDSCH via PDCCH / DCI is shown in 5 time slots (time slots 0 to 4). When multiple TRPs send PDCCH and multiple TRPs send PDSCH, the terminal can be configured with multiple TCI states for receiving PDCCH and multiple TCI states for receiving PDSCH.

[0342] exist Figure 10 In (e), the 2Rx beam UE can determine the default spatial parameters based on multiple TCI states configured for the latest slot of the configured CORESET with the lowest ID during the duration of the default spatial parameters.

[0343] In this scenario, during the duration of the default space parameters, when other additional CORESETs are configured / exist, the terminal may encounter ambiguity regarding whether the default space parameters will be determined / updated based on the additional CORESETs. If the additional CORESET is CORESET M (i.e., a CORESET configured with multiple TCI states), the default space parameters can be updated based on the multiple TCI states configured for the additional CORESET M. If the additional CORESET is CORESET S (i.e., a CORESET configured with one TCI state), it may become unclear whether the default space parameters determined based on multiple TCI states will be updated based on one TCI state of the additional CORESET S, or if so, what will be updated.

[0344] The following describes an example of how this disclosure resolves such ambiguity.

[0345] Figure 10 (f) illustrates the case where there is a CORESET (i.e., CORESET S) configured with a single spatial parameter (e.g., 1 TCI state) within the shaded area (e.g., the duration of the default spatial parameter).

[0346] Example 3-1

[0347] exist Figure 10 In the example of (f), CORESET S can be defined as the default space parameter that is not used to update the duration of the default space parameter.

[0348] If at least one CORESET M exists during the default space parameter duration, the default space parameter can be updated based on the space parameter of the CORESET with the lowest ID among at least one CORESET M in the latest time slot where the corresponding CORESET exists.

[0349] Example 3-2

[0350] exist Figure 10 In the example of (f), when CORESET S is or may be a CORESET for MTRP PDSCH scheduling (e.g., when at least one code point configured with multiple TCI states is included in at least one pre-configured TCI code point), the terminal can... Figure 10 (f) The default space parameter is updated based on the multiple TCI states configured for the code point with the lowest ID / index among the code points configured with multiple TCI states, starting from the time after receiving from CORESET S during the duration of the default space parameter.

[0351] In Example 3-1, since the CORESET S with one TCI state is ignored for determining / updating and defining the default space parameters, the space parameters configured for CORESET S can be limited to one of the multiple default space parameters configured for the CORESET associated with the MTRP PDCCH of slot 0. To improve scheduling flexibility by removing such a restriction and applying the TCI state configuration for CORESETs more flexibly, the default space parameters can be determined / updated based on TCI code points, as in Example 3-2.

[0352] exist Figure 10 In the example of (f), when CORESET S is a CORESET used for STRP PDSCH scheduling (e.g., when a code point with multiple TCI states configured is not included in at least one pre-configured TCI code point), CORESET S can be defined as not being used to update the default space parameter during the default space parameter duration.

[0353] As another example, if the terminal is configured with the higher-level parameter enableTwoDefaultTCI-States (i.e., when it is configured to perform downlink reception via the two Rx default beams for the terminal (which are different from the UE capability report)), then when there is no SFN CORESET among the CORESETs existing in the latest time slot (i.e., a CORESET with two TCI states configured), the terminal can determine the default spatial parameters for PDSCH reception / buffering based on the two TCI states configured for the lowest TCI code point among the code points(one or more) with two TCI states configured.

[0354] As an additional example, if the terminal is configured with the higher-level parameter enableTwoDefaultTCI-States (i.e., when configured to perform downlink reception via the two Rx default beams for the terminal (as opposed to UE capability reports)), then when the CORESET with the lowest ID in the latest time slot is not the SFN CORESET (i.e., the CORESET with two TCI states configured), the terminal can determine the default spatial parameters for PDSCH reception / buffering based on the two TCI states configured for the lowest TCI code point among the two TCI code points configured with two TCI states.

[0355] According to Example 3-2, the default space parameters can be determined differently depending on whether there is an SFN CORESET in the latest time slot CORESET, or depending on whether the CORESET with the lowest ID in the latest time slot is an SFN CORESET.

[0356] Example 3-3

[0357] exist Figure 10 In the example of (f), when CORESET S is a CORESET used for STRP PDSCH scheduling (e.g., when a code point with multiple TCI states configured is not included in at least one pre-configured TCI code point), a portion of the default space parameters can be updated based on one TCI state configured for CORESET S.

[0358] exist Figure 10 In example (f), two default space parameters can be determined based on the two TCI states configured for the MTRP PDCCH reception of slot 0, and after CORESET S occurs, one of the two default space parameters can be updated based on one TCI state configured for CORESET S.

[0359] For example, before CORESET S with TCI state 2 appears in slot 1, the default space parameters are determined to be TCI states 0 and 1, and if CORESET S appears, the first default space parameter can be maintained as TCI state 0 (i.e., corresponding to the first TCI state of the two TCI states), and the second default space parameter can be updated from TCI state 1 of CORESET S (corresponding to the second TCI state of the two TCI states) to TCI state 2.

[0360] In Example 3-2, the default space parameters are maintained by determining / updating the TCI state configured for CORESET S and determining the default space parameters. Therefore, the space parameters configured for CORESET S can be limited to one of several space parameters configured for the CORESET associated with the MTRP PDCCH. To improve scheduling flexibility by removing such restrictions and applying the TCI state configuration for CORESETs more flexibly, a portion of the default space parameters can be updated based on the space parameters configured for CORESET S as in Example 3-3.

[0361] exist Figure 10 (e) and Figure 10 In (f), the case of MTRP PDSCH being scheduled by MTRP PDCCH is used as an example, but it is not limited to this, and the above example can also be applied to the case of STRP PDSCH being scheduled by MTRP PDCCH.

[0362] Example 4

[0363] In the above example, the method for determining the default spatial parameters can be applied differently depending on the number of spatial parameters configured for the CORESET associated with the PDCCH and / or whether the PDSCH scheduled by the corresponding PDCCH is an MTRP PDSCH or a STRP PDSCH (or whether code points with multiple TCI states are included in the TCI code points).

[0364] Such operations may increase the implementation complexity of the base station and the terminal. Therefore, the base station can directly indicate the default spatial parameters to the terminal to avoid increasing the implementation complexity.

[0365] For example, the base station can configure / indicate to the terminal a TCI state (or QCL reference RS) for determining the default spatial parameters, and the terminal can use the configured / indicated TCI state (or QCL reference RS) to determine / update the default spatial parameters regardless of the number of TCI states configured for CORESET and / or whether it is any of MTRP / STRP PDSCH.

[0366] Such default space parameter configuration / indication can be provided to the terminal via (new) RRC signaling, or via MAC-CE signaling and RRC signaling, for more dynamic (or faster) default space parameter changes / updates. For example, at least one default space parameter candidate can be configured / indicated to the terminal via RRC signaling, and one of the candidates can be configured / indicated to the terminal via MAC-CE signaling.

[0367] Therefore, when the default space parameter is explicitly / directly indicated to the terminal, the terminal no longer follows the method of determining / updating the default space parameter based on one or more TCI states configured for the TCI code point or based on one or more TCI states configured for the CORESET with the lowest ID in the latest time slot, but can determine / update the default space parameter based on the explicitly / directly indicated value. If the default space parameter is not explicitly / directly indicated, the default space parameter can be determined according to embodiments 1 to 3 described above.

[0368] In the examples of embodiments 1 to 4 above, NCJT based on a single DCI and NCJT based on multiple DCIs can be applied as MTRP PDSCH transmission methods. In other words, while the examples above exemplarily describe NCJT based on a single DCI, they are not limited thereto, and the examples above can also be applied to NCJT based on multiple DCIs (e.g., when multiple CORESET pool indices are configured) (each CORESET pool index can correspond to one TRP). For example, in NCJT based on multiple DCIs, two Rx (default) beam UEs can determine / update default spatial parameters based on the spatial parameters configured for the CORESET with the lowest ID in the latest time slot of each CORESET pool. In this case, when multiple spatial parameters are configured for the CORESET with the lowest ID in the latest time slot of each CORESET pool, one of the spatial parameters (e.g., the first TCI state) can be determined as the default spatial parameter according to the examples above.

[0369] As an additional example, it can be assumed that multiple spatial parameters are configured for the CORESET with the lowest ID in the latest time slot, and the corresponding CORESET belongs to both CORESET pool indices 0 and 1. In this case, the first spatial parameter among the multiple spatial parameters can be determined as the default spatial parameter for CORESET pool index 0, and a second spatial parameter can be pre-committed / defined to be determined as the default spatial parameter for CORESET pool index 0. Configuring multiple spatial parameters for a CORESET can correspond to the situation where multiple TRPs cooperatively send the PDCCH of the corresponding CORESET, so the corresponding CORESET can belong not only to CORESET pool index 0 (the CORESET pool used by TRP 0) but also to CORESET pool index 1 (the CORESET pool used by TRP 1).

[0370] For example, when the pool index of the CORESET that sends the PDSCH to the PDCCH is considered to be i (i = 0 or 1), a default space parameter for PDSCH reception / buffering can be determined for the CORESET belonging to pool index i. If CORESET A, configured with two TCI states, belongs to both CORESET pool indices 0 and 1, the default space parameter can be determined based on the TCI states configured for CORESET A. Here, the default space parameter can be determined based on pool index i, based on some of the TCI states configured for CORESET A. In other words, for i = 0, the default space parameter can be determined by using the first TCI state out of the two TCI states, and for i = 1, the default space parameter can be determined by using the second TCI state out of the two TCI states. If the CORESET that can send scheduled PDSCH is configured not only in pool index 0 but also in pool index 1, then a first default space parameter can be configured from the CORESET belonging to pool index 0 for PDSCH reception (e.g., based on the space parameter configured for the CORESET with the lowest ID in the latest time slot belonging to pool index 0), and a second default space parameter can be configured from the CORESET belonging to pool 1 to use both default space parameters (e.g., based on the space parameter configured for the CORESET with the lowest ID in the latest time slot belonging to pool index 0).

[0371] The above examples primarily describe the default spatial parameters associated with PDSCH scheduled by PDCCH, but are not limited to this, and the examples can also be applied to the default spatial parameters associated with aperiodic (AP) CSI-RS triggered by PDCCH. For example, after PDCCH reception, the terminal can receive downlink signals based on the default spatial parameters for the beamSwitchTiming duration pre-reported by the terminal.

[0372] If no downlink signal exists during this duration, the terminal can determine the default spatial parameters for AP CSI-RS reception / buffering based on the spatial parameters configured for the CORESET with the lowest ID in the latest time slot. In this case, when multiple TCI states are configured for the corresponding CORESET, the terminal can determine one of the multiple TCI states as the default spatial parameter, or it can determine all of the multiple TCI states as the default spatial parameters based on its capabilities (e.g., 1RX beam UE or 2RX beam UE).

[0373] When a downlink signal is present within that duration, the terminal can determine the default spatial parameters for AP CSI-RS reception / buffering based on the spatial parameters of the received downlink signal. In this case, when a corresponding downlink signal is received through multiple spatial parameters, the terminal can determine one of the multiple spatial parameters as the default spatial parameter, or it can determine all of the multiple spatial parameters as the default spatial parameters according to its capabilities (e.g., 1RX beam UE or 2RX beam UE).

[0374] Regarding duration, when a TCI code point with multiple spatial parameters is included among at least one TCI code point pre-configured for the terminal, the default spatial parameters for AP CSI-RS reception / buffering can be determined based on the multiple spatial parameters configured for the corresponding TCI code point.

[0375] For this duration, when the TCI code point pre-configured for the terminal does not include a TCI code point configured with multiple spatial parameters, the default spatial parameters for AP CSI-RS reception / buffering can be determined based on the multiple spatial parameters configured for the CORESET associated with the PDCCH that triggers AP CSI-RS.

[0376] When an additional CORESET occurs during this duration, and multiple spatial parameters are configured for the additional CORESET, the default spatial parameters for AP CSI-RS reception / buffering can be determined / updated based on the multiple spatial parameters configured for the additional CORESET.

[0377] When an additional CORESET occurs during this duration, and the CORESET with multiple spatial parameters configured is not included in the additional CORESET, the default spatial parameters for AP CSI-RS reception / buffering can be determined based on the multiple spatial parameters configured for the TCI code point.

[0378] During this duration, the terminal can receive AP CSI-RS based on the spatial parameters (e.g., TCI state or QCL type D RS) of the CORESET with the lowest ID in the latest time slot of the CORESET pool to which the DCI that triggered the AP CSI-RS belongs. In this case, if the CORESET belongs to both CORESET pools 0 and 1, the first spatial parameter can be used as the default spatial parameter for CORESET pool 0, and the second spatial parameter can be committed / defined as the default spatial parameter for CORESET pool 1.

[0379] In the above example, the case of two spatial parameters is used as an example of multiple spatial parameters for receiving PDCCH / PDSCH, but the scope of this disclosure is not limited thereto, and it may also include the case of at least three spatial parameters.

[0380] In the example above, the scenario of configuring multiple TCI states for a single CORESET can be replaced by a scenario where multiple CORESETs configured with one TCI state are configured to repeatedly / partially transmit the same DCI. For example, CORESET 1 and CORESET 2, both configured with one TCI state, can be configured for a terminal, and the corresponding CORESETs 1 and 2 can be multiplexed (e.g., FDM) in slot 0 and used to repeatedly / partially transmit the same DCI. In this case, the terminal can determine two default spatial parameters based on the spatial parameters configured for CORESET 1 (e.g., TCI state or beam) and the spatial parameters configured for CORESET 2 (e.g., TCI state or beam) for the duration of the default spatial parameters.

[0381] Figure 11 This is a diagram illustrating an example of signaling between the network side and the terminal to which embodiments of this disclosure may be applied.

[0382] Figure 11 This refers to signaling between the network side (e.g., TRP 1, TRP 2) and the terminal (UE) in cases where multiple TRPs (or multiple cells, where all TRPs can be replaced by cells in the following text) can be used, as exemplified by the examples or combinations thereof disclosed herein. Here, the UE / network side is merely an example and can be represented by, for example... Figure 12 The various equipment replacements shown are applied. Figure 11 This is merely for ease of description and does not limit the scope of this disclosure. Additionally, omissions may be made depending on the circumstances and / or configuration, etc. Figure 11 Some of the steps shown.

[0383] refer to Figure 11For ease of description, signaling between two TRPs and the UE is considered; however, it is self-evident 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 comprising multiple TRPs, or it can be a cell comprising multiple TRPs. In the example, ideal / non-ideal backhaul can be configured between TRP 1 and TRP 2 on the network side. Furthermore, the following description is based on multiple TRPs, but it can be equivalently extended and applied to transmissions across multiple planes. Additionally, in this disclosure, the operation of a terminal receiving signals from TRP1 / TRP2 can be interpreted / described (or may be an operation) as the terminal receiving signals from the network side (through / using TRP 1 / 2), and the operation of a terminal sending signals to TRP1 / TRP2 can be interpreted / described (or may be an operation) as the terminal sending signals to the network side (through / using TRP1 / TRP2), or it can be interpreted / described in reverse.

[0384] Additionally, as mentioned above, "TRP" can be applied by replacing it with expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pec cell, etc.), TP (transmitter point), base station (gNB, etc.). As mentioned above, TRPs can be classified based on information about CORESET groups (or CORESET pools) (e.g., index, ID). In the example, when a terminal is configured to perform transmission and reception using multiple TRPs (or cells), this might refer to configuring multiple CORESET groups (or CORESET pools) for a terminal. Such configurations regarding CORESET groups (or CORESET pools) can be performed via higher-level signaling (e.g., RRC signaling, etc.). Furthermore, a base station can generally refer to the object that performs data transmission and reception with the terminal. For example, a base station can be a concept including at least one TP (transmitter point), at least one TRP (transmitter and receiver point), etc. Additionally, TP and / or TRP can also include the base station's panel, transmission and reception units, etc.

[0385] Specifically, Figure 11 This indicates the signaling used in the case of an M-TRP (or M cell in the following text, where all TRPs can be replaced by cells, or even when multiple CORESETs are configured from a TRP, it can be assumed to be an M-TRP) when the terminal receives a single DCI (i.e., when a TRP sends a DCI to the UE). Figure 11 Suppose that TRP 1 is the representative TRP for sending DCI.

[0386] exist Figure 11Although not shown, the UE can send capability information to the network side via / using TRP 1 (and / or TRP 2). For example, the capability information may include information indicating whether the UE supports operations according to the examples of this disclosure.

[0387] The UE can receive configuration information regarding transmission and reception based on multiple TRPs from the network side via / using TRP 1 (and / or TRP 2) (S205). The configuration information may include information related to network-side configuration (i.e., TRP configuration), resource information (resource allocation) related to transmission and reception based on multiple TRPs, etc. In this case, the configuration information can be sent via higher-layer signaling (e.g., RRC signaling, MAC-CE, etc.). Alternatively, when the configuration information is predefined or pre-configured, the corresponding steps can be omitted. For example, the configuration information may include configuration related to CORESET / CCE configuration information / information related to the search space / information related to repeated transmissions of the control channel (e.g., PDCCH) (e.g., whether to perform repeated transmissions / the number of repeated transmissions, etc.), as described in the examples of this disclosure.

[0388] For example, the UE in S205 ( Figure 12 100 / 200 in the middle) from the network side ( Figure 12 The above operations of receiving configuration information related to transmission and reception based on multiple TRPs (200 / 100) can be described below. Figure 12 This is achieved using the devices described. For example, refer to... Figure 12 At least one processor 102 can control at least one transceiver 106 and / or at least one memory 104, etc., to receive configuration information related to transmission and reception based on multiple TRPs, and at least one transceiver 106 can receive configuration information related to transmission and reception based on multiple TRPs from the network side.

[0389] The UE can receive DCI and data 1 scheduled by the corresponding DCI from the network side via / using TRP 1 (S210-1). Additionally, the UE can receive data 2 from the network side via / using TRP 2 (S210-2). Here, the DCI can be configured to schedule both data 1 and data 2.

[0390] For example, the DCI may include information about the TCI status (indication) as described in the examples of this disclosure, resource allocation information about DMRS and / or data (i.e., spatial / frequency / temporal resources), and information related to repeated transmissions. For example, information related to repeated transmissions may include whether the DCI is repeatedly transmitted, the number of repetitions, and whether a one-time transmission is performed. For example, the code point of the TCI field in the DCI may be defined differently for cases where the DCI is repeatedly / partially transmitted via multiple TRPs and cases where the DCI is transmitted via a single TRP. In other words, the UE may apply / interpret the TCI status composition / configuration differently for a specific code point depending on whether STRPs / MTRPs are used. Furthermore, the DCI and data (e.g., data 1, data 2) may be transmitted via control channels (e.g., PDCCH, etc.) and data channels (e.g., PDSCH, etc.). Additionally, steps S210-1 and S210-2 may be performed simultaneously, or one may be performed before the other.

[0391] For example, TRP1 and / or TRP2 may repeatedly / partially transmit the same DCI. In one example, the PDCCH candidate for each TRP used to transmit the DCI may correspond to a different TCI state. In other words, the control channel (e.g., PDCCH) through which the DCI is transmitted may be repeatedly transmitted based on TDM / FDM / SDM methods, or the same control channel may be transmitted partially. For example, the DCI format that can be transmitted according to each TRP may be configured equivalently or differently. For example, HARQ-ACK (e.g., ACKNACK) related indicators (e.g., C-DAI, T-DAI, PRI, CCE index) may be determined based on the DCI reception time.

[0392] For example, a terminal may receive / buffer data based on default spatial parameters for a predetermined duration after receiving the DCI. The predetermined duration may correspond to the duration during which the offset between the time the terminal receives the DCI and the time the terminal receives the data is equal to or less than the value of a predetermined parameter (e.g., timeDurationForQCL, beamSwitchTiming, etc.). The default spatial parameters described in the example above may be determined based on at least one of spatial parameters configured for at least one code point (e.g., a TCI code point) pre-configured for the terminal or spatial parameters configured for at least one CORESET including the received DCI.

[0393] For example, in S210-1 / S210-2, UE ( Figure 12 100 / 200 in the middle) from the network side ( Figure 12The above operations of receiving DCI 1 and / or DCI 2 and / or Data 1 and / or Data 2 (200 / 100) can be described below. Figure 12 This is achieved using the devices described. For example, refer to... Figure 12 At least one processor 102 can control at least one transceiver 106 and / or at least one memory 104, etc., to receive DCI 1 and / or DCI 2 and / or data 1 and / or data 2, and at least one transceiver 106 can receive DCI 1 and / or DCI 2 and / or data 1 and / or data 2 from the network side.

[0394] The UE can decode data 1 and data 2 received from the network side via / using TRP 1 (and / or TRP 2) (S215). For example, the UE can perform channel estimation and / or blind detection and / or data decoding based on the examples of this disclosure.

[0395] For example, the UE in step S215 ( Figure 12 The above operations for decoding data 1 and data 2 (100 / 200) can be described below. Figure 12 This is achieved using the devices described. For example, refer to... Figure 12 At least one processor 102 can control at least one memory 104, etc., to perform the operation of decoding data 1 and data 2.

[0396] The UE can send HARQ-ACK information (e.g., ACK information, NACK information, etc.) about DCI and / or Data 1 and / or Data 2 to the network side via / using TRP 1 and / or TRP 2 (S220-1, S220-2). In this case, the HARQ-ACK information about Data 1 and Data 2 can be combined into one. Alternatively, the UE can be configured to send HARQ-ACK information only to a representative TRP (e.g., TRP 1), and can omit the transmission of HARQ-ACK information to other TRPs (e.g., TRP 2).

[0397] For example, based on the examples of this disclosure, HARQ-ACK information (e.g., ACK information, NACK information, etc.) regarding the DCI (or the PDCCH that transmits the DCI) can be sent to the network side via / using TRP 1 and / or TRP 2. For example, based on the examples of this disclosure, parameters (e.g., C-DAI, T-DAI, PRI, CCE index) related to the HARQ-ACK information (e.g., ACK / NACK codebook) can be determined according to the DCI reception time. For example, when multiple DCIs, including repeatedly transmitted DCIs, are received, the reception order of the multiple DCIs can be determined based on the reception time (e.g., MO) of the first DCI among the repeatedly transmitted DCIs. Parameters (e.g., C-DAI, T-DAI, PRI, CCE index) related to the HARQ-ACK information (e.g., ACK / NACK codebook) can be determined based on the determined DCI reception order.

[0398] For example, the UE in S220-1 / S220-2 ( Figure 12 100 / 200) from the network side ( Figure 12 The above operation of sending HARQ-ACK information about data 1 and / or data 2 (100 / 200) can be described below. Figure 12 The device implementation in [the document / reference]. Figure 12 At least one processor 102 can control at least one transceiver 106 and / or at least one memory 104, etc., to send HARQ-ACK information about data 1 and / or data 2, and at least one transceiver 106 can send HARQ-ACK information about data 1 and / or data 2 to the network side.

[0399] Figure 11 The example illustrates the transmission and reception process based on a single DCI in the MTRP scenario, but with... Figure 11 The relevant descriptions can also be applied similarly to TRP 1 and TRP 2 to transmission and reception processes based on multiple DCIs.

[0400] As described above, the aforementioned network-side / UE signaling and operations can be performed by the devices described below (e.g., Figure 12 This can be achieved through devices in the network. For example, the network side (e.g., TRP 1 / TRP 2) may correspond to the first wireless device, and the UE may correspond to the second wireless device, and in some cases, the reverse can be considered.

[0401] For example, the aforementioned network-side / UE signaling and operations can be processed by at least one processor (e.g., 102, 202), and the aforementioned network-side / UE signaling and operations can be used to drive Figure 12At least one processor (e.g., 102, 202) has its commands / programs (e.g., instructions, executable code) stored in memory (e.g., ...). Figure 12 In at least one memory (e.g., 104, 204) in the memory.

[0402] The general-purpose devices disclosed herein can be used.

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

[0404] refer to Figure 12 The first wireless device 100 and the second wireless device 200 can transmit and receive wireless signals through various radio access technologies (e.g., LTE, NR).

[0405] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may additionally include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this disclosure. For example, the processor 102 may transmit a wireless signal including the first information / signal via the transceiver 106 after generating first information / signal by processing information in the memory 104. Furthermore, the processor 102 may receive a wireless signal including a second information / signal via the transceiver 106, and then store information obtained through signal processing of the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information relating to the operation of the processor 102. For example, the memory 104 may store software code including commands for performing all or part of the processes controlled by the processor 102 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this disclosure. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). Transceiver 106 may be connected to processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used with an RF (radio frequency) unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0406] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may additionally include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation 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 via the transceiver 206. Additionally, the processor 202 may receive wireless signals including fourth information / signals via 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 operation flowcharts included in this disclosure. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). Transceiver 206 may be connected to processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used with an RF unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0407] The hardware components of wireless devices 100 and 200 will be described in more detail below. However, they are not limited to this; one or more protocol layers may be implemented by one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102 and 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 operation flowcharts included in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this disclosure. One or more processors 102 and 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 this disclosure to provide them to one or more transceivers 106 and 206. One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206 and obtain PDUs, SDUs, messages, control information, data, or information in accordance with the descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this disclosure.

[0408] One or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. In examples, 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 one or more processors 102, 202. The descriptions, functions, processes, proposals, methods, and / or operation 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. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this disclosure may be included in one or more processors 102, 202 or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this invention may be implemented by firmware or software in the form of code, commands, and / or command sets.

[0409] One or more memories 104, 204 may be connected to one or more processors 102, 202 and are capable of storing data, signals, messages, information, programs, code, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard disk drive, registers, digital memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located internally and / or externally to one or more processors 102, 202. Furthermore, one or more memories 104, 204 may be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0410] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or operation flowcharts of this disclosure to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this disclosure from one or more other devices. For example, one or more transceivers 106, 206 can be connected to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Furthermore, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts included in this disclosure via one or more antennas 108, 208. In this invention, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may process the received wireless signals / channels, etc., by converting them from RF band signals to baseband signals using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the 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, the one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0411] The above embodiments combine the elements and features of this disclosure in a predetermined form. Unless otherwise expressly stated, each element or feature should be considered optional. Each element or feature can be implemented without combination with other elements or features. Furthermore, embodiments of this disclosure may include combinations of certain elements and / or features. The order of operations described in the embodiments of this disclosure may be changed. Some elements or features of one embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. It is clear that embodiments may include combinations of claims where there is no explicit dependency in the claims, or may be included as new claims by amendment after the application.

[0412] It will be apparent to those skilled in the art that this disclosure may be practiced in other specific forms without departing from the essential characteristics of this disclosure. Therefore, the foregoing detailed description should not be construed as restrictive in every respect, but rather as illustrative. The scope of the invention should be determined by a reasonable interpretation of the appended claims, and all variations within the equivalent scope of this disclosure are included within the scope of the invention.

[0413] The scope of this disclosure includes software or machine-executable commands (e.g., operating systems, applications, firmware, programs, etc.) that operate in a device or computer according to methods of various embodiments, and non-transitory computer-readable media that store such software or commands and are executable in the device or computer. Commands that can be used to program a processing system to perform 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 using a computer program product including such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, and may include non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory may optionally include one or more storage devices located remotely from the processor. Alternatively, the non-volatile memory devices in the memory may include non-transitory computer-readable storage media. The features described in this disclosure can be stored in any machine-readable medium to control the hardware of a processing system and can be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using results from embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0414] Here, the wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may include narrowband Internet of Things (IoT) for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the aforementioned names. Alternatively, the wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may perform communication based on LTE-M technology. Here, in 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 of the following standards: 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. Alternatively, the wireless communication technology implemented in the wireless devices 100 and 200 of this disclosure may include at least any one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and it is not limited to the aforementioned names. In the example, ZigBee technology can generate a PAN (Personal Area Network) associated with small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0415] Industrial applicability

[0416] The method proposed in this invention is mainly described using 3GPP LTE / LTE-A and 5G systems as examples, but it can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method for a terminal to receive downlink transmission from a base station in a wireless communication system, the method comprising: The terminal receives from the base station at least one of the following: first configuration information relating to at least one TCI state configured for at least one Transmission Configuration Indicator (TCI) code point, or second configuration information relating to at least one TCI state configured for at least one Control Resource Set (CORESET). The terminal receives downlink control information (DCI) from the base station in the first time unit. as well as The terminal receives the downlink transmission from the base station in the second time unit based on the default TCI state. Specifically, this is based on the absence of a TCI code point configured with multiple TCI states in the activation command via the Media Access Control (MAC) CE control element, and the downlink transmission being a Physical Downlink Shared Channel (PDSCH) transmission, or Based on the fact that no other downlink signal was received using the downlink transmission and that the downlink transmission was an aperiodic Channel State Information-Reference Signal (CSI-RS) transmission: The default TCI state is determined as the first TCI state among a plurality of TCI states indicated for a particular CORESET.

2. The method according to claim 1, wherein: The specific CORESET is the CORESET with the lowest CORESET identifier in the latest time unit.

3. The method according to claim 1, wherein: The offset between the first time unit and the second time unit is less than a predetermined time threshold.

4. The method according to claim 3, wherein: Based on the fact that the downlink transmission is the PDSCH transmission, the predetermined time threshold is the timeDurationForQCL parameter, or Based on the fact that the downlink transmission is the aperiodic CSI-RS transmission, the predetermined time threshold is the beamSwitchTiming parameter.

5. The method according to claim 1, wherein: The terminal is configured to perform or has the capability to perform the reception of the DCI via the Physical Downlink Control Channel (PDCCH) based on multiple TCI states in a single time unit.

6. The method according to claim 1, wherein: The TCI state includes parameters for configuring a quasi-co-address QCL relationship between at least one downlink reference signal RS and at least one demodulation reference signal port or at least one CSI-RS port of the PDSCH.

7. The method according to claim 1, wherein: The time unit is a time slot or symbol defined based on the subcarrier interval.

8. A terminal for receiving downlink transmissions from a base station in a wireless communication system, the terminal comprising: At least one transceiver; as well as At least one processor, said at least one processor being connected to said at least one transceiver, Wherein, the at least one processor is configured to: The at least one transceiver receives from the base station at least one of the following: first configuration information relating to at least one TCI state configured for at least one Transmission Configuration Indicator (TCI) code point, or second configuration information relating to at least one TCI state configured for at least one Control Resource Set (CORESET). Receive downlink control information (DCI) from the base station via the at least one transceiver in a first time unit; and Based on the default TCI state, the downlink transmission is received from the base station in the second time unit via the at least one transceiver. Specifically, this is based on the absence of a TCI code point configured with multiple TCI states in the activation command via the Media Access Control (MAC) CE control element, and the downlink transmission being a Physical Downlink Shared Channel (PDSCH) transmission, or Based on the fact that no other downlink signal was received using the downlink transmission and that the downlink transmission was an aperiodic Channel State Information-Reference Signal (CSI-RS) transmission: The default TCI state is determined as the first TCI state among a plurality of TCI states indicated for a particular CORESET.

9. A base station for performing downlink transmission in a wireless communication system, the base station comprising: At least one transceiver; as well as At least one processor, said at least one processor being connected to said at least one transceiver, Wherein, the at least one processor is configured to: The at least one transceiver sends to the terminal at least one of the following: first configuration information relating to at least one TCI state configured for at least one Transmission Configuration Indicator (TCI) code point or second configuration information relating to at least one TCI state configured for at least one Control Resource Set (CORESET). The at least one transceiver sends downlink control information (DCI) to the terminal in a first time unit; and Based on the default TCI state, the downlink transmission is sent to the terminal via the at least one transceiver in the second time unit. Specifically, this is based on the absence of a TCI code point configured with multiple TCI states in the activation command via the Media Access Control (MAC) CE control element, and the downlink transmission being a Physical Downlink Shared Channel (PDSCH) transmission, or Based on the fact that no other downlink signal was received using the downlink transmission and that the downlink transmission was an aperiodic Channel State Information-Reference Signal (CSI-RS) transmission: The default TCI state is determined as the first TCI state among a plurality of TCI states indicated for a particular CORESET.

Images